Posted by Garry Jones on 10/18/06 15:04
"Rik" <luiheidsgoeroe@hotmail.com> skrev i meddelandet
news:a0bbd$45363b89$8259c69c$11868@news2.tudelft.nl...
> Yes. print_r($_SESSION); to check what your session actually holds.
> Be warned that session_start() has to be declared BEFORE any output, or it
> won't work. So not in 'the centre' of your page, but as one of the first
> things 'on top'. Even sending out a simple space or line-break before
> session_start() will render it useless.
Done that and I am getting this. (Since I posted I turned error reporting on
in a setting my web hotel service allows users to change).
Warning: session_start() [function.session-start]: Cannot send session
cookie - headers already sent by (output started at
/customers/scfmotion.se/scfmotion.se/httpd.www/sitedefs.php:67) in
/customers/scfmotion.se/scfmotion.se/httpd.www/scfma_edt_pwd.php on line 34
Warning: session_start() [function.session-start]: Cannot send session cache
limiter - headers already sent (output started at
/customers/scfmotion.se/scfmotion.se/httpd.www/sitedefs.php:67) in
/customers/scfmotion.se/scfmotion.se/httpd.www/scfma_edt_pwd.php on line 34
So what does
"session cookie" and "session cache limiter" - mean?
Okay, it does seem like I have to move session_start somewhere else in the
code. Thats a bit of a nightmare because the code itself should only have
session_start based on a couple of conditions. These conditions are met when
that php code segment is called for. I am going to have to make a copy of
the very same if statements higher up and start the session earlier. That
should do it if I have understood you correctly.
Garry Jones
[Back to original message]
|