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 - Story #101904 (Accepted): CKEditor5 UIhttp://forge.typo3.org/issues/1019042023-09-13T03:56:05ZBenjamin Franzkeben@bnf.dev
<p>Tracker for UI related CKEditor5 bugs or tasks.</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 #101288 (Resolved): sudo-mode opens module contents without backend frame when u...http://forge.typo3.org/issues/1012882023-07-07T13:08:44ZBenjamin Franzkeben@bnf.devTYPO3 Core - Bug #97144 (Closed): Slow module scrolling in Google Chrome on Linuxhttp://forge.typo3.org/issues/971442022-03-08T15:09:57ZBenjamin Franzkeben@bnf.dev
<p>Scrolling the list module with 100 entries causes FPS to drop to <15fps on Google Chrome (v99) with Linux during scrolling.<br />This is for sure a Chrome Bug, but reveals that <code>overflow: hidden</code> and <code>scrolling="no"</code> on the module iframe is not a good idea.</p>
<p>It would be great to remove the <code>scrolling="no"</code> parameter from the module iframe and enable scrolling on <html> instead of .module-body</p>
<p>There are some past issues to take into account when changing the module-scrolling semantics: <a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: Correct horizontal scrolling in iOS browsers (Closed)" href="http://forge.typo3.org/issues/83841">#83841</a> <a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: rte_ckeditor displaces dropdown overlays and jumps to top of page on crome/safari (Closed)" href="http://forge.typo3.org/issues/80116">#80116</a> <a class="issue tracker-1 status-5 priority-6 priority-high2 closed" title="Bug: RTE CKeditor top-positioning for maximize and combopanels is broken in browsers with webkit (Closed)" href="http://forge.typo3.org/issues/82780">#82780</a></p>
<p>Using overflow: auto on <code><html></code> as suggested in <a class="external" href="https://forge.typo3.org/issues/80116#note-7">https://forge.typo3.org/issues/80116#note-7</a> was mainly avoided because of mobile iOS overscroll behaviour, otherwise this could have already been changed with: <a class="external" href="https://review.typo3.org/c/Packages/TYPO3.CMS/+/55647">https://review.typo3.org/c/Packages/TYPO3.CMS/+/55647</a></p>
<p>Consider using the standardized <code>overscroll-behaviour</code> property to fix issues on that part.</p> 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 #92239 (Closed): SymfonyEventDispatcher is not symfony/event-dispatcher-contract...http://forge.typo3.org/issues/922392020-09-09T12:09:37ZBenjamin Franzkeben@bnf.dev
<p><b>Fatal error</b>: Declaration of TYPO3\CMS\Core\Adapter\SymfonyEventDispatcher::dispatch(object $event, ?string $eventName = NULL): object must be compatible with Symfony\Contracts\EventDispatcher\EventDispatcherInterface::dispatch($event) in <b>[…]typo3/sysext/core/Classes/Adapter/SymfonyEventDispatcher.php</b> on line <b>26</b><br /></p>
<p><a class="external" href="https://bamboo.typo3.com/browse/CORE-GTN-229">https://bamboo.typo3.com/browse/CORE-GTN-229</a></p> TYPO3 Core - Bug #91398 (Closed): Serialization of ObjectManager is brokenhttp://forge.typo3.org/issues/913982020-05-14T13:11:34ZBenjamin Franzkeben@bnf.dev
<p>This is broken in v10 since the introduction of dependency injection in:<br /><a class="external" href="https://review.typo3.org/c/Packages/TYPO3.CMS/+/58255">https://review.typo3.org/c/Packages/TYPO3.CMS/+/58255</a></p>
<p>Using:<br /><pre>
serialize($this->objectManager)
</pre></p>
<p>Results in the following exception:</p>
<pre>
(1/1) Exception
Serialization of 'Closure' is not allowed
</pre> TYPO3 Core - Bug #91316 (Closed): MetaTagManagerRegistry instance not unique in uncached pluginshttp://forge.typo3.org/issues/913162020-05-06T09:04:27ZBenjamin Franzkeben@bnf.dev
<p>Reported by Aristeidis Karavas (Apr 28th at 11:51) via Slack:<br /><a class="external" href="https://typo3.slack.com/archives/C025BQLFA/p1588067478426300">https://typo3.slack.com/archives/C025BQLFA/p1588067478426300</a></p>
<blockquote>
<p>Why in TYPO3 v10 this won't set the meta tags in frontend?<br />$metaTag = $this->metaTagManagerRegistry->getManagerForProperty($key);<br />$metaTag->addProperty($key, $metaTagValue);<br />If i debug it, it sets everything right but it won't be displayed in the frontend</p>
</blockquote>
<p>The reason is that the PageRenderer stores a new Singleton via <code>GeneralUtility::setSingletonInstance</code> in <code>__wakeup</code>.</p>
<p>That updates <code>MetaTagManagerRegistry</code> instances retrieved via <code>GeneralUtility::makeInstance</code>, but not those injected via symfony DI,<br />where the object will already have been generated, as it is loaded during EXT:seo/ext_localconf.php loading and GeneralUtility::makeInstance<br />will call the DI container.</p>
<p>This issues happens when the PageRenderer was serialized and is unserialized for <code>USER_INT</code> plugins (e.g. uncached extbase plugins).</p>
<p>Same applies to AssetCollector, which is serialized and unserialized as well.</p> TYPO3 Core - Bug #91074 (Rejected): typo3conf/ folder is not created when using a custom app-dir ...http://forge.typo3.org/issues/910742020-04-17T01:15:10ZBenjamin Franzkeben@bnf.dev
<p>In composer mode in composer.json:</p>
<pre><code>"extra": {<br /> "typo3/cms": {<br /> "app-dir": "custom",<br /> "web-dir": "public" <br /> }<br /> },</code></pre>
<p>In this case Environment::$projectPath would be /path/to/root/custom and Environment::$publicPath would be /path/to/root/public.</p>
<p>The typo3conf folder is then generated in /path/to/root/custom/typo3conf instead of /path/to/root/public/typo3conf.</p>
<p>This is actually by accident, because "custom" and "public" have the same length.<br />Reason is the code in <a class="external" href="https://git.typo3.org/Packages/TYPO3.CMS.git/blob/9fb677f6f3b3a1cd584b9ef183b35da771d3e25d:/typo3/sysext/install/Classes/FolderStructure/DefaultFactory.php#l134">https://git.typo3.org/Packages/TYPO3.CMS.git/blob/9fb677f6f3b3a1cd584b9ef183b35da771d3e25d:/typo3/sysext/install/Classes/FolderStructure/DefaultFactory.php#l134</a><br /><pre>
$publicPath = substr(Environment::getPublicPath(), strlen(Environment::getProjectPath())+1);
</pre><br />which tries to substract the project path from the public path, while assuming that project path is an ancestor, which results in a public path <code>""</code> to be calculate.<br />The result should rather be <code>"../public"</code>.</p>
<p>We should rather generate a relative path and adapt the FolderStructur Factory to handle relative paths, include partent dots ("..").</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 #86372 (Closed): CacheManager 'assets' cache is not configurable in ext_localcon...http://forge.typo3.org/issues/863722018-09-25T14:39:41ZBenjamin Franzkeben@bnf.dev
<p>Since commit <a class="external" href="https://review.typo3.org/c/54020/">https://review.typo3.org/c/54020/</a> + followup <a class="external" href="https://review.typo3.org/54061">https://review.typo3.org/54061</a> (released only in v9) it is no longer possible to configure the 'assets' cache in ext_localconf.php files.</p>
<p>The IconRegisty is loaded in backend mode and reads the configuration (caches from 'assets') during object construction.<br />IconRegistry is usually instantiated during ext_localconf.php (due to extensions registering icons),<br />and therefore create's the 'assets' cache during ext_localconf.php loading.</p>
<p>After CacheManager has created the assets cache once, it will never be recreated again,<br />when the final configuration is set, after all ext_localconf.php files have been loaded.</p> TYPO3 Core - Task #83953 (Closed): Inject the PackageManager into the DependencyResolverhttp://forge.typo3.org/issues/839532018-02-17T18:58:36ZBenjamin Franzkeben@bnf.dev