Like I just said – “if it goes off without a hitch then I’ll be very surprised!”. I am not surprised. While it seemed to go down well, there was one very annoying technical problem (and once browser problem). And this is really bugging me now…

So before the upgrade, as you all know, the main page of the blog was located at /blog. And all posts under it started with /blog. That was all fine, everything worked well together and peace was abounds

Now, it’s a different story. First thing after upgrading, everything would work, except the blog home page. /blog would cause IE to say it can’t display it, and Chrome would complain about a redirect loop. All posts, archives, categories, tags etc. were completely fine, just not the main page. Changing the permalink to /rants, as it is now fixes the solution, but now going to /blog leads you to that post I made about the joke K8 and Maxi had about being sent letters by the “Blogging Commission of Ireland”, since it’s permalink starts with blog.

The underlying point is this, and this is the big thing – on my server, I don’t have WP in the root directory, but rather in the /blog directory. Up until half an hour ago (or so), everything worked fine and dandy. Accessing a file that actually existed in the directory brought me to it, and anything else was treated as a permalink and processed. Now, it’s just fecked.

I’d say the simple solution must be to just change the folder in which WP resides, so that I don’t have to change the permalinks to everything and have Googlebot try and re-archive everything all over again (as it was when I originally made the blog a “sub-section” of my site). But I still want to know why on earth I’m having this issue in the first place!

UPDATE @ 16:47 - Right, core directory re-named and blog home re-permalinked. WPG2 gave out a little though, since it’s too stupid to use the siteurl function…