« Attack of the Killer GPUs | Main | Multiple Mac (Tiger) Logins for Testing »

MovableType Weirdness Again

Listen to this articleListen to this article

Some of you may have noticed some decidedly odd behaviour with the blog the past couple of days: you couldn't post comments; and I couldn't post new entries. Somehow—I't's still a mystery—things just stopped working. The suspicion I have is that there was some problem with the Berkeley DB files after a server upgrade but I can't be sure.

For the most part, MT behaves itself pretty well—to-date I've hardly had any problems—but when I do have a problem it usually requires quite a bit of effort to work out what went wrong and fix it (if possible).

So anyways, after unloading, reloading, repairing, upgrading MovableType and performing all manner of other unix witchcraft—most of it performed at 3am—things are finally back up and running again. The next step will be to migrate from Berkeley DB to Postgres in the next day or two so there may be a few more minor interruptions a long the way.

The upshot of all this is of course that I'm now running on the latest (and hopefully greatest) version of Movable Type. Having said that, blogging ain't my profession—god save you all—so I'm not sure that an upgrade of MT actually buys me much except some more long nights attempting to work out why things stopped working.

Everything seems to be in or-der but if you notice any more weirdness please let me know, otherwise I'll get back to eating my orange sher-bert

Update (1 September 2005): Ahh yes, I knew it was too good to be true. Robert kindly informs me that comments are still busted: you can read them just not post them. After a little investigation, it looks like there is some problem with the new version of SCode. It worked for me because I'm authenticated on my own blog but it doesn't seem to work for anyone who isn't authenticated. Sheesh! Maybe I need to write a suite of tests for my own blog!?

Thankfully, the solution is pretty simple. Thanks to the author of the plugin who responded to my forum posting: The file SCode.pm contains the "$app->{requires_login} = 1;". This should probably read: "$app->{requires_login} = 0;".

Update (2 September 2005): All converted to PGSQL now thanks to the truly awesome support people at MovableType. They ironed out the last little issues with upgrading and now I'm off Berkely DB. Hopefully this now means no more file corruptions.

TrackBack

Listed below are links to weblogs that reference MovableType Weirdness Again:

» It's everything but easy to upgrade Movabletype 3.2 from dense
Despite Six Aparts warm promises of the easiest upgrade ever, upgrading Movabletype to version 3.2 is everything but painless. To be frank, it's a full featured pain in the ass. I'm not sure wether they do this by purpose or... [Read More]

» Painful upgrade to Movabletype 3.2 from dense
Despite Six Apart's warm promises of the easiest upgrade ever, upgrading to Movabletype to version 3.2 is everything but painless. I'm not sure how well their strategy goes, leaving enough users out there without a clue, hoping they will be... [Read More]

Comments

I upgraded to MT 3.2 last night as well; the main things that seem improved are the plugin management and the funky templates available with the StyleCatcher plugin.

One thing I can say: I've had less problems with a MySQL backend then I did with Berkley DB.

Ok...comments are working again...Shame I had to ditch SCode. Hmmm.

Of course, you could always move to Wordpress :-) Upgrading always seems to be pretty smooth for me.

I investigated that as an option but I have multiple blogs and wordpress only supports one per installation. :(

Post a comment