ID:               15927
 Updated by:       [EMAIL PROTECTED]
 Reported By:      [EMAIL PROTECTED]
 Status:           Bogus
 Bug Type:         Scripting Engine problem
 Operating System: Linux 2.4.17/RH 7.2
 PHP Version:      4.0.6
 New Comment:

Thank you, you pointed me to the reason for my problem:
In the .htaccess file I found:
    php_value display_errors true
must be:
    php_flag display_errors on

That means: Due to this syntactically wrong statement in the
htaccess-file PHP overides the default and sets this flag to "false". I
think this is not the desired behaviour,
isn't it?


Previous Comments:
------------------------------------------------------------------------

[2002-03-07 05:57:04] [EMAIL PROTECTED]

... and your php.ini error_reporting settings are?

------------------------------------------------------------------------

[2002-03-07 05:35:45] [EMAIL PROTECTED]

Okay, perhaps I should stressen that there is no error mesage
whatsoever. In my case, it took me several hours to find this little
one. It's very annoying that PHP doesn't issue a syntax error message.

------------------------------------------------------------------------

[2002-03-07 05:25:05] [EMAIL PROTECTED]

This just gives a parser error for me (tested with 4.0.6 and current
cvs).

------------------------------------------------------------------------

[2002-03-07 05:24:51] [EMAIL PROTECTED]

If there is a parse error, the script doesn't execute.

Not a bug > bogus

------------------------------------------------------------------------

[2002-03-07 05:21:42] [EMAIL PROTECTED]

<?php
echo('X');
error_log('X', 0);
$daten_verlag[$rubrik['id']]] = $daten_rubrik;
?>

One bracket too much!
This makes PHP issue just 5 Bytes to the browser, regardless of any
code following or preceeding this line.
I think it doesn't even execute the code because there doesn't appear
anything in the logs, too.

------------------------------------------------------------------------


-- 
Edit this bug report at http://bugs.php.net/?id=15927&edit=1

Reply via email to