[wp-hackers] Plugins -- new header fields: max-compatible and
xel at netgra.de
Thu Apr 3 07:45:14 GMT 2008
A hardlimit to top isn't really a good idea I think.
First - als DD32 mentioned - you are able to upgrade wordpress without
deactivating plugins (isn't recommended but *is* possible however)
If I write a plugin today it will - of course - support 2.5. It would not be
too smart to write a plugin only for outdated versions.
It may or may not support 2.6 - how should I know when I release this
version of the plugin, which upcomming versions of wordpress will be
supported? This values are not subject to change after the files are
downloaded by the user. Before downloading the user should read what is
written on that download page and there should be written that it doesn't
support WP Version XY if the Plugin Author knows.
You know: If a user is told that plugins will not work with his version of
WP this is a good thing - if he belives Plugins will work until he gets this
message telling him it won't this is bad. Bad because no one can predict
until which version his plugin will work and so they will not fill this
value or will fill it with a value which doesn't make any sense. The "Tested
up to" - soft limit would be gread to show up in the backend however. Same
with the hardlimit "requires Version XY or higher".
2008/4/3, DD32 <wordpress at dd32.id.au>:
> On Thu, 03 Apr 2008 13:47:50 +1100, Jeremy Visser <jeremy.visser at gmail.com>
> On Wed, 2008-04-02 at 16:20 -0500, Stephen Rider wrote:
> > > 1) When upgrading I don't have to slog through source files looking
> > > for what's going to work and what's not.
> > >
> > In that case, WordPress should automatically offer to deactivate
> > untested plugins before starting the upgrade.
> Thats not really possible, The upgrade proceedure is to upload the new
> files, and then continue on working, The upgrade functionality only makes
> any needed changes to the database.
> No plugins are touched, they're just loaded as usual.
> So its possible post-upgrade when all the plugins are loaded to offer to
> deactivate any which have not been tested to work OK, but its kind of
> pointless at that stage.
> It would be possible to give a message "Warning: Several plugins which you
> have active have not been tested with this version of wordpress, please
> check they work OK", its not really needed, after an upgrade, checking
> plugins is usually one of the first things.
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers