#101408Fluid debug output is displayed on page even if adminpanel not enabled / not logged in
Description
This probably was reported before, but was then fixed and has now reappeared: https://forge.typo3.org/issues/85087
I usually don’t use Fluid debug output in adminpanel and usually don’t enable it on production but I did that recently by accident.
Several days later I loaded a page, the debug output was displayed, the admin panel was not even activated.
What made matters worse, the debug output was also displayed if not logged in the BE (using different browser).
versions
- reproduced in v11, did not check newer versions yet.
Reproduce
1. Flush all cache (including system cache)
2. Enable admin panel
3. Activate checkbox “Fluid debug output“
4. Load page: debug output is displayed) (ok)
5. deactivate adminpanel (via the toggle)
6. load page again: debug output is displayed (unexpected)
7. load page in different browser (not logged in): debug output is displayed (bad)
8. Deactivate the checkbox “Fluid debug output“
9. refresh page CTRL-SHIFT-r (or flush cache in adminpanel): debug output still displayed
finally, flush cache
vendor/bin/typo3 cache:flush
Is now ok
Suggestion
I think this should be changed (at least in production context)
- the debug output should not be saved
- or better: not possible to enable “Fluid debug” checkbox in production context
Screenshot
Reviews 2
Related issues 3
Files 1
History 915
-
Sybille Peters changed Related to #85087 <span data-processor="relativetime" data-value="2023-07-21T14:46:17+00:00" > 07/21/23, 14:46 </span>
-
Sybille Peters changed Related to #86675 <span data-processor="relativetime" data-value="2023-07-21T14:47:07+00:00" > 07/21/23, 14:47 </span>
-
Sybille Peters changed subject
Fluid debug output is displayed on page even if adminpanel not enabled (debug output is persisted to page cache)Fluid debug output is displayed on page even if adminpanel not enabled / not logged in <span data-processor="relativetime" data-value="2023-07-21T14:48:51+00:00" > 07/21/23, 14:48 </span> -
Torben Hansen commented and changed status
NewAccepted <span data-processor="relativetime" data-value="2023-11-28T08:13:31+00:00" > 11/28/23, 08:13 </span> -
Gabriel Kaufmann TYPOworx GmbH | NewMedia commented <span data-processor="relativetime" data-value="2025-02-13T11:02:00+00:00" > 02/13/25, 11:02 </span>
This bug is till present with TYPO3 v12 as we recently noticed (on a production website).
I think there are two approaches to get this finally fixed:
1. We need to check if BE-User is logged in and Admin-Panel is present.
If yes – we must make shure the caching is disabled (there already is a cache-toggle checkbox for Admin-Panel)2. We could implement Fluid Compiler around debug statements making shure these statements are written with condition in fluid code-cache to avoid cached output for non-admins/be-users.
-
Webadmin no-lastname-given commented and changed TYPO3 Version
1113 <span data-processor="relativetime" data-value="2025-12-08T08:01:41+00:00" > 12/08/25, 08:01 </span>We can confirm that this is still a problem in v13. As soon as an editor unknowingly activates the checkbox, the red boxes appear in the frontend and remain until the entire cache has been cleared.
To make matters worse, hiding the option doesn’t work, see #102090
-
Webadmin no-lastname-given changed Related to #102090 <span data-processor="relativetime" data-value="2025-12-08T08:01:59+00:00" > 12/08/25, 08:01 </span>
-
Gerrit Code Review pushed patch set 1 for main to change 96398 status
AcceptedUnder Review <span data-processor="relativetime" data-value="2026-10-06T06:45:34+00:00" > 10/06/26, 06:45 </span> -
Gerrit Code Review pushed patch set 2 for main to change 96398 <span data-processor="relativetime" data-value="2026-10-10T09:11:02+00:00" > 10/10/26, 09:11 </span>
-
Gerrit Code Review pushed patch set 1 for 14.3 to change 96834 <span data-processor="relativetime" data-value="2026-10-18T17:00:11+00:00" > 10/18/26, 17:00 </span>
-
Georg Ringer commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2026-10-18T17:05:16+00:00" > 10/18/26, 17:05 </span>Applied in changeset commit:229450e0a27168be6cdf8d8402feafc1e3accad1.
-
Gerrit Code Review pushed patch set 2 for 14.3 to change 96834 status
ResolvedUnder Review <span data-processor="relativetime" data-value="2026-10-19T15:51:46+00:00" > 10/19/26, 15:51 </span> -
Gerrit Code Review pushed patch set 3 for 14.3 to change 96834 <span data-processor="relativetime" data-value="2026-10-19T16:09:33+00:00" > 10/19/26, 16:09 </span>
-
Gerrit Code Review pushed patch set 4 for 14.3 to change 96834 <span data-processor="relativetime" data-value="2026-10-19T17:43:39+00:00" > 10/19/26, 17:43 </span>
-
Georg Ringer commented and changed status
Under ReviewResolved <span data-processor="relativetime" data-value="2026-10-19T20:50:16+00:00" > 10/19/26, 20:50 </span>Applied in changeset commit:92a1082ef719a40802bebdaa23033afc237f2412.
I can confirm the issue. As soon as the layouts/templates/partials are rendered once through admin tool, they are cached. The cached items also contain information about the
debugstate, which might result in non cached pages will include debug information when requested by regular users.