After turning on Dynamic Publishing for Archive templates, I immediately could no longer load mt.cgi, make postings via the API or, well, do anything:



Could it be that MT is trying to somehow create mt.cgi etc. dynamically? I know that sounds stupid, but I can't figure out what's wrong.

I've verified that mt.cgi is in the cgi-bin, the path is correct, everything.

Please help out!

I would recommend that you first remove the dynamic templating code from the .htaccess and try to go to mt.cgi and see if it works. I've noticed that often when a cgi script gives a 500 error, mtview.php kicks in because ErrorDocuments have been incorrectly configured.

If that does work then what pages are dynamic? If its only archives, then you can move the dynamic templating .htaccess code to your archives/ directory.

I fixed it. Turns out that .htaccess was overriding my cgi-bin files, which sit inside the static web path where .htaccess was published.

thanks