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)
[...] upgrade to the newly released Wordpress 2.8. The easy part of upgrading was I was able to use the Upgrade plugins with a single click, install new plugins or themes from an URL or by uploading a file, see which [...]
Hey White Shadow
Thanks for all the hard work man! Looking good so far.
something went completely nutz after the update last night…
whatever the screen on admin front-end I am I get the message:
Warning: Invalid argument supplied for foreach() in /public_html/wp-content/plugins/one-click-plugin-updater/oneclick-plugin-updater.php on line 633
and if I go to the installed plugins page, I get tons of that… any idea?
Might be fixed in 2.4.9.
thanks yea….
had some problems with the latest version on 2.8 when mass updating, several plugins didn’t get reactivated, possibly all, didn’t pay that much attention.
is it jsut me or has anyone else seen the same problem?
[...] One Click Plugin Updater: WordPress (since v2.7) has plugin update functionality, but it requires multiple steps with first needing to fill FTP password. This plugin not only makes upgrades a one-click affair, but also provides an easy way to install plugins / themes. [...]
Good job with this plugin, easy to use, works great, thanks
[...] Untuk perubahan themes ini memerlukan Plugin One Click Installer berupa ZIP File yang harus di download terlebih dahulu, silahkan ambil filenya: KLIK DISINI. Atau bisa download menuju penyedianyanya langsung KLIK DISINI. [...]
Why the OneClick Plugin Updater 2.4.9 doesn’t works well on my personal site once I upgraded to Wordpress 2.8…??
It can updates the plugin(s) but cannot remove the “There is a new version of [pluginname] available” statement…
Why should I do?
For one, you shouldn’t leave identical comments on four other posts. I get the comment notification either way.
I don’t know exactly why that would happen, but I’ve uploaded a minor uptade that might fix the problem. Now the message(s) should go away once you update a plugin.
Sorry for your inconvenience… /(-.-)\
I’m too panic about that..that problem came on my busiest time..
Sorry..
Waiting for your help…and I’ll report it to you ASAP…Thanks…
Hmm..not yet resolved..
The updates announcement still showed up below the plugin line…
But, the statement go away if I try to deactivated and activated OneClickPluginUpdater after I updates another plugins..
It can resolve the problem but wasting the time if another plugins updates are coming everyday…
So?
Not yet resolved with your 2.4.11 version…
The update statement(s) still showed up after a plugin(s) has(have) been updated…
Open in new tab to view the screenshots of the problem…
Don’t forget to tell me if you has finished the screenshot download so I can delete that screenshots…thx…
Screenshot 1
Screenshot 1
What can I help?
I’ve got the screenshots. However, I’m unable to reproduce the problem (and thus I can’t fix the bug either). The update notification always goes away when I successfully upgrade a plugin.
Hmm…so, what can I do? (-?-)
The problem come to me on every WordPress installation on my mossackanme.web.id server, too…not only on my OpinionBlog…
Are debug mode can help us?
The debug mode would show you more information about the installation/upgrade process, but I doubt you’d find anything relevant there. I’m sorry I can’t suggest anything helpful.
Upgrading several plugins at the same time doesn’t work. It redirects me to the white screen after each update.
I think it’s timing out during the upgrade. Turn on the debug mode in Plugins -> Upgrade Settings and see at which point does it stop (note : when in debug mode, the updater will not reactivate the plugins it updates).
[...] All in One SEO Pack, Bad Behavior, Cleaner Gallery, Enhanced WP-ContactForm, Google XML Sitemaps, One Click Plugin Updater, Shadowbox JS, Twitter Widget Pro, wp-cache, WP-Cumulus & WP Widget [...]
And whats new in new builds of plugin? Where I can see changelog?
I’ve been getting this error on my php error log when trying to update multiple plugins: [12-Jun-2009 03:47:52] PHP Warning: Invalid argument supplied for foreach() in /home3/proveiss/public_html/wp-content/plugins/one-click-plugin-updater/oneclick-plugin-updater.php on line 633
when I click the Upgrade Automatically button, it returns me a 500 server error page and tells me to check the log – which shows the before mentioned message
hmmm there were 2 plugins for upgrade: the first time it gave me an error, but actually upgraded one of the plugins… next time didn’t gave me any error at all and upgraded the other plugin…
@ iMike : See the revision log.
@ JohnnyC : This should be fixed in the next minor version.
Resolved with your 2.4.13..!!
I don’t know what really being happened,,bu thanks for your works…
GodBlessUs.. \(^o^)/
Good job with this plugin, easy to use, works great!
thanks!!!
Hi, can you fix 500 Internal error in plugin and update Firefox addon ? Thank you. Sorry, I don’t speak english.
The 500 error is the most despicable one, it doesn’t give any clues about what might be wrong. Offhand gues – maybe you could try fiddling with your file permissions in /wp-content/plugins/, see if the plugin actually has write access.
I’ll put updating the addon on my to-do list. It probably won’t be very soon, but I’ll get around to it.
hey WS, I figured one thing today when upgrading some plugins… not all plugins give the 500 error, and even when the error happens at my site, all the times it succesfully upgraded the plugin, but didn’t re-enabled it back.
Today it happened (already upgraded WP to 2.8.2) when I tried to upgrade Lifestream to it’s latest version. I got a 500 error, but the plugin was upgraded – it just wasn’t re-enabled.
Along with Lifestream a couple other plugins were asking for upgrade, They weren’t upgraded when the 500 error happened, so I clicked “upgrade all” again, and everything went just fine, no error, and plugins upgraded and enabled correctly.
Hope this can help you out solving this 500 nightmare! =)
If it’s limited to certain plugins… Memory exhaustion comes to mind – some plugins are much bigger than others, so downloading/unzipping/updating them could make the updater use up all available memory and crash. Check the download size and/or directory size of the plugins that upgraded correctly and those that didn’t.