PHP Manager is a must-have for all WordPress on IIS installations
I ran across this – PHP Manager – a bit ago and installed the tool here on the site to see if it would work as well as the screen shots on codeplex seemed to promise. Historically being a .NET guy, I feel that my PHP optimization skills are still a bit to be desired, so I wasn’t surprised at all to see the tool report back a non-optimal installation here on BrokenToken.
What’s nice is that the add-in made it very easy to pinpoint several settings that needed to be changed, and it let me do so in bulk and implement all changes in one fell swoop. Be sure to do an ‘iisreset’ after any changes so that they are picked up and put into effect.
One word of caution, though: if you like to keep your php.ini file neat and organized, this add-in will group all of it’s settings changes into one section of the file (usually somewhere in the middle – don’t ask me why) and kill whatever kind of ‘.ini feng shui’ you might have going on. I’m admittedly a bit obsessive about such things, so I found it necessary to move the settings around, but nonetheless the add-in is effective and reliable.
There are both x64 and x86 builds available. Have at it and hopefully get a better-running PHP install as a result!
2 thoughts on “PHP Manager is a must-have for all WordPress on IIS installations”
Thanks a lot for the comment. I tested out both of your clarifications and everything is just as you say, so I stand ammended!
It’s a great utility and really helps out the PHP/IIS community, as it takes a lot of trial/error out of the equation.
I am glad you find this tool useful. Couple of clarifications:
1. It is usually not necessary to do iisreset after php settings are changed. If you set iis setting monitorChangesTo (and PHP Manager does set it), then anytime php.ini is changed the settings get picked up right away without the need to recycle/restart iis.
2. The logic for adding/updating settings in php.ini are as follows: If PHP manager changes an existing setting in php.ini then it will change it in the same place where it was originially located in the file. When new setting is added, PHP Manager check which section this setting belongs to and adds it at the end of that section. When you enable or add new extension it goes at the end of php.ini file.