Martin Norland wrote:
Personally I disagree with this. Yes it's easy, but you should never enable
a feature to fix a bug or problem when it can be tracked down (although
obviously in time critical situations, using it as a 'band aid' is -
sometimes - necessary). With a quick pointer he was
I suggest you to activate Output Buffering at beggining of your code. It's
so easy and should not modify the output of your code.
This prevents your error Headers already sent.
At the first line of your PHP code, insert ob_start() and in the end of
your code insert ob_clean_flush().
If you do
David Martínez wrote:
I suggest you to activate Output Buffering at beggining of your code.
It's so easy and should not modify the output of your code.
This prevents your error Headers already sent.
At the first line of your PHP code, insert ob_start() and in the end
of your code insert
Hey Folks,
I have a script that times out the session if there is no activity in a
certain amount of time. If there is no activity the HEADER()
redirects to the logout page and kills the session. Everything works
fine on our test server, but when I test the script on the production
server,
Craig Hoffman wrote:
Hey Folks,
I have a script that times out the session if there is no activity in a
certain amount of time. If there is no activity the HEADER() redirects
to the logout page and kills the session. Everything works fine on our
test server, but when I test the script on the
Check that there is no output generated before your script hits the
Header() function calls. The most common mistake I've noticed is that if
you require() or include() many files before you call Header(), and if
there is any content outside of the ?php ? tags in the includ()'ed
or require()'d
Thanks guys. There was a space after the closing ? tag.
Best,
Craig
On Apr 28, 2005, at 2:08 PM, Patel, Aman wrote:
Check that there is no output generated before your script hits the
Header() function calls. The most common mistake I've noticed is that
if you require() or include() many files
