You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The reason will be displayed to describe this comment to others. Learn more.
Thanks! That seems to work. Although, I have found a tiny bug. If we have PHP logging enabled in templates, and set PHP mode to Disabled (none) first, and then re-enabled it with FPM, then PHP logging for the FPM pool is still disabled. Worth mentioning, that the same operation works just fine when switching from disabled to FCGI mode, i.e. PHP logging gets enabled, but not in FPM mode. Also, if you create a new domain and FPM is the default execution mode and PHP logging is enabled in templates then logging for the PHP pool is getting to set correctly (to enabled) but if you toggle FPM->none-FPM, then logging is not getting re-enabled, even though it's set to on in templates.
Besides (related), can we please not print the following message when disabling PHP and PHP error log is enabled? It creates noise for nothing:
The reason will be displayed to describe this comment to others. Learn more.
Sure, I'll fix that confusing message. Maybe I'll also make the PHP log use the default path when switching out of "none" mode, although this could be confusing to the user if they has logging disabled before switching modes originally..
8c0b326
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! That seems to work. Although, I have found a tiny bug. If we have PHP logging enabled in templates, and set PHP mode to Disabled (
none
) first, and then re-enabled it with FPM, then PHP logging for the FPM pool is still disabled. Worth mentioning, that the same operation works just fine when switching from disabled to FCGI mode, i.e. PHP logging gets enabled, but not in FPM mode. Also, if you create a new domain and FPM is the default execution mode and PHP logging is enabled in templates then logging for the PHP pool is getting to set correctly (to enabled) but if you toggle FPM->none-FPM, then logging is not getting re-enabled, even though it's set to on in templates.Besides (related), can we please not print the following message when disabling PHP and PHP error log is enabled? It creates noise for nothing:
8c0b326
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, I'll fix that confusing message. Maybe I'll also make the PHP log use the default path when switching out of "none" mode, although this could be confusing to the user if they has logging disabled before switching modes originally..
8c0b326
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why don't we set it to whatever it is on the template, the same way we do it when creating a virtual server?
8c0b326
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will do ..
8c0b326
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just checked in a fix for that..
8c0b326
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Excellent. Thanks. It seems to work just fine!