Fix: WordPress Plugin Update Broke Site
Roll back to the previous version without losing settings. Three methods depending on your access level.
Last updated: October 2026
Install the free "WP Rollback" plugin if you can still access wp-admin. It adds a "Rollback" link next to every plugin, letting you revert to any previous version in one click.
If wp-admin is inaccessible, use the file manager method below.
What's actually happening
A plugin updated itself (or was updated automatically) and the new version has a bug, a breaking change, or an incompatibility with another plugin/theme/PHP version. Your settings are safe — they live in the database. Only the plugin files changed.
Good news: Rolling back the plugin files won't touch your settings. Your content, options, and database are unaffected. The fix is just swapping files.
If you can access wp-admin — WP Rollback (easiest)
- Install and activate the free WP Rollback plugin
- Go to Plugins → Installed Plugins
- Click Rollback next to the plugin that broke the site
- Select the previous version from the dropdown
- Click Rollback — WordPress replaces the files automatically
Pro tip: WP Rollback also works for themes. Same flow, different menu.
If you can access wp-admin — manual replacement
When you don't want to install another plugin. Works for any plugin on wordpress.org.
- Go to
wordpress.org/plugins/[plugin-slug]/ - Click the Advanced View link at the bottom
- Scroll to Previous Versions
- Download the version you want as a ZIP
- In wp-admin, go to Plugins → Add New → Upload Plugin
- Upload the ZIP, choose Replace current with uploaded
- WordPress installs the older version over the newer one
Warning: Don't deactivate the plugin first. Uploading over the active plugin preserves your settings. Deactivating risks losing plugin-registered data in some edge cases.
If you have SSH access — WP-CLI
Fastest method if you're comfortable with the terminal.
# List plugins with available versions
wp plugin list
# Roll back a specific plugin
wp plugin install plugin-slug --version=1.2.3 --force
# Example
wp plugin install woocommerce --version=8.4.0 --force
# Deactivate auto-updates for this plugin
wp plugin auto-updates disable plugin-slugPro tip: The --force flag is required to overwrite an existing plugin. Without it, WP-CLI skips the install because the plugin is already present.
If wp-admin is completely inaccessible
Recovery requires file access. This works even when nothing loads.
- Connect to your host via SFTP or the hosting file manager
- Rename
wp-content/plugins/[plugin-slug]to[plugin-slug]-broken - This disables only that plugin, not all plugins — the site should load
- Download the previous version from wordpress.org
- Extract and upload the old version, replacing the renamed folder
- Reactivate the plugin in wp-admin
Pro tip: If you don't know which plugin broke it, rename the whole wp-content/plugins folder to plugins-disabled first to restore access, then bisect.
After you roll back — the follow-up steps
- Disable auto-updates for the rolled-back plugin. Otherwise it'll update again tonight and break the site again.
- Check the plugin's support forum. Search for reports from other users — usually someone reports the same bug within 24 hours.
- Subscribe to the plugin's changelog. When a fix is released, update deliberately.
- Consider a replacement. If a plugin updates slowly and breaks often, that's a signal to find a better-maintained alternative.
- Write down what broke. If you have a log of past plugin updates that broke things, you'll update more cautiously in the future.
🛡️ How to prevent this next time
- Disable auto-updates site-wide. Add
define('AUTOMATIC_UPDATER_DISABLED', true);towp-config.php. - Test on staging first. Every serious host has staging. Update there, wait a day, then push to production.
- Backup automatically before every update. UpdraftPlus, BlogVault, or your host's built-in backup.
- Update in batches. Don't update 15 plugins at once. Update 2–3, verify, next batch.
- Read the changelog before updating. "Breaking changes" in the changelog is a red flag — wait a week.
- Watch for "Tested up to" behind your WP version. If the plugin isn't tested on your WP version, wait.
- Join the plugin's Slack or forum. Most maintainers announce breaking changes before release.
❓ Frequently asked questions
How do I roll back a WordPress plugin update?
Download the previous version from the plugin's wordpress.org page (click Advanced View → Previous Versions), then upload it via Plugins → Add New → Upload. Or install the WP Rollback plugin and click Rollback next to the plugin.
Will rolling back lose my plugin settings?
No. Plugin settings live in the database, not the plugin files. Rolling back the files doesn't touch wp_options. The only risk is if the newer version changed the database schema — in that case, some settings may not be readable by the older version.
What if the plugin developer has already released a fix?
Check the plugin's changelog. If a hotfix is out, update to the fix instead of rolling back. If not, roll back and disable auto-updates until the developer responds.
How do I prevent plugin updates from breaking my site?
Test on staging first, disable auto-updates on critical plugins, keep automatic backups, and check the plugin's support forum for reports after each update. Follow the plugin's changelog before updating.
Can I roll back if I don't have a backup?
Yes. The previous version is available on wordpress.org for free plugins. For premium plugins, download the previous version from your account dashboard on the vendor's site.