WordPress.org

Ready to get started?Download WordPress

Forums

[resolved] White Screen Returns on Save Draft, Preview, Commenting (22 posts)

  1. jd99
    Member
    Posted 1 year ago #

    I erased and reloaded 3.5.1 after getting white screen errors and a "header" error. Reloading and deleting old plug ins seemed to make the errors go away. I continuously checked previewing posts and making comments on the blog and those functions worked. All seemed to be well.

    Then I wrote a new post. As soon as I hit "save draft," the white screen returned. Now I get it every time I save, preview, try to add a comment, or even logout (all of which I could do before successfully).

    This is the sole error I get when I save a draft or make a comment:

    Warning: Cannot modify header information - headers already sent by (output started at /services2/webpages/c/h/christianfighterpilot.com/public/blog/wp-settings.php:3) in /services2/webpages/c/h/christianfighterpilot.com/public/blog/wp-includes/pluggable.php on line 876

    However, when I try to logout, I get

    Warning: Cannot modify header information - headers already sent by (output started at /services2/webpages/c/h/christianfighterpilot.com/public/blog/wp-includes/functions.php:3) in /services2/webpages/c/h/christianfighterpilot.com/public/blog/wp-login.php on line 368

    Warning: Cannot modify header information - headers already sent by (output started at /services2/webpages/c/h/christianfighterpilot.com/public/blog/wp-includes/functions.php:3) in /services2/webpages/c/h/christianfighterpilot.com/public/blog/wp-login.php on line 380

    and 14 more just like it.
    Warning: Cannot modify header information - headers already sent by (output started at /services2/webpages/c/h/christianfighterpilot.com/public/blog/wp-includes/functions.php:3) in /services2/webpages/c/h/christianfighterpilot.com/public/blog/wp-includes/pluggable.php on line 697

    I've referenced those lines (cookies and author information) and can't figure out why I suddenly have an error.

    Any help?

  2. WPyogi
    Volunteer Moderator
    Posted 1 year ago #

    Would probably be better to continue in your earlier thread on this issue so people know what has already been tried...
    http://wordpress.org/support/topic/warning-headers-already-sent-reference-line?replies=6

  3. WPyogi
    Volunteer Moderator
    Posted 1 year ago #

    You can change that one back to "unresolved" BTW.

  4. WPyogi
    Volunteer Moderator
    Posted 1 year ago #

    Now that I said that, I looked at your site and if you use View Source - it looks like there are some empty lines above the DOCTYPE - so those would be in the header.php file - did you modify that file, by chance?

    You could try opening that file and removing all spaces before the first php tag - see this:

    http://codex.wordpress.org/FAQ_Troubleshooting#How_do_I_solve_the_Headers_already_sent_warning_problem.3F

  5. jd99
    Member
    Posted 1 year ago #

    I didn't modify header.php, though I did use the WP Admin panel appearance option to upload a graphic.

    I don't see any empty lines in the source file. I've read that FAQ before and don't have lines at the end or beginning. I've used both FrontPage and ExpressionWeb to ftp the files.

  6. jd99
    Member
    Posted 1 year ago #

    The "empty" lines in View Source are PHP comments in the original file that precede the DOCTYPE html.

  7. WPyogi
    Volunteer Moderator
    Posted 1 year ago #

    Those empty lines in View Source aren't normally there - just looked at a test install. Not sure that's the problem - but maybe worth a try.

  8. jd99
    Member
    Posted 1 year ago #

    I'm not sure how to delete them since they're not in the actual file. The PHP bumps right against the DOCTYPE, and I didn't touch that file.

    I just tried to delete blank lines at the end of all the wp files and generated a 500 error for my trouble. Reloaded the files.

  9. WPyogi
    Volunteer Moderator
    Posted 1 year ago #

    You could try downloading a new copy of twentytwelve to your local computer and replacing the header.php file via FTP.

  10. jd99
    Member
    Posted 1 year ago #

    I just deleted the theme, reinstalled it. Same problem.

  11. jd99
    Member
    Posted 1 year ago #

    I deleted and re-uploaded the php files within wp-admin -- no change.

    I deleted and re-uploaded the php files within wp-includes -- everything now works...for the time being, as far as I can tell. I still don't know what caused the white screen issue.

    I went through the same test steps: commented, edited, previewed, new draft, everything worked.

    I just don't know why.

  12. WPyogi
    Volunteer Moderator
    Posted 1 year ago #

    Hmm, weird indeed. But glad it's working now anyway. If it reappears, if anyone can help you sort it, esmi and catacaustic in the other thread know a hell of a lot (more than I do) so I'd put my money on them :).

  13. WPyogi
    Volunteer Moderator
    Posted 1 year ago #

    It would be good to update that other thread for the time being as well - just so they don't dive into it.

  14. jd99
    Member
    Posted 1 year ago #

    Six hours after having a working blog, I reattempted one thing: saving a test draft blog. Got a white screen. Tried commenting, previewing, same thing.

    Deleted, reuploaded wp-admin and wp-includes files (not folders), still didn't work.

    Deleted, reuploaded root wp files (not folders), started working. Turned on the config debug option, and got no errors.

    What can possibly be breaking?

    It wasn't my intention to have two open threads on this; I'll point the other one here.

  15. jd99
    Member
    Posted 1 year ago #

    The site continues to break (white screen as above) for a reason I can't explain. It isn't immediate, because I walk away from a working site and come back to a broken one. I'm not sure if its time or some action being taken. This last time, when I couldn't leave a comment without getting a white screen, uploading the root files didn't help, but the includes files did. I can't conceive a rhyme or reason for why different files fix it different times.

  16. jd99
    Member
    Posted 1 year ago #

    In a predictable fashion, my blog will work perfectly fine, and then a few hours later I will return to it and as soon as I try to do anything like preview a post, approve a comment, etc, I get a white screen. The error is

    Warning: Cannot modify header information - headers already sent by (output started at /services2/webpages/c/h/christianfighterpilot.com/public/blog/wp-settings.php:3) in /services2/webpages/c/h/christianfighterpilot.com/public/blog/wp-includes/pluggable.php on line 876

    I can repair the site by re-uploading all the files (not folders) from the includes and root wp folder. I've tried uploading them in different orders, but until I get all of the files uploaded, I continue to get the error. The site will continue to work perfectly until I come back to it a few hours later.

    The only plug in I have operating is akismet. I have a twentytwelve-child running with no changes to those files and very few modifications themselves.

    Any help would be appreciated, as re-uploading the blog every few hours is unsustainable.

  17. jd99
    Member
    Posted 1 year ago #

    New item: I downloaded the old wp-config prior to overwriting it, and it had new code at the top. It was a 2500 character php line that started and ended like this:

    <?php eval(gzinflate(base64_decode(' redacted ')));?>

    Anybody know what that is?

  18. Krishna
    Volunteer Moderator
    Posted 1 year ago #

    That is base 64 code, sometimes used by hackers to hide scripts and other info they want to use - though base 64 is used for many other good purposes. However, there is no chance that can be in your config.php file. Looks like an intrusion or hack.
    You may decode it or paste it at http://pastebin.com/ and post the link here.

  19. Krishna
    Volunteer Moderator
    Posted 1 year ago #

    Sorry Jan, it's a cross-post.

  20. Nothing to be sorry about. ;)

  21. jd99
    Member
    Posted 1 year ago #

    Thank you for that quick reply; I apologize for the immediate post when I saw something new. I web-searched portions of the code and started to come to the same conclusion.

    As described, I have deleted my entire blog, changed the passwords, and uploaded a clean WP install. For now, the site is working. Hopefully, there isn't a hidden hacked file somewhere else I don't know about.

Topic Closed

This topic has been closed to new replies.

About this Topic