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 #103382 (Resolved): Context-Menu placed in invisible area when opened at bottom ...http://forge.typo3.org/issues/1033822024-03-13T09:21:55ZBenjamin Franzkeben@bnf.dev
<p><a class="external" href="https://typo3.slack.com/archives/C03AM9R17/p1710271829140209?thread_ts=1710244943.836959&cid=C03AM9R17">https://typo3.slack.com/archives/C03AM9R17/p1710271829140209?thread_ts=1710244943.836959&cid=C03AM9R17</a><br /><a class="external" href="https://typo3.slack.com/archives/C03AM9R17/p1710244943836959">https://typo3.slack.com/archives/C03AM9R17/p1710244943836959</a></p> TYPO3 Core - Task #103358 (Resolved): Make admin user creation optional in CLI installerhttp://forge.typo3.org/issues/1033582024-03-11T09:32:20ZBenjamin Franzkeben@bnf.dev
<p>Improve the CLI command `setup` to allow instance creation<br />without enforcing admin user and password to be defined.</p>
<p>This enables to create tiny test setups where no admin user is<br />needed or where users are imported from fixtures.</p> TYPO3 Core - Task #103354 (Resolved): Update TypeScript to 5.4http://forge.typo3.org/issues/1033542024-03-09T16:24:33ZBenjamin Franzkeben@bnf.devTYPO3 Core - Task #103081 (Resolved): Failing nightlies due to incorrect window sizehttp://forge.typo3.org/issues/1030812024-02-08T10:54:12ZBenjamin Franzkeben@bnf.dev
<p><a class="external" href="https://git.typo3.org/typo3/CI/cms/-/pipelines/52871">https://git.typo3.org/typo3/CI/cms/-/pipelines/52871</a></p>
<pre>
1) PageTreeFilterCest: Clear filter reloads page tree without filter applied
Test Acceptance/Application/PageTree/PageTreeFilterCest.php:clearFilterReloadsPageTreeWithoutFilterApplied
Step Can see "inline mngroup","#typo3-pagetree-tree .nodes-list"
Fail Failed asserting that any element by '#typo3-pagetree-tree .nodes-list' on page /typo3/module/web/list?id=51
Elements:
+ <div> New TYPO3 site
Root
styleguide TCA demo
staticdata
ctrl common
ctrl minimal
displaycond
elements basic
elements folder
elements group
elements imagemanipulation
elements rte
elements select
elements slugs
elements t3editor
file
flex
inline 11
inline 1n
inline 1n1n
inline 1nnol10n
inline 1nreusabletable
inline expand
inline expandsingle
inline foreignrecorddefaults
contains text 'inline mngroup'
Scenario Steps:
19. $I->canSee("inline mngroup","#typo3-pagetree-tree ...") at Acceptance/Application/PageTree/PageTreeFilterCest.php:83
18. $I->canSee("elements group","#typo3-pagetree-tree ...") at Acceptance/Application/PageTree/PageTreeFilterCest.php:82
17. $I->waitForElementVisible("//*[text()='inline expa...") at Acceptance/Application/PageTree/PageTreeFilterCest.php:81
16. $I->waitForElementNotVisible("#typo3-pagetree ....",10) at Acceptance/Application/PageTree/PageTreeFilterCest.php:116
15. $I->waitForElement("#typo3-pagetree-tree .nodes...",10) at Acceptance/Application/PageTree/PageTreeFilterCest.php:115
14. $I->pressKey("#typo3-pagetree #typo3-pagetree-...","") at Acceptance/Application/PageTree/PageTreeFilterCest.php:78
Artifacts:
</pre>
<p><img src="http://forge.typo3.org/attachments/download/38243/TYPO3.CMS.Core.Tests.Acceptance.Application.PageTree.PageTreeFilterCest.clearFilterReloadsPageTreeWithoutFilterApplied.headless.fail.png" alt="" loading="lazy" /></p> TYPO3 Core - Bug #89764 (Closed): Boolean Container parameters are incompatible with Symfony 5.0http://forge.typo3.org/issues/897642019-11-25T08:31:44ZBenjamin Franzkeben@bnf.dev
<p>Symfony 4.4 deprecated support for non-object services:<br /><a class="external" href="https://github.com/symfony/dependency-injection/commit/6f11b359ab9cc97838bc9fa7cf1480528bdcb54f">https://github.com/symfony/dependency-injection/commit/6f11b359ab9cc97838bc9fa7cf1480528bdcb54f</a></p>
<p>Symfony 5.0 introduced type declaration in Container->set which causes an exception when we set synthetic boolean services:<br /><a class="external" href="https://github.com/symfony/dependency-injection/blob/501d3378459fdc7993dc29b55c7d14fc27172768/Container.php#L144">https://github.com/symfony/dependency-injection/blob/501d3378459fdc7993dc29b55c7d14fc27172768/Container.php#L144</a></p>
<p>Argument 2 passed to Symfony\Component\DependencyInjection\Container::set() must be an object or null, bool given, called in […]/typo3/sysext/core/Classes/DependencyInjection/ContainerBuilder.php on line 99</p>
<p>at Symfony\Component\DependencyInjection\Container->set('_early.env.is_unix', true)</p> TYPO3 Core - Bug #88825 (Closed): Exception during Dependency Injection Container compilation whe...http://forge.typo3.org/issues/888252019-07-23T14:39:06ZBenjamin Franzkeben@bnf.dev
<p>This is with TYPO3 v10 installed using composer, without EXT:scheduler being available.</p>
<p>Installtion step 5 fails due to container being built. Frontend and Backend can not be opened.</p>
<pre>
During class fetch: Uncaught ReflectionException: Class TYPO3\CMS\Scheduler\Task\AbstractTask not found in […]/public/typo3/sysext/reports/Classes/Task/SystemStatusUpdateTask.php:28
Stack trace:
#0 […]/vendor/composer/ClassLoader.php(444): include('/home/ben/src/t...')
#1 […]/vendor/composer/ClassLoader.php(322): Composer\Autoload\includeFile('/home/ben/src/t...')
#2 […]/vendor/typo3/class-alias-loader/src/ClassAliasLoader.php(130): Composer\Autoload\ClassLoader->loadClass('TYPO3\\CMS\\Repor...')
#3 […]/vendor/typo3/class-alias-loader/src/ClassAliasLoader.php(120): TYPO3\ClassAliasLoader\ClassAliasLoader->loadClass('TYPO3\\CMS\\Repor...')
#4 [internal function]: TYPO3\ClassAliasLoader\ClassAliasLoader->loadClassWithAlias('TYPO3\\CMS\\Repor...')
#5 [internal function]: spl_autoload_call('TYPO3\\CMS\\Repor...')
#6 […] in […]/public/typo3/sysext/reports/Classes/Task/SystemStatusUpdateTask.php on line 28
</pre> 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>