Plugin and theme updates
WordPress Broken After a Plugin Update
The last plugin you clicked is the first suspect, not always the only one. Rollback is a tool, not a strategy. Staging and a backup come first.
Direct answer
A plugin update can fatal the PHP process, enqueue a broken script that kills checkout, or change a database schema the theme still assumes. White screen is a fatal. “Update succeeded” with a broken layout is often CSS/JS or a removed hook. Treat them differently.
How to diagnose without making it worse
- If you have a host snapshot from before the update, that is the cleanest rollback. Do not run more updates on the broken production site.
- If you see the critical-error screen, follow the critical error guide. Get the file name from the log before you disable every plugin.
- If the admin still loads, open the plugin list. Use a rollback plugin only on staging first. Rolling back on a live Woo store can leave a half-migrated table.
- Compare PHP version and the plugin’s readme. Many “broke after update” cases are “host moved to PHP 8.2 the same week.”
- For checkout or cart only, check whether a cache plugin started caching those URLs after the update. See checkout not working.
What not to do
- Do not click Update on the remaining plugins “to get current.”
- Do not delete the plugin folder if it owns custom tables you still need.
- Do not disable page cache globally as a first step on a busy store. Exclude cart and checkout instead.
Simple fixes from $79. Critical Error Rescue from $149. Final quote after diagnosis.
Care plans exist so updates are tested before production.