I’m pretty sure all the other WordPress bloggers out there noticed the shiny bar in their WordPress admin panels, announcing the release of Wordpress 2.3.2, about 18 days ago.
If there is one thing I hate at the moment, it’s having to upgrade my blog while I’ve done custom modifications and copy all those files by hand. To save all you other folks some hastle, I’ve looked at the actual changes and the adjusted files. Based on my findings I’ve created a simple bash script that updates your blog (and makes a backup before doing so
)
Beware: the following commands are from WordPress 2.3.1 to WordPress 2.3.2. Use at your own risk.
Shell instructions
- Login to your box with ssh
- wget http://www.labcoding.com/scripts/wp-update && chmod u+x wp-update
- ./wp-update -d /full/path/to/your/wp-blog/root
You should get the following output:
$ sudo ./wp-update -d /var/www/html/www.labcoding.com/
Grabbing the latest version from WordPress.org
–19:19:13– http://wordpress.org/latest.tar.gz
=> `latest.tar.gz’
Resolving wordpress.org… 72.233.56.139, 72.233.56.138
Connecting to wordpress.org|72.233.56.139|:80… connected.
HTTP request sent, awaiting response… 200 OK
Length: unspecified [application/x-gzip]
[ <=> ] 884,822 50.06K/s
19:19:30 (51.83 KB/s) – `latest.tar.gz’ saved [884822]
Creating backup of current WordPress files, just in case…
Your blog has been updated to 2.3.2! No running of update.php is needed for this release.
$
NOTE: To be on the safe side I’ve added checks to see if the SOURCE version is 2.3.2 and the DESTINATION is 2.3.1. Also, a backup is created in your home directory, just in case.
Also, i run this command through sudo because of certain rights on my filesystem. Be sure to check the file permissions and ownership after your done.
Enjoy!
June 21st, 2009
1 Comment at "Upgrading from WordPress 2.3.1 to WordPress 2.3.2"
[...] upgraded my previously mentioned version of wp-update. A simple bash script that only updates the files that were changed in the [...]
Comment Now!