We need this big time people!!
We need this big time people!!
Excellent Idea. It would be a great help to the bloggers.
While I would very much like to know how many people use my plugins, I don't think phoning home is the right way;
the ideal way as I see it now would be to query get_plugin_data.php on wp-plugins.net, together with some way of automatically submitting new versions (I don't know about others, but I'm very lazy, so I have scripts that help me do a "release" with a single command; hmm, maybe it's time to get working and make a script that logs on to wp-plugins.net and posts the new version :))
also, some usage statistics for get_plugin_data from wp-plugins wouldn't hurt (I think number of uniques per week/month would be enough to give a reasonable sizing of the user base)
Okay, if I can take a stab in the dark...
I've gone ahead and created a plugin that checks for updates, but it relies on the plugin creators to modify their core plugin file, and add a plain text file to their server somewhere. Bear with me here...
1) The developer edits their plugin file, adding a line which gives the location of the text file with the update info, for example:
Update URI: http://pali.sirimangalo.org/wppun.txt
This could go in below the homepage line which reads:
Plugin URI: http://pali.sirimangalo.org/
2) The developer creates the appropriate file with two lines (can always add more...), for example:
version: 1.1 location: http://pali.sirimangalo.org/files/jawp.zip
The first line is the latest version available, the second line is the location for downloading the latest version available. We could add lines for supported wp version, no problem. For this example, I've kept it simple.
3) The end-user downloads and enables the wp-update-notifier plugin, here:
Much code was borrowed from:
Plugin Name: WP-Plugin List Plugin URI: http://www.wiso.cz/2006/09/20/my-first-wordpress-plugin-wp-plugin-list-10/ Description: WP Plugin List is a simple plugin to allow yout post your current WordPress 1.5+ Author: Martin Wiso Author URI: http://www.wiso.cz/ Version: 1.0
4) The end user downloads the modified version of their favorite plugin. Here's a simple (read: useless) plugin which simply adds a message text to the admin screen like the "Hello Dolly" plugin:
5) The end user goes to the admin panel, clicks on plugins and then the updates submenu, and gets somethings like the following screenshot:
Clicking on the new version link should, if all goes well, download the new version of the plugin. It's a start anyway...
Typo3 does it, Firefox can, too, why shouldn't WordPress? :-)
Definitely simplifying a Blogger's life.
plain/text is crap as it can't be cached by wordpress. i'd rather prefer to use simple xml-files. magpieRSS could do a conditional get (thats included in wp and stored in the db), so you don't produce that much traffic and slowification in the admincp
maybe one should push the idea of get_plugininfo() (that could be easily accessed like bloginfo() is at the moment).
this could simplify plugin-versioning (thus updating)
localization (what is the .mo named like? plus where is it), and of course writing plugins. sad it has been assigned into a future verison.
@_erik_ I agree that text files aren't the best idea, I guess Yuttadhammo suggested it as getting developers to create an extra xml file would be more of a challange than an small txt file ???? :-S
The WP team have integrated the plug-in section here into the SVN, if they would be so nice as to provide a url like http://wordpress.org/extend/plugins/akismet/latest which returned the latest stable build from the SVN, then I think we might be onto a winner :-)
I think this should be something built into core WordPress. Ideally, I would see it connecting back to this site and simply grabbing the latest stable version listed here. If a plugin isn't here, too bad, no update checking for them.
Oh snap, I just read the comment from linickx right before me, he's suggesting the same thing basically.
Seems like the ideal thing to do now that we have a central plugin directory here at wordpress.org.
This topic has been closed to new replies.