Key takeaways
- Stop updating, and work out exactly what changed: a plugin, the theme, WordPress itself or the server’s PHP version.
- A “critical error” usually means WordPress has emailed the site’s admin address a recovery mode link. Use it to pause the faulty plugin.
- Roll back the one plugin or theme that broke things. Restore a full backup only when several things changed or the database was updated.
- WordPress now rolls back some failed automatic plugin updates by itself, but it can’t spot a broken layout, form or checkout.
If a WordPress update broke your site, don’t keep clicking “update” or start deleting things. First find out what changed. Then use recovery mode to get back into the dashboard, roll back the plugin or theme that caused the fault, or restore the backup taken just before the update.
What changed when the site broke?
Updates break sites when new code clashes with something already there. Before you fix anything, write down:
- the time the problem started
- which items were updated (check Dashboard, then Updates, or the email WordPress sends after automatic updates, as WordPress.org explains)
- whether your host changed the PHP version recently
- what’s broken: the whole site, the admin area, or one feature such as a form or checkout
That list tells you where to look. If one plugin updated, it’s the prime suspect. If ten things updated at once, you may need a backup.
What does “There has been a critical error on this website” mean?
It means PHP hit a fatal error and WordPress stopped loading the page. Since WordPress 5.2, a feature called recovery mode catches these errors. It shows visitors a short message and emails the site’s admin address with details and a special link (WordPress Core).
Clicking that link and logging in puts you into recovery mode. The broken plugin or theme is paused for you only, so visitors still see the error until you fix it. The dashboard tells you which extension failed and lets you deactivate it.
Can’t find the email? Check spam, and check which address is set under Settings, then General. It’s often an old staff member or the developer who built the site.
How do I roll back a plugin update?
- Get into the dashboard. Use the recovery mode link, or, if you can’t, open your hosting file manager and rename the plugin’s folder in wp-content/plugins (for example, add “-off” to the end). WordPress then deactivates it.
- Download the previous version. For free plugins, the plugin’s WordPress.org page has an “Advanced View” with a list of earlier versions. For premium plugins, check your account with the plugin’s seller.
- Upload it. Go to Plugins, then Add New, then Upload Plugin. WordPress will offer to replace the current version with the one you uploaded.
- Reactivate and test. Check the pages, forms and checkout that were broken.
- Pause updates for that plugin. Turn off auto-updates for it, and check the developer’s support forum before trying the next version.
What if a theme or WordPress core update caused it?
A theme update replaces the theme’s files. If someone edited the theme directly, those changes vanish. When a WordPress theme update lost changes like this, the long-term fix is a child theme.
WordPress core itself rarely causes the fault. More often, an old plugin isn’t ready for the new version. Fix or replace that plugin rather than downgrading WordPress, which leaves you without security fixes.
When should I restore a backup instead?
Restore the whole site when several things updated together, when you can’t tell which one failed, or when an update changed the database. WooCommerce and some page builders run database updates that rolling back the plugin files won’t undo.
Be careful on a shop. Restoring a backup from this morning removes any orders, enquiries or sign-ups since then. Note them down first, or ask your host to restore the files only.
This is where website backups you can restore earn their keep. A backup you have never tested is a hope, not a plan.
Doesn’t WordPress roll back failed updates on its own?
Partly. Since WordPress 6.3, a manual plugin update that fails part-way through restores the previous copy (WordPress Core). WordPress 6.6 added a check after automatic plugin updates. If the update causes a PHP fatal error, WordPress puts back the old version and emails the site admin (WordPress 6.6 Field Guide).
That safety net only catches fatal errors. It won’t notice a broken menu, a contact form that stops sending, or a checkout that fails on mobile. Our guide to WordPress auto updates explains when to switch them on.
How do I stop updates breaking my site again?
- Back up first, every time. WordPress.org recommends backing up your database “always before an upgrade” (WordPress.org).
- Test on a staging copy. A WordPress staging site lets you try updates where customers can’t see them.
- Update in small batches. If something breaks, you’ll know which update did it.
- Check what matters after each round. Home page, contact form, checkout, and any booking or quote tools.
- Read the changelog for major version jumps, such as 4.x to 5.0.
If that sounds like a job you’d rather not own, our safe, tested WordPress updates service does it for you. Compare our website maintenance plans to see which level fits.
Frequently asked questions
Should I turn off all plugins to find the problem?
Only if you can’t tell which update caused it. Deactivating everything can break layouts and settings that depend on those plugins. Start with the plugin that updated most recently. If that doesn’t help, deactivate the rest one at a time, testing after each, until the site works again.
I never got the recovery mode email. What now?
Check your spam folder and confirm which address is set as the site admin email. If you still can’t get in, use your hosting file manager or SFTP to rename the faulty plugin’s folder. WordPress deactivates it, and you can then log in normally and roll it back.
Can I roll back a premium plugin?
Usually, yes. Most premium plugin sellers let you download earlier versions from your account area. If they don’t, restoring a backup taken before the update is the safest option. Then contact the seller’s support with details of the error so they can fix it in the next release.
Is it safe to stay on the old version of a plugin?
Only for a short time. Updates often fix security holes, and 91% of new WordPress vulnerabilities found in 2025 were in plugins (Patchstack). Treat a rollback as a pause, not a permanent fix. Watch for the next release, test it on staging, then update again.
Will restoring a backup lose my recent orders?
It can. A full restore puts the database back to the moment the backup was taken. Any orders, enquiries or new accounts since then disappear. Export or note them first, or ask your host whether they can restore the files only and leave the database alone.
Sources
- Fatal Error Recovery Mode in 5.2, Make WordPress Core, published 16 April 2019, accessed 13 November 2026
- Merge Proposal: Rollback Auto-Update, Make WordPress Core, published 19 April 2024, accessed 13 November 2026
- WordPress 6.6 Field Guide, Make WordPress Core, published 25 June 2024, accessed 13 November 2026
- Plugin and themes auto-updates, WordPress.org Documentation, accessed 13 November 2026
- Backups, WordPress Advanced Administration Handbook, accessed 13 November 2026
- State of WordPress Security in 2026, Patchstack, accessed 13 November 2026