[wp-hackers] Plugin Management and Autoupdate System
computerguru at neosmart.net
Sun Jul 30 21:28:46 GMT 2006
> do_action('upgrade_' . trim( $_GET['plugin'] ));
That would work :)
> The download link could be a zip file which just gets unzipped.
I guess that would work.. That would require either exec() support or php
compiled with zip...
It can unlink() recursively the plugin directory.
We must make it clear though that _any_ plugin with more than one file (even
a readme) should have it's own DIR no matter what - then we can unlink and
be sure we're doing the right thing.
> -----Original Message-----
> From: wp-hackers-bounces at lists.automattic.com [mailto:wp-hackers-
> bounces at lists.automattic.com] On Behalf Of Peter Westwood
> Sent: Monday, July 31, 2006 12:16 AM
> To: wp-hackers at lists.automattic.com
> Subject: Re: [wp-hackers] Plugin Management and Autoupdate System
> Computer Guru wrote:
> > About the install and uninstall routines, is this OK?
> > We'll support three functions:
> > +Upgrade
> > +Install
> > +Remove
> > Upon successfully deleting the old plugin file and replacing it with
> > the new one, the server will GET myplugin.php?upgrade
> Surely this should be a normal wordpress hook like the activate
> deactivate ones - that would be a more standard way of achieving this.
> So you would have a call like the following in the upgrade process
> after the new file had been downloaded and installed:
> > And the same for the rest.
> > Upgrade/Install/Remove routines will be just pure PHP that will
> > require _zero_ user intervention. If user input is needed, it should
> > be asked for upon first run (for install only, the rest shouldn't
> need anything anyway).
> > Also, I need some suggestions on handling multi-file plugins.
> > Do we define some more metadata, say "chainloaded files:" that will
> > downloaded along with the plugin, or do we ....?
> Peter Westwood
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers