New 24/7 monitoring and daily cloud backups now included in every Shield Pro plan.

Plugins

Learn how to roll back a WordPress plugin after an update.

A plugin update can remove features you rely on or trigger a fatal error. Rolling back means restoring the previous plugin files and sometimes the database rows that changed during upgrade.

Time: 20-35 minutes Level: Intermediate
Neil McNaught, founder of BugShield and WordPress author
Written by
Written by
Updated
Updated

What this problem looks like

WordPress does not include one-click plugin downgrade in core. Rollback means replacing wp-content/plugins/plugin-slug/ with the last known good copy.

Some plugins migrate database options on upgrade. If settings look wrong after rollback, restore the database table rows from backup or re-run the plugin setup wizard.

Fastest rollback from backup

  1. Open your backup tool or hosting snapshot.
  2. Restore only wp-content/plugins/problem-plugin/ from before the update.
  3. Clear object cache and opcode cache if your host provides buttons for them.
  4. Reload wp-admin and confirm the version number in Plugins list.

Install an older version manually

Download the previous release from the vendor account or the wordpress.org plugin directory release archive.

Delete or rename the current plugin folder, then upload the older ZIP via Plugins → Add New → Upload Plugin or File Manager, SFTP, or FTP.

Rollback with WP-CLI over SSH

Only run the commands below if you have SSH access to the server. They will not work inside File Manager.

bash
cd /path/to/wordpress
wp plugin deactivate my-plugin
wp plugin install my-plugin --version=2.4.1 --force
wp plugin activate my-plugin

When wp-admin is offline

Rename wp-content/plugins/my-plugin to my-plugin.off via File Manager, SFTP, or FTP to stop the fatal error.

Upload the older plugin folder into wp-content/plugins/.

Rename back to my-plugin only after files are in place.

Prevent repeat bad updates

Document working versions per site. Test updates on staging and keep auto-updates off for revenue-critical plugins.

Subscribe to vendor release notes so you know when a broken build is patched.

When to stop DIY and hire help

Database migrations make some rollbacks risky without a developer. BugShield can roll back plugins and repair schema issues at a confirmed fixed price with Vault access to your hosting.

Questions answered

WordPress plugin rollback FAQs

Answers about choosing a safe version, protecting database changes, restoring plugin files, vulnerabilities, and testing before another update.

Can I downgrade from the Plugins screen?

Core does not offer downgrade buttons. Use backup restore, manual ZIP upload, or WP-CLI with a specific version over SSH.

Will rollback delete plugin settings?

Usually settings remain in the database. If the new version altered tables, you may need a database restore to match the older files.

Where do I find old wordpress.org versions?

Open the plugin page on wordpress.org, click Advanced View, and download previous tags from the Development section.

Is rollback the same as deactivate?

No. Deactivate stops the plugin but leaves new files in place. Rollback replaces those files with an older build.

Should I back up before rolling back a WordPress plugin?

Yes. Save current files and the database first, even when the update is broken, so recent orders and data can be protected during recovery.

How do I choose a safe WordPress plugin version to restore?

Use the latest version known to work with your WordPress, PHP, theme, and related plugins. Download it only from the official developer or directory.

Is it safe to roll back a plugin with a known vulnerability?

Only as a short controlled recovery when no safer compatible release exists. Restrict exposure and update to a secure fixed version as soon as possible.

Can a WordPress plugin rollback reverse database changes?

Replacing files does not normally reverse database migrations. A newer schema may not work with older code, so check vendor guidance before rolling back complex plugins.

How do I stop WordPress automatically reinstalling the broken update?

Disable automatic updates for that plugin temporarily, document the reason, and re-enable them after the compatible release has been tested.

What should I test after a WordPress plugin rollback?

Test the original fault plus wp-admin, forms, login, scheduled jobs, emails, and complete sales or membership journeys connected to the plugin.

Would you rather a developer fixed it?

Request a fix at a confirmed price and speak directly with the BugShield developer working on your site.

Request a Fix