#91080Populate site settings to TypoScript constants
Description
In older TYPO3 versions it is possible to define constants for the Template via page TSconfig.
This possibility has been removed with #88564.
A similar functionality, based on site configuration, has been proposed with #89107 and #89102, but had to be reverted and delayed.
The re-implementation shall now provide settings defined in the site configuration (e.g. storage pids and similar things) as constants in TypoScript.
In another feature, these settings shall also be provided “as constants” for TSconfig.
This ultimately completes the concept of having a central place of FE/BE independent configuration, which can be used in FE (Template) and BE (TSconfig) specific configuration.
Reviews 2
Related issues 11
- Task #88564Drop PageTS "TSFE.constants" functionality
- Feature #89102Read settings for sites from <config>/sites/<siteIdentifier>
- Epic #89107Introduce Site Settings
- Feature #91081Populate site settings to TSconfig
- Bug #92528TypoScript site constants not always populated
- Bug #93746Conditions in Page TSconfig using site settings trigger errors when page with UID 0 is selected in BE
- Feature #93875Populate site settings depending on language to TypoScript constants
- Bug #94150Constants in Page TsConfig with multiple sites, caching problem
- Bug #97172TemplateAnalyzer does not show constants populated from site settings for nested sites
- Feature #97816New TypoScript parser
- Bug #102357PageTsConfig: site settings / constants are not substituted in FormEngine