Strange Extbase Variable Dump "Design" on an Whoops, looks like something went wrong. page
[BUGFIX] Add proper scope for styling of DebugExceptionHandler
The styling of the debug output is "namespaced" with `.exception-page`
to avoid influencing other CSS definitions.
Reviewed-by: Andreas Fernandez <firstname.lastname@example.org>
Tested-by: Andreas Fernandez <email@example.com>
Reviewed-by: Josef Glatz <firstname.lastname@example.org>
Tested-by: Josef Glatz <email@example.com>
Tested-by: TYPO3com <firstname.lastname@example.org>
Reviewed-by: Markus Poerschke <email@example.com>
Tested-by: Markus Poerschke <firstname.lastname@example.org>
Reviewed-by: Georg Ringer <email@example.com>
Tested-by: Georg Ringer <firstname.lastname@example.org>
#3 Updated by Christoph Schwob 8 months ago
Georg Ringer wrote:
thanks for creating the issue!
Is there some custom CSS maybe included?
nope. completely clean v9 instance with a tt_address plugin (this throws the error for the Whoops, looks like something went wrong. page) without any css from this extension.
in the source of the page are are only the inline styles from DebuggerUtility.php and DebugExceptionHandler.php, but no external css files.
(I've also included the TS Template for ext:fluid_styled_content CSS but it's not included in FE on this error page)
#5 Updated by Georg Ringer 8 months ago
Cant reproduce that but having an exception stacktrace AND a debug output at the same page is not a good idea and nothing for in production. I would prefer using a debugger like xdebug or if you are using DebuggerUtility or print, then do a die and it looks better.
can be fixed, low prio