Feature #91080
closed
Populate site settings to TypoScript constants
Added by Markus Klein over 4 years ago.
Updated over 4 years ago.
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.
- Related to Task #88564: Drop PageTS "TSFE.constants" functionality added
- Related to Feature #89102: Read settings for sites from <config>/sites/<siteIdentifier> added
- Status changed from Accepted to Under Review
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to Closed
- Related to Bug #92528: TypoScript site constants not always populated added
- Related to Bug #93746: Conditions in Page TSconfig using site settings trigger errors when page with UID 0 is selected in BE added
- Related to Feature #93875: Populate site settings depending on language to TypoScript constants added
- Related to Bug #94150: Constants in Page TsConfig with multiple sites, caching problem added
- Related to Bug #97172: TemplateAnalyzer does not show constants populated from site settings for nested sites added
- Related to Bug #102357: PageTsConfig: site settings / constants are not substituted in FormEngine added
Also available in: Atom
PDF