You clicked “Update”, and now something is wrong: a page layout has collapsed, the contact form won’t submit, or visitors see an error instead of your homepage. It’s stressful — but it’s also one of the most common and most recoverable WordPress problems.
The key is to work in order and change one thing at a time.
Work out what exactly is broken
Before touching anything, write down what you see and when it started:
- Is the whole site down, or only certain pages or features?
- Is the admin dashboard still accessible?
- Which updates were applied, and in what order?
- Is there an error message? Copy it exactly.
If visitors see “There has been a critical error on this website”, follow our separate guide to the WordPress critical error — it covers recovery mode and debug logs.
Protect what you have
If the site takes orders or enquiries, note that anything created since your last backup would be lost by a full restore. Take a fresh backup of the current state — even broken — so you can always return to this point while you investigate.
Find the suspect
The most recent update is the most likely cause, but not always the only one. A few ways to narrow it down:
- Check the error log. PHP errors often name the file — and the plugin folder — where the problem occurred.
- Deactivate the most recently updated plugin and check whether the problem disappears.
- Switch temporarily to a default theme if the problem is visual and the theme was updated.
# Deactivate one suspect plugin
$ wp plugin deactivate plugin-folder-name
# Check recent PHP errors (path depends on your setup)
$ tail -n 50 wp-content/debug.logRoll back the update — or restore
Once you know the cause, you have two main options:
- Roll back one component — reinstall the previous version of the plugin or theme. This keeps all other changes, including new orders and entries. See how to roll back a plugin update.
- Restore the pre-update backup — fastest when several things are broken, but it undoes everything since the backup.
Report the conflict and plan the retry
A rollback is a pause, not a fix. Check the plugin’s support forum or changelog — others may have reported the same conflict and a fix may already be on the way. Plan to retry the update on a staging site once it’s resolved, so the problem doesn’t return unnoticed.
How to avoid the next one
Most broken updates are preventable with a routine: a fresh backup before updating, updates in small groups, major releases tested on staging, and a quick check of key pages and forms straight afterwards. That is exactly the routine behind our safe update process — and in our care plans, fixing a problem caused by an update we applied is part of maintenance.
Frequently asked questions
Why does WordPress break after an update?
Usually because of a conflict: a plugin or theme that isn’t compatible with the new version of WordPress, another plugin or the server’s PHP version. Less often, an update fails halfway and leaves files incomplete.
Should I restore a backup straight away?
Not necessarily. A full restore also undoes anything that changed since the backup — new orders, form entries, content. If you can identify the one update that caused the problem, rolling back that update is often safer.
How do I know which plugin caused the problem?
Start with what changed most recently, check the error log, and deactivate suspects one at a time — ideally on a staging copy. The error message often names the plugin’s folder.
How can I prevent this next time?
Take a fresh backup before updating, update in small groups, test on staging for major releases, and check key pages and forms straight afterwards.
