TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692018-03-20T06:46:09ZTYPO3 Forge
Redmine TYPO3 Core - Task #84490 (Closed): Add missing HTTP status code presets for PSR-7 responseshttp://forge.typo3.org/issues/844902018-03-20T06:46:09ZBenjamin Franzkeben@bnf.dev
<p>The list of status codes/reason phrases should be synchronized with<br /><a class="external" href="http://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml">http://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml</a></p> TYPO3 Core - Task #84126 (Closed): Remove comments that contain v4 or FLOW informationhttp://forge.typo3.org/issues/841262018-03-03T12:42:52ZBenjamin Franzkeben@bnf.dev
<p>Whether a class or functionality is not available or available<br />differently in v4 or FLOW is not relevant for TYPO3 CMS.<br />They should be removed.</p> TYPO3 Core - Task #84117 (Closed): Do not reinitialize CacheManager and PackageManager in clearAl...http://forge.typo3.org/issues/841172018-03-02T14:09:54ZBenjamin Franzkeben@bnf.dev
<p>Those (re)initializations originate from <a class="external" href="https://review.typo3.org/19605">https://review.typo3.org/19605</a><br />were reinitializeClassLoaderAndCachesAndPackageManagement()<br />was used to "Reinitialize the class loader during clear cache actions" <br />(according to phpdoc).</p>
<p>Then with the changes in <a class="external" href="https://review.typo3.org/29811">https://review.typo3.org/29811</a><br />reinitializeClassLoaderAndCachesAndPackageManagement()<br />was dropped and splitted into unregisterClassLoader(),<br />flagCachingFrameworkForReinitialization().<br />initializeCachingFramework() and initializePackageManagement().<br />(just historical info, still all good)</p>
<p>Then <a class="external" href="http://review.typo3.org/39827">http://review.typo3.org/39827</a> came and dropped unregisterClassLoader<br />but left the CacheManager and PackageManager reinitialization in place<br />superfluously. It's superfluous as the original usecase was to<br />reinitialize the class loader which is no longer required.</p> TYPO3 Core - Task #84109 (Closed): Merge the package DependencyResolver into the PackageManagerhttp://forge.typo3.org/issues/841092018-03-01T19:38:55ZBenjamin Franzkeben@bnf.devTYPO3 Core - Task #84107 (Closed): Stop monkey patching CacheManager configuration in InstallToolhttp://forge.typo3.org/issues/841072018-03-01T16:55:38ZBenjamin Franzkeben@bnf.dev
<p>Instead of creating the cacheManager and then disabling all cache confiurations afterwards, the desired state should simply be enforced inside the CacheManager.</p> TYPO3 Core - Task #84102 (Closed): Set COMPOSER_ROOT_VERSION to 9.2.0@dev for bamboohttp://forge.typo3.org/issues/841022018-03-01T11:55:15ZBenjamin Franzkeben@bnf.dev
<p>If typo3/testing-framework needs to be synced with changes<br />in core it needs to require the dev branch of the upcoming<br />release as the compatibility to previous releases needs to<br />be dropped.<br />Therefore it has to define a dependency in composer.json like:<br /> "typo3/cms-core": "^9.2@dev"</p>
<p>If composer install is executed with COMPOSER_ROOT_VERSION<br />set to 9.1.0 that produces a conflict, therefore the version<br />should be raised to 9.2.0@dev.</p> TYPO3 Core - Task #84099 (Closed): Decouple SystemEnvironmentBuilder from Bootstraphttp://forge.typo3.org/issues/840992018-03-01T11:10:58ZBenjamin Franzkeben@bnf.dev
<p>Do not rely on defined constants or methods from Bootstrap<br />to be usable on it own (at some point).</p> TYPO3 Core - Task #84083 (Closed): ApplicationContext should consistently be retrieved from Gener...http://forge.typo3.org/issues/840832018-02-28T15:28:39ZBenjamin Franzkeben@bnf.dev
<p>ClassLoadingInformation reads from Bootstrap, that should be adapted to use GeneralUtility.</p>
<p>Bootstrap code states:</p>
<pre>
* Use \TYPO3\CMS\Core\Utility\GeneralUtility::getApplicationContext() instead
</pre>
<p>Therefore the method should just be removed.</p> TYPO3 Core - Task #84082 (Closed): A LogRecord should not rely on global state (requestId from Bo...http://forge.typo3.org/issues/840822018-02-28T15:17:33ZBenjamin Franzkeben@bnf.devTYPO3 Core - Task #84015 (Closed): Use PSR-7 request params in viewpage modulehttp://forge.typo3.org/issues/840152018-02-22T21:25:11ZBenjamin Franzkeben@bnf.dev
<p>Since changeset I3020aa7a9cffd92d4b96afd4d4044979a771db5b<br />the viewpage module is a native PSR-7 controller, therefore<br />GeneralUtility _GP() and getIndpEnv() should no longer be used.</p> TYPO3 Core - Task #83966 (Closed): Consolidate singleton usagehttp://forge.typo3.org/issues/839662018-02-19T18:22:40ZBenjamin Franzkeben@bnf.dev
<p>There is Bootstrap::getInstance()->getEarlyInstance() and<br />GeneralUtility::makeInstance() to retrieve (global) instances.<br />Sometimes the former, sometimes the latter is used (e.g. to<br />retrieve the PackageManager).<br />As there is no obvious reason why diffrent methods are used, this<br />should be unified to one way to retrieve singletons.</p>
<p>Furthermore classes should not know whether something is an<br />early instance or not. Implementation details like that<br />should be abstracted into a singleton container.<br />That (currently) is GeneralUtility::makeInstance().</p> TYPO3 Core - Task #83961 (Closed): Remove unused bootstrap dependency from frontend RequestHandlerhttp://forge.typo3.org/issues/839612018-02-19T14:15:03ZBenjamin Franzkeben@bnf.dev
<p>Due tue moving FE and BE user authentication to middlewares, the Bootstrap instance is no longer needed in the frontend request handler.</p> TYPO3 Core - Task #83954 (Closed): Do not use Bootstrap->getInstance()::populateLocalConfigurationhttp://forge.typo3.org/issues/839542018-02-17T19:00:15ZBenjamin Franzkeben@bnf.devTYPO3 Core - Task #83953 (Closed): Inject the PackageManager into the DependencyResolverhttp://forge.typo3.org/issues/839532018-02-17T18:58:36ZBenjamin Franzkeben@bnf.devTYPO3 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>