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)
That’s a weird error. And I don’t think it’s caused by the plugin… Might be something with your browser or server configuration. Try it in a different browser perhaps? Or maybe the plugin didn’t upload properly to the server, you could try uploading it again.
hmmm… I have a bunch of other plugins running (thats why I need yours…
) and no problems. Your plug can be installed/activated, but whenever I try to autoupdate a plugin, this 406 error shows up… Standard Firefox 2.x on Mac, standard Linux hosting at Hostnine… nothing special.
Will try some more things tomorrow and report back!
Thanks for your lightning-fast answer!
This might also help you – HTTP 406 Error
There’s also a less radical solution.
Hi White Shadow, I that I’m not the only one. If you need mo testerz holla at me (dont worry I’m french, my english come from songs I heard, lol). I’m really interested on the special debug version too! I’ll be back…(from movies too)
@MacVids : Here’s something to try -
Create a .htaccess file in your “one-click-plugin-updater” directory and put these lines in it :
@LGDA : Try this debug version. I’ve also made a few changes that might make it work… maybe.
Shadow, you are da hero!
I killed this mod_wannabesecure-thingy, and your plug now works on the shared hosting as smoothly as it did on my own vserver before!
Thanks a bunch, mate!
Great, congratulations and such
Ok, so, it works better, I updated the all in one seo pack but I had an error report, I uploaded it here for you:
http://www.legrenierdalice.com/_blabla/blogpix/errorrepot.txt
I just had to activate the plug and everything seems to be ok, i cheked my plugin folder with filezilla, it looks ok.
I dont really understand the error report, if you have the time to give me a solution to have it working 100% it would be cool, if you can.
Thank you!
The updated plugin wasn’t activated automatically because you’re running the debug version. Everything else seems more-or-less okay in that report (at least it works, apparently). To disable debug mode just open one-click-plugin-updater.php and change the line that says “var debug = true;” to “var debug = false;”.
Works fine, thank you very much!
It’s super. Now I don’t waste time on updating plugins. Thanks a lot!
I get this error after I fixed the permissions and cannot figure out what temp file this reffers to. Seems like a great plugin if we can get it working. Any suggestions?
Error : couldn’t create a temporary file.
The plugin needs to create a temporary file to store the new version (a zip file) before it can extract it. It uses a built-in PHP function to determine where to store the file (tempnam()).
Do you have enough diskspace left on the partition that holds the temporary files? And what OS does your server have?
Actually, scratch that – just try the version I uploaded now. I suspect it might work better.
The updater doesn’t update for me the plugin page just reloads its self without any error messages.
I already set the permissions to the plugin directory. What line do I need to add to my php.ini?
Have you got the latest version? Some other people have reported the same problem before, but it should be mostly fixed in the current version.
If you have the latest version, you can open the one-click-plugin-updater.php file and change the line that says “var debug = false;” to “var debug = true;” to get a detailed report of what the plugin tries to do.
As for the php.ini lines, I don’t know what you’re talking about
version 1.1.6 .. I set debug true and got a long list of text. The following looks interesting:
gzopen() found, will use PclZip.
Error: PclZip reports failure. ‘PCLZIP_ERR_BAD_FORMAT (-10) : Unable to find End of Central Dir Record signature’
gzopen() not found or PclZip error. Running unzip instead.
unzip returned value ‘0′. unzip log :
Array
(
[0] => Archive: /tmp/PLGXhAsVH
[1] => peters-custom-anti-spam-image packaged: Mon, 03 Dec 2007 03:40:03 +0000
)
extractPlugin() succeeded.
Plugin extracted, deleting temporary file ‘/tmp/PLGXhAsVH’
Upgraded plugin was not active. Will redirect back to plugin list.
Interesting, but I can’t think of anything at the moment :/
I am still getting the same cannot create tmp file error message.
Any other suggestions? The site is hosted on a linux system, pretty standard settings. There is plenty of room on the partition to create the necessary files.
Here is the error again:
Error : couldn’t create a temporary file ”.
I just updated the plugin, but still have the same problem. The plugin I am using right now is version 1.6.
As I wrote above, you can try to “open the one-click-plugin-updater.php file and change the line that says “var debug = false;” to “var debug = true;” to get a detailed report of what the plugin tries to do.” That might give you more information about the error.
Other than that, I don’t see what could be wrong. Maybe it can’t create the file because of file permissions (seems very unlikely)? Hmm.
sorry that was version 1.1.6
Will save the new version archive (zip) to a temporary file ”.
Warning: couldn’t create a temporary file at ”.
Using alternate temporary file ‘/hsphere/local/home/world/theworldbyroad.com/wordpress/wp-content/plugins/one-click-plugin-updater/PLGPBZzrg’.
About to extract the new version.
I also changed the permissions of the folder for the plugin to 777.
I see that for some reason it couldn’t find the system’s temp folder, so it tried to use the plugins own folder to store the temporary file, which worked because you changed the permissions. So, problem solved
(more or less; you can set “debug” to false again.)
I’ll check if I can do anything about it failing to locate the system-wide temp. directory. I have edited the log you posted to only leave in the important parts – this page is getting very large…
It executes now, but the plugin is not updated after it executes. Below the plugin there is still a notification that the plugin is not up to date.
Have you tried setting the target plugin’s directory and/or files to 777? I know it’s not very secure, but if it works then, we can at least be sure it’s a file permission issue.
Hi, I’m the author of OneClick installer (http://anirudhsanjeev.org/oneclick/), the next version of oneclick will incorporate this along with many new features. Would you be interested in merging the code or the projects and/or contributing to development?
email me at anirudh $at$ anirudhsanjeev $dot$ org
Email sent.
[...] Wordpress Automatic Upgrade que actualiza el WordPress en unos 5 o 6 clics desde el administrador y One Click Plugin Updater que actualiza plugins de la misma [...]
I haven’t tried the one-click installer in a while (since right after the plugin competition) but it never worked with the simplicity, power, and effectiveness of the single click plugin updater. So, I would love to see these two plugins work together, but what I’d like to see is the single-click updater influence the one-click installer. That, or keep them separate.
That’s just me.