So, the last post I put up simply stated that I had failed in installing Worpress 2.6 on my own server. The permalinks were messed up and it looked a lot like an issue that a lot of people were having.

But, the catch was: the problem persisted when I tried to use Wordpress 2.5.1. Hmmm…wonder what’s up.

So today, I started thinking that it might be an Apache issue, rather than a Wordpress issue. So, taking a break from a massive project I’m doing (only so much performance data you can process before brain freeze), I started to poke around.

AllowOverride All

That did it. I was not letting Apache read the damn .htaccess file that Wordpress installed.

Excuse the thudding of my head on the desk.

Many apologies to the Automattic team. This user haz th dumb.

I decided over the weekend to have a go at running my own install of Wordpress 2.6, with an aim to perhaps hosting my own blog again, with the obvious gains in flexibility and monetization.

Let’s just say that it was frustrating.

The most frustrating part was the permalink issue. All known and posted fixes failed to resolve the issue of getting the permalinks to match those seen in this blog, which is the content I would be migrating. There is no clear and simple fix for those of us who just want the software to work, without having to spend two hours hacking.

I will try again when 2.6.1 is released, but it strikes me as odd that this made it out the door. However, I have seen worse unintended features appear in released software.