What we hate most about Movable Type isn’t that we actually have to pay for a multi-user license of what should ideally be free, but that we have to live with dreaded White-Screen-Of-Deaths (WSODs) and Internal Server Errors (Error 500). Yes, yes. The Internal Server Errors bug should have been resolved already. But as the announcement says, only hosts that actually bother to update their CPanels (or whatever command panel software they bundle in with your hosting plan) will actually resolve the bug.

And yes, our host isn’t one of these hosts that keep up with this kind of relatively minute mySQL updates. Apparently, many hosts haven’t resolved this problem either - leaving quite a number of frustrated MT users (normally office users). In fact, even when this “isolated bug” is resolved, other errors could as easily pop-up.

Switching hosts is an alternative, but it’s an irritating one. How we wish we could just abandon MT for WordPress right now! Now, that’s a great piece of trouble-free, and financially-free software.

P.S. A blog platform switch isn’t practical given the SERP losses that we would have to shoulder.