TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692024-03-26T13:38:30ZTYPO3 Forge
Redmine TYPO3 Core - Task #103488 (Under Review): Move EXT:frontend TypoScript to configuration folderhttp://forge.typo3.org/issues/1034882024-03-26T13:38:30ZBenjamin Franzkeben@bnf.devTYPO3 Core - Task #103485 (Under Review): Provide lib.parseFunc via ext:frontendhttp://forge.typo3.org/issues/1034852024-03-26T08:54:11ZBenjamin Franzkeben@bnf.devTYPO3 Core - Task #103450 (Under Review): Extract site persistence into separate servicehttp://forge.typo3.org/issues/1034502024-03-21T11:23:38ZBenjamin Franzkeben@bnf.dev
<p>The SiteConfiguration service is currently needed during installation<br />phase for writing site configurations. This limits symfony dependency<br />injection usage and basically requires that all services needed by<br />SiteConfiguration need to be defined and manually wired in<br />ServiceProvider php code.</p>
<p>The writing part is now split into a separate service that can be used<br />in EXT:install SetupService as before.</p> TYPO3 Core - Feature #103439 (Under Review): Site TypoScripthttp://forge.typo3.org/issues/1034392024-03-20T14:35:14ZBenjamin Franzkeben@bnf.dev
<p>Allow TypoScript without requiring sys_template records.</p>
<p>Idea: A site can define TypoScript and include other dependencies via profiles (<a class="issue tracker-2 status-8 priority-4 priority-default child" title="Feature: Site Profiles that ship Settings, TypoScript, TSConfig, Templates and enabled Content Elements (Under Review)" href="http://forge.typo3.org/issues/103437">#103437</a>)</p> TYPO3 Core - Feature #103437 (Under Review): Site Profiles that ship Settings, TypoScript, TSConf...http://forge.typo3.org/issues/1034372024-03-20T14:16:04ZBenjamin Franzkeben@bnf.dev
<p>From <a class="external" href="https://forge.typo3.org/issues/103034">https://forge.typo3.org/issues/103034</a></p>
<blockquote>
<p>Site Settings, it is a must-have to include site setting presets from extensions and to override them.</p>
</blockquote> TYPO3 Core - Task #103075 (New): Use full module paths in navigationComponenthttp://forge.typo3.org/issues/1030752024-02-07T14:15:39ZBenjamin Franzkeben@bnf.dev
<p>see <a class="external" href="https://review.typo3.org/c/Packages/TYPO3.CMS/+/81411/93#message-147d54d2d072d7baab287befc7c81a35c131c53e">https://review.typo3.org/c/Packages/TYPO3.CMS/+/81411/93#message-147d54d2d072d7baab287befc7c81a35c131c53e</a></p> TYPO3 Core - Task #102560 (Under Review): Enable TypeScript strictNullCheckshttp://forge.typo3.org/issues/1025602023-11-30T08:28:25ZBenjamin Franzkeben@bnf.dev
<p>This is to avoid bugs like <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Backend Login Screen shows JS Error (Closed)" href="http://forge.typo3.org/issues/91913">#91913</a> or <a class="issue tracker-1 status-3 priority-4 priority-default closed" title="Bug: Page TSConfig crashes browser with T3Editor extension enabled (Resolved)" href="http://forge.typo3.org/issues/101893">#101893</a></p> TYPO3 Core - Story #101906 (Under Review): CKEditor5 missing pluginshttp://forge.typo3.org/issues/1019062023-09-13T06:46:57ZBenjamin Franzkeben@bnf.dev
<p>CKEditor Plugins that where shipped in TYPO3 v11, but miss in TYPO3 v12</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 - Epic #98287 (New): Use web components (via lit) in TYPO3 Backendhttp://forge.typo3.org/issues/982872022-09-07T18:46:15ZBenjamin Franzkeben@bnf.dev
<p>The scope of this epic is to use web components as replacement for the distribution of application logic between HTML templates and CSS/JavaScript files.</p>
<p>A side effect will often be that jQuery becomes useless/cumbersome and is implicitly superseded due do the native reactivity and scroping of web components.</p>
<p>Also see <a class="external" href="https://review.typo3.org/q/topic:lit">https://review.typo3.org/q/topic:lit</a></p> TYPO3 Core - Feature #97150 (Accepted): Support dependency injection for routing aspectshttp://forge.typo3.org/issues/971502022-03-09T07:59:12ZBenjamin Franzkeben@bnf.dev
<p>Reported by John Miller in <a class="issue tracker-1 status-6 priority-4 priority-default closed" title="Bug: GeneralUtility::makeinstance() container fetch should be allowed with or without arguments. (Rejected)" href="http://forge.typo3.org/issues/97149">#97149</a>, routing aspects do not allow dependeny injection as $settings array is passed uncondtially to aspects.</p>
<p>An <code>SettingsAwareInterface</code> should be aded that allows settings to be set via a setter method instead of the constructor arguments</p> TYPO3 Core - Bug #91220 (Accepted): ExtensionManager dependency calculation does not take extensi...http://forge.typo3.org/issues/912202020-04-28T11:40:12ZBenjamin Franzkeben@bnf.dev
<p>When one extension depends on two extensions where both extensions depend on a third one, but with a different set of matching versions, then ExtensionManager is unable to find the common dependency version that is allowed by both extensions, because it decided for a very too early.</p>
<p>Sound very complicated in written words, therefore an example:</p>
<p>Two custom extensions: "master" and "other_ext"</p>
<p>EXT:master (allowing powermail v6-v8 and depending on `other_ext`)</p>
<pre><code>'constraints' => array(<br /> 'depends' => array(<br /> 'typo3' => '9.5.0-9.5.99',<br /> 'powermail' => '6.0.0-8.99.99',<br /> 'other_ext' => '*',<br /> ),<br /> ),<br />EXT:other_ext (allowing only powermail v6)</code></pre>
<pre><code>'constraints' => array(<br /> 'depends' => array(<br /> 'typo3' => '9.5.0-9.5.99',<br /> 'powermail' => '6.0.0-6.99.99',<br /> ),<br /> ),</code></pre>
<p>When installing "master" on 9.5 the error "powermail was requested to be downloaded in different versions (6.2.0 and 7.4.0)." will be thrown.</p>
<p>That is because the latest version of powermail is used when checking dependencies for "EXT:master" – the compatible v6 should/could be taken into account as both extensions are marked to be compatible with it and v6 itself is marked to be v9.5 compatible.</p>
<p>Note: This is <strong>not</strong> a bug that was introduced with <a class="external" href="https://review.typo3.org/c/Packages/TYPO3.CMS/+/64308/">https://review.typo3.org/c/Packages/TYPO3.CMS/+/64308/</a> (that patch is fine) – it's just an additional and more complex case.</p>
<p><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Special dependencies are not checked during install of dependencies (Closed)" href="http://forge.typo3.org/issues/91179">#91179</a> is therefore related, but not the source of this bug.</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 #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