TypoScript module (Site management)
The TypoScript backend module can be used to debug the TypoScript configuration that you provided via your site as described in "Hello world" example in TypoScript or via your site set as described in the Site Package Tutorial, chapter The TypoScript-only version.
Before TYPO3 v13 TypoScript was managed via database records, called "TypoScript records". It is still possible doing this and you will see it in older examples or installations that have been updated and not refactored. This module can also be used to manage TypoScript records. Its usage is described in TypoScript Reference, chapter TypoScript backend module.
In the context of this guide we concentrate on the new way of providing TypoScript via the site only.
The TypoScript module consists of the following submodules. You can switch them in the docheader:
Switch between the TypoScript submodules in
TypoScript Overview
Global overview of all pages with active TypoScript definitions (TypoScript records and site sets). Useful if you have more then one site or more then one TypoScript record in one site.
Constant Editor
Before site settings were introduced with TYPO3 13, TypoScript constants where used to define values once and reuse them across TypoScript definitions.
Constants can still be used for backward compatibility reasons but the Constant Editor is not available if you are using site sets. Other then site settings, TypoScript constants are only available within TypoScript.
It is therefore recommended to always use site settings.
Edit TypoScript record
Only available if TypoScript records are being used. Can be used to edit those records. As we manage TypoScript within the site in this Guide it is out of scope of this Guide. Its usage is described in the TypoScript reference, chapter Submodule "Edit TypoScript Record".
Active TypoScript
This module can be used to debug the active TypoScript. During loading and pre compiling TypoScript configuration can override or unset definitions made in another file.
How exactly this happens depends on things like dependencies between the used site sets.
For example if a site set in your site package configures:
page.20 = TEXT
page.20.value = AppleAnd the set of another extensions configures:
page.20 = TEXT
page.20.value = BananaIt depends on how these sets are loaded weather the page. ends up
being set to "Banana" or "Apple".
If the site set of our site package depends on the Banana set, the SitePackage set overrides the Banana set and the Active TypoScript submodule will show you the value "Apple" while it never mentions Banana.
This module therefore shows you the compiled version of the TypoScript.
The module can also be used to simulate what happens if certain TypoScript Conditions are being met or how site settings / TypoScript constants are replaced.
Chapter Debug the TypoScript in the backend module "Active TypoScript" demonstrates the usage of this module in a concrete example.
Included TypoScript
This submodule is helpful in debugging in which order TypoScript files were included and @import statements were resolved.
If the "Banana" from the example in Active TypoScript was overridden, you can use this module to find out where it might have been overridden.
This module is also described in the TypoScript reference, chapter Submodule "Included TypoScript".