Preserve WP-CLI Error Logs in SafeUpdates for Better Troubleshooting
I'm requesting an enhancement to the SafeUpdates feature to preserve detailed WP-CLI error messages after the staging environment is cleaned up.
Current Issue:
When SafeUpdates fails (particularly with premium plugins showing SU-103 errors), the detailed WP-CLI error output is lost when the temporary staging environment is destroyed. This makes troubleshooting nearly impossible, as we only get generic error codes.
Requested Feature:
Please add the ability to capture and store the complete WP-CLI error output from failed updates, making it accessible in the SafeUpdates history or logs section.
Business Impact:
Without detailed error messages, SafeUpdates has limited value for sites with premium plugins, as we can't identify the root cause of failures or work with plugin developers to resolve compatibility issues.
Expected Outcome:
Users should be able to access specific WP-CLI error messages to properly troubleshoot failed updates and improve the overall reliability of the SafeUpdates feature.
Shannon Little
shared this idea