Since I hate it when I can’t get things done when everybody else seems to get it done, I’m still fiddling with the new versions of Apache, PHP and MySQL. On my laptop I decided to give Apache 2.0.59 (the latest 2.0.x) a try, to see if I could make the PHP-module work on that version. To my surpise, this version also gave me the error “No MySQL support”. Starting PHP from the commandline (PHP.EXE or PHP-CGI.EXE) with the -m option still revealed that the MySQL (or MySQLi) extension was loaded properly.
When running PHPINFO.PHP from the newly installed server I noticed one small thing. The PHP directory was not included in the path. Did I in all horror remove it again from the PATH? A quickly opened command-prompt learned I did not: it was still on the path. So….how come the stupid webserver can’t find it. Should it be that I need to restart Windows. Noooooo. Of course not. But since it’s only my laptop, why not give it a try.
I guess you can see where this story is heading. After a restart, PHPINFO.PHP showed the correct PATH and magically also MySQL information. And yes, PHP works as a module.
Geez….how stupid is that? Restart Windows because some process that starts services does not recognize the new path yet. Even more stupid: Windows does not warn you about that. There are a lot of warnings in Windows to which I say: get lost and never come back. But here one would be in place.
Back to the original testbed. I’ll let you know.