[wp-testers] Fail to upgrade wp2.0.1 RC1

[Peter Westwood]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

David House wrote:
> On 02/02/06, Craig <nuclearmoose at gmail.com> wrote:
>> I suppose that this is dangerous ground, but is there not a way to have WP
>> disable all of the plugins when upgrading?
> 
> http://trac.wordpress.org/ticket/2377
> 
> That should deactivate plugins on upgrade. We also need a little
> message saying 'Now reactivate your plugins one by one' after the
> upgrade, to make sure none of them are faulty.

I'm not a fan of this patch as it stands.

I am not a complete fan of deactivating all plugins on upgrade either
but we should at least store the list of active plugins and provide a
way of reactivating them easily.

Maybe a button should appear on the plugins page which allows you to
reactivate your plugins - either all at one or one at a time for easy
testing?

Maybe the saved array of plugins could be used to highlight within the
plugins page using an alternate colour which plugins were active before
upgrade?

I have never personally had a problem with plugins breaking an upgrade.

Maybe we can do something with the php error handling functionality to
capture errors and if they lead back to a plugin offer the user the
ability to deactivate the relavent plugin - I am will to investigate
this if people think it is a good idea.

westi
- --
Peter Westwood
http://blog.ftwr.co.uk
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFD4oZYVPRdzag0AcURAgIcAJ0S777PYZXBWCrLn5jMlXEHtPMUMwCeJH8l
jBrZ7KZNwZV9xmhq2XZbPyU=
=Kh94
-----END PGP SIGNATURE-----