Trapped in Limbo

Warning, cruddy code terminology sure to give anyone a headache ahead…

Welcome to our new server. Don’t get too comfortable. See, we chose this host because they didn’t do cruddy stuff like suPHP or PHPsuexec. In fact, they promised us they weren’t going to use such crudware on their servers.

So, a week or two ago, guess what we got in our inbox? Yes, a notice that our new host was going to deploy suPHP. Gee, thanks for keeping your promises.

We decided to go ahead this morning (at the cost of a full night’s sleep) with the move. Our new host assured us that their new version of suPHP which fixed all the Path_Info issues that screw up our Knowledge Base. So, we did the switch this morning.

Guess what trouble we’re having right now? You guessed it, screwed up Knowledge Base links, stemming from a problem with Path_Info… caused by suPHP.

So, we’re really ticked at this new host, they don’t know what to do… we can’t re-open the forums until we’re on a server that we’re going to be on for the rest of the month (and hopefully year… or two). So, we’re stuck in a read-only mode basically.

Wondering what host this is? InMotion Hosting. Hope they like the advertising. They’ve “escalated” the matter. But we’re coming up on eight hours without a status update.

So, sorry. But right now, I really could care less. We’ve had two botched server moves… neither of which was our fault, and this time we even went the extra mile to get assurances on a code basis.

I may have to go on vacation until I can get readers to pony up for the cost of these sleepless nights… it’s just not worth my time to cut hosting costs… even if it is cutting them 90%. And no, I’m not joking. Bad news is, that “ponying up” will probably come in the form of full-page advertising (meaning, you can’t access the site until you watch an ad… yeah, I know, nobody wants that, but we may not have a choice).