Update to the new service: Our gracious host does not have the latest Mysql modules running. This caused a slight pain-in-the-ass with the move from our previous assholic-host, Hostsltd. I got around my configuring MT to use the Berkeley DB_File settings. I know enough about it to understand that that (BTW, I hate that double-thing that the english language allows--Savage, you have been summoned) configuration uses static files, which can be suspect at times.

Well, I haven't been to the Mint much as of late. But today I was able to post a quickie. Interestingly enough, I happened to try to view a previous comment made by a rider and found that the comment pop was empty, even though the page had a number of comments tallied with the post. Strange, wouldn't you say?

I did some testing, a few new comments, etc. The smtp setting is fine, all comments are getting their e-mail notifications. The static index page is tallying the comments, but the comments are not viewable, at all.

I get on the live chat with Dotster, our host. They call it a blog-ware issue. I smell DB_File , and it is cooked.

I reconfigured things to a new DB and rebuilt everything. Though, some of the comments from December of last year--on, have been nuked. I have no idea why. They were missing from the export, but present in some of the static html files that get built through MT. There's no consistency in file corruption. Sorry about the loss of content.

I will perform regular exports to maintain a shred of integrity. But seriously, who thought the Mint was actually an archive of anything?

Note to the riders: your PW's have been reset to the original default when I imported the content.