An error we can't seem to fix... Help?

angeleyz · #1 09-17-2003, 04:38 PM

Okay, we thought we had fixed this, but I was just checking my error logs a min. ago and I'm seeing a TON of these errors still. Charles (my husband) says that people simply have their cookie settings too high and so our site is blocking the cookies being set, causing this error. But I just wanted to run it by someone else -- just in case anyone else has had this same problem in the past. This problem only started when we upgraded our site to PHP Nuke 6.8, which was about 2 wks ago now. If anyone can offer any ideas or feedback it would be much appreciated. Thx!

Quote:

[Wed Sep 17 17:32:12 2003] [error] PHP Warning: Cannot modify header information - headers already sent by (output started at /home/acidburn/public_html/header.php:32) in /home/acidburn/public_html/includes/sessions.php on line 250

[Wed Sep 17 17:32:12 2003] [error] PHP Warning: Cannot modify header information - headers already sent by (output started at /home/acidburn/public_html/header.php:32) in /home/acidburn/public_html/includes/sessions.php on line 249

abstraktMedia · #2 09-18-2003, 05:03 AM

There's an option in php.ini which should solve this....

Usually the prgrammers avoid this with some other ways of page redirection or by using output buffering functions provided in php...

angeleyz · #3 09-18-2003, 05:19 AM

Hmmm, I'll pass on the word... However, might I note that this ONLY happens when people try to access the forums.... :?

abstraktMedia · #4 09-18-2003, 06:26 AM

Hm...hm....could you please post me the URL of the forum that displays this...you can use PM if you don't wanna make it public and in the meanwhile I'll try to think something out(professional deformation as beeing web-developer

)

Is that phpBB forum??

angeleyz · #5 09-18-2003, 11:01 AM

http://www.babiesandbellies.com/modules.php?name=Forums

Note: Not everyone gets the error message -- only some people are getting it. I personally do not get it. When they get the above said messages, they are unable to post at all. Despite clearing cookies/temp files/offline files. So I can't tell if this is user error (they're cookie settings are too high) or an error on my end.

And as mentioned in my original post, this is PHP Nuke 6.8

abstraktMedia · #6 09-22-2003, 12:06 PM

Hello...and sorry for the delay...my wife and I were(actualy are still) sick and have a flue so I was staying away from comp for a few days...

I was thinking about your problem(I don't get that message) but I don't think it has anything to do with cookies...

Whe I started as a developer that was a very annoying message but I found a way to avoid it in my coding practice....

This message comes up when you're trying to redirect the page with the header() command in PHP or doing something with the HTML headers using that command....it works fine but you have to call it before any HTML tags...

example
[code:1:572aea2822]
<html>
<head>
<?php
header("Location: some_page.php");
?>
</head>
...
[/code:1:572aea2822]
and here's where you'll get the error because <html> tag was send to browser before header() command.....

The only solution I see here is to find the file that causes this and add at the very begining ob_start();
and at the very end ob_flush();

Hope this helps....

angeleyz · #7 09-22-2003, 12:35 PM

Hmmm, thx for the help! I'll check it out

*edited to say -- I hope you are feeling better now! My whole family just went through a flu bug too. I woke up feeling pretty crappy, but took some pills and now I feel better.

abstraktMedia · #8 09-22-2003, 01:04 PM

I hope you are feeling better now!

Thanx..I am a bit....

But my wife isn't

I woke up feeling pretty crappy, but took some pills and now I feel better

I was feeling like this whole week and over the weekend and thought I'll kill it with pills but I saw that I just have to "kill" it in bed

Just a tip: try to find out what browsers people that got that message are using....It might be very usefull info....

I personally am a MozillaFirebird man

angeleyz · #9 09-22-2003, 02:03 PM

Yeah, that's what I've been trying to find out. The ones I've been getting complaints from lately hvae been AOL users and Mac users. The AOL-ers I've told to try using IE, but that doesn't work for them either. I forget what browser the Mac user had

However... we think we found the problem. It was actually in the posting script -- it was trying to send information to some strange server... :? So now we just gotta wait and see if that fixes it since neither of us were having this problem at all.

Oh, I think I forgot to mention in my original post, but these people only get these errors when trying to post.

Thx for the help