Forums

[resolved] Blank Screen of Death Solution! (3 posts)

  1. ljmac
    Member
    Posted 3 years ago #

    Well, I've been messing around with 2.5, 2.5.1 and the just released 2.6, and no matter what I do, when I try to install any of them, I get the same blank screen and the same PHP error from /wp-admin/includes/media.php.

    However, I noticed 2.3.3 and earlier didn't have this file, so I decided to try installing it. Voila! It works!

    So I was obviously installing it correctly, but there is clearly a serious bug in the code of /wp-admin/includes/media.php (from WordPress 2.5 upwards).

    As this file relates to the new admin interface, it explains whey some people are getting blank admin screens after upgrading to 2.5 and later, while other people (like me) simply can't install it in the first place.

    I am going to need some very serious convincing that this bug has been fixed before I even consider "upgrading" to a newer WordPress version.

  2. ljmac
    Member
    Posted 3 years ago #

    For the benefit of the authors of WordPress, here's the PHP error I'm getting in 2.5/2.6 again:

    2.5.1:

    PHP Parse error: syntax error, unexpected T_ENCAPSED_AND_WHITESPACE, expecting T_STRING or T_VARIABLE or T_NUM_STRING in [URL removed for security reasons]/wp-admin/includes/media.php on line 154

    2.6:

    PHP Parse error: syntax error, unexpected T_ENCAPSED_AND_WHITESPACE, expecting T_STRING or T_VARIABLE or T_NUM_STRING in [URL removed for security reasons]/wp-admin/includes/media.php on line 197

    As you can see, they both produce the same error - it's just on a different line (presumably due to this file growing in 2.6).

  3. ljmac
    Member
    Posted 3 years ago #

    I have now found a solution to this issue that works with WordPress 2.5 and later! Unlike other php aps I've used, WordPress 2.5.x upwards seems to require UNIX carriage returns. Hence, if you edit a file on your PC or your Mac, it will have a Mac or PC style carriage return in the file, and this will completely break it.

    The only way I've found to solve this issue is to use a text editor (like TexEdit Plus on the Mac) which allows you to convert all the carriage returns back to UNIX carriage returns when you've finished editing.

    Note that when I first encountered this issue, I could not install WordPress 2.5.x upwards at all. However, since I figured this out, I've been able to run my blog for 2 months now without a single blank screen.

Topic Closed

This topic has been closed to new replies.

About this Topic