How Rollbacks Work

Understanding how WP Rollback works behind the scenes helps you use it more effectively and troubleshoot any issues that might arise.

The Rollback Process

When you confirm a rollback, WP Rollback runs a set of steps in order and shows each one on screen. If a step fails, the rollback stops and shows the error. WP Rollback (Free) runs six steps. WP Rollback Pro adds a seventh, Verifying package integrity….

1. Enabling maintenance mode…

• Turns on maintenance mode if the plugin is active, or if the theme is the active theme or its parent
• Skipped for inactive plugins and themes

2. Download requested version…

• WP Rollback (Free) downloads the version from WordPress.org
• WP Rollback Pro uses a Local archive of that version if your site has one. If not, it asks Plugin Vault for it (with an active license), and downloads from WordPress.org if the Vault doesn't have it.

3. Creating version archive…

• For premium plugins and themes (anything not on WordPress.org), saves a ZIP of the installed version as a Local archive before it's replaced
• Skipped for WordPress.org plugins and themes
• Skipped if an archive of the installed version already exists
• If the archive can't be created, the rollback continues without it

4. Validating package integrity…

• WP Rollback (Free) checks that the downloaded file is there
• WP Rollback Pro runs full package validation and stops the rollback if the package fails

5. Verifying package integrity… (Pro only)

• For Plugin Vault downloads, compares the file's SHA-256 checksum with the one the Vault sent. If they don't match, the rollback stops before any files are replaced.
• Skipped for WordPress.org downloads and Local archives

6. Replacing files…

• Checks that the download is a valid ZIP file
• For a plugin, deactivates it if it's active and moves its folder to wp-content/upgrade-temp-backup/plugins, like WordPress does during updates. For a theme, removes its folder.
• Unzips the version you picked into wp-content/plugins or wp-content/themes
• If a plugin's new version can't be unzipped, moves its folder back, so the version you had keeps running
• Reactivates the plugin if it was active, then deletes the moved folder. An active theme stays active.
• Anything stored inside the plugin or theme folder can be replaced or removed. Settings saved in the database are kept.
• Clears PHP's code cache for the replaced files, so the next page load runs the version you rolled back to

7. Cleaning up temporary files…

• Turns maintenance mode off if it's still on
• Deletes the downloaded ZIP and the temporary data WP Rollback stored for this rollback

Safety Features

Premium Asset Protection

WP Rollback Pro provides two ways to roll back premium plugins and themes:

1. Plugin Vault — The primary source for premium rollbacks. Plugin Vault is a shared, community-contributed library of verified plugin and theme ZIPs available to all Pro users with an active license. Because versions are sourced from the Vault, you do not need to have WP Rollback installed before an update to roll back a premium asset.

2. Local Archives — WP Rollback saves a ZIP of a premium plugin or theme before each update and before each rollback. These appear as "Local" versions in the rollback UI and are useful for restoring the exact version your site was running. WP Rollback (Free) creates them too, but restoring them requires Pro.

Note: Neither source includes database backups — only plugin and theme files are preserved.

Maintenance Mode

While an active plugin or theme is being replaced, logged-out visitors see a short "Maintenance Mode" page. Logged-in users who can update plugins or themes still see the site normally. WP Rollback turns it off as soon as the files are replaced, or right away if any step fails. If a rollback is interrupted, the page turns itself off after 10 minutes.

What WP Rollback Checks

• WP Rollback (Free) checks that the downloaded file exists, then that it's a valid ZIP file.
• WP Rollback Pro also runs package validation on every download and checks the SHA-256 checksum of every Plugin Vault download.
• If a check fails, the rollback stops before any files are replaced.

What Gets Rolled Back

Plugin Rollbacks

• Core plugin files
• Plugin version number
• Function definitions and classes
• Admin interfaces and settings pages

Theme Rollbacks

• Theme template files
• Stylesheet files
• Theme functions

What Doesn't Get Rolled Back

