WP automatic upgrade issues
|
View:
New views
6 Messages
—
Rating Filter:
Alert me
|
 |
WP automatic upgrade issues
by Rich Pedley
::
Rate this Message:
At present I don't believe there are any checks to see if plugins are
compatible when the upgrade takes place. Surely a check on the readme for the 'Tested up to' value could at least flag potential plugins that may cause issues. As it is at present people may have installed plugins that no longer work with that version. Like wise, and I don't know if this has been implemented or not, a similar check on the plugin against the version of WP installed should be done when installing direct from WP.org. This could also be extended to a check when activating any plugin. Thoughts? -- my mind is on a permanent tangent http://cms.elfden.co.uk/ _______________________________________________ wp-hackers mailing list wp-hackers@... http://lists.automattic.com/mailman/listinfo/wp-hackers |
|
|
Re: WP automatic upgrade issues
by scribu
::
Rate this Message:
>
> Like wise, and I don't know if this has been implemented or not, a > similar check on the plugin against the version of WP installed should > be done when installing direct from WP.org. This could also be > extended to a check when activating any plugin. > There already is a warning if you try to install a plugin that "hasn't been tested on your version of WP". -- http://scribu.net _______________________________________________ wp-hackers mailing list wp-hackers@... http://lists.automattic.com/mailman/listinfo/wp-hackers |
|
|
Re: WP automatic upgrade issues
by Rich Pedley
::
Rate this Message:
2009/6/14 scribu <scribu@...>:
> There already is a warning if you try to install a plugin that "hasn't been > tested on your version of WP". > shows how long it is since I installed a plugin that wasn't one of mine :) thanks for confirming that side, now should the auto upgrade do similar checks? -- my mind is on a permanent tangent http://cms.elfden.co.uk/ _______________________________________________ wp-hackers mailing list wp-hackers@... http://lists.automattic.com/mailman/listinfo/wp-hackers |
|
|
Re: WP automatic upgrade issues
by Demetris
::
Rate this Message:
On Sun, Jun 14, 2009 at 4:14 PM, Rich Pedley<elflop@...> wrote:
> At present I don't believe there are any checks to see if plugins are > compatible when the upgrade takes place. Surely a check on the readme > for the 'Tested up to' value could at least flag potential plugins > that may cause issues. As it is at present people may have installed > plugins that no longer work with that version. > [SNIP] I was thinking this morning about opening a ticket for this. For example: You have 3 plugins that have not been tested for compatibility with WordPress 2.8: * Plugin A * Plugin B * Plugin C [ Thank you, WordPress! Please, deactivate these plugins for me before upgrading. ] [ Don’t deactivate anything. Just upgrade! I know what I’m doing. ] Something like this could save users (and also people who try to support users) from a lot of trouble. Cheers, Demetris http://op111.net/ _______________________________________________ wp-hackers mailing list wp-hackers@... http://lists.automattic.com/mailman/listinfo/wp-hackers |
|
|
Re: WP automatic upgrade issues
by Lynne Pope
::
Rate this Message:
2009/6/15 Demetris <kikizas@...>
> On Sun, Jun 14, 2009 at 4:14 PM, Rich Pedley<elflop@...> wrote: > > At present I don't believe there are any checks to see if plugins are > > compatible when the upgrade takes place. Surely a check on the readme > > for the 'Tested up to' value could at least flag potential plugins > > that may cause issues. As it is at present people may have installed > > plugins that no longer work with that version. > > > [SNIP] > > I was thinking this morning about opening a ticket for this. > > For example: > > You have 3 plugins that have not been tested for compatibility with > WordPress 2.8: > > * Plugin A > * Plugin B > * Plugin C > > [ Thank you, WordPress! Please, deactivate these plugins for me > before upgrading. ] > > [ Don’t deactivate anything. Just upgrade! I know what I’m doing. ] What about [WordPress will deactivate plugins before proceeding with your upgrade.] Followed by [Upgrade complete. Please check that your plugins are compatible with this version before activating <link to codex compatibility list>] Yeah, I know that not all compatible plugins get added to the list (and not all incompatible plugins get added either) but this sure would be an incentive for developers to make sure their updated plugins *were* listed ;) Every major upgrade sees forum posts where WordPress gets blamed for problems simply because users are not checking that their plugins are up-to-date. A bit of education would not go amiss. I prefer that plugins are automatically deactivated for two reasons - (a)The Codex already tells users to deactivate plugins before upgrading; and (b) doing this isolates any issues & makes it easier to identify where errors may be occurring. Lynne _______________________________________________ wp-hackers mailing list wp-hackers@... http://lists.automattic.com/mailman/listinfo/wp-hackers |
|
|
Re: WP automatic upgrade issues
by Mike Schinkel-5
::
Rate this Message:
If an upgrade is going to disable plugins as a user I would like to know which plugins BEFORE I upgrade. Disabling incompatible plugins might cause a site to disable critical functionality, or worse crash in the case of a theme that has been modified to call functions within plugins directly.
-Mike Schinkel Custom Wordpress Plugins http://mikeschinkel.com/custom-wordpress-plugins ----- Original Message ----- From: "Lynne Pope" <lynne.pope@...> To: wp-hackers@... Sent: Sunday, June 14, 2009 11:24:02 AM GMT -05:00 US/Canada Eastern Subject: Re: [wp-hackers] WP automatic upgrade issues 2009/6/15 Demetris <kikizas@...> > On Sun, Jun 14, 2009 at 4:14 PM, Rich Pedley<elflop@...> wrote: > > At present I don't believe there are any checks to see if plugins are > > compatible when the upgrade takes place. Surely a check on the readme > > for the 'Tested up to' value could at least flag potential plugins > > that may cause issues. As it is at present people may have installed > > plugins that no longer work with that version. > > > [SNIP] > > I was thinking this morning about opening a ticket for this. > > For example: > > You have 3 plugins that have not been tested for compatibility with > WordPress 2.8: > > * Plugin A > * Plugin B > * Plugin C > > [ Thank you, WordPress! Please, deactivate these plugins for me > before upgrading. ] > > [ Don’t deactivate anything. Just upgrade! I know what I’m doing. ] What about [WordPress will deactivate plugins before proceeding with your upgrade.] Followed by [Upgrade complete. Please check that your plugins are compatible with this version before activating <link to codex compatibility list>] Yeah, I know that not all compatible plugins get added to the list (and not all incompatible plugins get added either) but this sure would be an incentive for developers to make sure their updated plugins *were* listed ;) Every major upgrade sees forum posts where WordPress gets blamed for problems simply because users are not checking that their plugins are up-to-date. A bit of education would not go amiss. I prefer that plugins are automatically deactivated for two reasons - (a)The Codex already tells users to deactivate plugins before upgrading; and (b) doing this isolates any issues & makes it easier to identify where errors may be occurring. Lynne _______________________________________________ wp-hackers mailing list wp-hackers@... http://lists.automattic.com/mailman/listinfo/wp-hackers _______________________________________________ wp-hackers mailing list wp-hackers@... http://lists.automattic.com/mailman/listinfo/wp-hackers |
| Free embeddable forum powered by Nabble | Forum Help |
