MovableType, Kung-Log and me
I did something to cause MovableType to corrupt its databases. I was posting an entry using Kung-Log and I think I put in a Ping URL that was for a blog entry and not for traceback. After I did that, I couldn't add any more entries. When I visited the mt.cgi, I saw perl warnings from Serialize.pm.
None of my incantations of db_dump and db_load were able to restore, so I saved a copy of the archives, re-installed MT, and reposted the entries.
Wheeeeee.
This very tardy update is because I was out of town when Adrian replied and I hadn't had a chance to respond.
Adrian, I didn't mean to imply it was a bug in Kung-Log. I was more frustrated with myself and MovableType.
Since KL does not manipulate the datebases – it only communicates with MT using XMLRPC – I really find it highly implausible that caused your database to fail. I went and tried to replicate your bug (posting an entry with a blog entry url), but didn’t get any corruption to occur.
Dude, use a real database. :-) I’m using PostgreSQL on mine.