"Warning: session_start, Warning: cannot modify header&

Regular Joined: Jun 08, 2007 Posts: 54

A user posted this in my pm and all he was trying to do was login using FireFox.

Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /home/content/xxxx/modules/Your_Account/language/lang-english.php:262) in /home/content/xxxx/includes/gfx_check.php on line 106

Warning: Cannot modify header information - headers already sent by (output started at /home/content/xxxx/modules/Your_Account/language/lang-english.php:262) in /home/content/xxxx/modules/Your_Account/index.php on line 1026

Warning: Cannot modify header information - headers already sent by (output started at /home/content/xxxx/modules/Your_Account/language/lang-english.php:262) in /home/content/xxxx/modules/Your_Account/index.php on line 1084

Would cleaning out his cookies, history and such clear all of the problems or do I have to modify my htaccess file (as hitwalker suggests in post: http://www.ravenphpscripts.com/postt8279.html). Can someone explain why this is happening? Is it a FireFox issue and if so, is there a fix that I can apply?

Thanks in advance....I'll have him clean out everything in the meantime.

registered · Site Admin Joined: Jun 04, 2004 Posts: 6437

kittyprrrs, be careful about posting your root path - it can be used against you by attackers (I removed it).

I'd normally suggest searching the forums for answers to this, but it seems you've already done that. I'd verify the php.ini settings and modify .htaccess if necessary.

Which version of RN are you using?

registered · Posted: Sat Jun 23, 2007 3:46 pm

Do you have $display_errors turned on or something? I get similar messages too, but they only appear in the server logs.

registered · Posted: Mon Jun 25, 2007 10:52 am

Do you have a space or new line after the ?> in modules/Your_Account/language/lang-english.php

Posted: Tue Jun 26, 2007 7:28 am

Sorry...I've had my face shoved in php books....I've now just emerged! Did I mention, I'm even more confused now then I was before!? hahahahaha!

Kguske, thank you! I must have been really tired to post everything like that. I know when I have been working on stuff so long, I just can't see straight and I do stupid things like that. Thank you so much!

I'm using RN 2.10 and loving it so far. As far as the php.ini file, what would I be looking for? As for htaccess, what should I look to change?

Gremmie, yes I did, I changed it back to FALSE so, hopefully that will fix it.

technocrat...omg...yes! why would such a little thing like that cause such chaos?

Thank you all, very much. Let's all sit back and see it this fixed it!

Posted: Tue Jun 26, 2007 8:45 am

Good one technocrat, I should have read the error message more carefully.

I see a lot of that stuff in my log files, mainly from the forums.

Posted: Tue Jun 26, 2007 9:14 am

Anything after the ?> gets treated as HTML. I am going to guess your using DreamWeaver?

Posted: Tue Jun 26, 2007 9:53 am

Hey technocrat, no...I only use DW for HTML/CSS....I use EditPad Pro for all my other stuff (php, sql....etc.)....I might have forgotten to delete it when I was trying to insert that "private message" code.

Thank you, this is just another notch on my "learning" belt. I will forever, remember that anything after the ?> will get treated as an HTML tag.

Thank you everyone again! Seriously...I learn something new everyday from reading this forum.

registered · Posted: Wed Jun 27, 2007 7:05 am

kittyprrrs, again, just for your "learning process", it really only becomes a problem when it is a script that is included prior to the normal HTTP headers are sent (which is done in header.php). This can vary slightly by module BTW.

What is happening is that if any HTML is returned back to the browser before the "real headers", PHP passes a default header to the browser. Since the headers have already been "sent", once the normal headers are sent back in header.php, you get the "headers already sent" error.

Posted: Fri Jun 29, 2007 10:10 am

Thanks montego, I think I actually understood that (for a change!). I swear, if I read this from day one (back 1 year ago) I don't think I would have understood this.

So basically, just triple check all my previous "altered" versions of xxxx.php that I was working on and make sure that all spaces or hard enters are removed or this error will 'pop' up. I never thought such a tiny thing like a 'hard return' would wreck havoc with header issues.

I think I need to get a bigger belt soon! Razz

Posted: Sat Jun 30, 2007 12:58 pm

Quote:

So basically, just triple check all my previous "altered" versions of xxxx.php that I was working on and make sure that all spaces or hard enters are removed or this error will 'pop' up

kittyprrrs, if you are now working just fine, I would not worry about it. It really is not EVERY file, only those that are included up before header.php.

Just now that when you see this error, you will know what to do. Wink