Hi
I am using your wonderful product for a while now, and I have to say its the best 99$ I ever spend. My developing go's a lot faster and I now enjoy programming in PHP.
Yesterday I had the message there was a upgrade, so I downloaded it and installed. After entering the new activation code you send me, I wanted to see the new version at work. But that was a real disappointment. This new system was not able to connect to my local MySQL database anymore. It constantly told me the socket was wrong or the database was not running. What is not the case, because I did not change anything.
After a day I removed the new version, and went back to the previous version. After that everything was working fine again. I expected that after installing the new version everything wood work like before. It is possible that its just a small thing that I need to change, but I don't have the time to search days to find out what is wrong.
Sinsearely
D. Gevaerts
juanc says:
VS.Php 2.8 comes with PHP 5.3 which uses a new, faster mysql library called mysqlnd. What version of MySQL are you using? perhaps there is a known compatibility issue between it and the new mysqlnd library.
If you are using MySql 5, things should work just fine as long as you don't use a custom php.ini
Juan
IainDowns says:
HI, Juan.
I'm having this problem as well. I've upgraded and mysql no longer connects. I don't care if this is because the php is newer - I don't want newer, I want one that matches my production system!
Also, XDebug will not run at all. It crashes as soon as my app is launched.
I'm going to have to revert to the v2.7 until you can come up with a solution!
Iain
juanc says:
Iain,
Please read the following on upgrading to VS.Php 2.8
http://www.jcxsoftware.com/jcx/node/2953
Thanks,
Juan
IainDowns says:
I don't believe I had any custom entries in php.ini nor in .httpd.conf.
In any case I deleted the php.ini in the project folder and it was recreated and still mysql wasn't accessed.
I'm reasonably sure that I had the project set up NOT to use a custom ini file.
Any other ideas?
Iain
dsmario says:
I'm using php.ini and .httpd.conf files that are created for me by VS 2.8. In fact, I created new PHP project using existing codes. It is still not connecting to the database.
juanc says:
What version of MySQL are you using? PHP 5.3 uses a new Mysql library called mysqlnd.
IainDowns says:
Is 5.1.37-community - Win 64
Iain
md123 says:
From my experience, 64 bit has been very poorly supported on windows build. For example, only the vsphp 2.8 version has allowed me to step in on a 64 bit machine. But, I suspect some of the dlls haven't been properly compiled because I get some errors too when some modules are loaded via the php-xdebug.ini (in your Program Files\Jcx Software\Php5) folder. Go figure.
dsmario says:
Mine's "5.0.89-community-nt"
DavidG says:
Yes, that is the same that I did. It has no use if you need to write 2 versions of your work. One that work on locally, and one on the server it needs to run on.
The 2.7 works just fine, for me.
vividearth says:
If any of you still have this issue you can fix it by changing localhost to 127.0.0.1 in your database settings. The new mysql driver has trouble resolving localhost in windows.
See http://bugs.php.net/bug.php?id=45150 for more info.
juanc says:
Of you can disable IPv6. If IPv6 is enabled, localhost resolves to the machine's IPv6.
I had the same issue with the built-in engine where the browser open http://localhost and I had to change it to http://127.0.0.1
Thanks,
Juan
juanc says:
BTW one way to confirm is to ping localhost and see the adress that shows up. In my system it shows the IPv6 address.