Work Package #48275: TypoScript consistency
Drop support for node based TypoScript files
TypoScript files should no longer be searched in the subpath "Nodes".
The concept of TypoScript specific to a Node was abandoned in favor of a centralized TypoScript configuration. Any changes to the rendering based on nodes and node structure should be realized by using Matchers and EEL expressions in the central TypoScript.
The reasons were the following:
- you have one place to understand the whole rendering of a site
- the TS for the site is cacheable extremely well
- many team members did not like the node-path-to-file-system-magic and thought it was fragile
Updated by Christopher Hlubek over 8 years ago
I talked to Berit about this change and we came to the conclusion that there are certain requirements where overriding / replacing the TypoScript in the node structure make sense:
- A landing page inside the node tree where the rendering is changed heavily
- Continually changing one part of the site (e.g. preparing a relaunch) or composing a site of different sites
Of course this concept is one of the most misused in current TYPO3 CMS but also offers a great deal of flexibility. So we should favor and communicate the matcher based approach as the recommended one. It would be okay for me to remove the file based matching for now and leave the definition of TypoScript nodes for now.
Updated by Christian Müller over 8 years ago
For a relaunch I would even say you might want to create a new site package or better work on a separate host. In such a scenario using matchers might become a bit cumbersome. For a landing page you can pretty easily work with a separate Page object from the root matcher. I will try to write some Best Practice How-Tos about such scenarios.