TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692024-03-21T04:31:37ZTYPO3 Forge
Redmine TYPO3 Core - Bug #103444 (Resolved): YamlFileLoader has no logger instancehttp://forge.typo3.org/issues/1034442024-03-21T04:31:37ZBenjamin Franzkeben@bnf.dev
<p>Uncaught TYPO3 Exception Call to a member function error() on null<br />thrown in file /home/ben/src/TYPO3.CMS/typo3/sysext/core/Classes/Configuration/Loader/YamlFileLoader.php<br />in line 171</p> TYPO3 Core - Bug #101482 (Resolved): Mariadb acceptance test error detection not workinghttp://forge.typo3.org/issues/1014822023-07-29T07:43:51ZBenjamin Franzkeben@bnf.dev
<p>See <a class="external" href="https://typo3.slack.com/archives/C03AM9R17/p1690614726567099?thread_ts=1690593575.789689&cid=C03AM9R17">https://typo3.slack.com/archives/C03AM9R17/p1690614726567099?thread_ts=1690593575.789689&cid=C03AM9R17</a></p> TYPO3 Core - Bug #101480 (Resolved): Invalid null coalescing fallback to boolean in record listhttp://forge.typo3.org/issues/1014802023-07-29T06:59:54ZBenjamin Franzkeben@bnf.dev
<p>Causes an error since <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Add native type declarations to GU array methods (Closed)" href="http://forge.typo3.org/issues/101453">#101453</a></p>
<pre><code>Core: Exception handler (WEB: BE): TypeError, code #0, file /builds/typo3/CI/cms/typo3/sysext/core/Classes/Utility/GeneralUtility.php, line 801: TYPO3\CMS\Core\Utility\GeneralUtility::trimExplode(): Argument #2 ($string) must be of type string, bool given, called in /builds/typo3/CI/cms/typo3/sysext/backend/Classes/RecordList/DatabaseRecordList.php on line 2242- TypeError: TYPO3\CMS\Core\Utility\GeneralUtility::trimExplode(): Argument #2 ($string) must be of type string, bool given, called in /builds/typo3/CI/cms/typo3/sysext/backend/Classes/RecordList/DatabaseRecordList.php on line 2242, in file /builds/typo3/CI/cms/typo3/sysext/core/Classes/Utility/GeneralUtility.php:801 -</code></pre> TYPO3 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 - Bug #93132 (Closed): Localization carousel doesn't move slideshttp://forge.typo3.org/issues/931322020-12-21T10:33:31ZBenjamin Franzkeben@bnf.dev
<p>Bootstrap carousel item has been renamed to carousel-item.</p>
<p><img src="http://forge.typo3.org/attachments/download/35704/localization-carousel-doesnt-move.png" alt="" loading="lazy" /></p>
<p>See <a class="external" href="https://getbootstrap.com/docs/5.0/components/carousel/">https://getbootstrap.com/docs/5.0/components/carousel/</a></p> TYPO3 Core - Bug #89891 (Closed): Temporary assets can not be removed in install tool, exception ...http://forge.typo3.org/issues/898912019-12-06T22:37:42ZBenjamin Franzkeben@bnf.dev
<p>Exception is:</p>
<p>Too few arguments to function TYPO3\CMS\Core\Resource\ResourceFactory::__construct(), 0 passed in […]/typo3/sysext/core/Classes/Utility/GeneralUtility.php on line 3461 and exactly 1 expected</p>
<p>Solution:<br />The ResourceFactory needs to be defined by a service provider to be available in install tool mode.</p> TYPO3 Core - Bug #88808 (Closed): Warning in AbstractConfigurationManagerTesthttp://forge.typo3.org/issues/888082019-07-19T20:45:19ZBenjamin Franzkeben@bnf.dev
<pre>
TYPO3\CMS\Extbase\Tests\Unit\Configuration\AbstractConfigurationManager
⚠ Controller of switchable controller actions can be a fully qualified class name
┐
├ Trying to configure method "getSwitchableControllerActions" which cannot be configured because it does not exist, has not been specified, is final, or is static
│
</pre> TYPO3 Core - Bug #88576 (Closed): SiteProcessorTest produces a warning because of wrong method mo...http://forge.typo3.org/issues/885762019-06-17T16:35:22ZBenjamin Franzkeben@bnf.dev
<pre>
1) TYPO3\CMS\Frontend\Tests\Unit\DataProcessing\SiteProcessorTest::nullIsProvidedIfSiteCouldNotBeRetrieved
Trying to configure method "getSiteFinder" which cannot be configured because it does not exist, has not been specified, is final, or is static
</pre> TYPO3 Core - Bug #87622 (Closed): Minimum required prophecy version is incompatible with object (...http://forge.typo3.org/issues/876222019-02-02T06:08:41ZBenjamin Franzkeben@bnf.dev
<p>Recent changes like <a class="external" href="https://review.typo3.org/c/59600/">https://review.typo3.org/c/59600/</a> introduced <code>object</code> return type decarations which are only supported as of prophecy version 1.7.5.<br />This caused nightly, composer minimum builds, to fail: <a class="external" href="https://bamboo.typo3.com/browse/CORE-GTN-UT2PHP72-646">https://bamboo.typo3.com/browse/CORE-GTN-UT2PHP72-646</a></p>
<p>Therefore the default minimum – as required by phpunit (^1.7) – needs to be raised to 1.7.5.</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 - Bug #83867 (Closed): ProductionExceptionHandler: assumes TSFE is always availablehttp://forge.typo3.org/issues/838672018-02-12T21:56:06ZBenjamin Franzkeben@bnf.dev
<p>Uncaught Error: Call to a member function isBackendUserLoggedIn() on null<br />in […]/typo3/sysext/core/Classes/Error/ProductionExceptionHandler.php:103</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 #79043 (Closed): PSR-7 non 302 redirects do not workhttp://forge.typo3.org/issues/790432016-12-20T09:25:18ZBenjamin Franzkeben@bnf.dev
<p>If a Response object sets a status code other than 302 and adds a Location header,<br />Core\Bootstrap::sendResponse will always sent a 302 response code, instead of the defined one.</p>
<p>This is because the php header() function implicitly sets the response code to 302 if a location header is sent:<br /><a class="external" href="http://php.net/manual/en/function.header.php#refsect1-function.header-parameters">http://php.net/manual/en/function.header.php#refsect1-function.header-parameters</a></p> TYPO3 Core - Bug #78730 (Closed): rtehtmlarea: isRequiredClass check is incorrecthttp://forge.typo3.org/issues/787302016-11-17T09:58:40ZBenjamin Franzkeben@bnf.dev
<p>Given the following TSConfig:</p>
<pre><code>RTE {<br /> classes {<br /> btn-default {<br /> name = Default Button<br /> requires = btn<br /> }<br /> btn-primary {<br /> name = Primary Button<br /> requires = btn<br /> }<br /> btn.selectable = 0<br /> }<br /> }</code></pre>
<p>The incorrect isRequiredClass check causes the btn class to be<br />removed from the RTE toolbarbuttons. This happens because it's<br />considered unneded in DOM.removeClass(), which is called by<br />DOM.addClass() (to remove incompatible classes).</p>
<p>The check in isRequiredClass was probably copied from<br />some classesRequired lookups, but forgot to inverse the<br />class that's searched for.</p>
<p>This also fixes the RTE to properly remove the selectable=0 class<br />(e.g. btn), when a class that requires the aformentioned is removed<br />(e.g. btn-primary).</p>
<p>(Note: To avoid further incompatibilities between classes configured<br />for the RTE content and the RTE toolbar, it should be consided to not<br />render RTE Buttons using DOM.addClass())</p>