[wp-hackers] WP automatic upgrade issues

Lynne Pope lynne.pope at gmail.com
Sun Jun 14 15:24:02 GMT 2009

2009/6/15 Demetris <kikizas at gmail.com>

> On Sun, Jun 14, 2009 at 4:14 PM, Rich Pedley<elflop at googlemail.com> 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

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.


More information about the wp-hackers mailing list