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 #103473 (Resolved): Account for double click pagetree timeout in acceptance testshttp://forge.typo3.org/issues/1034732024-03-23T06:28:58ZBenjamin 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 - 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 - 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 #103420 (Resolved): runTests.sh cleanupshttp://forge.typo3.org/issues/1034202024-03-19T07:20:44ZBenjamin Franzkeben@bnf.devTYPO3 Core - Bug #102243 (Under Review): RTE CKEditor5 "externalPlugins" configuration is not mig...http://forge.typo3.org/issues/1022432023-10-24T11:58:09ZBenjamin Franzkeben@bnf.dev
<p>The following CKEditor config loaded and configured the wordcount plugin in TYPO3 v11, but does not in TYPO3 v12.4.0-v12.4.7:</p>
<pre><code class="yaml syntaxhl" data-language="yaml"><span class="na">editor</span><span class="pi">:</span>
<span class="na">externalPlugins</span><span class="pi">:</span>
<span class="na">wordcount</span><span class="pi">:</span>
<span class="na">resource</span><span class="pi">:</span> <span class="s2">"</span><span class="s">EXT:rte_ckeditor/Resources/Public/JavaScript/Contrib/plugins/wordcount/plugin.js"</span>
<span class="na">maxCharCount</span><span class="pi">:</span> <span class="m">100</span>
<span class="na">maxWordCount</span><span class="pi">:</span> <span class="m">50</span>
<span class="na">showCharCount</span><span class="pi">:</span> <span class="kc">true</span>
<span class="na">showRemaining</span><span class="pi">:</span> <span class="kc">true</span>
</code></pre>
<p>Note that this was not the recommended v11 config for "internal" plugins, but it did work and was used according to Josef Glatz (who reported this).</p>
<p>Note that the equivalent "official" v11 style config works and is properly migrated:</p>
<pre><code class="yaml syntaxhl" data-language="yaml"><span class="na">editor</span><span class="pi">:</span>
<span class="na">config</span><span class="pi">:</span>
<span class="na">extraPlugins</span><span class="pi">:</span>
<span class="pi">-</span> <span class="s">wordcount</span>
<span class="na">wordcount</span><span class="pi">:</span>
<span class="na">maxCharCount</span><span class="pi">:</span> <span class="m">100</span>
<span class="na">maxWordCount</span><span class="pi">:</span> <span class="m">50</span>
<span class="na">showCharCount</span><span class="pi">:</span> <span class="kc">true</span>
<span class="na">showRemaining</span><span class="pi">:</span> <span class="kc">true</span>
</code></pre>
<p>Ideally both formats would be supported in TYPO3 v12.</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 - Task #101615 (Under Review): Remove implicit wait timeout from acceptance testshttp://forge.typo3.org/issues/1016152023-08-08T08:09:17ZBenjamin Franzkeben@bnf.devTYPO3 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 #93270 (Under Review): BroadcastMessage.fromData() is not idempotenthttp://forge.typo3.org/issues/932702021-01-12T06:35:24ZBenjamin Franzkeben@bnf.dev
<p>If BroadcastMessage is recreated using <code>BroadcastMessage.fromData()</code> it does not retain the original object structure. This is because <code>BroadcastMessage.fromData()</code> nests the entrire data (which includes a <code>payload</code> property itself) into another wrapping <code>payload</code> property.</p>
<p>Given following JavaScript code (executable in a Browser console in a window of the TYPO3 Backend):</p>
<pre><code class="javascript syntaxhl" data-language="javascript"><span class="nb">window</span><span class="p">.</span><span class="nf">require</span><span class="p">([</span><span class="dl">'</span><span class="s1">TYPO3/CMS/Backend/BroadcastMessage</span><span class="dl">'</span><span class="p">],</span> <span class="p">({</span><span class="nx">BroadcastMessage</span><span class="p">})</span> <span class="o">=></span> <span class="p">{</span>
<span class="kd">const</span> <span class="nx">bm1</span> <span class="o">=</span> <span class="k">new</span> <span class="nc">BroadcastMessage</span><span class="p">(</span><span class="dl">'</span><span class="s1">component</span><span class="dl">'</span><span class="p">,</span> <span class="dl">'</span><span class="s1">eventName</span><span class="dl">'</span><span class="p">,</span> <span class="p">{</span><span class="na">foo</span><span class="p">:</span> <span class="dl">'</span><span class="s1">bar</span><span class="dl">'</span><span class="p">})</span>
<span class="c1">// Create bm2 from bm1, as if bm1 has been sent via broadcastchannel</span>
<span class="kd">const</span> <span class="nx">bm2</span> <span class="o">=</span> <span class="nx">BroadcastMessage</span><span class="p">.</span><span class="nf">fromData</span><span class="p">(</span><span class="nx">bm1</span><span class="p">)</span>
<span class="nx">console</span><span class="p">.</span><span class="nf">log</span><span class="p">(</span><span class="dl">'</span><span class="s1">bm1</span><span class="dl">'</span><span class="p">,</span> <span class="nx">bm1</span><span class="p">.</span><span class="nx">payload</span><span class="p">)</span>
<span class="nx">console</span><span class="p">.</span><span class="nf">log</span><span class="p">(</span><span class="dl">'</span><span class="s1">bm2</span><span class="dl">'</span><span class="p">,</span> <span class="nx">bm2</span><span class="p">.</span><span class="nx">payload</span><span class="p">)</span>
<span class="p">})</span>
</code></pre>
<p>The expected result/output is that <code>payload</code> contains the same value for both <code>BroadcastMessage</code> instances:<br /><pre>
bm1 {foo: "bar"}
bm2 {foo: "bar"}
</pre></p>
<p>While it actually is:<br /><pre>
bm1 {foo: "bar"}
bm2 {payload: {foo: "bar"}}
</pre></p>
<p><code>BroadcastMessage.fromData()</code> should be fixed to be idempotent, while keeping backwards compatibility (to existing event-subscribers) by doing the "additional" payload wrapping in <code>BroadcastMessage.createCustomEvent</code>. The "good" thing is, that BroadcastMessage isn't used directly by subscribers, it is transformed into a <code>CustomEvent</code>, therefore this can be fixed without breaking BC.</p>