Databases
StackOverflow2013
Postsdbo
POUpgrading Wordpress 2.8.5 to 3.3.2, white screen of death
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUpgrading Wordpress 2.8.5 to 3.3.2, white screen of death
    primarykey
    data
    text
    <p>I'm trying to upgrade an old wordpress installation for a friend. I've got the following setup:</p> <ul> <li>remote LAMP live server running 2.8.5 Wordpress</li> <li>remote LAMP test server, currently horked after an attempted manual update from 2.8.5 to 3.3.2.</li> <li>local MAMP server to replicate test server</li> </ul> <p>I started out overconfident, because, hey, I've done this before, no problem. So I started with the <a href="http://codex.wordpress.org/Updating_WordPress#Manual_Update" rel="nofollow">seven step manual update</a> instead of the <a href="http://codex.wordpress.org/Upgrading_WordPress_Extended" rel="nofollow">extended manual update instruction</a>. (Mistake #1: I don't have a full backup of the test server, just the wp-admin and wp-includes, though I have the theoretically identical live server to pull from if necessary.)</p> <p>White screen of death. OK, I probably deserved as much. I <a href="http://codex.wordpress.org/Editing_wp-config.php#Debug" rel="nofollow">turned on debugging</a> and made sure there was a writable debug log file. Still blank screen of death. Disabled the plugins. Still white screen.</p> <p>So I duplicated the live server back to my local MAMP server, to get a functional 2.8.5 mirror, then updated it to 3.3.2. Success: sort of-- it failed in the exact same way, so I could debug it. Turns out the update required a default theme to be separately uploaded. Yay! When I added the theme, I see output to the log file, I see a happy blog page. Switch the themes back: broken, and no logging. </p> <p>So I go back to my test server, remove all themes but twentyeleven. No luck. OK, twentyten. No luck. The same default theme used in my local version. No luck. I now have a debug enabled (but no logs generated), plugin-free, default-themed manual upgrade with a white screen of death.</p> <p>I double-check all of the SO threads, WP help threads, etc-- yep, I've done everything they suggest. So instead of debugging core files one by one, I started over: copied the <b>functional</b> WP install from my local server (which should be identical to the dysfunctional remote WP install) to the remote test server (I see the expected "can't connect to db" message), update the wp-config, and see... nothing. WSOD. </p> <p>There is something that is making this code work on my local server and blank in a non-debuggable way on the remote server. Can anybody point me towards something else to try? </p> <p>If all else fails, I guess I'll do a manual install of 3.3.2 instead of the upgrade, but I'm leery of that for the live server. </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USbuzzo
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COIf the same files work locally but not remotely, there's a difference between the servers. My first guess is the version of PHP - which version are you running? You need 5.2.4 or greater, and MySQL 5.0 or greater.
      singulars
      1. POUpgrading Wordpress 2.8.5 to 3.3.2, white screen of death
      1. USuser1337
    2. COLAMP remote test server: PHP Version 5.3.8; MySQL 5.1.59. Locally, running PHP Version 5.2.17 and MySQL 5.5.9 on a MAMP server.
      singulars
      1. POUpgrading Wordpress 2.8.5 to 3.3.2, white screen of death
      1. USbuzzo
    3. COMake an intermediary step? 2.8.5 -> 3.0 -> 3.3.2
      singulars
      1. POUpgrading Wordpress 2.8.5 to 3.3.2, white screen of death
      1. USbrasofilo
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload