Automatic Plugin Upgrade could break new plugins that require special instructions for upgrading
|Reported by:||nerrad||Owned by:||anonymous|
|Severity:||major||Keywords:||dev-feedback 2nd-opinion has-patch|
First off, I love the new "automatic download" and upgrade feature for plugins coming with 2.5. A couple of concerns though:
- Does this disable the plugin first and then reactivate it after the download or does the automatic download just overwrite the files? If it's the latter this could cause problems where a plugin being upgraded needs to run the activation hook to bring in new changes.
- There doesn't seem to be anyway for plugin authors to indicate special instructions for upgrading from older versions.
- A good temp solution would be to simply put in a warning for users to check the plugin page on WordPress.org first for any special upgrade instructions.
- Introduce a new file type/name that if plugin authors include with their plugin will be executed following the ftp allowing special upgrade tasks to be done. I suggest _pluginname-upgrade.php.
- Create a new tag for the readme.txt file in plugin packages (i.e. Special Instructions) so that when the readme.txt file is parsed it will put in an alert and display the special instructions in the plugin list. Plugin authors would then have a way of notifying potential users of possible problems with a simple automatic upgrade.
Change History (16)
Note: See TracTickets for help on using tickets.