frommeandClaude Opus 5.5
0ac58c1033
The set includes the same ep_theme TypoScript the root templates included statically, and config/sites/*/settings.yaml hold the constants of each site's root template, generated with TYPO3's own TypoScript parser and kept under their old names, so no TypoScript changes. They are plain values without definitions, so nothing is type-converted. Rolling out takes a second step: the root templates, with their clear flags, still replace everything the set provides, so this deploy alone changes nothing. .ddev/plans/sql/2026-10-27-site-sets.sql then hides them and moves their setup (date picker presets, partner IDs, ...) into extension templates editors keep maintaining. Extension templates further down the tree keep applying on top. Verified locally on a prod copy: - the resolved constants and setup of 43 pages (every site root, every page with an extension template below it, every page layout) are identical before the deploy, between deploy and SQL, after the SQL and after its rollback - a crawl of all 1912 frontend URLs is identical before and after Rollback: always run 2026-10-27-site-sets-rollback.sql BEFORE rolling back this code, or the sites have no TypoScript at all in between. Co-Authored-By: Claude Opus 5.5 <[email protected]>
2 lines
65 B
Plaintext
2 lines
65 B
Plaintext
@import 'EXT:ep_theme/Configuration/TypoScript/setup.typoscript'
|