TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692024-03-19T07:46:03ZTYPO3 Forge
Redmine TYPO3 Core - Task #103421 (Resolved): Update ckeditor5 to 41.2.1http://forge.typo3.org/issues/1034212024-03-19T07:46:03ZBenjamin Franzkeben@bnf.dev
<p><a class="external" href="https://github.com/ckeditor/ckeditor5/releases/tag/v41.2.1">https://github.com/ckeditor/ckeditor5/releases/tag/v41.2.1</a></p> TYPO3 Core - Task #103351 (Resolved): Avoid duplicate image crop (crop-crop-scale to crop-scale)http://forge.typo3.org/issues/1033512024-03-08T18:55:39ZBenjamin Franzkeben@bnf.devTYPO3 Core - Task #103297 (Resolved): Add composer-mode to our acceptance test matrixhttp://forge.typo3.org/issues/1032972024-03-06T10:42:13ZBenjamin Franzkeben@bnf.dev
<p>All applicable acceptance tests should also executed<br />in composer mode in order to cover possible regressions for this mode.</p> TYPO3 Core - Bug #103296 (Resolved): Composer-Mode public resource paths are not correctly resolv...http://forge.typo3.org/issues/1032962024-03-06T10:28:44ZBenjamin Franzkeben@bnf.dev
<pre>
Refused to apply style from 'https://t3core.localhost/Build/composer/public/typo3/main?token=80d4c64f1e289e50651c299d3e3a173d58b7c763' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
</pre>
<p><img src="http://forge.typo3.org/attachments/download/38296/inline-ajax-public-resource-url-wrong-composer-mode.png" alt="" loading="lazy" /></p>
<p>Found via patchset 9 of <a class="external" href="https://review.typo3.org/c/Packages/TYPO3.CMS/+/83027/9">https://review.typo3.org/c/Packages/TYPO3.CMS/+/83027/9</a><br /><a class="external" href="https://git.typo3.org/typo3/CI/cms/-/jobs/3016881">https://git.typo3.org/typo3/CI/cms/-/jobs/3016881</a></p>
<pre>
1) Inline1nCest: Disable an Inline Element which has no checkbox for disabled state
Test Acceptance/Application/FormEngine/Inline1nCest.php:disableInline1nInlineElementWithoutRenderedDisableField
Found following JavaScript errors in the browser console:
18:25:42.44 SEVERE - http://web/typo3/record/edit?token=7f59b97d48ea3fd858f2b2c1bc91542804b38b1e&edit%5Btx_styleguide_inline_1n%5D%5B1%5D=edit&returnUrl=/typo3/module/web/list?token%3De6f62f45187ab9f4523b043b9357378cf58cdf7c%26id%3D127%26table%3D%26pointer%3D1 - Refused to apply style from 'http://web/typo3/main?token=56002678c4b7605eb7a5d9d1760554f92e7bf5d1' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
Scenario Steps:
19. $I->click("button span[data...","[data-field-name...") at Acceptance/Application/FormEngine/Inline1nCest.php:172
18. $I->waitForElement("input[data-formengine-input-na...") at Acceptance/Application/FormEngine/Inline1nCest.php:169
17. $I->click("div[data-bs-togg...","[data-field-name...") at Acceptance/Application/FormEngine/Inline1nCest.php:168
16. $I->click("inline_2") at Acceptance/Application/FormEngine/Inline1nCest.php:165
15. $I->waitForText("Edit Form",3,"h1") at Acceptance/Application/FormEngine/Inline1nCest.php:44
14. $I->click("#recordlist-tx_styleguide_inline_1n a[a...") at Acceptance/Application/FormEngine/Inline1nCest.php:43
Artifacts:
Png: /builds/typo3/CI/cms/typo3/sysext/core/Tests/../../../../typo3temp/var/tests/AcceptanceReports/TYPO3.CMS.Core.Tests.Acceptance.Application.FormEngine.Inline1nCest.disableInline1nInlineElementWithoutRenderedDisableField.ci.composer.headless.fail.png
Html: /builds/typo3/CI/cms/typo3/sysext/core/Tests/../../../../typo3temp/var/tests/AcceptanceReports/TYPO3.CMS.Core.Tests.Acceptance.Application.FormEngine.Inline1nCest.disableInline1nInlineElementWithoutRenderedDisableField.ci.composer.headless.fail.html
</pre> TYPO3 Core - Bug #103294 (Resolved): Race condition in DI cache persistencehttp://forge.typo3.org/issues/1032942024-03-06T09:10:49ZBenjamin Franzkeben@bnf.dev
<p>With <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Improve dependency injection container caching (Closed)" href="http://forge.typo3.org/issues/90418">#90418</a> the container cache has been excluded from the<br />regular cache-flush-pipeline.<br />Therefore flushing has been explicitly performed when writing a<br />new cache entry (with the intent to clean up old cache entries).</p>
<p>Issue is: Cleaning up the entire folder by deleting the folder means<br />a concurrent request – that is creating the same DI cache as well –<br />will fail to write the cache when the folder is (re)moved in that<br />moment.</p>
<pre>
In SimpleFileBackend.php line 232:
The temporary cache file "/var/www/html/typo3temp/var/cache/code/di/65e832cba8809119262340.temp" could not be written.
</pre> TYPO3 Core - Task #103287 (Resolved): Revert "[TASK] Format fluid format tags consistently"http://forge.typo3.org/issues/1032872024-03-05T14:32:10ZBenjamin Franzkeben@bnf.dev
<p>The patch has been merged with too few votes.</p> TYPO3 Core - Task #103278 (Resolved): Use TypoScript static file dependency chain in EXT:styleguidehttp://forge.typo3.org/issues/1032782024-03-04T22:46:48ZBenjamin Franzkeben@bnf.dev
<p>Load TypoScript dependencies via include_static_file.txt which<br />is the defined pattern for loading dependencies of a static template,<br />ensuring that both constants and typoscript setup of dependencies are<br />loaded, without having to load all required dependencies both in<br />constants.typoscript and setup.typoscript.</p> TYPO3 Core - Task #103151 (Resolved): Feature-96874-CKEditor5.html#css-styling should be updated;...http://forge.typo3.org/issues/1031512024-02-19T12:36:08ZBenjamin Franzkeben@bnf.dev
<p>Posted by <a class="user active user-mention" href="http://forge.typo3.org/users/3351">@Markus Klein</a> on <a class="external" href="https://typo3.slack.com/archives/C025BQLFA/p1708344285858899">https://typo3.slack.com/archives/C025BQLFA/p1708344285858899</a></p>
<p>RST should be updated:<br /><a class="external" href="https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/12.0/Feature-96874-CKEditor5.html#css-styling">https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/12.0/Feature-96874-CKEditor5.html#css-styling</a></p>
<p>Got outdated with:</p>
<blockquote>
<p>81295: [BUGFIX] Apply CKEditor5 CSS scoping client-side | <a class="external" href="https://review.typo3.org/c/Packages/TYPO3.CMS/+/81295">https://review.typo3.org/c/Packages/TYPO3.CMS/+/81295</a></p>
</blockquote> TYPO3 Core - Task #103109 (Resolved): Important-102799-TYPO3_CONF_VARSGFXprocessor_stripColorProf...http://forge.typo3.org/issues/1031092024-02-13T11:10:01ZBenjamin Franzkeben@bnf.dev
<p>One patchset was missing from <a class="external" href="https://review.typo3.org/c/Packages/TYPO3.CMS/+/82940">https://review.typo3.org/c/Packages/TYPO3.CMS/+/82940</a> that had been forget to be updated to updates on the main branch.</p> TYPO3 Core - Task #103104 (Resolved): Use first class closures for service provider factorieshttp://forge.typo3.org/issues/1031042024-02-13T00:24:44ZBenjamin Franzkeben@bnf.dev
<p>Adapt the service provider compiler to perform the same level of<br />optimization as for the array-based callable syntax:<br />We unrol the static closure into it's static components (class name and<br />method name). That means the effective generated dependency injection<br />php code is the same as before with the gain of better DX.</p> TYPO3 Core - Task #103086 (Resolved): Allow execution of acceptance tests with local chromedriver...http://forge.typo3.org/issues/1030862024-02-09T05:57:26ZBenjamin Franzkeben@bnf.dev
<p>A local instance can sometimes be better debugged and odd behaviour easier introspected, when acceptance tests are possible to be run on the host instead of in containers only.</p>
<p>The testing setup should be adapted to allow that using codeception <code>--env</code> parameter</p> TYPO3 Core - Feature #103043 (Resolved): Modernize tree rendering and implement RTL and dark modehttp://forge.typo3.org/issues/1030432024-02-05T06:09:42ZBenjamin Franzkeben@bnf.devTYPO3 Core - Task #93773 (Closed): Move SVG Tree to Lit Elementshttp://forge.typo3.org/issues/937732021-03-18T13:41:48ZBenjamin Franzkeben@bnf.dev
<p>The entire SVG Tree should be a HTML element, to allow further<br />reduction of d3 usage in favor of native HTML5 APIs.</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 #86492 (Closed): stdWrap on config.additionalHeaders is broken for (fully) cache...http://forge.typo3.org/issues/864922018-10-01T09:56:28ZBenjamin Franzkeben@bnf.dev
<p>The feature to use stdWrap for additionalHeaders was introduced in v9 development cycle: <a class="external" href="https://review.typo3.org/c/50142/">https://review.typo3.org/c/50142/</a><br />It seems this is broken since the initial commit (and is still in master).</p>
<p>Suppose using the following TypoScript (as suggested in the documentation):</p>
<pre>
config.additionalHeaders {
10 {
# The header string
header = X-TYPO3-foo:
header.dataWrap = |{page:uid}
}
}
</pre>
<p>Both the original commit 2124bba49f68f5c35705c5c499abe6a0ee95a6cf and current master result in an Exception for a page that is read from cache because <code>TypoScriptFrontendController->cObj</code> is not initialized:</p>
<pre>
? $this->cObj->stdWrap(trim($header), $options['header.'])
Oops, an error occurred!
Call to a member function stdWrap() on string.
</pre>
<p>cObj is initialized in TSFE::newCObj, which is called by <code>TSFE::preparePageContentGeneration</code>, which itself is only called if the page is uncached or rendered initially (for good reasons).</p>
<p>I'm not sure whether we should revert this feature, instead of fixing this and implcitly allowing uncached stuff to be executed (through stdWrap) for a fully cached page. Things like these may be better handled by middlewares.</p>