ID: 21046 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Open +Status: Feedback Bug Type: Output Control Operating System: linux PHP Version: 4.3.0RC2 New Comment:
What error loging mechanism are you usingl: syslog, file, something else? Previous Comments: ------------------------------------------------------------------------ [2002-12-16 13:35:09] [EMAIL PROTECTED] oops, sorry, that should read: Could not set cookie, log errs on, display_errs off ------------------------------------------------------------------------ [2002-12-16 13:34:39] [EMAIL PROTECTED] oops, sorry, that should read: ------------------------------------------------------------------------ [2002-12-16 11:23:35] [EMAIL PROTECTED] phpinfo() reports that display_errors is off. Running the script that [EMAIL PROTECTED] suggested produces the output: Could not set cookie, log errs on, display_errs Also, php is running as a cgi binary. ------------------------------------------------------------------------ [2002-12-16 10:36:50] [EMAIL PROTECTED] Could you try this version instead, and report the output? <? error_reporting(E_ALL); if (!$undefinedVariable) { if (setcookie ("code","123456")) { print "Cookie set, "; } else { print "Could not set cookie, "; } } print (ini_get('log_errors')) ? 'log errs on, ' : 'log errs off'; print (ini_get('display_errors')) ? 'display errs on' : 'display_errs off'; ?> ------------------------------------------------------------------------ [2002-12-16 10:35:49] [EMAIL PROTECTED] In the same directory as your script put a script with <?php phpinfo(); ?> Then in the output of that script check what the display_errors is set to, it is possible that you are either using the wrong .ini file, httpd.conf overwriting your settings for the virtual host or you have .htaccess that changes display_errors to On. So far, neither I nor other developers who have tried to replicate the problem you've described were able to do so. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/21046 -- Edit this bug report at http://bugs.php.net/?id=21046&edit=1