So I have a client I’m developing a website for. The client has been great to work with, and we’ve made good progress on the new site. But there was a problem: The client kept complaining that he couldn’t reach his site — he was getting “not found” error messages. He could, at one point, get to the site without the “www” — which was particularly strange because one of the first things I do on a new site is implement a 301 permanent redirect from the non-www to the www version of the URL.

I checked the DNS settings on the server. I did traceroutes from my computer. I went to websites in other parts of the country and did traceroutes. I pinged. I double-checked and triple-checked the nameservers. Everything was exactly right, and I was tearing my hair out trying to figure out why the client couldn’t reach his own site.

Finally, it struck me: The client was searching for the site, using the search box on Yahoo and Comcast.

Once I told him that his site not indexed yet (because it’s brand new), and that he needed to enter the URL directly into the browser’s address bar — voila! Problem solved.

This is one to file away to deal with future “can’t reach my site” issues.

Note to website designers and developers: If you ever have clients who can’t reach their site, check to see if they’re searching for it.

I received a well-written, but completely absurd, spam e-mail yesterday. It started out by saying:

“I was looking at websites under the keyword face lift cape coral and came across your site tropicalwebworks.com. I see that you’re ranked #1 on page 18 in google.

I am not sure if you are aware of why you’re ranked this low but more importantly how easily correctable this is.”

(Read on: A Face Lift in Cape Coral?)

WordPress version 2.6 just came out. I installed it from scratch on a new blog (Fix My Knee, a chronicle of my many knee surgeries). The installation went beautifully, and I liked the new Admin interface.

I decided I should upgrade Tropical Blogging to the new version. Of course, I made sure I had backups of all the files, and a backup of the MySQL database, before doing anything.

I downloaded a fresh copy of WordPress, de-activated all my plugins per the instructions, followed the instructions to upload the files, and then followed the instructions to update the database. (Which basically consisted of clicking an “Update” button.)

All my posts were still there. But all the categories were missing! No, actually, they weren’t missing — they had numbers but no category names, and none of the posts were assigned to any categories.

I found a couple of posts on the WordPress support forum about this, but they weren’t any real help. The database structure had changed — there was no longer a “categories” table in the database. There’s a “category-to-tag” converter and a “tag-to-category” converter in the admin area, and I tried both, but neither one did anything.

I ended up manually re-creating each category, then manually assigning each post to appropriate categories. I almost just went back to my old WordPress installation, but I have this weird obsessions where once I start down a road I really hate to give up and go back.

I also discovered that my theme doesn’t work with this new version. It appears to work, initially — the home page of the blog loads just fine. But clicking any of the posts to “read more” results in an error. So I have to use a different theme, or get into troubleshooting that theme. Bah!

I’d like to update my clients’ WordPress-based blogs, but I sure don’t have time to muck around doing crap like that. For now I’ll take a pass. I hope WordPress addresses this issue, or those blogs will just forever have to be stuck on whatever version they’re currently runninng.