I have been testing website Extensions on Windows Server 2016.
The changes I make to a website’s ASP, Perl, or ColdFusion settings are reflected in applicationHost.config. That’s fine, as long as I haven’t changed a PHP setting.
But if I change the PHP version, then all of the handler mappings are copied into the website’s web.config, starting with a <clear /> directive.
Once that is done, I can no longer use SolidCP to make changes to ASP, Perl, or ColdFusion. Any changes would be applied to applicationHost.config where they are ignored.
Therefore (1) I think the PHP configuration should probably be maintained in applicationHost.config only.
I have a few more observations which might be bugs or missing features:
(2) In FastCGI configuration, the PHP choices are based on whatever handlers are listed in the IIS serverwide setting. Additional PHP handlers that are set up in <fastCgi> section are ignored.
(3) The control panel isn’t showing any option to disable PHP or ASP.NET.
(4) The control panel doesn’t “see” ColdFusion unless the “Server” application pool is running with the same bitness as ColdFusion. (I think there might be some more issues with ColdFusion 11 but I haven’t done much testing yet.)
(5) If anyone knows how to configure the control panel to recognize Strawberry Perl without Helicon Zoo (probably CGI mode), I’d like to know!
- Views1066 times
- Answers0 answers