Give local.ini a preference in multi-php.ini editor
Open Discussion
As a cPanel user and a server administrator I would like local php.ini and user.ini files to override settings adjusted in the MultiPHP editor, to ensure my edits are retained.
I saw there was different behavior with php 5.6. There was even no preference added to any files. $
In 7.0 and 7.1 there is, so I think this should be fixed accordingly.
php 5.6 example:
php7 and up
As you can see in 7.0 local.ini will always come last and will always override anything. I think it should have a preference like "40-local.ini" for example.
This way it will be possible to choose other files which can override it.
I saw there was different behavior with php 5.6. There was even no preference added to any files. $
In 7.0 and 7.1 there is, so I think this should be fixed accordingly.
php 5.6 example:
php7 and up
As you can see in 7.0 local.ini will always come last and will always override anything. I think it should have a preference like "40-local.ini" for example.
This way it will be possible to choose other files which can override it.
Same here, the .ini file created by MultiPHP ini editor overrides our own "hierarchy". There should be a solution to have a single ini file that has higher precedence as all other cPanel "default" ones.
Same here, the .ini file created by MultiPHP ini editor overrides our own "hierarchy". There should be a solution to have a single ini file that has higher precedence as all other cPanel "default" ones.
With PHP-FPM, we are unable to easily use a custom per-user php.ini file. The FastCGI backend that PHP-FPM uses simply does not allow. This means that "MultiPHP INI Editor" is almost useless to in this situation (With PHP-FPM enabled).
An alternative is to use the ".user.ini" custom feature that PHP allows for.
So, if the domain has FPM enabled will be interesting that the "MultiPHP INI Editor" creates a .user.ini file (instead the php.ini) with the configured values.
With PHP-FPM, we are unable to easily use a custom per-user php.ini file. The FastCGI backend that PHP-FPM uses simply does not allow. This means that "MultiPHP INI Editor" is almost useless to in this situation (With PHP-FPM enabled).
An alternative is to use the ".user.ini" custom feature that PHP allows for.
So, if the domain has FPM enabled will be interesting that the "MultiPHP INI Editor" creates a .user.ini file (instead the php.ini) with the configured values.
Last night our cPanel WHM server automatically updated to version 64. As a result PHPs "allow_url_fopen" was disabled, because local.ini was changed. This should never be able to happen, how can I otherwise rely on the automatic updates.
Last night our cPanel WHM server automatically updated to version 64. As a result PHPs "allow_url_fopen" was disabled, because local.ini was changed. This should never be able to happen, how can I otherwise rely on the automatic updates.
Replies have been locked on this page!