WordPress.org

Ready to get started?Download WordPress

Forums

Warning: Cannot modify header information (4 posts)

  1. mriannnnnn
    Member
    Posted 11 years ago #

    I looked around and could not find any posts on this subject and if there are I apologize for double posting.
    anyhoo, I have updated to the latest and greatest version and I keep getting an error of "Warning: Cannot modify header information" when I try to login. I will paste at bottom full text.
    I have gotten rid of all my custom code and other things but I keep getting this error. It is only on my local machine so you will not be able to see it on the net. I use it to test and have a personal blog that I use for a work journal.
    Warning: Cannot modify header information - headers already sent by (output started at /xxx/wordpress/wp-config.php:28) in /xxx/wordpress/wp-login.php on line 254
    Warning: Cannot modify header information - headers already sent by (output started at /xxx/wordpress/wp-config.php:28) in /xxx/wordpress/wp-login.php on line 255
    Warning: Cannot modify header information - headers already sent by (output started at /xxx/wordpress/wp-config.php:28) in /xxx/wp-login.php on line 256
    Warning: Cannot modify header information - headers already sent by (output started at /xxx/wordpress/wp-config.php:28) in /xxx/wordpress/wp-login.php on line 257
    Warning: Cannot modify header information - headers already sent by (output started at /xxx/wordpress/wp-config.php:28) in /xxx/wordpress/wp-login.php on line 258

  2. Anonymous
    Unregistered
    Posted 11 years ago #

    Header errors appear when you send output data to the browser before headers and cookies are set. This output includes white space, returns, tabs and other characters.
    I'd suggest opening up the wp-config.php and make sure there's no white space, tabs, or returns lurking around before or after the opening and closing php tags. Also if you added custom code make sure that there's nothing printing anything to the screen before headers and cookies are set. It would be hard for any of us to pin point exactly where the problem could be without actually seeing the code.

  3. mriannnnnn
    Member
    Posted 11 years ago #

    well that did it. while editing the config file there must of been some white space.
    Problem solved thanks.
    Might want to add some usability text in the "wp-config-sample.php" file so people know not to do that.

  4. mriannnnnn
    Member
    Posted 11 years ago #

    now I guess I'll move onto the other SQL problems heh

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags

No tags yet.