WP Rollback – Rollback Plugins and Themes

Changelog

2.0.7

• Fix: Resolved a bug with plain permalink websites which caused a rest_no_route error when trying to rollback a plugin or theme. Thanks, @afizesan for helping pinpoint the issue.
• Fix: Update the way the React app is loaded to suppress React 18+ warnings.
• Tweak: Bumped the plugin’s minimum required WordPress version to 6.0+ for best compatibility with new React components in UI.

2.0.6

Fix: The release corrects the paths used in plugin file includes and requires. The unnecessary forward slashes at the start of each file path have been removed. This change ensures proper file inclusion and requirement, avoiding potential issues with file not found errors.

2.0.5

• New: In this version we’ve brought back the “trunk” option to rollback to. This allows plugin or theme developers who use trunk for beta testing to rollback to the latest trunk version. Thanks, @megamenu for suggesting this be brought back.
• Fix: Refactored how plugin avatar images are checked so that all available image types and sizes are checked. This resolves an issue where some plugins would not display an avatar image.
• Fix: On the final rollback confirmation screen, the plugin name field was outputting raw HTML. This has been fixed to properly display the plugin name, even if it contains some html characters.

2.0.4

• Fix: Resolved issue REST route not including proper permission callback which created a PHP notice. Thanks, @rom1our for submitting the issue.
• Fix: Resolve issue with REST API and multisite installs not being able to properly communicate with the endpoint.

2.0.3

• Fix: A few additional strings in JavaScript needed to be internationalized. Thanks, @pedro-mendonca for contributing the fix.

2.0.2

• Fix: Resolves an issue with WP Rollback not being able to communicate to its REST API on WordPress subdirectory installs. Thanks, @emaralive for reporting the issue.

2.0.1

• Fix: Resolved an issue with the POT file not properly being generated at release. This resolves the issue with the new UI not being able to be translated.

2.0.0

• New: Introducing version 2.0! In this new version the UI is now better looking and snappier than ever. The branding has also been updated to look and feel more modern.

1.7.3

• Fix: Resolved an issue with plugin rollbacks not correctly setting a filepath for the plugin being rolled back. Props to WP.org user @itmesteren for the fix.

1.7.2

• Fix: Ensure that the “Rollback” button displays properly when a WordPress site only has a single theme installed. Thanks @eldertech for your help uncovering this bug.
• Fix: Minor CSS fixes for the Rollback page.
• Tweak: Update the WordPress.org readme.txt file to have better instructions for translating the plugin. We also fixed a few typos.

1.7.1

• Fix: Prevent PHP notice when rolling back a plugin or theme on PHP 7.4.

1.7.0

• Tweak: Removed the WP Time Capsule staging button and banner.

1.6.0

• New: You now have the ability to rollback to the trunk for plugins. This is useful for beta testing releases and more. Thanks to karpstrucking for making this happen. #45
• New: Add actions “wpr_plugin_success”, “wpr_plugin_failure”, “wpr_theme_success”, and “wpr_theme_failure” for developers.
• New: If a plugin or theme does not have any tagged releases to select from then then an informative notice appears rather than empty space for a better user experience. #42
• Tweak: Use the WP.org API to retrieve plugin release version information for more reliable results. #35

1.5.1

• Tweak: Added additional information about the importance of Staging and Backups and links to our preferred plugin.

1.5

• New: You can now view plugin changelogs within the rollback screen. #7
• New: Added support for WordPress Multisite rollbacks for themes and plugins. #22
• New: Rollback button is fixed to the bottom of the page now to prevent long scrolls for rollbacks with many versions. #23
• New: Updated the WP.org plugin header graphic. #37

1.4

• New: Updated plugin’s text domain to the plugin’s slug of ‘wp-rollback’ to support WordPress’ GlotPress translations. #28
• New: Gulp automated POT file generation and text domain checker. #28
• Fix: Check the WP install’s themes transient is present, if not fetch it to see if a theme can be rolled back. Allows rollbacks for new WP installs or in a case where the transient is not set properly.#27

1.3

• Tested compatibility with WordPress 4.4 and verified as working; bumped up compatibility
• Fix: Trying to get property of non-object warning. #20
• Improvement: Better version sorting now using usort & version_compare. #16

1.2.4

• New: Portuguese translations added.
• Fix: Limit HTTP requests to Plugin page only. Report 1 Report 2

1.2.3

• Fixed: XSS hardening. Thanks @secupress
• Fixed: CSRF patch regarding missing nonces. Thanks @secupress
• Improvement: escape all of the things.

1.2.2

• New: Russian translations from @Flector – thanks!
• Fix: Replaced use of wp_json_encode to support older WordPress versions. Report

1.2.1

• Fix: Rollback link appears on non wp.org plugins – thanks @scottopolis. #14
• Removed unnecessary WP_ROLLBACK_VERSION constant.

1.2

• New: Swedish translation files – Thanks @WPDailyThemes.

1.1

• Fixed “Cancel” button which was falsely submitting the form.

1.0

• Initial plugin release. Yippee!
• Adds “Rollback” link to all plugins from the WordPress repo on the plugin screen.
• Adds “Rollback” link to all themes from the WordPress repo inside the modal details screen.
• The “Rollback” page allows you to choose which version you want to rollback to.