Troubleshooting
Website Broken After an Update? Here's How to Fix It
You updated a plugin, theme, or CMS core and now your site is broken. Maybe it's a white screen. Maybe the layout is wrecked. Maybe forms stopped working. Don't panic — this guide covers the most common causes, how to fix each one, and how to prevent it from happening again.
- Step-by-step diagnosis and fix guide
- The 6 most common post-update failures
- How to prevent update breakage automatically
Do this first
Immediate steps when your site breaks after an update
1. Stop — don't apply additional updates
Every additional change makes diagnosis harder. Don't click "update" on other plugins hoping it fixes things. Isolate the problem first.
2. Check if the site is completely down or partially broken
Open your site in a private/incognito browser window (to bypass cache). Is it:
- Completely blank (white screen)? → Likely a PHP fatal error. See the White Screen of Death guide.
- Loads but looks wrong (broken layout, missing styles)? → CSS or theme file issue. Clear your cache first.
- Loads but features don't work (forms, buttons, cart)? → JavaScript or plugin conflict.
- Shows an error message? → Read the error. It usually tells you exactly what file/function caused the problem.
3. Clear all caches
Before doing anything else, clear: your browser cache, your caching plugin (WP Super Cache, W3TC, LiteSpeed), your CDN cache (Cloudflare, etc.), and any server-side cache (Redis, Varnish). Many "broken" sites are just serving cached versions of pre-update pages that reference files that no longer exist.
11
Detection rules
23+
Stack playbooks
Free
1 site
6 common causes
Why websites break after updates
Plugin conflict
CriticalTwo plugins use the same function name, hook, or library version. After one updates, the other crashes. The site may show a fatal error, white screen, or partial functionality loss.
Theme incompatibility
CriticalA theme update changes CSS class names, template structure, or JavaScript dependencies. Custom CSS breaks. Child theme overrides stop matching. The layout collapses.
PHP version mismatch
CriticalA plugin update requires PHP 8.1+ but your host runs PHP 7.4. The plugin loads, hits an unsupported syntax, and crashes. Often shows a white screen with no visible error.
Cached old assets
ModerateYour caching plugin or CDN still serves the old version of a JS or CSS file. The HTML references new class names or functions that don't exist in the cached asset. Everything looks broken.
Database migration failure
ModerateA major update (WooCommerce, WordPress core) needs to run a database migration. The migration fails silently or times out. The plugin's frontend expects new data structures that don't exist.
.htaccess corruption
ModerateAn update rewrites your .htaccess file with bad rules. Redirects loop, URLs return 404, or the entire site becomes inaccessible. Common with SEO plugins and permalink changes.
Fixes
How to fix each cause
Plugin conflict
Deactivate all plugins via wp-admin (if accessible) or by renaming wp-content/plugins to wp-content/plugins-disabled via FTP/SFTP. If the site works, reactivate plugins one by one until you find the conflict. Then check if there's a compatibility patch or contact the plugin developer.
Theme incompatibility
Switch to a default theme (Twenty Twenty-Four) via wp-admin or by renaming your theme folder via FTP. If the site works with the default theme, the issue is in your theme. Check the theme changelog for breaking changes, update your child theme, or roll back the theme update.
PHP version mismatch
Check your hosting panel (cPanel, Plesk, or the host's custom dashboard) for the PHP version setting. Check the plugin's requirements on wordpress.org. Either upgrade your PHP version (recommended) or roll back the plugin to its previous version via FTP.
Cached old assets
Clear every cache layer: browser → caching plugin → CDN → server cache. If using Cloudflare, do a full purge (not just the homepage). If using a caching plugin, delete the cache directory entirely. Then reload in an incognito window.
Database migration failure
Go to wp-admin. Major plugins like WooCommerce often show a "Update database" prompt. Run it. If it times out, increase your PHP max_execution_time or run it via WP-CLI: wp wc update.
.htaccess corruption
Rename .htaccess to .htaccess-broken via FTP. Go to wp-admin → Settings → Permalinks → click "Save Changes" (this regenerates .htaccess). If you can't access wp-admin, create a minimal .htaccess with the default WordPress rules.
Never again
How to prevent update breakage
Post-update monitoring
Set up website monitoring that validates every asset on your site after updates. When a plugin update breaks a JS file, you get an alert with the exact broken resource — not a customer complaint hours later.
Test on staging first
Clone your site to a staging environment and test updates there before applying to production. Most managed WordPress hosts (WP Engine, Kinsta, SiteGround) offer one-click staging.
Keep backups
Before any update: take a full backup (files + database). Use your host's backup system or a plugin like UpdraftPlus. If an update breaks everything, you can restore in minutes.
Update one thing at a time
Update plugins individually, not in bulk. If something breaks, you know exactly which update caused it. Bulk updates make debugging a nightmare.
Post-update FAQ
For minor/security updates: yes, enable auto-updates. For major version updates: no. Major updates can change functionality, remove features, or introduce incompatibilities. Test major updates on staging first, then apply to production with monitoring active.
Connect via FTP/SFTP. Rename the wp-content/plugins folder to disable all plugins. If the site loads, rename it back and deactivate plugins one by one. If it's a theme issue, rename your theme folder in wp-content/themes to force the default theme.
If you updated multiple plugins at once: deactivate all, then reactivate one by one. The site will break again when you activate the problematic plugin. If you updated one plugin: that's your culprit. Roll it back via FTP by replacing the plugin folder with the previous version from wordpress.org.
Monitoring can't prevent the breakage, but it catches it within minutes instead of hours. Sitewatch validates every JS, CSS, and image file on your pages. When a plugin update breaks a script, you know immediately — not when a customer emails you.
Catch update breakage before your users do
Free plan available. Monitor your WordPress site in 60 seconds.