TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692023-07-29T07:42:45ZTYPO3 Forge
Redmine TYPO3 Core - Task #101481 (Closed): Revert "[!!!][TASK] Add native type declarations to GU array...http://forge.typo3.org/issues/1014812023-07-29T07:42:45ZBenjamin Franzkeben@bnf.dev
<p>CI test failures were not catched properly.</p> TYPO3 Core - Task #96707 (Closed): Fix PHPStan errors in JavaScript module classeshttp://forge.typo3.org/issues/967072022-01-31T10:35:53ZBenjamin Franzkeben@bnf.devTYPO3 Core - Task #96704 (Closed): Harden event listener automagic parameter type resolutionhttp://forge.typo3.org/issues/967042022-01-31T07:50:21ZBenjamin Franzkeben@bnf.dev
<p>Do only auto-resolve the event name if the reflection type<br />of the first parameter is a ReflectionNamedType [1] as<br />only this subclass of ReflectionType defines the getName() method.</p>
<p>[1] <a class="external" href="https://www.php.net/manual/en/class.reflectionnamedtype.php">https://www.php.net/manual/en/class.reflectionnamedtype.php</a></p> TYPO3 Core - Task #96703 (Closed): Fix definition availability checks in DI compiler passeshttp://forge.typo3.org/issues/967032022-01-31T07:28:01ZBenjamin Franzkeben@bnf.dev
<p>findDefinition() doesn't actually return a boolean (or null)<br />value on failure but throws an exception instead. As an alternative<br />$container->hasDefintion may be used to check for definition availability.</p> TYPO3 Core - Task #96691 (Closed): Add phpstan plugin for psr/containerhttp://forge.typo3.org/issues/966912022-01-30T15:02:37ZBenjamin Franzkeben@bnf.devTYPO3 Core - Bug #93233 (Closed): Backend Group Comparison is brokenhttp://forge.typo3.org/issues/932332021-01-06T15:46:40ZBenjamin Franzkeben@bnf.dev
<pre>
(1/1) Error
Typed property TYPO3\CMS\Core\Authentication\AbstractUserAuthentication::$userSession must not be accessed before initialization
in /home/ben/src/TYPO3.CMS/typo3/sysext/core/Classes/Authentication/AbstractUserAuthentication.php line 1012
* @return mixed
*/
public function getSessionData($key)
{
return $this->userSession->get($key);
}
</pre> TYPO3 Core - Task #88721 (Closed): Hook up ContainerInterface in backend route dispatcherhttp://forge.typo3.org/issues/887212019-07-11T11:55:58ZBenjamin Franzkeben@bnf.dev
<p>Backend RouterDispatcher use the symfony provided PSR-11 container to retrieve services from the container, if available.</p> TYPO3 Core - Task #87735 (Closed): Do not use ObjectManager to instantiate PageTitleProviderManagerhttp://forge.typo3.org/issues/877352019-02-19T00:05:16ZBenjamin Franzkeben@bnf.dev
<p>PageTitleProviderManager is not marked as internal and public API of<br />EXT:core should not depend on initialization through the EXT:extbase<br />ObjectManager.</p>
<p>PageTitleProviderManager actually does not use any ObjectManager features,<br />so the current instantiation in TypoScriptFrontendController can simply be<br />replaced by GeneralUtility::makeInstance().</p> TYPO3 Core - Bug #87229 (Closed): checkDataSubmission is missing in extension scannerhttp://forge.typo3.org/issues/872292018-12-19T20:05:14ZBenjamin Franzkeben@bnf.dev
<p>In <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Deprecate hooks superseded by PSR-15 middlewares (Closed)" href="http://forge.typo3.org/issues/86279">#86279</a> checkDataSubmission slipped through and was forgotten to be mentioned in a .rst file and the extension scanner configuration.</p> TYPO3 Core - Bug #83946 (Closed): Content-Type for some backend ajax routes and eID scripts broke...http://forge.typo3.org/issues/839462018-02-16T21:06:04ZBenjamin Franzkeben@bnf.dev
<p><a class="external" href="https://review.typo3.org/c/55754">https://review.typo3.org/c/55754</a> refactored all PSR-7<br />related controllers to remove an own response.</p>
<p>Missing is the fact that ajax routes used a<br />pre-generated response with application/json<br />Content-Type header.<br />eID scripts did not use a pre-generated header<br />at all.</p> TYPO3 Core - Task #83864 (Closed): Directly wire Application and RequestHandlerhttp://forge.typo3.org/issues/838642018-02-12T19:09:43ZBenjamin Franzkeben@bnf.dev
<p>Bootstrap should not contain application specific code (HTTP vs CLI). The Application should handle their request handlers themselves.</p> TYPO3 Core - Task #83726 (Closed): HTTP RequestHandlers should use strict typinghttp://forge.typo3.org/issues/837262018-01-29T21:12:35ZBenjamin Franzkeben@bnf.devTYPO3 Core - Task #83724 (Closed): HTTP RequestHandlers should always return a PSR-7 ResponseInte...http://forge.typo3.org/issues/837242018-01-29T21:03:15ZBenjamin Franzkeben@bnf.dev
<p>The PSR-15 middleware interfaces [1] require that RequestHandlers always return a Response.<br />In order to support PSR-15 middleware (at some point), TYPO3 request handlers should do the same.</p>
<p>A NULL return value should rather be replaced with a PSR-7 Response that's either ignored by Core\Bootstrap or a Response with a 200 status code and an empty body.</p>
<p>[1] <a class="external" href="https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-15-request-handlers.md">https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-15-request-handlers.md</a></p> TYPO3 Core - Bug #79107 (Closed): Extensionmanager shows incorrect warning in composer modehttp://forge.typo3.org/issues/791072016-12-29T13:24:05ZBenjamin Franzkeben@bnf.dev
<p>The warning should be an info instead, as the warning can't be resolved besides not using composer:</p>
<blockquote><blockquote>
<p>The system is set to composer mode. Please notice that it is not possible to add an extension with the Extension Manager. You have to use composer to add further extensions to your system.</p>
</blockquote></blockquote> TYPO3 Core - Bug #78719 (Closed): Backend Login ignores redirect_urlhttp://forge.typo3.org/issues/787192016-11-16T15:03:24ZBenjamin Franzkeben@bnf.dev
<p>The commit 9099b64c (<a class="external" href="http://review.typo3.org/39234">http://review.typo3.org/39234</a>) introduced a new form API, and forgot to pass the GET parameter 'redirect_url' into the login template, the hidden input field is never filled.</p>
<p>That means redirect_url works for already logged-in users, but not if the user has to login first.</p>