Warren Vail wrote:
Mike,
While that's not the only way to go somewhere else, if it is the way the other guy wrote the code to get around, ripping it out an replacing it with something else could be a problem. The error message you are referring to indicates that something was sent to the browser before it attempted to send a header (usually used to get around). One line number in the message refers to a line of code that output something before the header function was executed, the other to the line number of the header statement itself.
Most common causes of this is a debug message designed to show values of variables during debug was executed before the header statement. Solution: either fix the bug and remove the debug display (usually an echo), or remove
Good suggestion here. I'd also add that you can set up error logs, automated email messages (send these in batches, you just never know when one error is going to send 1,000 messages to you) and such to keep yourself informed whenever there are errors.
-- PHP Windows Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php