May 17, 2002
Untitled
It’s a pain in the pants when you have to migrate one of your externally hosted sites to another server because one ISP has been swallowed up by another. It is also an enormous pinch in the toches to have development on that site frozen for a better part of a week because the actual time of migration is not known. However, the most significant boot to the bottom is when the migration actually takes place, during the middle of a business day I might add, and you suddenly realize that your new ISP has neglected to mention that server-side includes aren’t activated by default. Of course, this wouldn’t be an issue if your site hadn’t used SSI for the primary navigation, the generic page footers, and a significant portion of the product display pages. Not a huge problem, you say to yourself in a manner positively brimming with self-confidence. After all, both servers are running Apache and naturally the server configurations will be similar since they’re migrating a couple hundred other sites besides your own, right? They wouldn’t think of forgetting about something as fundamentally useful as include file support would they? Of course not. Just stuff a “AddHandler server-parsed .html” declaration into the .htaccess file and we’ll be back in business. That’ll show ’em. And you know, it would’ve shown them too, except that the ISP also neglected to mention that SSI has been completely disabled for security reasons. And they weren’t about to turn it on for you or your little dog either. No exceptions. That’s ok you grumble, somewhat subsonically. I was going to convert the entire site to PHP anyway. Just not this afternoon. Feh.
This item was posted by .
Categories:
Leave a comment or send a trackback from your own site.