Single Click Plugin Updater WordPress Plugin
This plugin extends the plugin update notification feature introduced in WordPress 2.3 by adding an “update automatically” link to update notifications. When you click the link, the new version of the corresponding plugin is downloaded and installed automatically. It also lets you know which plugins have update notifications enabled.
Update 06.04.2008 : Version 2.0.1 with much more features is out. More info here.
Download it now! (37 Kb)
How It Works (In Detail)
To be able to display the new link this plugin will hide the original update notification and display a slightly modified one. Here’s what happens when you click the “update automatically” link :
- If the plugin that needs to be updated is active, it is deactivated.
- The Plugin Updater retrieves the plugin’s page from Wordpress.org and finds the download link.
- The new version is downloaded and extracted to the wp-content/plugins directory (this directory must be writable by the Updater plugin).
- If necessary, the updated plugin is re-activated.
All this happens in the background, so if everything works OK you’ll end up back at the “Plugins” tab. If there are any errors the plugin will display an error message and abort the upgrade.
Requirements
- WordPress 2.3 or newer.
- CURL library installed or allow_url_fopen enabled in php.ini. If you don’t know what that means, don’t worry - at least one of these is available on most webservers by default.
- The /plugins directory must be writable by WordPress. The exact file permissions depend on the server configuration. Read more about file permissions. 666 or 755 may be sufficient, and 777 will always work, though this is not recommended due to security risks.
The plugin has been tested and works under Firefox 2.x, Opera 9.x and, as of version 1.0.5, Internet Explorer.
Installation
To install the plugin, please follow these steps:
- Download the one-click-plugin-updater.zip file (below) to your computer.
- Unzip the file.
- Upload “one-click-plugin-updater” folder to the “/wp-content/plugins/” directory.
- Activate the plugin through the ‘Plugins’ menu in WordPress.
That’s it.
Download
one-click-plugin-updater.zip (40 Kb)
July 30th, 2008 at 10:48 pm
pls l have this errror when l want to use this plugin. pls what do l do? pls give me step by step how to correct it from scratch. lam using version 2.2.9
Will save the new version archive (zip) to a temporary file ‘/tmp/PLGWpTIYb’.
About to extract ‘/tmp/PLGWpTIYb’.
Extracting files from /tmp/PLGWpTIYb…
So far, the type is set to ‘theme’.
Need to load PclZip.
gzopen() found, will use PclZip.
PclZip failed!
PclZip says : ‘PCLZIP_ERR_BAD_FORMAT (-10) : Unable to find End of Central Dir Record signature’
July 28th, 2008 at 5:01 pm
@Grant Barrett - Thanks for letting me know. Fixed.
July 28th, 2008 at 3:36 pm
There’s a cosmetic issue caused by a conflict between WP Super Cache 0.6.5 and One Click Plugin Updater 2.2.8.
Any time there is a plugin that needs to be updated, OCPU always says that the name of the plugin is WP Super Cache, even though it places the little alert underneath the correct plugin and even though the updates work just fine. If there’s more than one plugin needing to be updated, then the alerts all say WP Super Cache Here’s a screen grab:
http://www.waywordradio.org/wp-supercache-conflict.jpg
July 27th, 2008 at 1:51 pm
Well, I don’t know. You could hack the plugin to use unzip instead of PclZip if you want - edit the line 831 :
function extractFile( $zipfile, $type='autodetect', $target = '', $use_pclzip=true
Change "true" to "false" :
function extractFile($zipfile, $type='autodetect', $target = '', $use_pclzip=false
Might help.
July 27th, 2008 at 11:41 am
I ‘ve already use the latest version !
July 26th, 2008 at 7:52 pm
@billyduc - It looks like PclZip doesn’t work on your server… Do you have the latest version of the plugin (2.2.8)? Some older versions had this problem with PclZip.
July 26th, 2008 at 7:18 pm
HI white Shadow…Your Plugin is great..It ’s help me save time very much…
But I have the problem when click to UPGRADE ALL or AUTOMATIC UPGRADE….
It return me an error…I followed your installation instruction…and have already chmod to 777…you may see my picture http://depchai1vung.googlepages.com/InstallerError.png
July 25th, 2008 at 5:12 pm
This is a great plug in
July 24th, 2008 at 8:24 pm
@Patrick Curl - The plugin doesn’t intentionally change the file owner, but any files it creates (and possibly files it overwrites, too) will be owned by the same user account under which the webserver/PHP engine are running. There’s nothing I can do about this - it depends entirely on your server configuration. most likely the problem was caused by a configuration change, too.
July 24th, 2008 at 8:03 pm
I love this plugin, but over the past few weeks it has been messing things up a bit - since the 2.6 change in wordpress.
Apparently it is changing the ownership of the files it updates, and the only way I can change them back is to contact my host’s customer support which is extremely lousy to begin with…
Is there a way to keep the plugin from changing the user?
July 23rd, 2008 at 7:57 pm
@Marcel - Debug mode should be off by default, and I’m sure it is off in the latest version. Irregardless of how it came to be enabled, you can turn debug mode off in Plugins -> Upgrade Settings. Uncheck the box “Enable debug mode”.
July 23rd, 2008 at 6:26 pm
Problem with the latest 2 versions …
“Error reporting set to E_ALL.
.
.
.
(Debug version = redirection will not happen. Script execution finished.)”
Why is it in a debug version?
July 20th, 2008 at 8:43 pm
@nurikabe - Thanks, that is actually a minor, stealthy bug. I’ll fix it right away.
July 20th, 2008 at 8:28 pm
Minor annoyance: Warning: mb_stristr() [function.mb-stristr]: Empty delimiter. in /var/www/…/wordpress/wp-content/plugins/one-click-plugin-updater/oneclick-plugin-updater.php on line 253
I should probably just hide warnings, but thought I’d let you know.
July 20th, 2008 at 2:34 pm
@Fizzgigg - Updates are supported for plugins that are hosted on WordPress.org. WordPress.org has an API that my plugin (and WordPress itself) use to find out if a particular plugin has updates available.
Hosting a plugin on wordpress.org is free; details here.
July 20th, 2008 at 1:49 pm
I still use some plugins that doesn’t work with this plugin in the sense that the plugin can’t detect if there is an update available. It’s not because of this plugin, mind you, but the other plugins.
From a developers point of view, is it hard to implement support for update plugins? Is there a faq or information about how to do it? It would be nice to try to convince the developer of the plugins that doesn’t support updating to implement it. The quest for update support, so to speak.
July 16th, 2008 at 1:45 pm
Congrats to you for the latest improvement in this plugin. The bugs have disappeared, and all is working like a charm. Very useful.
Thanks,
Chris
June 25th, 2008 at 9:43 pm
Hmm. I have wp-super-cache active on this blog, too, and it doesn’t seem to cause any problems.
June 25th, 2008 at 8:08 pm
Well… I found the problem…. I don’t know why but if ocpu and wp-super cache are both active there is the problem… however I don’t really need wp super cache so this is not a problem for me
June 25th, 2008 at 7:25 pm
Uhmm… I don’t remember if this appens after an update… I can try on another installation (but in the same server) and test it…
June 25th, 2008 at 6:19 pm
@Engelium - so this only started happening recently? I haven’t made any changes to the plugin in the last few days, so the source of the problem is likely some other software. Have you upgraded or installed a new plugin right before the problem appeared? Also, changes in server configuration might cause strange bugs to appear.
June 25th, 2008 at 5:26 pm
Hi
since a few days if this plugin is active I can’t access to the administration of WP …. I have only a totally blank page (also the sources are blank) O_o
The only way to access is delete the plugin throught FTP …. Why does this appens and how can I solve?
Tnx a lot
June 24th, 2008 at 9:33 am
[...] 插件主页 [...]
June 17th, 2008 at 12:30 pm
Can you elaborate on this “disappearance”? Does that mean that you no longer see the “Plugins” item in the dashboard menu, or that you can’t access it (how?), or that the “Plugins” tab is empty (if so, does it show at least something)? Or something else entirely?
P.S.
Sorry for not answering earlier - I’m having problems with my ISP.
June 17th, 2008 at 6:57 am
I had the same exact problem.
Help! Please!
June 15th, 2008 at 2:18 am
After installing the plugins, all my plugins dissappeared and I do not have access to them. Any help would be appreciated.
June 11th, 2008 at 5:28 pm
[...] it turns out I needn’t have worried about updating all the plugins - enter Single Click WordPress Plugin Updater. Where have you been all my WP life! Needless to say this little plugin beauty saved me from [...]
June 9th, 2008 at 1:23 pm
thx for the answer. I changed the option to 775 on the plugins settings, but maybe it was too late. I’ll change the permissions again, and as soon as a new update is available I’ll try it out again.
June 9th, 2008 at 12:43 pm
@ovidiu - I don’t think this is a bug in the plugin’s access-detection routine. As you can see from the log, the plugin actually can’t write the file in question.
However, it thinks it can write to the folder. You could check if this is correct by trying to install a new plugin using the installer at Plugins/Install Plugin. If that works the problem is most likely with the specific file(s) that the plugin can’t overwrite.
It might have something to do with the fact that since recently the plugin will try to chmod 755 any files it extracts (configured on the settings page), but it seems unlikely.
June 9th, 2008 at 9:39 am
oh, and I have one more idea: sometimes when I had problems with your plugin, I used the built in update, via FTP, so that might have reset the rights on the folders?