Posted April 19th, 2010 by smclenithan
The latest build of 2.9 seems to ignore using a custom php.ini, my ini file in the project directory is being overwritten every time. I also tried editing the php.ini in the php 5.3 folder and the php-xdebug.ini neither one of them is the source file that gets copied to my project when debugging (added special comments to tell).
In fact I don't know where it is getting the php.ini to copy to my project as there are only those 2 ini files that are the same file size (70KB).
Thanks
// Steve
smclenithan says:
After some poking around, I've narrowed this problem down to only the 5.3 profile. 5.2 works fine. I also found that if I set the custom php.ini to be outside my project directory, where vs.php would normally auto copy it, it will sort of use it, but it doesnt load any extensions (pdo_mysql, etc etc) so that's of no help.
Anyone else seeing something similar?
// Steve
juanc says:
php.ini for 5.2 and 5.3 is far different. So you can't use the same for both.
juanc says:
it copies the file from the vs.php\php 5.3\php-xdebug.ini
Juan
smclenithan says:
Ok this is strange, my desktop install is working fine using that ini path, but my tablet is copying it from I don't know where, I even added some comments at the top and it is not copying that file, I think I'll try a full reinstall and see what happens.
JRS says:
Not sure if it's related but I found an issue with using the custom php.ini as well.
Using VS.PHP 2.9 with PHP 5.3.x, when specifying the custom php.ini path in the VS project properties, you MUST end the path with a slash. If your path does not end with the slash, the customized php.ini is not used. Once the path ends with the required slash, your debug sessions will then use your expected settings from the customized php.ini file.
As described in the tutorial video,
http://www.jcxsoftware.com/jcx/vsphp/tutorials/custom_phpini
I hope this helps someone else trying to debug their issues when using a custom php.ini file.
Jason