[wp-trac] [WordPress Trac] #64155: Add stack trace to failed plugin update error notifications

[WordPress Trac]

#64155: Add stack trace to failed plugin update error notifications
-------------------------------------+-------------------------------------
 Reporter:  tlloancy                 |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Upgrade/Install          |     Version:  6.8.3
 Severity:  normal                   |  Resolution:
 Keywords:  needs-testing needs-     |     Focuses:  administration, php-
  patch                              |  compatibility
-------------------------------------+-------------------------------------

Comment (by tlloancy):

 @afragen: Thanks for the plugin — I’ll test it on a **staging copy** of
 https://yspania.com or https://gatasya-yoga.com to capture the next
 failure **without risking production**.

 But **this is exactly my point**:
 - Admins **shouldn’t need a custom debug plugin** to understand *why* an
 auto-update failed.
 - `WP_DEBUG_LOG` is on → **debug.log stays empty**.
 - Failure email → **zero details**.
 - Manual update works, auto-retry works later → **but no trace of the root
 cause**.

 Your tool is great for **developers**, but **core should log stack traces
 by default** in failure emails/logs — so **any admin** can diagnose issues
 like:
 - Silent fatal in a plugin (`wp_cache_flush()` killing cron)
 - Timeout / memory
 - Filesystem lock

 And maybe even they can help themselves after that with plugins such as WP
 Control for instance.

 I’ll run your plugin on staging and share results if a failure occurs.
 But **this ticket is about making WordPress *self-diagnosing* for all
 users**, not just those who can install debug tools.

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