[wp-hackers] fwiw: informing a user that a updated plugin is avaiable

Glenn glenn at slaven.net.au
Fri Feb 24 03:07:28 GMT 2006


That's great Per, I've been trying to come up with a solution to that 
same problem. 

I've been toying with using the svn server on wp-plugins.org and 
flagging an update when a new tag is created, have it sit
as a plugin itself and have it check once a day for updates.  I was 
trying to come up with something that would be able to be used by any 
plugin author, and wouldn't take much time up.  My idea was to have a 
plugin that people could install that would work as a plugin update 
manager, so all the checking update code could be contained within that 
and not have to be done for each plugin.  The other alternative I 
thought was to have a standard function/method that could be stuck into 
a plugin if the author wanted to use the update facility. 

Of course for this to work it would require the use of a standard 
repository to be used like wp-plugins.org.

Glenn


Per Soderlind wrote:
> One of the main problems a plugin author has, when he/she updates a plugin,
> is to tell the user that a new version is avalable.
>
> Here's how I do it using Prototype:
> http://soderlind.no/download/plugin_updated_demo.zip
>
> You'll find a full implementation in the latest version of my ImageManager
> plugin:
> http://soderlind.no/archives/2006/01/03/imagemanager-20/
>
>
> Kind regards,
> Per
>
> Prototype:
> http://prototype.conio.net/
> Prototype quick ref:
> http://www.snook.ca/archives/000531.php
> Prototype doc:
> http://www.sitepoint.com/print/painless-javascript-prototype 
> http://www.sergiopereira.com/articles/prototype.js.html 
>
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>
>
>
>
>   




More information about the wp-hackers mailing list