Require Plugin developers to make available “last known good version”

  • signcarver

    (@signcarver)


    7 years, 3 months ago

    Some plugins only allow downloading the latest version. If the latest version is broken there is no easy way to revert to the last version, especially if that plugin author doesn’t make it available.

    I know that you can always download each version before you install it, thus keeping your own archive.

    However this method is not practical if you manage many sites and use an updater program such as manageWP or InfiniteWP.

    Include this requirement to your Release checklist/manual and enforce it on all vendors that list their plugins with wordpress.org.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    7 years, 3 months ago

    Include this requirement to your Release checklist/manual and enforce it on all vendors that list their plugins with wordpress.org.

    Important note: there are not any vendors in WordPress.org.

    I think that this is an interesting suggestion but let’s be realistic too. All of the latest versions of plugins are considered the “last known good version”. No one uploads code here that intentionally has bugs.

    Plugin authors do have the ability t0 make a version as “Development” in the Developers tab of their plugin page. For example, you can see that on Akismet’s page.

    https://wordpress.org/plugins/akismet/developers/

    I do agree with you and think it’s good to have multiple versions available easily on the plugins page. But I’m not sold on the idea to make that a requirement.

    Thread Starter signcarver

    (@signcarver)

    7 years, 3 months ago

    I apologize if i have the “vendor” terminology wrong but surely you understand the point. Somehow a developer puts his plugin on this site. I hope that WordPress vets the developer and plugin to some degree.

    It isn’t a question of whether someone intentionally uploads a bad version. It is a fact, though, that it happens. If you happen to use that plugin in multiple sites, you are screwed.

    Why wouldn’t you make it a requirement. The vendor surely has the “last known good version” that was released and tested. How difficult is is that he provides that version?

    It would have solved the problem many of us had with BestWebsoft’s gallery plugin that broke many sites.

    • This reply was modified 7 years, 3 months ago by signcarver. Reason: correct spelling error
    • This reply was modified 7 years, 3 months ago by signcarver. Reason: spelling error
    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    7 years, 3 months ago

    I’m sorry you had a problem with a plugin.

    How difficult is is that he provides that version?

    Mild to very difficult? It also wouldn’t fix your problem. The only thing that can help you or users when that happens is a) having good backups and b) knowing how to restore them when needed.

    That’s not really an unreasonable ask that people are responsible for their sites. 😉

    All versions of all plugins uploaded to the WordPress repository worked on the developer’s site before it was uploaded. I can’t say that they turned DEBUG on but it worked. As you’ve personally demonstrated this caused you and others problems when other installations had problems.

    If you like, that would be the previous version but updates are sometimes released as either a fix or to address a critical security issue.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Require Plugin developers to make available “last known good version”’ is closed to new replies.