WordPress Plugin Update Broke the Site
Your site or a key feature stopped working right after updating WordPress, a plugin, or your theme — the timing is your best clue, and most of these fixes are reversible.
Common signs of this issue
- The site looked fine, then broke immediately after running updates.
- A specific feature — form, slider, checkout, booking, layout — stopped working while the rest survived.
- You see an error message, a broken layout, a white screen, or the "critical error" notice.
- The admin shows warnings about an incompatible plugin or a PHP error.
- Nobody ran updates, but the site broke overnight — auto-updates count as updates too; check your email for update notices.
Safe checks you can do yourself
None of these require sharing passwords with anyone.
- Write down exactly what updated and when — from your email notifications or the admin's Updates screen. On a multi-update day, the list of what changed is the suspect lineup.
- Confirm you can still reach
/wp-admin. If yes, nearly every fix below is doable from the dashboard, reversibly. If no, see the critical-error and white-screen guides, which cover locked-out recovery. - Check for a recent backup (host or plugin) before changing anything — knowing your restore point exists makes every next step safer.
- Deactivate the most recently updated plugin, re-test the site, reactivate, and move to the next. One at a time, with a test between — tedious, reversible, and it isolates the culprit in most cases.
- Hard-refresh (Ctrl+F5 / Cmd+Shift+R) and clear any caching plugin between tests — stale caches routinely make a fixed site still look broken, or a broken site look intermittently fine.
- Check whether your theme updated too — theme/plugin mismatches after simultaneous updates are common, and briefly switching to a default theme (Twenty Twenty-Four) is a clean test.
- Once the culprit plugin is identified, check its page on wordpress.org — the support forum and reviews will usually show other users hit by the same broken release, often with the developer's fix timeline.
What this usually means
Two pieces of software stopped getting along: a plugin release that hasn't caught up with a WordPress or PHP change, or a plugin and theme that now conflict. It's rarely mysterious — the thing that changed most recently is the thing that broke, which is why the timeline outranks every diagnostic tool.
The proportionate fix is surgical: roll back the one problem plugin to its previous version (a rollback plugin or your backup does this), or deactivate it until the developer ships a fix — not undoing everything or restoring the whole site.
If the same plugin breaks repeatedly across updates, or hasn't been updated by its developer in over a year, that's an abandonment signal — the durable fix is replacing it with a maintained alternative, not another rollback.
What not to do
- Don't mass-delete plugins — deactivating is reversible and preserves settings; deleting can throw away configuration you can't easily rebuild.
- Don't re-run all updates again hoping things self-correct — you'll muddy the timeline that would have identified the culprit.
- Don't make changes on the live site with no backup confirmed — that's how a broken feature becomes a broken business.
- Don't stop updating forever because one update burned you — outdated plugins are the number-one way WordPress sites get hacked, which is a far worse failure mode.
- Don't restore a full site backup to fix one plugin — you'll lose every order, post, and form entry since the backup for a problem with a two-minute fix.
When to get help
Get help promptly when the broken feature earns money (checkout, booking, lead forms), when you can't reach the admin, or when the deactivation test doesn't isolate a culprit — conflicts between three or more components are genuinely fiddly. With your list of what updated and when, a professional can usually isolate and roll back the problem quickly. Longer term, the prevention kit is cheap and boring: staging site, automatic backups, and updating one thing at a time.
Not sure what to do next?
Answer a few short questions and we'll point you to the safest next step — DIY, a freelancer, or a direct review. No passwords required.
Is this a business website? If this issue may be costing you leads, sales, or trust, you may want a direct review instead of trial and error.
Frequently asked questions
Can I undo a plugin update?
Usually yes — a rollback plugin (like WP Rollback) reinstalls the previous version from wordpress.org, or a recent backup restores it. Identify the culprit first via one-at-a-time deactivation, then roll back only that one.
The site broke overnight and nobody touched it. How?
Auto-updates. WordPress can update plugins, themes, and itself on its own schedule. Check the admin's update history and your email for notifications — the overnight update is your culprit list.
Should I just stop updating plugins?
No — unpatched plugins are the leading cause of hacked WordPress sites, and a hack costs far more than a broken slider. The answer is safer updating: backups first, one at a time, staging site for the important stuff.
How do I know which plugin broke the site?
Start from what updated most recently (email notices or the Updates screen), deactivate that one, and test. Work down the list one at a time. If the site broke at update time, the culprit is on that day's list.
What's a staging site and do I need one?
A private copy of your site where updates get tested before touching the live one. Many hosts offer one-click staging. If your site takes orders or bookings, it converts update-day from a gamble into a routine.
The plugin developer hasn't fixed the bug. What now?
Stay rolled back or deactivated short-term, and watch the plugin's support forum for the fix release. If weeks pass in silence, treat the plugin as abandoned and migrate to a maintained alternative — limping along on old versions accumulates security risk.