#108811TypoScript Module shows TypoScript from disabled SysTemplate (hidden=1) as active and valid
Description
When viewing Active TypoScript in the backend TypoScript module, TypoScript originating from a disabled SysTemplate record (hidden = 1) is still shown as active and valid.
Although the disabled SysTemplate is correctly ignored in the frontend rendering, the backend TypoScript module continues to display its constants and setup as if they were active. This leads to an inconsistency between backend visualization and frontend behavior.
Steps to Reproduce
- Create a root page SysTemplate.
- Define a constant in the template, e.g.:
Constants
plugin.tx_myplugin.settings.example = 1
Setup
plugin.tx_myplugin.settings.example = {$plugin.tx_myplugin.settings.example}
- Save the SysTemplate and verify in the frontend that the value is applied.
- Disable the SysTemplate (hidden = 1).
- Open Backend → TypoScript module → Active TypoScript.
- The TypoScript module still shows plugin.tx_myplugin.settings.example = 1 as an active and valid TypoScript value.
- The module gives no indication that the value originates from a disabled SysTemplate.
- This contradicts the actual frontend behavior, where the TypoScript is no longer applied. Reload the frontend → the TypoScript from the template is no longer applied (correct behavior).
- TypoScript originating from disabled SysTemplate records (hidden = 1) should not be shown as active in the TypoScript backend module.
- Alternatively, such TypoScript should be clearly marked as coming from a disabled template.
- Backend visualization should accurately reflect the TypoScript evaluation used for frontend rendering.
*Impact*
This behavior is misleading and can cause significant confusion during debugging:
- Editors or developers may assume that a SysTemplate or TypoScript configuration is still active because it appears valid in the backend module.
- In reality, the frontend ignores the configuration entirely.
- This results in unnecessary troubleshooting and incorrect assumptions about TypoScript inheritance or overrides.
- Frontend behavior appears correct.
- The issue is limited to backend visualization in the TypoScript module.
- No workaround is known other than manually checking the enabled/disabled state of all involved SysTemplates.