When you have spent four days to find out why PHP 5.6.32 did not take into account the changes in its own php.ini, you will understand why this warning exists.Īnd, in addition, the Wamp settings allow you to no longer have this warning, but at your own risk.
This warning does not block or change anything about Wampserver. I remind you that this is only a warning to warn those who would like to change PHP version regardless of the fact that the PATH will always point to the previous version and that the new version of PHP will take into account the php.ini of the old version. 'php.exe' that it cannot find in the current working directory. Windows searches folders in the PATH to find executables i.e. %PATH% plus the new directory we want to add to it. "PATH=%PATH% says create a new PATH environmant variable with the current path i.e. If I would use the batch file as you suggested on Stackoverflow, where would I need to place the batch file and would require that I also change the PATH in the Environment Variable? And would that not conflict with Wampserver? "C:\\wamp64\\bin\\php\\php7.2.4\\php.exe" ->path set in the PATH Environment Variable Is there any other way to configure PHP so that no errors are encountered?
Using a PATH on Wampserver or PHP version is detrimental to the proper functioning of Wampserver. Wampserver does not use, modify or require the PATH environment variable. It seems that a PHP installation is declared in the environment variable PATH There is Wampserver path (c:/wamp64) into Windows PATH environment variable: (C:\wamp64\bin\php\php7.2.4\php.exe) Now, when I use ST-3 and Wampserver, Wampserver shows an error: I am using both Sublime Text 3 and Visual Studio Code, but am having problems running PHP in VSCode as it requires one to declare the path to PHP in Environment which I have done.
0 kommentar(er)
