• When I go to my admin screen (https://derekdavis.org/wp-admin), I get the following warning:

    Warning: Cannot modify header information – headers already sent by (output started at /home/11749/domains/derekdavis.org/html/wp-content/themes/cardeo-standard/functions.php:11) in /home/11749/domains/derekdavis.org/html/wp-includes/pluggable.php on line 850

    Please help!

Viewing 8 replies - 16 through 23 (of 23 total)
  • Old topic, but, this will help others I am sure.

    As stvwlf said,

    Chek in your site template folder. if you have a “functions.php” file in there, make sure there are no whitespaces, especially after the final closing ?> tag, and remove any line breaks (ie, make sure ?> is the final line of your file.

    I had EXACTLY this issue, where pluggable reads my template to see if there are any extra functions to be added, and breaks via pluggable.

    To test, simply rename your “functions.php” to “-functions.php” and you’ll that this could be the problem.

    Thank U Archetory

    I’ve tested all the suggestion on my site, but there’s only rename as “-functions.php” work~ it’s weird, but works!

    I fixed it on my site. You just must make sure you open up the correct line to edit.
    Example:
    Warning: Cannot modify header information – headers already sent by (output started at /var/www/vhosts/phattkicks.com/httpdocs/wp-includes/class.wp-scripts.php:54) in /var/www/vhosts/phattkicks.com/httpdocs/wp-includes/pluggable.php on line 711

    The error of the ?> space is on line 54, not 711 where it sounds like it is.

    7.

    Help me..I’ve read some messages but nothing can help me. some asked me to remove plugins but i can’t even see my homepage.What should I do?

    this is what I got. please I beg your help.

    Warning: Cannot modify header information – headers already sent by (output started at /home/coloncl3/public_html/budakhitam.com/wp-content/plugins/google-news-widget/google-news-widget.php:1) in /home/coloncl3/public_html/budakhitam.com/wp-includes/pluggable.php on line 868

    Hi,

    It is usually due to spaces, new lines, or other garbage at opening/closing PHP file <?php tag or after a closing ?> tag in wp-config.php. It can be other file too so need to check error message as it may list file name where the error occurred.

    You can either upload error file from the backup or edit erroneous file. To edit the file one need to check below mentioned points:

    1. Download the file mentioned in the error message.

    2. Open that file in a plain text editor

    3. Check that the very first characters are <?php

    4. Check that the very last characters are ?>

    5. Place the cursor between the ? and >

    6. Now press the DELETE key on your computer and keep that key pressed for at least 15 seconds.

    7. Now type > and

    8. Save without pressing any other key at all.

    That’s it!

    Thanks,

    Shane G.

    6. Now press the DELETE key on your computer and keep that key pressed for at least 15 seconds.

    7. Now type > and

    8. Save without pressing any other key at all.

    What his saying is to make sure that there arn’t any non-pritable charachters at the end of the file.

    Tahnks phenry, I edit and save the wp-config.php using notepad in coded ANSI diferent them normaly utf8

    and its Work’s

    GREAT

    I am having the same error message – something about not being able to modify header information – specifically:

    Warning: Cannot modify header information – headers already sent by (output started at /home/content/04/5805304/html/wp-content/plugins/affiliate-link1/affli-config.php:133) in /home/content/04/5805304/html/wp-content/plugins/wp-super-cache/wp-cache-phase2.php on line 71

    All of the previous advice sounds great – the only problem for me is that I cannot even log in in order to make any adjustments. Can anyone get me behind door #1??? Thank you in advance as this is VERY frustrating.

Viewing 8 replies - 16 through 23 (of 23 total)
  • The topic ‘Cannot modify header information – headers already sent’ is closed to new replies.