ansaurus

Question

Warning: session_start(): Cannot send session cache limiter - headers already sent

Answer 1

+1 A:

i don't know where but your script sent some output before, it's the warning message complete ? it's usually tell also where the output started.

If are unsure about where the output started you can try to use the output buffering libs. Put an ob_start(); at the very beginning of you script and $bad_output = ob_get_clean(); just before session_start(); now in the $bad_output you have the output that disturb your script.

Cesar 2010-04-24 07:04:37

this won't help against BOM

Col. Shrapnel 2010-04-24 07:16:22

i didn't know, never had BOM issues :)

Cesar 2010-04-24 07:37:45

I tried this but it doesn't show anything, i.e, string(0) "".The code is run in xampp and php 5.2. Any possible compatibilty issues or something?And the rest of the error is "output started at line 1"..but apparently there's nothing there.

shyam 2010-04-24 07:39:36

i checked wikipedia about "Unwanted BOM", as Syntax Error said, because i was curious... it's looks like your problem, you can find there also some advices about how to resolve :)

Cesar 2010-04-24 07:48:49

Answer 2

+2 A:

It's not unheard of for a BOM (Byte order mark) to lurk at the beginning of the file and screw this up, depending on the encoding (UTF-16 or also possible for UTF-8). Redirection wouldn't have anything to do with it.

See http://en.wikipedia.org/wiki/Byte_order_mark and scroll down to "Unwanted BOM"

Solution: view the page as Latin-1 and look for ï»¿ at the beginning. I've had this happen to me before.

Syntax Error 2010-04-24 07:06:10

ansaurus

tags:

views:

answers:

Warning: session_start(): Cannot send session cache limiter - headers already sent

related questions