Death to WSOD: Output information about what caused a fatal error

Created on 16 May 2011, about 13 years ago
Updated 26 June 2023, about 1 year ago

We have a whole culture of training around resolving the WSOD. But why? It seems that we can output some simple information that would make it clear what has happened.

This is a proof-of-concept patch that demonstrates what can be done. It is deliberately simple; it attempts to not do anything that would cause more trouble or complexity. We could do more:
* A stack trace
* Fancier formatting
* A link for more help
* Output to watchdog().

Here's what the user would see in a simple fatal:

This is inspired by Marcelius 22-Jan-2009 01:41 comment on set_error_handler() and with DRUPAL_ROOT sanitization code borrowed from sun's excellent πŸ“Œ Add backtrace to all errors RTBC .

✨ Feature request
Status

Closed: duplicate

Version

11.0 πŸ”₯

Component
BaseΒ  β†’

Last updated 6 minutes ago

Created by

πŸ‡ΊπŸ‡ΈUnited States rfay Palisade, CO, USA

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.69.0 2024