The automagic version does not like my blog in it’s current state with the lack of FTP, I don’t want that turned on, got no need for it. I’m wondering how well the automagic WordPress plugin updater works if the environment was how it expects, but do not feel like turning on unnecessary daemons, or make a dupe install of my blog to test that stuff.
OK, this is the WordPress plugin update process for my blog as seen from running the history command. It’s very very very simple, but manual on the command line
500 cd blog/wp-tmp/plugins/ 501 wget http://downloads.wordpress.org/plugin/bad-behavior.2.0.26.zip ; rm bad-behavior.2.0.25.zip 502 unzip bad-behavior.2.0.26.zip 503 rm -rf plugins/bad-behavior/ ; mv bad-behavior plugins/
That’s it the plugin has updated! It’s just that simple except for WP-Super-Cache, where it looses information when you remove the folder on 503. You will likely just have to chmod 777 wp-content, and then chmod back to what it was before.
Now let me explain the whole process, but first a couple key things;
- the plugins folder on 500 is just in any temp directory
- on 503 the plugins is a symbolic link to the actual WordPress plugins directory.
- I have a really BS manual link getting process. It’s a cut+paste from easiest place to get the link from. Right now that is from the blog’s plugins page. Go to the plugin with an update. Click “View version X.x.x’s Details” then look for and click “WordPress.org Plugin Page »” ; then copy the download link.
500, change directory to my blog's temporary directory for plugin stuff 501, get the new plugin zip file, after the manual link process above. ; remove the previous version .zip file 502, unzip the new version of the plugin, look for the "new versions" directory name 503, recursively remove the older version, "plugins/bad-behavior/" folder; then move the "new version" in place.

