--- Vincent Oostindie <[EMAIL PROTECTED]>
wrote:
> Not only that: if you are running a production
> server, you will probably
> want to log your error messages to a file (or
> syslog, or whatever),
> instead of printing them. So 'display_errors' should
> be off. If that is
> the case, you don't need to use @ anymore, because
> there will be no HTML
> output even in case of problems. The advantage of
> this is that you can
> use the exact same code on a development server
> (with display_errors =
> on) and a production server.
>
> Vincent
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
That is all well, but if php 4.2.1 interprets any
output (as errors not only screen errors) as something
that is sent before a header in a redirect, there is
no other way (that i'm aware of) around it.
Like this:
$user=$Session["user"];
if(!$Authorized)
{
header ("Location: http://jaggu.org";);
}
this will not work, you have to write:
@$user=@$Session["user"];
@if(@!$Authorized)
{
header ("Location: http://jaggu.org";);
}
To actually get the redirect.
On http://jaggu.org/info.php, you can see that
display_errors = off
In any case, I think you are onto something. I will
try to narrow down logging, to see if that might be
the problem.
Thanks for helping!
Olav Bringedal
jaggu.org
__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
