Bug #66785 [Com]: PHP_VERSION and non-cli phpinfo() points to 5.5.8

Edit report at https://bugs.php.net/bug.php?id=66785&edit=1 ID: 66785 Comment by: nihylum at gmail dot com Reported by: constantine dot exelsior at gmail dot com Summary: PHP_VERSION and non-cli phpinfo() points to 5.5.8 Status: Not a bug Type: Bug Package: Scripting Engine problem Operating System: Windows 8.1 PHP Version: 5.5.9 Assigned To: ab Block user comment: N Private report: N New Comment: Oh my.. ok i did checked the issue using that tool. Yes indeed, the apache2 handler has used another php5ts.dll which has arrived dead end on the harddisk after the uninstallation of the earlier used php stack ( which was indeed based on php 5.5.8 and also added his path to php to the system paths ). I recommend to modify the lookup logic for the apache2handler to seek first at his own directory for the php5ts.dll to prevent such side effects. An alternative would be to display the path to the current used php5ts.dll inside of the apache2handler block of phpinfo(), to help debugging such issues. Thank you for your support. Previous Comments: ------------------------------------------------------------------------ [2014-05-01 18:38:18] ab@php.net Hi, the screenshot illustrates again what you said previously and is nice. However you still didn't tell what you see with "php -i". Under circumstances that could show that ur pulling a wrong dll as well. Also, please get this tool http://technet.microsoft.com/en-us/sysinternals/bb896645 and check from where php5ts.dll is loaded. To do that it's better to set the a filter to "process name is httpd.exe". From what I see on your screenshot - it's better not to use relative paths in httpd.conf. Thanks. ------------------------------------------------------------------------ [2014-05-01 17:12:00] nihylum at gmail dot com http://thor.tr0y.de/php-5.5.12.version-bug.png picture explaination: green arrows = version is correct red arrows = path and configurations black arrows = version is incorrect paths that are not visible on the picture: server root is: /trinity-x64/bin/apache/ web root is: /trinity-x64/htdocs/www/ config is: /trinity-x64/config/ Installation process: - stop trinity-www ( apache 2.4.7 ) - delete all files from /trinity-x64/bin/php/ exempt: php.ini - extract php 5.5.12 package from windows.php.net to /trinity-x64/bin/php/ - start trinity-www ( apache 2.4.7 ) There is no other php installation on the entire system. This problem ( i think it is a bug ) happens only while using the apache module. Tested on: Desktop PC, 2 Ultrabooks with equal installation tasks ( All Windows 8.1 Update 1 x64 ). ------------------------------------------------------------------------ [2014-04-17 13:08:56] ab@php.net Looks like you're experiencing a configuration issue with your machine. You might indeed load the php5apache2_4.dll from 5.5.11, but it depends on php5ts.dll which you seem to be loading from from 5.5.8. I wouldn't even wonder if you see the same error with your console PHP when running php -i. To fix this I would suggest - do a clean install of Apache and PHP - check your %path% to not to contain other PHP versions - check your php.ini path to load from the correct location Thanks ------------------------------------------------------------------------ [2014-04-03 12:02:52] constantine dot exelsior at gmail dot com Yes, this problem happens on php 5.5.11 too ( this time tested: cli, apache module ). The PHP installation has been done after removing the old version. Yes i am sure that i used the correct dll inside of the correct directory: php5apache2_4.dll for apache 2.4.7 phpinfo() heading block shows php 5.5.8 PHP_VERSION shows php 5.5.8 on fastcgi and apache2handler PHP_VERSION shows php 5.5.11 on CLI Apache Signature shows: Apache/2.4.7 (Win64) OpenSSL/1.0.1e PHP/5.5.11 http://thor.tr0y.de/php-version-bug.png ------------------------------------------------------------------------ [2014-03-27 12:57:44] ab@php.net I see 5.5.9 with both apache and cli. Sure it was the right dll? Thanks. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=66785 -- Edit this bug report at https://bugs.php.net/bug.php?id=66785&edit=1