Just had to push movable type onto an apache2 / mod_perl2 box. Just for testing, so the main aim was not performance, but just having the bloody thing work.
Well apparently mod_perl 1.xx is supported, while mod_perl 2 is not.
Now I'm sure there are more elegant ways to tame MT in such an environment (and actually I would appreciate if the lazyweb could point me to them, since google is of little help), but if you have no time and are in desperate need of a quick hack, this may help: just go to your .htaccess and add
SetEnv MOD_PERL ''that will bail MT out of the mod_perl environment. Make sure also you don't have the handler set to perl-script.
Honestly I don't think there is much of an option and doubt there ever will be in regards to mod_perl 2 without significant changes in the space.
mod_perl support was added in to MT before FastCGI came (back?) into vogue and also before the mod_perl team blew it by totally changing the API in ways the were not backwards compatible. With FastCGI gaining popularity and attention in addition to being easier to install/maintain and supporting more then just Perl, I don't see there being enough demand to justify the effort at this point.
Also, on a totally diferent point, this error is appearing at the bottom of your screen:
main(/home/.dicken/ibru/bru.bzaar.net/mt2/plugins/RebuildQueue/../../php/mt.php) [function.main]: failed to open stream: No such file or directory in /home/.dicken/ibru/bru.bzaar.net/blog/mtview.php on line 7
Judging by this message it looks like you are running dynamic archives which goes through PHP and not Perl. I never recommend using the dynamic page functionality in MT. It was widely panned when it was released and has never gained traction with good reason.
Perhaps some of your issues are related to this?
If the issue is performance and scalability its being addressed in other ways. A fair bit of work has gone into running MT under FastCGI, ramping up the database performance of MT and the static publishing queue system. There has been some recent mention of a Perl-based system for dynamic archives, but nothing specific has been promised.
I doubt this was the info you were looking for, but I hope it lets you know where things stand.
Hi Timothy,
thanks for the very precious comment!
Actually the environment I was mentioning in the post (which is not this blog) is a test and my main aim was to get MT set as quickly as possible (and I had no rights to tweak the httpd.conf in this case).
I understand also the decision to support FastCGI instead of mod_perl 2, makes sense.
As for the warning below: I still have to check, but this blog has been semi-abandoned for a while and then I hastly upgraded to MT4, hence I'm sure there'll be plenty of errors around.
Looking forward to have some time to polish it a bit ;)