ID: 24397 Updated by: [EMAIL PROTECTED] Reported By: jlim at natsoft dot com Status: Open Bug Type: Apache related Operating System: Windows XP PHP Version: 5.0.0b1 (beta1) New Comment:
This is not a support forum, and this bug of name inconsistencies is being worked on (note that it's an open bug report). Please use http://www.php.net/support for support questions. Previous Comments: ------------------------------------------------------------------------ [2003-07-05 18:00:32] phpbugs at localpin dot com To me it's a no brainer that all the dlls for v5 should be called php5apache.dll etc. Even if the code INSIDE is IDENTICAL to v4. Who cares what the code is doing INSIDE? Outside, if it says it's v5 everyone is happy (I think?!) - OK, some poor disks everywhere gotta store a php5.dll and a php4.dll which are identical, but the usability gain everywhere is huge. I see 2 choices: a) you call the dlls php4xyz.dll (v4), php5xyz.dll (v5) etc. b) you call the dlls phpxyz.dll and distribute different version with each version. Nobody expects php.exe in v4 to be the same as php.exe in v5 for example. regards, Hugh, someone desperately and unsuccessfully struggling to get PHP5 working with Windows XP and Apache 1.3.something (I could tell you what the something was if I could get it running) but I get the message I've seen a lot in these bug reports: "Cannot load c:/php/sapi/php4apache.dll into server: (126) The specified module could not be found" I've got a v5 copy of php4ts.dll almost everywhere (c:\php, c:\windows\system32, in with the Apache .exe). Did I miss one? ;) I've named the php4_module line to php5_module (sure can't miss that one reading these bug reports!): LoadModule php5_module c:/php/sapi/php4apache.dll AddType application/x-httpd-php .php If anyone can point me to the source of knowledge on getting this working I would sure appreciate it. ------------------------------------------------------------------------ [2003-07-02 09:50:03] mike at digitalstruct dot com I believe that the file should also be called php5apache. The php4apache breaks consistancy and also makes it harder to run both 4 and 5 side by side. ------------------------------------------------------------------------ [2003-06-30 07:25:26] jlim at natsoft dot com Sorry The extension directory problem is bogus. I confused the php4 php.ini with the php5 php.ini settings. The other bugs mentioned are still relevant. ------------------------------------------------------------------------ [2003-06-29 23:56:56] jlim at natsoft dot com Description: ------------ Note the funky inconsistency below in the httpd.conf script that i had to use: php4apache.dll but php5_module Also the search path for php.ini and other files is WINDOWS/WINNT directory first. Shouldn't the current directory be first, eg: .;C:\WINDOWS like in PHP 4.3.2? Lastly, although the extension directory is correctly set (checked in phpinfo()), extensions do not appear to load. Reproduce code: --------------- # from httpd.conf script: LoadModule php5_module c:\php5\php5b1\php4apache.dll AddModule mod_php5.c AddType application/x-httpd-php .php ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=24397&edit=1
