Hello, My hosting company has just replaced the HDD's on my server and since the new install I am getting this error on signup with the aMember script that has always run with 100% reliability in the past. ----------------------------------------------------------------------------------------------------- Steve441234admin@mysite.org number= 5WARNING: Cannot modify header information - headers already sent by (output started at /home/steve01/public_html/amember/signup.php:311) in line 326 of file signup.php WARNING: Cannot modify header information - headers already sent by (output started at /home/steve01/public_html/amember/signup.php:311) in line 327 of file signup.php and on the next page I also get..... Steve441234admin@mysite.org number= 5WARNING: Cannot modify header information - headers already sent by (output started at /home/steve01/public_html/amember/signup.php:311) in line 326 of file signup.php WARNING: Cannot modify header information - headers already sent by (output started at /home/steve01/public_html/amember/signup.php:311) in line 327 of file signup.php WARNING: Cannot modify header information - headers already sent by (output started at /home/steve01/public_html/amember/signup.php:311) in line 43 of file free.inc.php ------------------------------------------------------------------------------------------------------ Does anyone have a clue on what this could be? I have the host working on it but they may need some clues as to the cause. I have CHMOD permissions set to 777 and despite the errors the script registers the new user as "pending" in aMember. It does not send the appropriate emails to admin for approval etc. Any ideas? Regards, Steve
I've seen this a number of times in a various situations: 1) Having blank lines at the end of the template file or php file. Have you made any changes to startup.php or startup.html (or any other files for that matter?) Check for extra lines that shouldn't be there. 2) Corrupt files (try, for example re-uploading startup.php and startup.html) 3) Having multiple "start session()" statements in a third party header file (didn't see any mention of this in your post though)