First, stop and take a breath
The worst thing to do after an update breaks your site is to keep clicking. Updating more plugins, clearing every cache and reinstalling things at random can turn a small problem into a tangled one. Most plugin update failures are easy to undo if you change one thing at a time.
Spend the first five minutes on these four things:
- Stop updating anything else. Leave the other updates alone until this one is sorted.
- Write down what changed. Note the plugin name and the version it went from and to.
- Capture what you see. Take a screenshot of any error message or broken page.
- Back up the broken site. It sounds odd, but a copy of the site as it is right now gives you a safe way to return to this exact state if a fix goes wrong.
Why plugin updates break sites
Knowing the cause helps you choose the right fix. These are the usual suspects:
- A conflict. The new version clashes with another plugin or with your theme.
- A PHP mismatch. The update needs a newer PHP version than your host runs, or the reverse.
- A half-finished update. The download was interrupted and the plugin's files are a mix of old and new.
- A database change. The update altered how data is stored, and something went wrong partway.
- An abandoned plugin. Nobody has maintained it, and a WordPress or PHP update broke it.
Our guide to plugins that stop working goes deeper on diagnosing these. This post is about undoing the damage safely.
What WordPress rolls back for you, and what it does not
WordPress has some built-in protection, and it is worth knowing how far it goes. If a manual plugin or theme update causes a fatal error, WordPress can restore the previous version. Since WordPress 6.6, the same safety net covers automatic plugin updates. After an automatic update, WordPress checks the site's homepage for a fatal error, and if it finds one, it puts the old version back and emails the site's admin address.
The key word is "fatal." WordPress catches the kind of failure where the site cannot load at all. It does not catch a layout that looks wrong, a contact form that quietly stops sending, or a checkout that errors out for customers. Those break the business without triggering the safety net, which is why a rollback sometimes has to be done by hand.
Option 1: You can still log in
If your dashboard works, this is the easiest path.
- Go to Plugins and deactivate the plugin that was just updated. Check whether the site works again. If it does, you have found the problem.
- Delete the plugin, but do this only if you are sure you have a backup or are willing to reconfigure it, as some plugins remove their settings when deleted.
- Install the previous version. On the plugin's page at WordPress.org, open Advanced View and scroll to Previous Versions. Download the version you were running before, then upload it under Plugins, Add New, Upload Plugin.
- Activate it and check your site.
Rollback plugins also exist that do this with a few clicks. They are convenient, but they are one more plugin on a site that is already misbehaving, so use them carefully.
Option 2: The site is down or you are locked out
If you see a white screen, a critical error message, or cannot reach the dashboard, you need to switch the plugin off from outside WordPress. Your hosting control panel almost always has a file manager, or you can use SFTP.
- Open the wp-content folder, then the plugins folder.
- Find the folder for the plugin that was just updated.
- Rename it, for example by adding "-off" to the end. WordPress treats the plugin as missing and stops loading it.
- Reload your site and dashboard. If they come back, install the previous version as in Option 1.
If you or your developer use WP-CLI, the same result takes one command, such as wp plugin deactivate plugin-name. To install a specific older version, use wp plugin install plugin-name --version=1.2.3 --force, replacing the name and version with your own. Our guides to the white screen of death and the critical error message cover what to do if the site is still down.
When rolling back the plugin is not enough
Rolling back a plugin swaps its files. It does not necessarily undo what the update did to your database. Some updates change how the plugin stores its data. If you then install the older version, it may not understand the newer data, and you may see odd behavior or errors even with the old files back.
That is when you restore a backup taken before the update. It is the cleanest way back, with one important catch: restoring an old backup also rewinds everything that happened on the site since. On a brochure site that is usually harmless. On a store, a membership site or anything with forms, you can lose orders, sign-ups or messages received after the backup was taken. If that is a risk, restore the backup to a separate test copy first and compare, or get help before touching the live site.
A backup also only helps if it exists and works. If you have never tried restoring yours, this is a good reason to find out before you need it.
After the fix: check it properly
The site loading is not the same as the site working. Before you call it done, go through the things that make or lose money: submit your contact form and confirm the email arrives, log in and out, add something to a cart and start a checkout, and look at the main pages on your phone. Then:
- Hold the update by not updating that plugin again until you know why it failed.
- Check the plugin's support page for other people reporting the same issue.
- Report it to the developer with the error message you captured.
- Retest the update on a copy of the site before applying it to the live one.
How to stop this happening again
Rollbacks are a recovery skill. The better goal is not needing one. That means testing updates on a staging copy, taking a backup right before each update, updating your most important plugins one at a time, and checking forms and checkout afterward, ideally with a visual comparison against the live site. We lay out the full approach in why WordPress updates need a process, not just a click.
Updating plugins safely takes time and discipline, and the people who skip it are usually too busy running the business, not careless. That is exactly the work managed WordPress operations takes over. If you would like someone else holding the safety net, take a look at our managed WordPress plans or our WordPress maintenance plan. If your site is down right now, our emergency support can help.
Sources
WordPress rollback behavior is described in the WordPress core team's rollback auto-update proposal.
