WordPress.org

Ready to get started?Download WordPress

Forums

Cannot modify header information - headers already sent (23 posts)

  1. tmtracy
    Member
    Posted 9 years ago #

    when I try to unaprove comments I get this warning:

    Warning: Cannot modify header information - headers already sent by (output started at /public_html/wp-admin/admin-header.php:8) in /public_html/wp-admin/post.php on line 569

    anyone know what to do?

  2. moshu
    Member
    Posted 9 years ago #

  3. tmtracy
    Member
    Posted 9 years ago #

    thanks a lot. cheers!

  4. tmtracy
    Member
    Posted 9 years ago #

    so far...that didn't work. I checked the files that it wanted, and edited them...still getting that same error.

  5. tmtracy
    Member
    Posted 9 years ago #

    I took out this line on post.php in the admin folder

    require_once('./admin-header.php');

    that was line 548, under the unaproove section. the aproove section did not have that line, so I took it out under the unaproove section and it's working fine...anyone know what that line does, or if there will be a problem without it?

  6. Umm... put that line back. You'll need to call admin-header.php for the proper operation of your admin interface. As quoted in the error, the problem is in admin-header.php on line 8.

  7. moshu
    Member
    Posted 9 years ago #

    Hmmm... I don't think it's a smart idea to take out lines (especially when they say "require") from the core files.
    Stick to the finding the white spaces! What text editor are you using?

  8. tmtracy
    Member
    Posted 9 years ago #


    case 'unapprovecomment':

    require_once('./admin-header.php');

    check_admin_referer();

    was the line...and after I removed it then it was fine...so, I should look in the file on line 8 then, ok.

    I put that line back...and I can not find any problems with admin-header.php and on line 8 is some html...

  9. tmtracy
    Member
    Posted 9 years ago #

    <title><?php bloginfo('name') ?> › <?php echo $title; ?> — WordPress</title>

    that is the line...

  10. tmtracy
    Member
    Posted 9 years ago #

    notepad is what I am using

  11. tmtracy
    Member
    Posted 9 years ago #

    all of my files for whatever reason don't have line breaks...instead they have an unknown BLOCK char...that I have to go through and replace all of them with a crlf...not sure why that either...

  12. lbessant

    Posted 9 years ago #

    Try TextPad or any other editor that understands about Unix-style line breaks. If you search here, you'll find plenty of suggestions for good text editors, many of them free. Notepad is really not up to the job....

  13. Download WordPress again, delete the admin-header.php file off of your server and upload a new copy from the fresh download.

    For a good text editor, see this list:

    http://codex.wordpress.org/Glossary#Text_editor

  14. tmtracy
    Member
    Posted 9 years ago #

    I tried reinstalling the whole thing...and it is still saying the same error. I have looked and corrected tons of whitespace in files and things are still being borked up...any other thoughts?

  15. What FTP app are you using?

  16. tmtracy
    Member
    Posted 9 years ago #

    filezilla

  17. tmtracy
    Member
    Posted 9 years ago #

    I have tried everything...anyone else have any ideas?!

  18. tmtracy
    Member
    Posted 9 years ago #

    I have checked the files over and over, reuploaded many times...I can't figure out anything that's wrong. any one know any more ideas, or how to email the developers?

  19. tmtracy
    Member
    Posted 9 years ago #

    any help would be great. =)

  20. Ryan Boren
    WordPress Dev
    Posted 9 years ago #

    There's nothing for the developers to fix. This is an issue caused by the text editor or ftp client. Are you uploading in ASCII mode?

  21. tmtracy
    Member
    Posted 9 years ago #

    what should I upload in...ascii?

  22. tmtracy
    Member
    Posted 9 years ago #

    I tried uploading in ascii mode...and I have looked for newlines like was posted about...does anyone else have this problem...if you click on manage then click unaproove on a comment. I can't see what's wrong...

  23. jjriv
    Member
    Posted 9 years ago #

    This bug is being caused by the require_once() command. It should not be adding html to the browser before doing a redirect. The browser has already received headers when it then sees a redirect header. That is why it geeks out. I'm not even sure why this line of code is there since this case redirects no matter what. Take out that line and the code works fine. The line isn't needed.

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags

No tags yet.