Hello, I'm using Movable Type 5.04 with MultiBlog 2.1 (default). I have an entry/page trigger already in use (working fine), but am encountering issues when adding a second, comment trigger.
It allows me to set it up (All blogs in website - on comment - rebuild indexes), but when posting a comment after saving my plugin changes, I encounter an Error 500. The comment does post AND the pages update ... but still, I'm getting an error on (what I can only assume is) the redirect to the "your comment was posted" page.
I've dug around now on the web for a while and have found no useful information. Any ideas on this end?
Reported on Movable Type 5

Hi, folisdhc,
I'd like to know your issue more in detail.
May I ask;
* Did 500 error occur only inside of your MT's dashboard, or on published websites?
* Did your website receive a comment, re-publish, and display a comment correctly?
* Or did you see 500 error in spite of the comment had been received and published correctly?
* May I see your website if I can, and write a comment for test?
Also, have a look at your webserver error log: whenever you see error 500, there most likely is some more information there.
See: http://www.movabletips.com/2010/02/premature-end-of-script-headers-error-500-movable-type-and-you.html
Maarten, it seems that my provider (1&1) does not provide error logs on shared hosting packages for "technical reasons". The only thing I've been able to dig up is what they call their CGI Output Monitor, which allows me to select a script and enter an optional parameter. It then executes it and displays information (that consequently means nothing to me).
When I ran mt-comments.cgi without any parameter, it gave me this:
Nick, to clarify - the Error 500 only occurs outside of the dashboard on the published website and ONLY when the comment trigger is enabled. Without the trigger, I experience no error and comments post correctly. With the trigger, the comments still post and the trigger causes a re-publish, but I get an Error 500 directly after hitting submit.
In short, when the trigger is enabled everything works, but I get an Error 500 after submitting a comment.
If you would like to try posting a comment, go ahead and use this thread: http://centroid.kontact.cc/news/2011/05/the-day-after.php#comments
I've temporarily created a test account to allow you to comment.
Username is "test"
Password is "mtype"
folisdhc,
I saw your test entry and the 500 error after I had posted a test comment.
I couldn't figure out what is the cause of the issue, because I could rebuild my website and blog with MultiBlog trigger, on my own MT environment, when I posted a comment to the blog.
So, please change the configuration of your MT's MultiBlog trigger setting, from "All websites and blogs in this system" to blog which you want to rebuild, and try to post a comment again.
I'd like to see the result.
Nick,
I went ahead and deleted my original trigger and applied one that is activated only by the blog I linked you to. Unfortunately I am still getting the Error 500.
I'm going to try to get a log from my web host (I just learned I can request one).
If you have any more ideas I'm ready to give them a try. Thanks for all your help already.
Hi, folisdhc,
After that, did you get the log data from your web host?
If you've got that, I'd like to check that and look into the causes.
If there were private information and wanted to hide, you can copy and paset only related lines.
Thanks.
Nick,
Unfortunately, my web host says that my account has no CGI logs that I could view error details on (I don't know why). Basically I have no way of knowing what is going wrong in the script. If you have any ideas let me know, but it seems like I'm sort of stuck.
folisdhc,
Hmm... really puzzled.
How about updating your Movable Type from MT5.04 to the latest version?
http://movabletype.org/
http://www.movabletype.org/2011/06/movable_type_511_and_5051_4361_security_updates.html
Now every MTs have their latest version and they are available.
You are using MT5.04, so MT5.051 is appropriate for you.
(I don't know whether you are using MTOS or MT Pro.)
Nick,
I really appreciate all your help. I will backup and then update and see what that does. I'm a little nervous just because MT has been really finicky in the recent past, but this could be a solution so I will definitely give it a try.