TypoScript
Changed in version 13.1
Until TYPO3 v13 frontend TypoScript files were kept in
EXT: by convention.
Extensions that need to be backwardly compatible should Support both site sets and TypoScript records.
Newly created extensions and site packages should use a Site set as a TypoScript provider
TypoScript constants should be stored in the file constants.
and TypoScript setup in setup..
Configuration/TypoScript/constants.typoscript
-
- Scope
- extension
- Path (Composer)
- packages/my_extension/Configuration/TypoScript/constants.typoscript
- Path (Classic)
- typo3conf/ext/my_extension/Configuration/TypoScript/constants.typoscript
Configuration/TypoScript/setup.typoscript
-
- Scope
- extension
- Path (Composer)
- packages/my_extension/Configuration/TypoScript/setup.typoscript
- Path (Classic)
- typo3conf/ext/my_extension/Configuration/TypoScript/setup.typoscript
These two files are made available for inclusion in TypoScript records by
Extension in
Configuration/TCA/Overrides/sys_template.php:
<?php
use TYPO3\CMS\Core\Utility\ExtensionManagementUtility;
defined('TYPO3') or die();
ExtensionManagementUtility::addStaticFile(
'my_extension',
'Configuration/TypoScript/',
'Examples TypoScript',
);
It is possible to use subfolders or a differently named folder instead, however, the file names have to stay the same.
Warning
In Sites that don't use Site sets it is possible, though not recommended, to have TypoScript that is always included. See ext_typoscript_constants.typoscript and ext_typoscript_setup.typoscript. These files are not included when a site uses a set.