Textura Design is a creative force specializing in business blogging for clients big and small.

Textura Design Blog

The Dreaded Movable Type Internal Server Error

posted by DL Byron on September 09, 2004

New site features, including a store/product blog, and other changes we’ve rolled out have been overshadowed by the Dreaded Movable Type Internal Server Errors. I’ve troubleshooted everything I can think of and now it’s time to replace the whole system - there’s a corruption somewhere. So, this week, I’ll update to MT 3.0 and see how it goes. Until then, the commenting system is buggy and other problems may occur. For reference, see Makiko’s Movable Type Mystery.


The Dreaded Movable Type Internal Server Errors have been corrected. So, when posting a comment, the user doesn’t get a 404. However, a new, not as dreadful “Exiting subroutine via next at lib/MT.pm line 289” is occuring. Working on that …

other posts tagged:


Sep 12  |  Geek said:

Did you get anywhere? I’m getting the same errors on my blog with a new install of MT3.

I’m just glad I decided to make a new install in a separate directory and not udpate my current blog… I’m thinking of switching too. This is just too much for a tool that used to be really simple and really robust. Now its just too flashy… :\

Sep 12  |  -b- said:

I did, see the design category archive for more posts. What Iíve had to do is stop using plugins. Unfortunately, that means, I have to go back and convert all Markdown formatted entries to html or text or live with the errors. The errors occur whenever the homepage tries to rebuild.

Sep 12  |  rob said:

so it’s the plugins you think? I just started having the problem about a week ago, and made my way around it today by exporting+importing+setting up another blog. frustrating to be sure.

Sep 13  |  -b- said:

I think that’s what I’ve narrowed it down to. What I’ll do next is reformat all Markdown entries, remove the plugin and see what happens. Instead of the export/import/setup option when this started happening, I upgraded to MT 3.0, which solved part of the problem, then the unitialized value started happening and I found it in my activity report.

Note: comments are closed.