• Resolved deeveearr

    (@deeveearr)


    Finally 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.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Jose

    (@giuse)

    When you deactivate this plugin it automatically remove all the versions.
    It didn’t happen in your case because of the fatal error.

    If you want to help other users, you should:

    If you don’t want to help let me know and I will close this thread because it would be unuseful.

    Plugin Author Jose

    (@giuse)

    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.

    Thread Starter deeveearr

    (@deeveearr)

    Not really, as I’ve had PlugVersions installed for three weeks.

    I tthought that there was something wrong with the Health Check plugin, Word Fence, and never even thought about it being PlugVersions.

    Now tthat I’ve found what it was, the plugin will never be returning.

    Plugin Author Jose

    (@giuse)

    According to my tests:

    • v. 0.0.3 gives no issues when you remove it from the page of plugins
    • v. 0.0.4 gives a fatal error when you remove the plugin
    • v. 0.0.5 fixes the fatal error and gives no issues when you remove the plugins

    You probably updated to v. 0.0.4 before deleting it.

    In any case, the last version v. 0.0.5 is without issues, and this is the only thing it’s important.
    Honestly, for me doesn’t matter if you use or do not use this plugin anymore. You don’t need to repeat it many times. This plugin is something that I offer for free and I’m happy most users take advantage of this plugin.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Plugin Needs a Rewrite’ is closed to new replies.