Aldoblog

I am in the process of upgrading Aldoblog to the latest version of WordPress. I think I’ve finished most of the work, with just some cleanup remaining where the new version of my formatting plug-in is behaving differently. It seems to only be affecting my longer instructional pieces, mostly for numbered lists, so the scope […]

Yet another WordPress update, and once again, no list of the changed files to make the minor update a little easier to install. Here’s a list of the differences.

Another update for WordPress, from 1.5.1 to 1.5.1.1. Here’s a list of the files that changed in this minor patch release.

I updated to WordPress 1.5.1 on Friday, after drinking a cocktail with Rochelle. Maybe not the best strategy for preparing for a software upgrade, but everything seems to be working fine. Let me know if you see something funky…

When I converted this site to WordPress, I decided to turn on commenting, and see what happened. I have gotten a fair number of really good comments, and from people I didn’t know, which was cool. I also got a ton of comment spam (most of which never made it online). Not cool.

So I did a few things about it.

OK, the new version of WordPress is going to get me into trouble. I need to get back to work, instead of continuing to fuss.

The WordPress upgrade instructions are pretty good, but they left out at least one recommendation I wish I’d heard before I got started.

I found myself unable to resist the draw of the cool. I had to go and upgrade to the latest version of WordPress.

As I have been working on this site, I’ve visited quite a few other weblogs run by WordPress, and occasionally see something that I’d like to know how to do myself. A little widget here, a list of related posts there, etc. Cool things, but nothing that says how to do them. So, if anyone ever has that thought about my site, here’s the info. (Hopefully other WordPress users will do this for their sites.)

I’ve run into a slight problem with the Staticize caching plug-in I was using to speed up WordPress on this site. It seems that $post->post_date isn’t correctly calculated on cached entries, even when you put them “outside” the cached page, and this screws up the time display on individual entries.