Attention
TYPO3 v10 has reached end-of-life as of April 30th 2023 and is no longer being maintained. Use the version switcher on the top left of this page to select documentation for a supported version of TYPO3.
Need more time before upgrading? You can purchase Extended Long Term Support (ELTS) for TYPO3 v10 here: TYPO3 ELTS.
Site Settings¶
It is possible to define a settings
block in a site's config.yml
which
can be accessed both in backend and frontend via the site object.
Additionally, these settings are available as "constants" in both TSConfig and TypoScript templates making it possible to configure for example site-wide storage PIDs which can be used in both frontend and backend.
Adding Site Settings¶
Add a settings
block to the config.yml
:
settings:
categoryPid: 658
styles:
content:
loginform:
pid: 23
Note
This example shows how to fill a constant of EXT:felogin via site settings (styles.content.loginform.pid
) and
configures a custom categoryPid
.
Accessing Site Settings in Page TSConfig or TypoScript¶
# store tx_ext_data records on the given storage page by default (e.g. through IRRE)
TCAdefaults.tx_ext_data.pid = {$categoryPid}
# load category selection for plugin from out dedicated storage page
TCEFORM.tt_content.pi_flexform.ext_pi1.sDEF.categories.PAGE_TSCONFIG_ID = {$categoryPid}
Note
The TypoScript constants are evaluated in this order:
Global
'defaultTypoScript_constants'
Site specific settings from the site configuration
Constants from
sys_template
database records