#110757Using the admin panel breaks fluid
Description
I frequently used this pattern to extend the default f-namespace:
$GLOBALS['TYPO3_CONF_VARS']['SYS']['fluid']['namespaces']['f'] ??= [];
$GLOBALS['TYPO3_CONF_VARS']['SYS']['fluid']['namespaces']['f'][] = 'Vendor\\Package\\ViewHelpers';
Pretty straight-forward and even recommended (when i integrated that).
As soon, as you use the admin panel to simulate a different date or something like that (i did not test much more, too angry at the moment), typo3 won’t find the fluid-core-viewhelpers anymore and start triggering warnings all over the place. This bug is so annoiying and it does not make any sense from my perspective as a developer. Why does fluid do different things, if the admin panel is enabled/active? Why should i bother using the admin panel, if it has side-effects?
This effectively makes the admin panel a bad thing for me becuase i do not know, if code will behave the same depending on this flag.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
History 3
-
Georg Ringer commented and changed status
NewNeeds Feedback 09/22/26, 17:13 -
Philipp Wrann commented and changed target version 10/09/26, 07:55
I could find the task where i encountered the problem but i could not trigger it again, sorry. We can only close this, if it happens again, i am gonna try to add all required steps to reproduce.
-
Georg Ringer changed status
Needs FeedbackClosed 10/09/26, 08:04
Hey,
thanks for your issue. Can you provide a stack trace or a simple way to reproduce that. What also would be interesting if this also breaks in 14 LTS as the registration mechanism changed (see #108524)