Installing WordPress on IIS

Okay all - I know it’s been a while since I’ve been around - and I apologize for that.  I see the spammers are bastards and are posting like crazy here, greeeeaaaat.  Thanks a lot, assholes.  I have to move hosts in the midst of probably my busiest season ever, I take a teensy shortcut and there you go.  You all suck.  (The spammers, I mean.)

ANYWAY…

So, I had the joy of trying to install WordPress on a Windows IIS Server.  Now, I think it’s no secret that I hate Windows servers.  It’s a personal preference, really.  Mainly because any time I’ve had to deal with a Windows hosting client, the reason the host chose Windows is because they have no idea what they’re doing, and the “tech support” would disappear every time I had a question about some stupid configuration setting, and then come back three weeks later asking “Did you get it figured out yet?”

Granted, there are some people out there who know what they’re doing.  But in my experience, IIS sucks unless you know what you’re doing - and 99% of the time, the people behind the server don’t have a clue.

That rant aside - I had a client who needed WordPress installed on IIS.  Two-and-a-half weeks later, I got it installed.  For those of you having this issue, I’m going to tell you what made the difference for me, so you don’t have to go through what I did.

Back on Track

Halle-freakin’-lujah.

Okay, I know the theme is still your default “Kubrick”, and my categories are gone (due to a REALLY stupid mistake on my part), but it’s back. Posts, comments - it’s all good.

But hey, it’s Saturday, and I have stuff to plant. So I’m taking a …

Oh this is awesome.