Bug #887
Wrong domain PHP Info indications
| Status: | New | Start date: | 02/03/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | Spent time: | - | |
| Target version: | - | |||
| Affected version: | 6.1.10 | Operating System: | ||
| Resolution: | Architecture: | |||
| Reproduceable: |
Description
In a domain's PHP Config information there are a number of values that cannot be set but the present value of these are shown instead. These indications are not reliable.
I see that ioncube and Zend optimization on server level are both activated and in fact the phpinfo() in my application confirm this. Still the indications on domain level say they are off.
This is on a slave server where mod_php_itk is active. I have set affected version 6.1.10 but it might have been there before.
History
Updated by Danny Terweij 3 months ago
Same behaviour at Master?
Are the loaders actualy loaded in php.ini from users domain? If not then there is the bug.
My Develop/test system:
PHP -> mod_php
Master - Domain : /home/httpd/mc9928.lan/php.ini -> Loaders present.
Slave - Domain : /home/httpd/sc9992.lan/php.ini -> Loaders present.
Did not yet moved to itk yet to see if the php.ini differs.
Updated by René Nieuwburg 3 months ago
I am not sure if the paths you gave me apply to mod_php type. I use a different method to verify.
On slave server level I change Zend, Ioncube, an Xcache settings in PHP Config and the changes are read back to me correctly.
When I go to an actual domain on the slave and check PHP Config then I see that the indications did not change, but when I verify with phpinfo I see that the changes actually did take place. For instance when I remove Zend optimization then I see that it is removed in the phpinfo on the domain level. So only the domain level PHP Config indicators are not telling the truth. Not really a severe bug, but it can lead to confusion.
This is only the slave, on the master server the indications are correct.
This has apparently nothing to do with the type of PHP, because both mod_php and mod_php_itk show the same behaviour.
Updated by Marek Zakrzewski 3 months ago
This might be related to this: http://project.lxcenter.org/issues/332