TYPO3 Core

Hey Tobias,

sounds like the problem of inclusion order of TypoScript. I guess you have the same problem with CSS Styled Content?

Hi Benni,

as I wrote in the description, with css_styled_content everything works as expected. I have an own extension for my templates. In the ext_tables.php I add the static templates:

\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addStaticFile($_EXTKEY, 'Configuration/TypoScript', 'My Template Configuration');

So I can add them in the Backend. That's the only static template I want to include there. Every other template should be included in e. g. setup.txt like described above. When doing this with css_styled_content everything is fine. With fluid_styled_content the parts like this are missing:

#############################################
## TypoScript added by extension "indexed_search" 
#############################################

When I add it directly in the backend it works. With css_styled_content both ways work. And I just change the path to the templates in this case (and install css_styled_content or fluid_styled_content of course - never both).

Tobi

Hi Tobias, are you aware of the PageTS fluid_styled_content provides and need to be added to the root page of your instance? Maybe you miss it, and this causes your problem?

See https://docs.typo3.org/typo3cms/extensions/core/latest/Changelog/7.5/Feature-38732-Fluid-basedContentElementsIntroduced.html

Hi Anja,

I also added the PageTS through an include in an external file. But there is only one file in fluid_styled_content for PageTS and it is for the NewContentElementWizard. I included it like this:

<INCLUDE_TYPOSCRIPT: source="FILE: EXT:fluid_styled_content/Configuration/PageTSconfig/NewContentElementWizard.ts">

The defined elements in this file show up correctly after adding it. So I think this is ok. PageTS is also only for backend I think. But the problem for me is in the frontend. Didn't find any other TS files to include in fluid_styled_content.

When adding the static templates in the backend, is there some additional magic happening?

Move the lines including your TS from ext_tables.php to ext_localconf.php and try again :-)

Tried to move this line from ext_tables.php to ext_localconf.php ..

\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addStaticFile($_EXTKEY, 'Configuration/TypoScript', 'My Template Configuration');

.. but then I can't even select the static template of my extension. So I think ext_tables.php is the right place for this.

Not the static files but the PageTS stuff - somehting similar happens, when you configure Gridelements with external files and include them in ext_tables.php
So it's just a wild guess but it could be the reason.

Yes, I use "\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addPageTSConfig" in ext_localconf.php already. So I think this should be fine. As stated above I don't do anything different than with css_styled_content and there it works as it should. I uninstall css_styled_content, install fluid_styled_content and adjust the include paths for the static templates in my external file. The standard TS is included - as I can see it in the template analyzer - but the dynamic parts are missing.

Hy! I just want to say that I experience the same problem.

For me this is even a must-have, since it is the only way to create file-based website configurations for modern deployment. Or am I missing another/better way?

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/45080