← All articles

A Plugin Update Broke My Site. Now What?

April 3, 2026 · 4 min read · by the upkept/dev team

If a plugin update broke your site, the fastest fix is to undo the update: restore the backup you took beforehand, or roll the plugin back to its previous version. If you did not take a backup, you find the culprit by deactivating plugins one at a time until the site returns, then deal with just that one. The important thing is not to panic and start deleting things at random, which usually makes it worse. Here is the calm version.

First, do not make it worse

A broken site is stressful, and stress leads to deleting files and toggling settings until something changes. Resist that. Random changes turn a one-plugin problem into a mystery. Work in order instead.

If the site is completely down, put up a simple maintenance message so visitors do not see errors while you work. Then start recovering.

The fastest fix: undo the update

You have two clean ways to undo it.

  1. Restore your backup. If you took a backup before updating, as every update should start with, restore it. The site returns to exactly how it was minutes ago. This is why the backup step matters so much.
  2. Roll back the plugin. If you did not back up, roll the specific plugin back to its previous version. Most plugins can be reverted, either through a rollback tool or by reinstalling the older version. The site should recover as soon as the offending version is gone.

Either way, the site should be working again within minutes. Now you can investigate calmly instead of in a crisis.

Which plugin actually caused it?

If you updated several plugins at once, you may not know which one broke things. This is exactly why updating one at a time matters. To find the culprit now:

  1. Deactivate all your plugins.
  2. If the site comes back, reactivate them one at a time, checking the site after each.
  3. When the site breaks again, the plugin you just activated is your culprit.

Sometimes it is not one plugin but a conflict between two, or between a plugin and your theme. The same one-at-a-time method finds those too.

What to do with the guilty plugin

Once you know which plugin broke the site, you have a few options:

  • Wait and update later. The plugin maker may release a fix within days. Keep it on the old version briefly and watch for an update.
  • Find an alternative. If the plugin is abandoned or keeps causing problems, replace it with a maintained alternative.
  • Get help. If the plugin is essential and the conflict is not obvious, this is a reasonable point to bring in someone who can dig into it.

Do not just leave it deactivated and forget about it if it was doing something important, and do not force the broken version back on and hope.

Stop it happening again

This is avoidable with a few habits, which are the core of safe maintenance:

  1. Back up before every update, and confirm the backup works.
  2. Update one plugin at a time, checking the site after each.
  3. For big updates, test on a staging copy first, so breaks never reach visitors.
  4. Do updates on a quiet day, never right before a busy period.

What to do next

Get the site working again first, by restoring or rolling back, then investigate at your leisure. Once it is stable, put the backup-first, one-at-a-time habit in place so the next update is boring instead of frightening. If updates keep breaking your site, that is often a sign of deeper conflicts worth a proper look, which an audit can start to surface.

Part of our guide to website problems.

Not sure what is actually wrong with your site?

Our $250 site health audit checks performance, security, broken forms, and outdated dependencies. You get a written report and a prioritised fix list, credited toward your first month if you start maintenance within 30 days.

Book the $250 site health audit