now that i can actually post again…

for those of you who have been paying attention, three days ago i switched host providers. i found one i liked (and i really like them, but that comes later), and switched the DNS settings for to point to the new nameservers. a day later, two days ago, the domain status was “ready”. for most people, there was no visible seam between the old server and the new one, unless you happened to hit for a couple of hours during the time when your nameserver was updating, but since it happened in the early hours of the morning, the probability is fairly low that anybody even noticed.

however, when i hit the URI, i got the old host server. i sort of vaguely anticipated this, and actually waited another 24 hours – so now we’re down to yesterday – before i started futzing with things. at first i thought it might be because the old IP address was stuck in a browser or network cache somewhere, but i rebooted my entire network, down to the router, and it still showed me the old host. this morning it still showed me the old host server, so i called the provider and discovered that, apparently, they’ve got their DNS servers set to manually update instead of automatically getting the most recent data every 24 hours (like everybody else in the motherfucking world – yet another reason why i switched host providers). once they had manually updated their DNS servers, everything worked like i thought it should.

the subdomain, however, was a different thing entirely. i knew that there was going to be a bit more difficulty moving the blog because of the database. i managed to download a SQL dump of the database, but then i discovered that myPHPadmin on the new host has a limitation of 8mb on files that are imported to a new database, and the database dump that i had was 12mb… and i had no way to access it other than to open it with a text editor. i found a php script called BigDump that was supposed to import large(ish) files to a new database, but i kept getting this weird error that seemed to indicate that the version of SQL that had created the database that i had downloaded was incompatible with the version of the version of SQL to which i was importing the file, in spite of the fact that they both appeared to be SQL 4.0.

at that point, i called the tech support people at the new host and gave them the problem, and within a few minutes they had figured out that the SQL from which i had exported the database had included CHARSET information that was default on their database host, had removed the offending lines of code from the database manually, and imported the database for me.

in other words, the tech support people actually helped me solve a problem, unlike the previous host’s tech support people who, with one exception, were of the opinion that if i didn’t know how to do it, why should they help me?

i’m still having a little difficulty figuring out where the email that’s supposed to be sent when people access the feedback form is going, but i’m fairly confident that everything will be working again in a day or so.

the difference: old host = 500mb of web space, tech support people who don’t actually help, $250 a year. new host = 500gb (half a terabyte!) of web space, tech support people who know what they’re talking about, $120 a year.

i like my new host! πŸ™‚