WooCommerce white screen (WSOD) after an update
Quick answer
A blank white screen after a WooCommerce or plugin update is almost always a PHP fatal error from an incompatible plugin, theme, or PHP version. The reliable fix is to roll back the update that caused it: restore from a backup, or disable the offending plugin via FTP/hosting file manager, then re-enable plugins one by one to find the conflict.
Symptoms
- Entire site or wp-admin shows a blank white page
- "There has been a critical error on this website"
- The break started immediately after an update
Common causes
- A plugin or theme incompatible with the new WooCommerce/WordPress version
- PHP version mismatch after an update
- PHP memory limit exhausted
- A corrupted plugin file from a failed update
How to check
- 1.Enable WP_DEBUG or check the server error log for the fatal error line
- 2.Note which update ran immediately before the screen went blank
- 3.Rename the plugins folder via FTP to confirm it's a plugin conflict
How to fix it
1. Restore from backup
The cleanest recovery is rolling back to the pre-update backup. If you have one, restore it and re-test before re-applying updates carefully.
2. Disable the culprit
Via FTP or your host's file manager, rename the offending plugin's folder to deactivate it, then reload the site.
3. Re-enable one by one
Bring plugins back individually to find the exact conflict, and update on staging before production next time.
4. Let auto-heal catch it
On managed WooCommerce sites, Liulum detects the fatal error and can auto-roll-back to the last healthy state (allow-listed, reversible, logged) while alerting you — so downtime is seconds, not hours.
How Liulum helps
Liulum watches this path continuously, tells you in plain English the moment it breaks, and on sites it manages can run a safe, allow-listed, reversible repair automatically — so an outage lasts seconds, not hours.
Protect your storeFrequently asked questions
How do I fix the WordPress white screen of death on WooCommerce?
Identify the update that caused it, then roll back — restore a backup or disable the offending plugin via FTP and re-enable plugins one at a time to find the conflict. Enabling debug mode reveals the exact fatal error.
How do I stop updates from breaking my store?
Test updates on a staging copy first, keep fresh backups, and run a pre-update risk scan. Applying plugin updates straight to a live store is the most common cause of e-commerce outages.
Can Liulum roll back a bad update automatically?
On WooCommerce sites Liulum manages, yes — a fatal error triggers a safe auto-rollback to the last healthy version, every step logged and reversible, with an alert to you. A pre-update risk scan also warns you before a risky update ships.