[wp-trac] [WordPress Trac] #64364: There has been a critical error on this website.

[WordPress Trac]

#64364: There has been a critical error on this website.
--------------------------+------------------------------
 Reporter:  dandavince    |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by johnbillion):

 * version:  6.9 =>


Comment:

 I agree that more often than not, it's frustrating seeing this critical
 error screen without it including any technical information about the
 error. It adds extra steps to the debugging process.

 I would be in favour of including the error message and stack trace but
 hiding it behind a toggle (eg using a `<details>` element so functional
 JavaScript isn't required). The idea being that a regular visitor to the
 site should not see technical information unless they click through to it,
 and the site owner can still access the info when they need it.

 The main concern is whether it's undesirable to expose technical details
 when `WP_DEBUG` is not set to true. This is the reason the underlying
 error message is only shown on the critical error screen when `WP_DEBUG`
 is true.

 I think this deserves some more discussion. Needs to take into account
 recovery mode too.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64364#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform