A Plugin Update Broke My Site. Now What?

It happens right after you do the responsible thing. You log in, see the update notices, click update, and now your site looks wrong, acts wrong, or will not load at all. Take a breath. An update breaking a site is one of the most common repairs I do, and in most cases it is fixable without losing anything.

Why updates break sites

Your website is not one program. It is WordPress, a theme, and a stack of plugins, all written by different people, all having to work together. An update changes one piece, and sometimes the other pieces cannot keep up. The usual reasons:

• A conflict. The updated plugin clashes with another plugin or with your theme.
• A PHP version problem. The new plugin version needs a newer version of PHP than your server runs, or the opposite, your host upgraded PHP and the old plugin cannot handle it.
• An abandoned plugin. Some plugins have not been maintained in years. They worked until the day something around them changed.
• A half-finished update. The update got interrupted partway, leaving the plugin in a broken in-between state.

None of this means you did something wrong by updating. Not updating is worse, because old plugins are how sites get hacked. The fix is updating safely, which I will get to.

The recovery order matters

When an update breaks a site, there is a safe order to work in, and jumping around costs time and sometimes data.

First, check for a backup. If your host or a backup plugin made a restore point before the update, restoring it is often the fastest clean fix. You lose nothing except the update itself, which is what you want.

Second, roll back just that plugin. If only one plugin updated and the site broke right after, rolling that single plugin back to its previous version usually brings the site back in minutes.

Third, isolate the conflict. If several things updated at once, the work is disabling pieces one at a time until the site recovers, which names the culprit. This is the same process used for a blank page, which I walk through in the white screen of death post. And if your site is all the way down, start with the website-down checklist before anything else.

What you should not do is update everything else hoping something fixes it, or delete the plugin and its data before you know it is the problem.

How to update safely from now on

Once the site is back, a few habits make this a non-event next time:

• Back up before you update. Every time, no exceptions. A backup turns a crisis into a ten-minute restore.
• Update one thing at a time. Update a plugin, check the site, then update the next. If something breaks, you know exactly who did it.
• Look at your site after. Actually visit the homepage, a product or service page, and test the contact form.
• Use staging for big updates. A staging copy lets you test major updates on a clone before they touch the live site.
• Retire abandoned plugins. If a plugin has not been updated by its author in a couple of years, find its replacement before it finds you.

Honestly, this routine is boring, and that is the point. Most update disasters come from clicking "update all" on a Friday afternoon and walking away.

For a lot of my clients, this whole routine is exactly why they are on the monthly support plan, updates handled in the right order with backups first, so a bad plugin never becomes their emergency. When I handle updates as part of ongoing website repair and support, a break like this gets caught and rolled back before customers ever see it.

And if you are staring at a freshly broken site right now, this is a fix I do live on screen share all the time. You watch the rollback happen, watch your site come back, and learn the safe order for next time in the process.