“There has been a critical error on this website”: how to recover after an update

A white screen or “critical error” right after an update is scary but usually quick to fix. Find the plugin that broke, recover safely, and stop it happening again.

You clicked “update all”, or an auto-update ran overnight, and now the site says “There has been a critical error on this website.” Maybe the cart is blank, or wp-admin won’t load. Deep breath: in most cases one plugin or theme is at fault, and WordPress has already told you which one.

New to fixing things yourself? Read the 10 rules we follow before touching a live store first.

1. Check your email first

When WordPress hits a fatal error, it emails the site’s admin address with the subject “Your Site is Experiencing a Technical Issue.” That email names the plugin or theme that crashed and includes a special recovery-mode login link.

  1. Find the email (check spam too).
  2. Click the recovery-mode link and log in.
  3. Deactivate only the plugin or theme it names.
  4. Check the site is back, then look for an update or an older version of that plugin.

2. If you can reach wp-admin

Go to WooCommerce → Status → Logs and open the fatal-errors log for the time the site broke. It names the file and plugin that failed.

3. Use your host’s restore

Most hosts keep daily backups with a one-click restore. Restoring files only to before the update is usually safe. Be careful with database restores: see the warning below.

4. Check the PHP version

Go to Tools → Site Health → Info and open the Server section to see your PHP version. Very old and very new PHP versions both cause crashes with some plugins. Ask your host before changing it.

5. Look for retired plugins

Go to Plugins → Installed Plugins and look for plugins that haven’t been updated in years or have been replaced by an official version. Old checkout and payment plugins often crash on newer WooCommerce.

What we usually find

  • Two extensions that stopped getting along after one of them updated
  • A parent theme updated without its child theme
  • A half-finished update that left a plugin’s files incomplete
  • A plugin running out of memory on a small hosting plan
  • Occasionally a bug in a new WooCommerce release, fixed by rolling back until the patch arrives

Stop it happening again

  • Turn off auto-updates for WooCommerce, payment, subscription and theme plugins.
  • Update one plugin at a time and check the shop and checkout after each.
  • If your host offers staging, update there first.

Stop and get help if

  • wp-admin won’t load at all. Renaming plugin folders in your host’s file manager works, but it’s easy to make things worse.
  • Your host offers to roll back the database. Every order since that backup will be lost.
  • The site was “repaired” by a database tool and orders now look wrong.