TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692021-02-23T01:21:03ZTYPO3 Forge
Redmine TYPO3 Core - Bug #93567 (Closed): Typo in MFA changeloghttp://forge.typo3.org/issues/935672021-02-23T01:21:03ZOliver BartschTYPO3 Core - Bug #93558 (Closed): Evaluate providers internal statehttp://forge.typo3.org/issues/935582021-02-22T11:07:11ZOliver Bartsch
<p>The providers methods, defined by the implementing Interface, should not rely on the controller to check if the request is feasible.</p> TYPO3 Core - Bug #93111 (Closed): RuntimeException since ResetPasswordCommand does not set applic...http://forge.typo3.org/issues/931112020-12-18T22:30:47ZOliver Bartsch
<p>The reset password command uses the method <code>createFakeWebRequest</code> to create a PSR-7. Since FluidEmail uses TSFE, TSFE:::getGlobalInstance() is called from the service container. This method however checks since <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Drop usages of TYPO3_MODE and TYPO3_REQUESTTYPE (Closed)" href="http://forge.typo3.org/issues/92953">#92953</a> for the application type. Since the application type is not set on faking the request, this fails and leads to: 'No valid attribute "applicationType" found in request object.'</p> TYPO3 Core - Task #93093 (Closed): Shortcuts should not store the whole url including token param...http://forge.typo3.org/issues/930932020-12-16T18:01:33ZOliver Bartsch
<p>To be able to introduce speaking urls for the backend, sys_be_shortcuts needs to be reworked since it currently stores the complete url in the database.</p> TYPO3 Core - Task #93060 (Closed): Shortcut title must be set by controllershttp://forge.typo3.org/issues/930602020-12-11T14:57:18ZOliver BartschTYPO3 Core - Feature #93048 (Closed): Introduce URL rewrites for Backend linkshttp://forge.typo3.org/issues/930482020-12-10T14:28:06ZOliver BartschTYPO3 Core - Task #93041 (Closed): Remove TypoScript option addQueryString.methodhttp://forge.typo3.org/issues/930412020-12-09T16:41:02ZOliver BartschTYPO3 Core - Bug #93023 (Closed): Rework session handlinghttp://forge.typo3.org/issues/930232020-12-07T21:42:05ZOliver BartschTYPO3 Core - Bug #92905 (Closed): Some formatting in master (TYPO3 11) changelog is brokenhttp://forge.typo3.org/issues/929052020-11-23T11:07:02ZOliver BartschTYPO3 Core - Bug #92447 (Closed): Multiple issues after streamline of DatabaseRecordListhttp://forge.typo3.org/issues/924472020-09-29T20:45:15ZOliver Bartsch
<p>Just stumbled over following issues (compared to latest 10)</p>
<ul>
<li>Localization column of localized records has no indention anymore</li>
<li>Possible localization buttons are rendered for -1 records</li>
<li>Possible localization buttons are rendered for free mode records </li>
<li>Possible localization buttons rendered for already localized languages after localizing Free mode records</li>
</ul>
<p>See Screenshots v10 and v11 for the comparison and v11(2) to see what happened after localization of free mode records.</p> TYPO3 Core - Bug #91126 (Closed): [EA] The operation results to '(int)$page['doktype']', please a...http://forge.typo3.org/issues/911262020-04-19T13:38:08ZOliver Bartsch
<p>Also the return statement could be simplified by using in_array instead of comparing each doktype.<br />And the `$page !== null` check is superflous as it is checked implicit by fetching the doktype.</p> TYPO3 Core - Bug #91112 (Closed): Wrong PHPDoc for dashboards ButtonProviderhttp://forge.typo3.org/issues/911122020-04-18T14:47:29ZOliver BartschTYPO3 Core - Bug #91056 (Closed): The template for the listWidget is missing the footer block whi...http://forge.typo3.org/issues/910562020-04-16T00:35:06ZOliver BartschTYPO3 Core - Bug #91055 (Closed): Some Widget template are missing the closing </html> taghttp://forge.typo3.org/issues/910552020-04-16T00:27:20ZOliver BartschTYPO3 Core - Task #91051 (Closed): Some widgets still use a private function to generate the butt...http://forge.typo3.org/issues/910512020-04-15T18:47:49ZOliver Bartsch
<p>Since there is a Utility, the corresponding method should be used consistent to unify the way buttons are created and also to remove duplicated code fragments.</p>