• Plugin/theme settings and configurations
• User data and content
• Database entries
• Custom modifications outside the plugin/theme directory

Version Sources

Each version in the rollback UI is labeled with a badge indicating where it comes from. Versions are listed newest first, and the version you have now is marked Installed.

Which sources you see depends on the plugin or theme:

• WordPress.org plugins and themes list WordPress.org versions only.
• Premium plugins and themes list Local archives and, with WP Rollback Pro and an active license, Plugin Vault versions. If a version is in both, the Local copy is used.

WordPress.org Repository (Repo)

The source for all free, open-source plugins and themes:

• Complete version history
• Compatibility information
• Release notes

Plugin Vault (Vault) — Pro Only

A shared library of premium plugin and theme versions, available exclusively to WP Rollback Pro users. See the full Plugin Vault documentation for details on coverage, verification, and legal requirements.

• ZIPs contributed by the WP Rollback Pro community and verified for integrity before distribution
• Covers premium plugins and themes from virtually any source, such as Envato, Kadence Pro, Astra Pro, GeneratePress Pro, Divi, Gravity Forms, and WooCommerce extensions
• No prior installation of WP Rollback is required to access Vault versions
• Versions appear with a Vault badge in the rollback UI
• A valid license for the plugin or theme is required to use Vault versions

Local Backups (Local)

Versions automatically archived from this specific site:

• Created for premium plugins and themes before each update and before each rollback. WordPress.org plugins and themes are not archived.
• Stored in a private folder inside wp-content/uploads named wp-rollback- followed by 32 random characters. Older versions of WP Rollback used wp-content/uploads/wp-rollback/, and existing backups are moved to the new folder automatically when you update.
• WP Rollback (Free) keeps the 5 most recent archives for each plugin or theme. WP Rollback Pro keeps 25 by default, and you can set any number from 1 to 100 in Settings → Archives. When the limit is reached, the oldest archive is removed first.
• Represent the exact version your site was running at the time of the backup
• Versions appear with a Local badge in the rollback UI
• Restoring Local versions requires WP Rollback Pro. WP Rollback (Free) lists them but asks you to upgrade.

When WP Rollback Pro restores a Local archive, the download step says Using local backup — download skipped.

Who Can Roll Back

• Rolling back a plugin requires the update_plugins capability. Administrators have it by default.
• Rolling back a theme requires the update_themes capability. Users who can update themes but not plugins can roll back themes.
• On multisite, only Super Admins can roll back. See Multisite.

Rollback Limitations

Version Availability

• Free version: Rollbacks are limited to versions available in the WordPress.org repository. If a version was removed by its author, it will not appear. Premium plugins and themes need WP Rollback Pro.
• Pro version: Pro can also roll back premium plugins and themes, using Plugin Vault versions and Local archives.

File Permissions

The web server must have write permissions to the plugin/theme directories.

Disk Space

Sufficient disk space is required for temporary files during the rollback process.

WordPress Core

WP Rollback does not support WordPress core rollbacks due to complexity and security concerns.

Technical Implementation

REST API

WP Rollback uses WordPress REST API endpoints for:

• Fetching version information
• Processing rollback requests
• Managing rollback steps
• Reporting status and progress

Hook System

The plugin integrates with WordPress hooks for:

• Adding rollback links to admin pages
• Registering menu items
• Handling upgrade processes
• Managing asset loading

Database Operations

Minimal database operations are performed:

• Storing rollback metadata
• Logging rollback activity (Pro version)
• Caching version information

Best Practices

Before Rolling Back

1. Create a full site backup
2. Test on a staging site first
3. Review version release notes
4. Check for known compatibility issues

After Rolling Back

1. Test functionality thoroughly
2. Monitor for any issues
3. Consider holding the current version
4. Document the rollback reason

Next Steps

• Learn about Plugin Rollbacks in detail
• Explore Theme Rollbacks specifics
• Understand Pro Features for advanced functionality
• Read the Plugin Vault documentation for coverage, verification, and license requirements