WordPress.org

Ready to get started?Download WordPress

Forums

wp-admin/post.php = Blank Screen | Deactivate All Plugins = Blank Screen??? (5 posts)

  1. rob33
    Member
    Posted 4 years ago #

    I've just checked 5 different WP sites of mine and none are letting me "update" posts.

    The screen just goes to ...wp-admin/post.php which is blank - and nothing has been saved.

    I've tried deactivating all plugins but I get the same result - blank screen - and none have been deactivated.

    All sites on same server.

    I could understand if it was just one site but "all"?

    Could this be a server issue? - I'm with namecheap.

    Also - I'm trying to update a mates site - and as opposed to a blank screen - it just hangs there and goes to The connection was reset.

    Any ideas would be great - thanks...

  2. It certainly sounds like a server issue since it all happened at once and you didn't do anything. Have you contacted your hosting provider?

  3. raymunde
    Member
    Posted 3 years ago #

    It's happening to me and I am using my localhost since I am just working on themes. Each time I publish, update or save as draft it goes to wp-admin/post.php = blank!

  4. raymunde
    Member
    Posted 3 years ago #

    My localhost Apache/2.0.63 (Unix) PHP/5.3.2 DAV/2, MySQL client version: 5.1.44, PHP extension: mysql

  5. madhavaji
    Member
    Posted 3 years ago #

    Hello,

    I had this problem and found a fix (for my particular version of it) with this post from Chris Hannah.

    Essentially I had inadvertently put some white space at the end of my functions.php file, like this..

    <?php
    
    Some functions.php code..
    
    ?>[some white space inserted here in error!]

    As Chris Hennan points out, adding

    php_flag output_buffering on
    to the .htaccess file does make php ignore the whitespace and WordPress works again.. if you're anything like though me you'll want to go find the whitespace and remove it.

    In any case, if you have the

    whitespace which was sent to the browser before the redirect was called resulting in a “headers already sent” problem
    either of these will solve it.

Topic Closed

This topic has been closed to new replies.

About this Topic