Comments on: MT 3.2 Final – 500 Error Bites

By: xdanger

xdanger — Wed, 20 Dec 2006 03:31:09 +0000

Apache Timeout value IS the problem !

By: base

base — Tue, 07 Nov 2006 08:11:20 +0000

Thanks! I'll let my hostingservice check the apache timeout value .

I'll let you know if it works!

By: Erik J. Barzeski

Erik J. Barzeski — Mon, 06 Nov 2006 14:51:01 +0000

base said on November 6, 2006:

Any Luck Yet ?

Look in the comments above. Or click this to see if you have the same cause of the problem as I had (a low Apache timeout value).

By: base

base — Mon, 06 Nov 2006 14:18:21 +0000

Any Luck Yet ?

I'm having the same 500-error problems ... and would like to rebuild my individual archive ....

By: dense

dense — Sun, 25 Sep 2005 19:15:07 +0000

It's everything but easy to upgrade Movabletype 3.2 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...

By: McAWilliams

McAWilliams — Fri, 16 Sep 2005 15:39:13 +0000

Hi erik,

I have also encountered the " No handler exists for tag Archive at lib/MT/Builder.pm line 170." message.

Did Brad sort that problem out for you too with his timeout thing.

Any help would be great.

John

By: MovableType 3.2 500 Error Solved | NSLog();

MovableType 3.2 500 Error Solved | NSLog(); — Mon, 29 Aug 2005 12:20:49 +0000

Brad Choate (yes, there's only one) spent some time with my "Error 500s with MovableType 3.2" issue yesterday and believes he's found the source of the problem: a low Apache Timeout value. Default used to be 1200, but that was...

By: Erik J. Barzeski

Erik J. Barzeski — Mon, 29 Aug 2005 12:14:04 +0000

Problem somewhat solved. Brad believes he's found the cause of the problem: a low Apache Timeout value. It's 5. Default, says Brad, is 300.

More information in the TrackBack.

By: Erik J. Barzeski

Erik J. Barzeski — Mon, 29 Aug 2005 00:14:45 +0000

Shelley has responded. Thanks. And Brad (Choate) has written to me as well to help solve the problem. Good stuff. 5pm (west coast) on a Sunday to boot. I didn't expect the problem to be resolved this weekend, but two days without someone saying "hey, we're still working on your problem" was a little odd. I'm glad they're still aware that the problem isn't resolved and are working on it.

By: Erik J. Barzeski

Erik J. Barzeski — Sun, 28 Aug 2005 13:31:37 +0000

Six Apart has not responded to my support request - despite a LOT of additional information (including full access information to the server, the MT login, and FTP) - since Friday. I hope that they don't take the weekends off there at 6A, even if they just released a new version, because the Internet and blogging don't know what a "weekend" is. This is the first time I've ever needed support - support I paid for - and thus far, I'm not really getting it. I'm very disappointed.