Warning: Cannot modify header information – headers already sent by (output star

  • Resolved moisesvaldesgaleria

    (@moisesvaldesgaleria)


    12 years, 8 months ago

    I cannot log in after instalation.

    Warning: Cannot modify header information – headers already sent by (output started at /home/…/public_html/wp-config.php:1) in /home/…/public_html/wp-login.php on line …

    and some others with /wp-includes/pluggable.php

    please help
    thx

Viewing 11 replies - 1 through 11 (of 11 total)
  • wpdevx

    (@wpdevx)

    12 years, 8 months ago

    moisesvaldesgaleria,

    It may be the blank lines issue – try having a look at the files listed in your case
    wp-login.php
    pluggable.php

    Once you have the file open in your editor – look for the very last line of code on the page. Locate this bit of code: ?>

    delete any space in between the last line of code and the “?>”

    Hope this helps.

    ce_bradm

    (@ce_bradm)

    12 years, 8 months ago

    I just wanted to chime in and add that if you have any questions about what wpdevx is talking about, there is WordPress documentation on this issue here as well:
    http://codex.wordpress.org/Answers-Troubleshooting#Headers_already_sent

    Thread Starter moisesvaldesgaleria

    (@moisesvaldesgaleria)

    12 years, 8 months ago

    Hi, thanks for your answer, but it continue. Here I send you all details (error messages and lines). best.

    1
    Warning: Cannot modify header information – headers already sent by (output started at /home/moises/public_html/wp-config.php:1) in /home/moises/public_html/wp-login.php on line 353
    Line 353: header(‘Content-Type: ‘.get_bloginfo(‘html_type’).’; charset=’.get_bloginfo(‘charset’));

    2
    Warning: Cannot modify header information – headers already sent by (output started at /home/moises/public_html/wp-config.php:1) in /home/moises/public_html/wp-login.php on line 365
    Line 365: setcookie(TEST_COOKIE, ‘WP Cookie check’, 0, COOKIEPATH, COOKIE_DOMAIN);

    3
    Warning: Cannot modify header information – headers already sent by (output started at /home/moises/public_html/wp-config.php:1) in /home/moises/public_html/wp-includes/pluggable.php on line 737
    Line 737: setcookie($auth_cookie_name, $auth_cookie, $expire, PLUGINS_COOKIE_PATH, COOKIE_DOMAIN, $secure, true);

    4
    Warning: Cannot modify header information – headers already sent by (output started at /home/moises/public_html/wp-config.php:1) in /home/moises/public_html/wp-includes/pluggable.php on line 738
    line 738: setcookie($auth_cookie_name, $auth_cookie, $expire, ADMIN_COOKIE_PATH, COOKIE_DOMAIN, $secure, true);

    5
    Warning: Cannot modify header information – headers already sent by (output started at /home/moises/public_html/wp-config.php:1) in /home/moises/public_html/wp-includes/pluggable.php on line 739
    line 739: setcookie(LOGGED_IN_COOKIE, $logged_in_cookie, $expire, COOKIEPATH, COOKIE_DOMAIN, $secure_logged_in_cookie, true);

    6
    Warning: Cannot modify header information – headers already sent by (output started at /home/moises/public_html/wp-config.php:1) in /home/moises/public_html/wp-includes/pluggable.php on line 934
    line 934: header(“Location: $location”, true, $status);

    esmi

    (@esmi)

    12 years, 8 months ago

    Solving “headers already sent” warnings

    Thread Starter moisesvaldesgaleria

    (@moisesvaldesgaleria)

    12 years, 8 months ago

    Links says “can be garbage between … “
    I deleted all spaces at the beginning on wp-config.php. Like this:

    <?php
    define(‘DB_NAME’, …

    but it doesnt work. where is the problem?

    ce_bradm

    (@ce_bradm)

    12 years, 8 months ago

    Check the spaces at the end (instead of the beginning), such as:

    ?>
MAKE SURE THERE ARE NO SPACES HERE
    Thread Starter moisesvaldesgaleria

    (@moisesvaldesgaleria)

    12 years, 8 months ago

    yes, is done. but still.
    thanks

    ce_bradm

    (@ce_bradm)

    12 years, 8 months ago

    In addition to checking for space in a new line, are there any spaces after the closing tag?

    MAKE SURE THERE ARE NO SPACES HERE
MAKE SURE THERE ARE NO SPACES HERE<?

?>MAKE SURE THERE ARE NO SPACES HERE
AND MAKE SURE THERE ARE NO SPACES HERE

    And to confirm, your checking this file?

    /home/moises/public_html/wp-config

    The error message specifically states:
    output started at /home/moises/public_html/wp-config.php, So I am 99% sure that file is where the problem is.

    danieldotcom

    (@danieldotcom)

    12 years, 8 months ago

    I have the same exact problem. Curiously, it is happening using Godaddy after I migrated my website from Windows to Linux.

    ce_bradm

    (@ce_bradm)

    12 years, 8 months ago

    I recommend that you download your wp-config.php file and open it with notepad and wordpad and ensure that you don’t have any spaces in those locations.

    A problem I see often is that the file will have characters such as ^M in them, which your host may need to help you with. Here are some links that may shed more light on the issue:

    http://www.nics.tennessee.edu/node/325

    http://www.freebsddiary.org/control-m.php

    danieldotcom

    (@danieldotcom)

    12 years, 8 months ago

    Solved it! I downloaded a fresh config file from WordPress.org, retyped all login and DB data and replaced the one in my site.
    Before that, I couldn’t identify any space or ^M character using notepad or notepad++. But, anyway, it’s solved 🙂

    Thanks.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Warning: Cannot modify header information – headers already sent by (output star’ is closed to new replies.