Issue Bug Closed

#108811TypoScript Module shows TypoScript from disabled SysTemplate (hidden=1) as active and valid

Hendrik Reimers 01/30/26, 11:54 updated 03/31/26, 08:10

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
Reference the constant in setup:
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.
Observed Behavior
  • 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).
Expected 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.
Additional Notes
  • 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.

Reviews 3

History 1019

  1. Garvin Hicking commented <span data-processor="relativetime" data-value="2026-01-30T16:17:17+00:00" > 01/30/26, 16:17 </span>

    Hi Hendrik,

    thanks for taking the time for this helpful bugreport. I think this came up earlier at some point, but I could not find related issues.

    I’ve created a patch that is actually quite light-weight. Maybe you can try if that fixes it for you as well, or if it has side-effects for you.

    Thanks,
    Garvin

  2. Nikita Hovratov commented <span data-processor="relativetime" data-value="2026-01-30T17:12:18+00:00" > 01/30/26, 17:12 </span>

    Garvin Hicking wrote in #note-2:

    > I think this came up earlier at some point, but I could not find related issues.

    I may have found it, can you check?

  3. Garvin Hicking commented <span data-processor="relativetime" data-value="2026-01-30T17:19:25+00:00" > 01/30/26, 17:19 </span>

    @nikitah nice, exactly! I’ll also check the start/endgime restriction then. “Not today”(tm) though. Thanks!

  4. Garvin Hicking commented <span data-processor="relativetime" data-value="2026-02-05T17:56:55+00:00" > 02/05/26, 17:56 </span>

    Hi @kern23 it would help me a lot to push this forward if you could test and vote on the patch I prepared :-)

  5. Silvio Kranzusch commented <span data-processor="relativetime" data-value="2026-02-06T07:35:04+00:00" > 02/06/26, 07:35 </span>

    I’ve testet the Patch an it looks fine to me.

  6. Garvin Hicking commented <span data-processor="relativetime" data-value="2026-02-08T20:19:24+00:00" > 02/08/26, 20:19 </span>

    If you want/can you could log into the patch tracker with your TYPO3 account and leave a +1 verified there (code review +1 would help too if you are able to understand the code).

    That would help me to move this patch forward.

  7. Hendrik Reimers commented <span data-processor="relativetime" data-value="2026-02-08T20:31:26+00:00" > 02/08/26, 20:31 </span>

    Sorry for the delay, as Silvio already wrote it works fine for us.
    Thanks for your quick solution and support. Appreciated it.

  8. Garvin Hicking commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-02-09T18:00:09+00:00" > 02/09/26, 18:00 </span>

    Applied in changeset commit:b59827fa4dc8c27eb49cbf53b00ede3c273e0a9a.