Fast, manual, incremental updating of WordPress
Automated disclaimer: This post was written more than 15 years ago and I may not have looked at it since.
Older posts may not align with who I am today and how I would think or write, and may have been written in reaction to a cultural context that no longer applies. Some of my high school or college posts are just embarrassing. However, I have left them public because I believe in keeping old web pages alive—and it's interesting to see how I've changed.
WordPress recently released 2.3.3 as an urgent security fix for 2.3.2. Rather than wiping all non-configured files from the tarball, and re-uploading said files by FTP, I used the fast and precise approach: Only upload changed files.
This assumes that you're only updating to the latest tarball (or zip file) from the WordPress download page
Now you have a list of what files changed.
Some folks are going to complain that I could do this all automatically by doing a SVN checkout from WP's Trac to my dev site. And that's great! If you write about how to do that, I could do this all automatically by doing a SVN checkout from WP's Trac to my dev site. And that's great! If you write about how to do that, I'll link to it whole-heartedly.
No comments yet.
Self-service commenting is not yet reimplemented after the Wordpress migration, sorry! For now, you can respond by email; please indicate whether you're OK with having your response posted publicly (and if so, under what name).