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

Peter Westwood peter.westwood at ftwr.co.uk
Fri Feb 3 18:44:39 GMT 2006


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

Craig wrote:
> Sweet! You code dudes are my heroes.
> 
> 
> On 2/3/06, David House <dmhouse at gmail.com> wrote:
>> On 03/02/06, Justin Moore <wantmoore at gmail.com> wrote:
>>> I really do like the idea to shade the auto-deactivated
>>> ones and give them a "re-activate" button instead of "activate"
>> I've attached a new patch to the bug [1] which replaces the old one
>> and adds these new features:
>>
>> * Deactivated plugins are stored in an option, deactivated_plugins and
>> are greyed out on the plugins page with 'deactivated in upgrade'
>> displayed after their name. The button is also labelled 'Reactivate'
>> instead of 'Activate'.
>> * Plugins deactivated are shown on the successful upgrade completed
>> screen.
>>
>> [1]: http://trac.wordpress.org/ticket/2377
>>

Cheers david!

This patch is nice.

Had a few issues with it when I tested on my trunk test install which i
think I have fixed in the new patch attached to the bug.

The only known issue with this patch at present is that if you upgrade
twice you lose you deactivated list which is a bit bad

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

iD8DBQFD46SXVPRdzag0AcURAhxXAJ9bUQcNfA+B2GcdHVvTpEI7Sz4MQgCguYKN
RDntpgF/76qcgkIKx0CNZ+Q=
=o8/Z
-----END PGP SIGNATURE-----



More information about the wp-testers mailing list