#24397 [Com]: Apache 1.3.27 inconsistencies with PHP5
ID: 24397 Comment by: phpbugs at localpin dot com 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: 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. Previous Comments: [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
#24928 [NEW]: error_log inconsistent in adding newline to files
From: phpbugs at localpin dot com
Operating system: Windows XP Home Edition
PHP version: 4.3.1
PHP Bug Type: Unknown/Other Function
Bug description: error_log inconsistent in adding newline to files
Description:
There is an inconsistency whether error_log gives a newline or not when
sending output, only based upon whether the file is not named (message
type 0) or named explicitly (message type 3).
i.e. when doing "error_log($msg)" a newline is automatically appended, but
when doing "error_log($msg, 3, $myfile)" a newline is not automatically
appended.
e.g. error_log($msg) gives:
1. My msg
2. My msg
3. My msg
4. My msg
but error_log($msg, 3, $another_file) gives:
1. My msg 2. My msg 3. M
y msg 4. My msg
Since in both cases the output is to a file, it seems to me that this is
inconsistent. Either BOTH should give an automatic newline, or NEITHER.
One can even imagine the case where the filename for both is identical
(e.g. both use the file "error.log"), yet because you specify the name of
the file explicitly, you don't get a 'free' newline char.
Reproduce code:
---
var $counter = 1;
var $log_elsewhere = true;
var $msg_prefix = "This is test number: ";
var $dev_filename = "c:/Program Files/Apache
Group/Apache/logs/dev_error.log";$elsewhere_log_name =
while (true) {
$msg = $msg_prefix . $counter;
if ($log_elsewhere) {
error_log($fileline, 3, $dev_filename);
// The following line should not be necessary
error_log("\n", 3, $dev_filename);
}
else {
error_log($fileline);
}
$counter++;
}
Expected result:
Without the extra newline sending, I would like the output to be identical
in both cases.
--
Edit bug report at http://bugs.php.net/?id=24928&edit=1
--
Try a CVS snapshot (php4): http://bugs.php.net/fix.php?id=24928&r=trysnapshot4
Try a CVS snapshot (php5): http://bugs.php.net/fix.php?id=24928&r=trysnapshot5
Fixed in CVS: http://bugs.php.net/fix.php?id=24928&r=fixedcvs
Fixed in release: http://bugs.php.net/fix.php?id=24928&r=alreadyfixed
Need backtrace: http://bugs.php.net/fix.php?id=24928&r=needtrace
Try newer version: http://bugs.php.net/fix.php?id=24928&r=oldversion
Not developer issue:http://bugs.php.net/fix.php?id=24928&r=support
Expected behavior: http://bugs.php.net/fix.php?id=24928&r=notwrong
Not enough info:http://bugs.php.net/fix.php?id=24928&r=notenoughinfo
Submitted twice:http://bugs.php.net/fix.php?id=24928&r=submittedtwice
register_globals: http://bugs.php.net/fix.php?id=24928&r=globals
PHP 3 support discontinued: http://bugs.php.net/fix.php?id=24928&r=php3
Daylight Savings: http://bugs.php.net/fix.php?id=24928&r=dst
IIS Stability: http://bugs.php.net/fix.php?id=24928&r=isapi
Install GNU Sed:http://bugs.php.net/fix.php?id=24928&r=gnused
#24928 [Opn]: error_log inconsistent in adding newline to files
ID: 24928
User updated by: phpbugs at localpin dot com
Reported By: phpbugs at localpin dot com
Status: Open
Bug Type: Unknown/Other Function
Operating System: Windows XP Home Edition
PHP Version: 4.3.1
New Comment:
The observant reader will notice that the sample code should use the
the variable $msg rather than $fileline:
error_log($msg, 3, $dev_filename);
error_log($msg);
;-)
Previous Comments:
[2003-08-04 01:07:53] phpbugs at localpin dot com
Description:
There is an inconsistency whether error_log gives a newline or not when
sending output, only based upon whether the file is not named (message
type 0) or named explicitly (message type 3).
i.e. when doing "error_log($msg)" a newline is automatically appended,
but when doing "error_log($msg, 3, $myfile)" a newline is not
automatically appended.
e.g. error_log($msg) gives:
1. My msg
2. My msg
3. My msg
4. My msg
but error_log($msg, 3, $another_file) gives:
1. My msg 2. My msg 3. M
y msg 4. My msg
Since in both cases the output is to a file, it seems to me that this
is inconsistent. Either BOTH should give an automatic newline, or
NEITHER.
One can even imagine the case where the filename for both is identical
(e.g. both use the file "error.log"), yet because you specify the name
of the file explicitly, you don't get a 'free' newline char.
Reproduce code:
---
var $counter = 1;
var $log_elsewhere = true;
var $msg_prefix = "This is test number: ";
var $dev_filename = "c:/Program Files/Apache
Group/Apache/logs/dev_error.log";$elsewhere_log_name =
while (true) {
$msg = $msg_prefix . $counter;
if ($log_elsewhere) {
error_log($fileline, 3, $dev_filename);
// The following line should not be necessary
error_log("\n", 3, $dev_filename);
}
else {
error_log($fileline);
}
$counter++;
}
Expected result:
Without the extra newline sending, I would like the output to be
identical in both cases.
--
Edit this bug report at http://bugs.php.net/?id=24928&edit=1
