Web Hosting Talk







View Full Version : WHT Error


Nedani
08-22-2002, 03:56 PM
I get the fallowing message on top of every page I see on WHT:

Warning: Cannot add header information - headers already sent by (output started at /usr/whtalk/www/newreply.php:1) in /usr/whtalk/www/admin/functions.php on line 1533

Let me know if I can help.

ned patter
08-22-2002, 04:58 PM
I was getting the same today.
At first I thought my connection speed was to fast for this site to handle.

Vinayak_Sharma
08-22-2002, 05:09 PM
same problem here, have sent the report to chicken

dbzgod
08-22-2002, 05:49 PM
Getting it too. Chicken can fix it though...

interactive
08-22-2002, 05:50 PM
whats going on is something is trying to echo before a cookie is being set...

The Prohacker
08-22-2002, 06:02 PM
Its a whitespace problem in the config.php


Make sure the first thing in the config.php is <?php and not a return or a space..

And make sure there is no extra whitespace at the end of the config.php...

Make sure the last thing in the file is ?> :D

WebDev
08-22-2002, 07:07 PM
What're you doing when you get the error? I've been trying to duplicate it for about half an hour now.

dbzgod
08-22-2002, 07:25 PM
I posted a message in the lounge and then refreshed the lounge main page and got it.

WebDev
08-22-2002, 07:25 PM
Nevermind I saw it, it seems to be intermittent, I'll have someone take care of it this evening, it's related to a stats tracking program. Shouldn't cause any problems with functionality in the meantime.

Chicken
08-22-2002, 11:22 PM
Be sure to email any forum problems to moderators@webhostingtalk.com so that someone on at that moment can have a look. I happen to be on vacation (doesn't it seem so? ;)) ...

SoftWareRevue
08-23-2002, 01:58 AM
Originally posted by Chicken
. . . . . I happen to be on vacation (doesn't it seem so? ;)) ... No.








Well, okay. Maybe you're not around as 'much' :D

combs
08-23-2002, 06:32 AM
I dont see any problem.

ned patter
08-23-2002, 10:11 AM
This is really what it was doing although i would imagine it's fixed now.