Bug #101656
closed
Using Include TypoScript in template fails to apply included template
0%
Description
When including a base-template via "Include TypoScript", the included template creates a nested sys_template node and is not applied to the page-rendering.
We do have several cases, where we have two or three websites with the same base-template and adaptions for the different sites.
Files
Updated by Jasmina Ließmann over 1 year ago
- Related to Feature #97816: New TypoScript parser added
Updated by Jasmina Ließmann over 1 year ago
- Status changed from New to Needs Feedback
Thank you for your report.
Since TYPO3 v12.4.5 provides fix for #101407 - could you please check if your problem still occurs in the current version 12.4.5?
Updated by Jasmina Ließmann over 1 year ago
- Related to Bug #101407: ext_typoscript_setup.typoscript is only available in one Page Tree (Multiple Sites) added
Updated by Kilian Frey about 1 year ago
I have updated the site and it works for most parts. Two issues persist:
The values for lib.contentElement.layoutRootPaths/partialRootPaths/templateRootPaths get reset and additional paths are lost.
A custom lib.parseFunc is not applied via {f.cObjec}. Although I don't know if that's related.
Updated by Christian Kuhn about 1 year ago
- Status changed from Needs Feedback to Closed
Thanks for feedback.
I understand your initial INCLUDE_TYPOSCRIPT issue vanished, so I hope it's ok to close here.
For the other things you mentioned: We relatively recently had a fix regarding the =< operator with #100115. I suppose the other two things may be related to that operator. I case the issues persist in your project with youngest v12 releases, could you please verify them again, reduce them to a good how-to-reproduce set, and report them as fresh issues, please?