(The topic should read "HOW to switch to php?")

As I continue to investigate performance tweaks and options in my 4.2 testbed, I'm looking at the possibility of switching either or both of the MT admin code and the generated blog from cgi to php, but I can't seem to find any comprehensive information on what is involved in such a transition.

For the Admin side of things, do I just need to copy or move the files under /path/to/mt/php/ to the corresponding directories in /path/to/mt and then point the browser at mt.php instead of mt.cgi? (I tried browsing to /mt/php/mt.php but got nothing but a blank page.)

As for the generated blog, I changed the publishing schema from static to dynamic and rebuilt the site, which renamed all the index .html files to .html.static and generated an mtview.php, but surfing to that page returned


I can't help thinking that I'm missing a step or two somewhere along the way, but either I'm getting increasingly myopic or the documentation is somewhat lacking in this area. Can anyone fill in the blanks for me, or tell me I'm an idiot and cite the page that I should have been reading in the first place? I'm running Win2k3 / IIS 6.0 / MT 4.2 / Perl5.8.8 / PHP 5.2.4

Thanks in advance.

I should point out that mysite.net/new/ is the root URL for my testbed, and /new/mtview.php does exist.

The stuff in that directory is used by the dynamic publishing process. It's not a rewrite of the entire application in PHP. That's going to be Perl for the foreseeable future.

I can't help you with the dynamic publishing system itself; never use it.

Thanks for the clarification.

Well I suspect I may be getting closer. According to the documentation, when switching to dynamic publishing MT generates two files: mtview.php and .htaccess, but on my system it's not creating the .htaccess file anywhere. Not that it really matters anyway, since IIS doesn't provide that functionality.

So it would seem that the missing piece of the puzzle is the configuration directives that would be passed to an apache server via .htaccess, which leads to the following questions:

• How can I find out what these changes are/should be? Microsoft has a How-To on migrating .htaccess rules to IIS
• Why doesn't MT generate some sort of error, or at least a warning, when switching from static to dynamic publishing under IIS? Surely I can't he the only fool who's tried this?
• Why is it not generating the .htaccess file, or at least generating an error in the log if the file creation fails?
• Am I barking up the wrong tree completely?

you could try making mtview.php your 404 custom error handler in IIS.