Firstly, that web page is out of date and contains a mis-match of instructions for old and new versions. The best place to obtain current information are directly from the apache, php, and mysql web sites and the documentation they publish. PHP works fine with Apache2.2 and you should probably be using the latest versions of all three pieces of software.
Is it just a phpinfo.php (i assume this has a phpinfo() statement in it) script that does not work or do all .php scripts not work and is this just with Firefox or does it actually work for a different browser? What does the "view source" of the page in the browser look like?
Quote:
|
I can't get PHP5 to recognize MySQL
|
What symptoms or errors do you have? Show the php script you are using.
Here is rundown of what I see based on the info you posted -
LoadModule php5_module php5apache2.dll - you need to specify the full file system path to where the .dll is located. Something like - LoadModule php5_module "C:\web\webserver\php\php5apache2_2.dll" (this it what it would be for Apache2.2)
Place a
PHPIniDir statement in the httpd.conf to indicate where the php.ini file is located. Something like - PHPIniDir "C:\web\webserver\php"
There is no guarantee that php is finding the php.ini you put in the windows folder and it is probably using defaults and any changes you have made to it are not being used.
For your numbered items -
1. If you do the above PHPIniDir item, there is no need to put anything in the windows folder.
2. Add the path to the php folder to your windows path statement and there is no need to copy any extension files around to get any extension to work. (you must either reboot or log off/log on for the actual path statement to be updated.)
3. What you have should work. Are the extension .dll files actually present in that folder?
4. Any changes to php.ini (assuming that php is using the one you are making changes to) or httpd.conf only take effect when the web server is stopped and started.
Unless you want to always enter the :8080 every time you type a url, I recommend using the default port 80. There are few poorly written anti-virus utilities that listen on port 80 and don't properly forward requests made to that port that would interfere with a web server using that port, but I have not seen many posts about this problem lately, so perhaps the current version of software causing this have been fixed.