WordPress Site Broke After an Update? Here's What Happened and How to Fix It
What you're seeing
- A white or blank screen, or a "There has been a critical error on this website" message, appearing right after an update finished
- A specific feature stopped working, such as a contact form, slider, checkout, or booking widget
- The layout is broken, misaligned, or unstyled, while the content itself is still there
- You can reach the front end but the wp-admin dashboard errors out, or vice versa
- Everyone else sees the broken version but you see the old one, or the reverse (a caching mismatch)
What causes it
A plugin conflicts with another plugin or your theme
The updated plugin changed how it loads scripts, hooks, or data, and another plugin or your theme expected the old behavior. Two plugins fighting over the same resource is the single most common cause of a post-update break. The site was fine until the new version shifted that timing.
The update needs a newer (or different) PHP version than your host runs
Modern plugin and core releases often require a recent PHP version, and code that worked on an older one can throw a fatal error after the update. The reverse also happens: an update uses syntax your host's older PHP can't parse. The version mismatch, not the plugin itself, is the real fault.
Deprecated code or a removed function
An update may remove or deprecate a function that your theme or another plugin still calls. When that call fails, you get a fatal error or a broken feature. This is common with older custom themes and plugins that haven't been maintained alongside WordPress core.
A broken or half-finished auto-update
Auto-updates can fail mid-process, leaving files partially written or a plugin out of sync with its database changes. The result is a fatal error or a feature that silently stops working, with no warning that the update didn't fully complete. Because it ran on its own, you may not even know which update caused it.
Cache showing a stale or mismatched version
Page caching, object caching, or a CDN can keep serving old files while the database expects the new ones, which produces broken layouts or missing functionality. Sometimes the update is fine and only the cache is wrong. Clearing every cache layer is the first thing to rule out.
A theme update overwrote your customizations
If custom code was added directly to a theme rather than a child theme, updating that theme wipes those changes. The site doesn't error, but your design, layout tweaks, or custom functions simply vanish. The fix is restoring those changes into a child theme so the next update can't erase them.
How to fix it yourself
If you're comfortable in wp-admin and you have a backup, here are the safe first steps to try, in order.
Take a backup before you touch anything
Even though the site is broken, back up the current files and database first so you can't make things worse. If you can't reach wp-admin, your host's backup tool or file manager can usually do this. Never start undoing an update without a restore point in hand.
Deactivate the plugin you updated most recently
If you know which plugin updated just before the break, deactivate it from the Plugins screen and check whether the site recovers. If you can't reach wp-admin, rename that plugin's folder in /wp-content/plugins via FTP or your host's file manager to force it off. If the site comes back, you've found the culprit.
Isolate the conflict by deactivating plugins
If the recent plugin wasn't it, deactivate all plugins, confirm the site works, then reactivate them one at a time until it breaks again. The plugin that breaks it is your conflict. This is tedious but it reliably points to the exact pair of plugins or the plugin-versus-theme clash.
Clear every cache layer
Purge your caching plugin, any server or object cache, and your CDN, then hard-refresh in a private browser window. A surprising number of "broken after update" reports are just a stale cache serving old files against a new database. Rule this out before assuming the code is at fault.
Restore from your last good backup
If you can't isolate the cause, roll back to the backup taken before the update. Be aware this also reverts any content, orders, or form entries created since that backup, so on an active site you can lose recent data. Restoring undoes the symptom but not the underlying incompatibility, so the same update can break it again next time.
Rather not risk it? We'll fix it for you.
If the DIY steps don't recover the site, or you'd rather not risk an active business site, that's where we come in. We back up first, identify exactly which update caused the conflict, roll back the offending piece, and resolve the underlying incompatibility so the fix holds, then we document every change we made so you have a record. Quick Fix is $129, backed by our money-back guarantee, and we'll set up version pinning and staged updates so a future update is tested before it ever touches your live site.