Conversation
review · 1 starsFinally managed to delete this plugin by going to my host’s cpanel and deleting it from my file manager (as trying to delete it from my WordPress install gave a critical error message). The reason? I consider any rollback plugin as one that you can use, then delete it when you’ve done the rollback. This plugin though does not allow that and needs to be installed and live to go back to an older version. However, trying to delete it is where the fun starts: On deactivating PlugVersions, ALL of the versions of plugins, and themes that have been rolled back now appear as NEW plugins that need to be removed and deleted. These plugins also appear in WordFence – but when you see which plugins need updating, nothing is there – they just appear in your admin bar as plugins that need updating. I needed to delete 21 versions of plugins and themes and as already mentioned, delete Plugversions from my hosting cpanel. Probably the worst plugin that I’ve ever installed.
Dear @deeveearr , When you deactivate PlugVersions from the page of plugins it removes all those folders that you had to remove via FTP. Look at the code included in uninstall.php. See here . You still had all the folders because you had a fatal error that prevented PlugVersion from cleaning the installation after deletion. Of course, the actions after deletion are triggered only if you remove the plugin in a standard way from the page of plugins. I have no idea about what happened, maybe a conflict with another plugin. Usually, other users open a thread on the support forum to report this kind of issue, and then we try to solve it. This plugin though does not allow that and needs to be installed and live to go back to an older version. How can you imagine you can roll back to a previous version if the plugin that manages the rollback is not active? Once you roll back, then of course you can uninstall this plugin. As you say it looks like when you deactivate this plugin it restores the versions that you had before the rollback. This is surely not true. Why do you say that? Or do you mean something else? The other issues regarding WordFence are already solved in the development version. I needed to delete 21 versions of plugins and themes This plugin DOES NOTHING with the themes. Are you sure you haven’t a second plugin for rollbacks? In any case, as already said, the additional versions of the plugins are removed when you delete PlugVersions from the page of plugins.
I understand what happened. The fatal error was an issue of PlugVersions v. 0.0.4 which was published 5 hours ago. The previous versions didn’t have this bug. This guy tried the plugin immediately after v.0.0.4 was published and deleted the plugin 🙂 We added the deletion of the plugin to the tests that are done before publishing a new version, so we can avoid that in the future a few minutes after we publish a new version someone tests it, and after triggering a bug that wasn’t seen during the test leaves a bad review 🙂 @deeveearr you can have a lot of success as a beta tester. If someone could find this bug before we were aware of it, it was only you 🙂 This bug is fixed with version v. 0.0.5.
Dear @deeveearr , When you deactivate PlugVersions from the page of plugins it removes all those folders that you had to remove via FTP. Look at the code included in uninstall.php. See here . You still had all the folders because you had a fatal error that prevented PlugVersion from cleaning the installation after deletion. Of course, the actions after deletion are triggered only if you remove the plugin in a standard way from the page of plugins. I have no idea about what happened, maybe a conflict with another plugin. Usually, other users open a thread on the support forum to report this kind of issue, and then we try to solve it. This plugin though does not allow that and needs to be installed and live to go back to an older version. How can you imagine you can roll back to a previous version if the plugin that manages the rollback is not active? Once you roll back, then of course you can uninstall this plugin. As you say it looks like when you deactivate this plugin it restores the versions that you had before the rollback. This is surely not true. Why do you say that? Or do you mean something else? The other issues regarding WordFence are already solved in the development version. I needed to delete 21 versions of plugins and themes This plugin DOES NOTHING with the themes. Are you sure you haven’t a second plugin for rollbacks? In any case, as already said, the additional versions of the plugins are removed when you delete PlugVersions from the page of plugins.
I understand what happened. The fatal error was an issue of PlugVersions v. 0.0.4 which was published 5 hours ago. The previous versions didn’t have this bug. This guy tried the plugin immediately after v.0.0.4 was published and deleted the plugin 🙂 We added the deletion of the plugin to the tests that are done before publishing a new version, so we can avoid that in the future a few minutes after we publish a new version someone tests it, and after triggering a bug that wasn’t seen during the test leaves a bad review 🙂 @deeveearr you can have a lot of success as a beta tester. If someone could find this bug before we were aware of it, it was only you 🙂 This bug is fixed with version v. 0.0.5.