[wp-trac] [WordPress Trac] #44458: Catch WSODs and provide a means for recovery for end users

[WordPress Trac]

#44458: Catch WSODs and provide a means for recovery for end users
-------------------------------------------------+-------------------------
 Reporter:  schlessera                           |       Owner:  (none)
     Type:  task (blessed)                       |      Status:  new
 Priority:  normal                               |   Milestone:  5.0
Component:  Bootstrap/Load                       |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-unit-tests needs-    |     Focuses:  multisite
  testing                                        |
-------------------------------------------------+-------------------------

Comment (by schlessera):

 @ibenic Parse errors happen when the PHP file is parsed so that the
 functions and methods can be declared.

 For an action/filter to work, the function/method it uses as a callback
 needs to be declared before the action/filter is triggered, and this is
 usually done right when the plugin is being loaded (but not always). So
 parse errors should in almost all cases be detected during the plugin
 loading stage.

 We're not currently doing anything with runtime errors. The main issue
 with runtime errors is that they are neither reliably broken (it could
 just have been a temporary hiccup) nor can they be properly traced back to
 their root cause (as the bug is often contained in one plugin, but another
 plugin then trips over the previous plugin's bad data and throws a fatal
 error).

 We'll have to discuss in more detail what types of errors we want to catch
 and how we want to handle them. For now, I opted to go with the safest
 route to test the mechanism.

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