Okay, after some lengthy upgrading steps from a corrupted db, I got .72 db entires to 1.0 without a hitch. It worked fine. Ugh, then I decided to mess with templete-functions.php and it didn't go so well, so I reuploaded the original file. It gave the error below even after replacing w/ the original file. So, I re-installed 1.0 completely, no good. So, I re-installed 1.0 AND used backup to restore a db (a copy I made when WP was perfectly working). Yet, this problem still persits when I try to login.
blog --> http://kangsta.com/banter
Warning: Cannot modify header information - headers already sent by (output started at /home/jaikang/public_html/banter/wp-includes/template-functions.php:2037) in /home/jaikang/public_html/banter/wp-login.php on line 254
Warning: Cannot modify header information - headers already sent by (output started at /home/jaikang/public_html/banter/wp-includes/template-functions.php:2037) in /home/jaikang/public_html/banter/wp-login.php on line 255
Warning: Cannot modify header information - headers already sent by (output started at /home/jaikang/public_html/banter/wp-includes/template-functions.php:2037) in /home/jaikang/public_html/banter/wp-login.php on line 256
Warning: Cannot modify header information - headers already sent by (output started at /home/jaikang/public_html/banter/wp-includes/template-functions.php:2037) in /home/jaikang/public_html/banter/wp-login.php on line 257
Warning: Cannot modify header information - headers already sent by (output started at /home/jaikang/public_html/banter/wp-includes/template-functions.php:2037) in /home/jaikang/public_html/banter/wp-login.php on line 258
wp-config.php - Cant write to header error (2 posts)
-
hangule
Posted 8 years ago # -
Mark (podz)
Posted 8 years ago #That error is usually caused by extra whitespace or extra carriage returns before the first <?php or after the last ?>
Check the files mentioned for this.
A good editor for this job is http://www.crimsoneditor.com/
Topic Closed
This topic has been closed to new replies.
