my.typo3.org issueshttps://git.typo3.org/services/archive/t3o/my/-/issues2018-07-23T10:26:27Zhttps://git.typo3.org/services/archive/t3o/my/-/issues/84no cron job is running2018-07-23T10:26:27ZStefan Busemannno cron job is runningAs an admin I like to use the scheduler module in the backend
AC:
* Scheduler tasks are runningAs an admin I like to use the scheduler module in the backend
AC:
* Scheduler tasks are runningSprint 5 (2018)https://git.typo3.org/services/archive/t3o/my/-/issues/38Group concept2019-05-22T10:09:25ZStefan BusemannGroup conceptAdd teams memberships (add badges for team membership,
https://drive.google.com/file/d/0B0kcR_NNv6sBZlhteWk2ZHhtd0E/view?usp=sharings)
https://github.com/TYPO3-Teams-Documentation/T3o-Team/edit/master/Documentation/Knowledgebase/LDAP/I...Add teams memberships (add badges for team membership,
https://drive.google.com/file/d/0B0kcR_NNv6sBZlhteWk2ZHhtd0E/view?usp=sharings)
https://github.com/TYPO3-Teams-Documentation/T3o-Team/edit/master/Documentation/Knowledgebase/LDAP/Index.rst
Create a concept for groups for fe_users:
* each team is a fe_group
*Groups*
* Teams
* Server
* t3.org
* Roles
* Member
* Lead
* personal_membership
* Level
* uid
* company_membership
* uid
* Level
* Roles
* editData (see invoices, edit data)
* admin (allowed to add / edit roles)
* Newsletter (liste der newsletter)
* newsletters (multiple values)
* certification
* type (editor, developer) (multiple values)
*Functions*
additional generic groups: "association members", "gold", "platinum", "certified integrators",...
* sync with ldap
* Add functions for
* group administration (invite users, confirm invitation by user // request membership, confirm membership by admin)
* group roles
* enter group, leave group
* add role, remove role
Result: https://docs.google.com/document/d/1J2iNP1VtlWlXfbxyrGSdo5jhqUandZM2uvSicGMvB_I/edit#
Next steps: Check hubspot integration, implement options
Sprint 4 (2019)Stefan BusemannStefan Busemannhttps://git.typo3.org/services/archive/t3o/my/-/issues/60Order of the AJAX login form events makes important information unavailable2018-11-02T07:24:48ZJo HasenauOrder of the AJAX login form events makes important information unavailableCurrently the loading of the AJAX login form is done together with the loading of the page. After filling out the login data and sending the form, the full page is reloaded, which again triggers the loading of the AJAX form. Depending on...Currently the loading of the AJAX login form is done together with the loading of the page. After filling out the login data and sending the form, the full page is reloaded, which again triggers the loading of the AJAX form. Depending on the login state either the same login form is shown again or the data of the successfully logged in user is shown.
The loading order raises the problem that important information about a login attempt and the login state is missing, so we can't show any message "login failed please try again", since we just know that the user is not logged in, but nothing about the attempt.
We discussed that in the team and came to the conclusion that the only reason for that AJAX approach was to get around caching problems of user related data. Instead of using an uncached variant like USER_INT or
https://fluidtypo3.org/viewhelpers/vhs/2.1.4/Render/UncacheViewHelper.html
AJAX actually would only make sense, when the form would be generated on click and give immediate feedback without reloading the page. This way we would only send one request to the server on demandand maybe reload the page once. The way it is implemented now, it could be done much easier with the uncached variants already mentioned, since a request is sent to the server with each page request anyway and a login creates another triple of requests.Sprint 5 (2018)https://git.typo3.org/services/archive/t3o/my/-/issues/63Activate RealURL2018-10-31T16:29:41ZStefan BusemannActivate RealURLAs a user i like to see speaking urls for my.typo3.org
UAC:
* Pages are shown as url path
* femanager get params are transferred into meaningful namesAs a user i like to see speaking urls for my.typo3.org
UAC:
* Pages are shown as url path
* femanager get params are transferred into meaningful namesSprint 5 (2018)https://git.typo3.org/services/archive/t3o/my/-/issues/28Add "no mail" field to user profiles2020-06-14T18:54:44ZStefan BusemannAdd "no mail" field to user profilesIt happened recently that the marketing team sent out a mail to all typo3.org users to promote their new shop site.
I wish that there is a checkbox in user profiles which lets you unsubscribe from those mails.
Additionally, I think that...It happened recently that the marketing team sent out a mail to all typo3.org users to promote their new shop site.
I wish that there is a checkbox in user profiles which lets you unsubscribe from those mails.
Additionally, I think that from a legal point of view, it needs to be clarified if such a field should be turned on or off for existing users (opt-in vs. opt-out).
From https://forge.typo3.org/issues/63470https://git.typo3.org/services/archive/t3o/my/-/issues/37Change for mail address2020-06-14T18:54:44ZStefan BusemannChange for mail address* User must confirm change of mail address by double opt in
* this feature must be implemented in femanager
* check if email adress must be unique* User must confirm change of mail address by double opt in
* this feature must be implemented in femanager
* check if email adress must be uniquehttps://git.typo3.org/services/archive/t3o/my/-/issues/50Setup Password and username restrictions2018-04-10T18:28:29ZStefan BusemannSetup Password and username restrictionsUAC
* [x] Username must contain at least 8 characters
* [x] Username must consist of alphanumeric characters - no special chars
* [x] Password must contain at least 12 charactersUAC
* [x] Username must contain at least 8 characters
* [x] Username must consist of alphanumeric characters - no special chars
* [x] Password must contain at least 12 charactersSprint 2018-03 (Release)https://git.typo3.org/services/archive/t3o/my/-/issues/54"You're successfully logged in now" shown when editing profile2019-03-28T06:08:27ZJo Hasenau"You're successfully logged in now" shown when editing profileWhen you edit the user profile after a successful login, the message "You're successfully logged in now" is shown, which seems to be wrong in this context.
Steps to reproduce
* Register at my.typo3.org (with auto confirmation active)
* ...When you edit the user profile after a successful login, the message "You're successfully logged in now" is shown, which seems to be wrong in this context.
Steps to reproduce
* Register at my.typo3.org (with auto confirmation active)
* go to edit profile => flash message is shown
Reason:
* Flash Message "successfully logged in now" is shown, when the next flash message container is shown
Possible solution
* redirect to a page, where the flash message is shown in the right context.Sprint 3 (2019)Keval PandyaKeval Pandyahttps://git.typo3.org/services/archive/t3o/my/-/issues/59Order of countries should be done by label not by value2020-06-14T18:54:45ZJo HasenauOrder of countries should be done by label not by valueThe list of countries in the user profile is sorted by original value instead of translated labels.
So "Schweiz" (CH) can be found before "Deutschland" (DE), which is confusing for the users.
Sorting should be done by translated label in...The list of countries in the user profile is sorted by original value instead of translated labels.
So "Schweiz" (CH) can be found before "Deutschland" (DE), which is confusing for the users.
Sorting should be done by translated label instead.https://git.typo3.org/services/archive/t3o/my/-/issues/114Reset Password throws error: Uncaught TYPO3 Exception Cannot unset string off...2018-07-10T11:14:43ZStefan BusemannReset Password throws error: Uncaught TYPO3 Exception Cannot unset string offsetsfrom info@web-hosting-uk.com
Uncaught TYPO3 Exception
Cannot unset string offsets
Error thrown in file
/home/my/ci/releases/7/html/typo3conf/ext/femanager/Classes/DataProcessor/CleanUserGroup.php in line 18.
21 In2code\Femanager\DataP...from info@web-hosting-uk.com
Uncaught TYPO3 Exception
Cannot unset string offsets
Error thrown in file
/home/my/ci/releases/7/html/typo3conf/ext/femanager/Classes/DataProcessor/CleanUserGroup.php in line 18.
21 In2code\Femanager\DataProcessor\CleanUserGroup::process(array)
/home/my/ci/releases/7/html/typo3conf/ext/femanager/Classes/DataProcessor/DataProcessorRunner.php:
00091: );
00092: $dataProcessor->initializeDataProcessor();
00093: $arguments = $dataProcessor->process($arguments);
00094: } else {
00095: throw new \UnexpectedValueException('Finisher does not implement ' . $this->interface, 1516373829946);
20 In2code\Femanager\DataProcessor\DataProcessorRunner::callClasses(array, array, TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer, TYPO3\CMS\Extbase\Mvc\Controller\Arguments)
/home/my/ci/releases/7/html/typo3conf/ext/femanager/Classes/Controller/AbstractController.php:
00381: $this->settings,
00382: $this->contentObject,
00383: $this->arguments
00384: );
00385: $this->request->setArguments($this->pluginVariables);
19 In2code\Femanager\Controller\AbstractController::initializeAction()
/home/my/ci/releases/7/vendor/typo3/cms/typo3/sysext/extbase/Classes/Mvc/Controller/ActionController.php:
00163: $this->initializeActionMethodValidators();
00164: $this->mvcPropertyMappingConfigurationService->initializePropertyMappingConfigurationFromRequest($request, $this->arguments);
00165: $this->initializeAction();
00166: $actionInitializationMethodName = 'initialize' . ucfirst($this->actionMethodName);
00167: if (method_exists($this, $actionInitializationMethodName)) {
18 TYPO3\CMS\Extbase\Mvc\Controller\ActionController::processRequest(TYPO3\CMS\Extbase\Mvc\Web\Request, TYPO3\CMS\Extbase\Mvc\Web\Response)
/home/my/ci/releases/7/vendor/typo3/cms/typo3/sysext/extbase/Classes/Mvc/Dispatcher.php:
00083: $controller = $this->resolveController($request);
00084: try {
00085: $controller->processRequest($request, $response);
00086: } catch (\TYPO3\CMS\Extbase\Mvc\Exception\StopActionException $ignoredException) {
00087: }
17 TYPO3\CMS\Extbase\Mvc\Dispatcher::dispatch(TYPO3\CMS\Extbase\Mvc\Web\Request, TYPO3\CMS\Extbase\Mvc\Web\Response)
/home/my/ci/releases/7/vendor/typo3/cms/typo3/sysext/extbase/Classes/Mvc/Web/FrontendRequestHandler.php:
00089: /** @var $response \TYPO3\CMS\Extbase\Mvc\ResponseInterface */
00090: $response = $this->objectManager->get(\TYPO3\CMS\Extbase\Mvc\Web\Response::class);
00091: $this->dispatcher->dispatch($request, $response);
00092: return $response;
00093: }
16 TYPO3\CMS\Extbase\Mvc\Web\FrontendRequestHandler::handleRequest()
/home/my/ci/releases/7/vendor/typo3/cms/typo3/sysext/extbase/Classes/Core/Bootstrap.php:
00197: $requestHandler = $requestHandlerResolver->resolveRequestHandler();
00198:
00199: $response = $requestHandler->handleRequest();
00200: // If response is NULL after handling the request we need to stop
00201: // This happens for instance, when a USER object was converted to a USER_INT
15 TYPO3\CMS\Extbase\Core\Bootstrap::handleRequest()
/home/my/ci/releases/7/vendor/typo3/cms/typo3/sysext/extbase/Classes/Core/Bootstrap.php:
00184: {
00185: $this->initialize($configuration);
00186: return $this->handleRequest();
00187: }
00188:
14 TYPO3\CMS\Extbase\Core\Bootstrap::run("", array)
13 call_user_func_array(array, array)
/home/my/ci/releases/7/vendor/typo3/cms/typo3/sysext/frontend/Classes/ContentObject/ContentObjectRenderer.php:
06335: ], [
06336: $content,
06337: $conf
06338: ]);
06339: } else {
12 TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer::callUserFunction("TYPO3\CMS\Extbase\Core\Bootstrap->run", array, "")
/home/my/ci/releases/7/vendor/typo3/cms/typo3/sysext/frontend/Classes/ContentObject/UserContentObject.php:
00039: $this->cObj->setUserObjectType(ContentObjectRenderer::OBJECTTYPE_USER);
00040: }
00041: $tempContent = $this->cObj->callUserFunction($conf['userFunc'], $conf, '');
00042: if ($this->cObj->doConvertToUserIntObject) {
00043: $this->cObj->doConvertToUserIntObject = false;
11 TYPO3\CMS\Frontend\ContentObject\UserContentObject::render(array)
/home/my/ci/releases/7/vendor/typo3/cms/typo3/sysext/frontend/Classes/ContentObject/ContentObjectRenderer.php:
00818: // Render content
00819: try {
00820: $content .= $contentObject->render($configuration);
00821: } catch (ContentRenderingException $exception) {
00822: // Content rendering Exceptions indicate a critical problem which should not be
10 TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer::render(TYPO3\CMS\Frontend\ContentObject\UserContentObject, array)
/home/my/ci/releases/7/vendor/typo3/cms/typo3/sysext/frontend/Classes/ContentObject/ContentObjectRenderer.php:
00734: $contentObject = $this->getContentObject($name);
00735: if ($contentObject) {
00736: $content .= $this->render($contentObject, $conf);
00737: } else {
00738: // Call hook functions for extra processing
9 TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer::cObjGetSingle("USER", array)
/home/my/ci/releases/7/vendor/typo3/cms/typo3/sysext/frontend/Classes/Controller/TypoScriptFrontendController.php:
03523: break;
03524: case 'FUNC':
03525: $incContent = $INTiS_cObj->cObjGetSingle('USER', $INTiS_config[$INTiS_key]['conf']);
03526: break;
03527: case 'POSTUSERFUNC':
8 TYPO3\CMS\Frontend\Controller\TypoScriptFrontendController::INTincScript_process(array)
/home/my/ci/releases/7/vendor/typo3/cms/typo3/sysext/frontend/Classes/Controller/TypoScriptFrontendController.php:
03485: do {
03486: $INTiS_config = $this->config['INTincScript'];
03487: $this->INTincScript_process($INTiS_config);
03488: // Check if there were new items added to INTincScript during the previous execution:
03489: $INTiS_config = array_diff_assoc($this->config['INTincScript'], $INTiS_config);
7 TYPO3\CMS\Frontend\Controller\TypoScriptFrontendController::recursivelyReplaceIntPlaceholdersInContent()
/home/my/ci/releases/7/vendor/typo3/cms/typo3/sysext/frontend/Classes/Controller/TypoScriptFrontendController.php:
03452: }
03453:
03454: $this->recursivelyReplaceIntPlaceholdersInContent();
03455: $this->getTimeTracker()->push('Substitute header section');
03456: $this->INTincScript_loadJSCode();
6 TYPO3\CMS\Frontend\Controller\TypoScriptFrontendController::INTincScript()
/home/my/ci/releases/7/vendor/typo3/cms/typo3/sysext/frontend/Classes/Http/RequestHandler.php:
00223: if ($this->controller->isINTincScript()) {
00224: $this->timeTracker->push('Non-cached objects', '');
00225: $this->controller->INTincScript();
00226: $this->timeTracker->pull();
00227: }
5 TYPO3\CMS\Frontend\Http\RequestHandler::handleRequest(TYPO3\CMS\Core\Http\ServerRequest)
/home/my/ci/releases/7/vendor/typo3/cms/typo3/sysext/core/Classes/Core/Bootstrap.php:
00313:
00314: // Execute the command which returns a Response object or NULL
00315: $this->response = $requestHandler->handleRequest($request);
00316: return $this;
00317: }
4 TYPO3\CMS\Core\Core\Bootstrap::handleRequest(TYPO3\CMS\Core\Http\ServerRequest)
/home/my/ci/releases/7/vendor/typo3/cms/typo3/sysext/frontend/Classes/Http/Application.php:
00077: public function run(callable $execute = null)
00078: {
00079: $this->bootstrap->handleRequest(\TYPO3\CMS\Core\Http\ServerRequestFactory::fromGlobals());
00080:
00081: if ($execute !== null) {
3 TYPO3\CMS\Frontend\Http\Application::run()
/home/my/ci/releases/7/vendor/typo3/cms/typo3/sysext/frontend/Resources/Private/Php/frontend.php:
00021: call_user_func(function () {
00022: $classLoader = require __DIR__ . '/../../../../../../vendor/autoload.php';
00023: (new \TYPO3\CMS\Frontend\Http\Application($classLoader))->run();
00024: });
2 {closure}()
/home/my/ci/releases/7/vendor/typo3/cms/typo3/sysext/frontend/Resources/Private/Php/frontend.php:
00022: $classLoader = require __DIR__ . '/../../../../../../vendor/autoload.php';
00023: (new \TYPO3\CMS\Frontend\Http\Application($classLoader))->run();
00024: });
1 require("/home/my/ci/releases/7/vendor/typo3/cms/typo3/sysext/frontend/Resources/Private/Php/frontend.php")
/home/my/ci/releases/7/vendor/typo3/cms/index.php:
00001: <?php
00002:
00003: require __DIR__ . '/typo3/sysext/frontend/Resources/Private/Php/frontend.php';Sprint 4 (2018)Marcus SchwemerMarcus Schwemerhttps://git.typo3.org/services/archive/t3o/my/-/issues/130Create LDAP container for ddev environment2020-06-14T18:53:15ZMarcus SchwemerCreate LDAP container for ddev environmentFor development purposes there must be a ldap container usable in the ddev environment.
It must be populated with dummy data, that can be used together felogin of the ddev instance.
* [x] Create ldap container and make accessible from ...For development purposes there must be a ldap container usable in the ddev environment.
It must be populated with dummy data, that can be used together felogin of the ddev instance.
* [x] Create ldap container and make accessible from the web container
* [ ] Set correct binddn
* [ ] Implement TYPO3 schema
* [ ] Create dummy data for ldap in ldif format
* [ ] Create corresponding fe_user data
* [ ] Provision both while container startup
* [ ] Add documentationhttps://git.typo3.org/services/archive/t3o/my/-/issues/133Please cache gravatar images locally2020-06-14T18:53:17ZFeedback from WebsitePlease cache gravatar images locally[Georg Ringer](mailto:georg.ringer@gmail.com) reported an issue
To improve privacy and performance please cache the gravatar images locally
Reported URL:https://my.typo3.org/index.php?id=23&tx_t3oslack_pi1%5Baction%5D=connect&tx_t3osla...[Georg Ringer](mailto:georg.ringer@gmail.com) reported an issue
To improve privacy and performance please cache the gravatar images locally
Reported URL:https://my.typo3.org/index.php?id=23&tx_t3oslack_pi1%5Baction%5D=connect&tx_t3oslack_pi1%5Bcontroller%5D=SlackUser&cHash=c4143ce98ba6f5694e30ce6c15f1ce8a
User Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36https://git.typo3.org/services/archive/t3o/my/-/issues/135Please provide feature to remove current user2020-06-14T18:54:45ZFeedback from WebsitePlease provide feature to remove current user[Georg Ringer](mailto:georg.ringer@gmail.com) reported an issue
would be nice to implement the "forget me" feature to remove a profile.
"Forget me" means:
1. Delete the user
1. Delete all assets related to the user
1. Remove extensio...[Georg Ringer](mailto:georg.ringer@gmail.com) reported an issue
would be nice to implement the "forget me" feature to remove a profile.
"Forget me" means:
1. Delete the user
1. Delete all assets related to the user
1. Remove extension keys without version
1. Transfer extension keys with version to `abandoned_extensions`
1. Remove all posts in forum
1. Remove the backend user
1. Anonymize the snippets in docs.typo3.org
1. Anonymize all occurences in articles, events and content on typo3.org
1. Remove reply on comments of the userhttps://git.typo3.org/services/archive/t3o/my/-/issues/192Password should be transferred to LDAP2018-09-14T07:34:21ZStefan BusemannPassword should be transferred to LDAPAfter a successful registration the password must be transferred to LDAPAfter a successful registration the password must be transferred to LDAPSprint 5 (2018)https://git.typo3.org/services/archive/t3o/my/-/issues/211Create 404 page2018-11-06T21:26:30ZDominik DörrCreate 404 pagemy.typo3.org is currently missing a 404 page.
* [x] Create a new 404 page or copy the page from typo3.org
* [x] Adjust pageNotFound_handling in LocalConfigurationmy.typo3.org is currently missing a 404 page.
* [x] Create a new 404 page or copy the page from typo3.org
* [x] Adjust pageNotFound_handling in LocalConfigurationSprint 6 (2018)Stefan BusemannStefan Busemannhttps://git.typo3.org/services/archive/t3o/my/-/issues/220Write depreciation (expiry) task for karma ledger entries2020-06-14T18:54:45ZMathias Bolt LesniakWrite depreciation (expiry) task for karma ledger entriesKarma ledger entries should expire after a certain period by setting the "expired" timestamp. We need a task for this.Karma ledger entries should expire after a certain period by setting the "expired" timestamp. We need a task for this.https://git.typo3.org/services/archive/t3o/my/-/issues/222Set up manual karma sources on my.typo3.org2020-06-14T18:54:46ZMathias Bolt LesniakSet up manual karma sources on my.typo3.orgThese sources should at least be:
* "Attended official TYPO3 event"
* "Attended TYPO3 Camp"
* "Attended TYPO3 User Group Meeting"
* "Attended TYPO3 Team Sprint"
* "Karma cash transfer"These sources should at least be:
* "Attended official TYPO3 event"
* "Attended TYPO3 Camp"
* "Attended TYPO3 User Group Meeting"
* "Attended TYPO3 Team Sprint"
* "Karma cash transfer"https://git.typo3.org/services/archive/t3o/my/-/issues/223Improve input data control in karma extension2020-06-14T18:54:46ZMathias Bolt LesniakImprove input data control in karma extensionThe extension doesn't check all the data it receives and doesn't throw good errors. This can be improved.The extension doesn't check all the data it receives and doesn't throw good errors. This can be improved.https://git.typo3.org/services/archive/t3o/my/-/issues/224Create task for rebuilding karma cache in user records once a week2020-06-14T18:54:47ZMathias Bolt LesniakCreate task for rebuilding karma cache in user records once a weekhttps://git.typo3.org/services/archive/t3o/my/-/issues/258Add LDAP test, after FE_User creation2020-06-14T18:54:46ZStefan BusemannAdd LDAP test, after FE_User creationAs an admin, I want to be informed, if an LDAP operation fails
*UAC*
* [ ] check LDAP, after a fe_user was created, if the record exists
* [ ] send a Slack message, if an operation fails
* [ ] create a log entry, if an operation failsAs an admin, I want to be informed, if an LDAP operation fails
*UAC*
* [ ] check LDAP, after a fe_user was created, if the record exists
* [ ] send a Slack message, if an operation fails
* [ ] create a log entry, if an operation failshttps://git.typo3.org/services/archive/t3o/my/-/issues/267Provide a LDAP deletion option2020-01-15T13:46:35ZStefan BusemannProvide a LDAP deletion optionAs an admin, I want to be able, to delete an LDAP account and have a special form, to initiate this process.
**UAC**
* [x] Provide a GDPR Module
* [x] Select a user to delete in GDPR Module
* [x] Add Gitlab Ticketnummer / OTRS Link
*...As an admin, I want to be able, to delete an LDAP account and have a special form, to initiate this process.
**UAC**
* [x] Provide a GDPR Module
* [x] Select a user to delete in GDPR Module
* [x] Add Gitlab Ticketnummer / OTRS Link
* [x] Add Info Message
* [x] Conirm deletion
* [x] create an entry with username and email in old_user table
* [x] delete user in LDAP
* [x] Create an OTRS ticket with instructions for the server team for additional systems ([admin@typo3.org](mailto:admin@typo3.org))
* [x] extend old user with deletion date
* [x] extend old user with name of admin user who initiated the deletion
* [x] extend old user with link to Gitlab / OTRS TicketSprint 6 (2019)Stefan BusemannStefan Busemannhttps://git.typo3.org/services/archive/t3o/my/-/issues/279add groups to synchronization2019-02-13T20:01:15ZThomas Löffleradd groups to synchronization*Created by: Avalarion*
Hey ho,
we need to synchronize all the groups from typo3.org to LDAP and adjust user memberships as well.
Have a nice day,
Bastian*Created by: Avalarion*
Hey ho,
we need to synchronize all the groups from typo3.org to LDAP and adjust user memberships as well.
Have a nice day,
Bastianhttps://git.typo3.org/services/archive/t3o/my/-/issues/291Do not expose confidential account requests to public issue tracker (gitlab)2019-03-30T08:14:28ZFeedback from WebsiteDo not expose confidential account requests to public issue tracker (gitlab)[Lars Michalowski](mailto:l.michalowski@fishfarm.de) reported an issue
Hi!
When trying to login at typo3.org without success I finally found this note (light blue box) on the login page (https://my.typo3.org/login/?no_cache=1):
"Impor...[Lars Michalowski](mailto:l.michalowski@fishfarm.de) reported an issue
Hi!
When trying to login at typo3.org without success I finally found this note (light blue box) on the login page (https://my.typo3.org/login/?no_cache=1):
"Important: If you have not logged in at typo3.org since Dez 2016, your user account is inactive.
Please use the feedback form below, if you want to recover your account and submit your username and your email used with this account. Otherwise we can't verify it."
Since this was true for me I used the yellow button "provide feedback" at the bottom of the page (this was the only feedback form I found on that page).
I entered my details (you can see it as issue #290 on https://git-t3o.typo3.org/t3o/my/issues).
I was absolutely not aware of the fact that my confidential request about reactivating my account would become public available as an issue on the official issue tracker of my.typo3.org!
So please consider the following:
1. Provide a confidential way of submitting account related requests and do not use the general feedback form for that.
2. Provide information on the general feedback form about the automated publication of the entered data on https://git-t3o.typo3.org/t3o/my/issues so users will be aware of that before submitting the form.
Thanks,
Lars Michalowski
Reported URL:https://my.typo3.org/login/?no_cache=1
User Agent:Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:66.0) Gecko/20100101 Firefox/66.0
**AC**
* [ ] Newly created tickets via Feedback Form need to be confidentialSprint 3 (2019)Stefan BusemannStefan Busemannhttps://git.typo3.org/services/archive/t3o/my/-/issues/293User activation process fails2019-03-30T09:38:11ZStefan BusemannUser activation process fails### Summary
If I click "reactive User" in the list view of pid = 0 in old user table, I receive no feedback and no fe user is created
### Steps to reproduce
1. look for the user "l-fish"
1. click reactivate
1. look again for the us...### Summary
If I click "reactive User" in the list view of pid = 0 in old user table, I receive no feedback and no fe user is created
### Steps to reproduce
1. look for the user "l-fish"
1. click reactivate
1. look again for the user "l-fish"
### Example URL
BE of my.typo3.org
### What is the expected *correct* behavior?
* user is deleted in old_user table
* user is created as fe_user in pid 5
* user is created in LDAP
* Backend provides a feedback (flash message)
**Acceptence Criterias**
* [ ] *correct* behavior is fulfilledSprint 3 (2019)Stefan BusemannStefan Busemannhttps://git.typo3.org/services/archive/t3o/my/-/issues/405support delete user2019-11-20T21:04:51ZStefan Busemannsupport delete userIf a user gets deleted, we need to:
* [ ] Remove the user in the ldap
* [ ] Add a "user" delete function in ig_ldap_sso_auth (if a user does not exist in ldap, but in local instance, the user must be removed in local instance)If a user gets deleted, we need to:
* [ ] Remove the user in the ldap
* [ ] Add a "user" delete function in ig_ldap_sso_auth (if a user does not exist in ldap, but in local instance, the user must be removed in local instance)Backlog