Support » Fixing WordPress » Blog Completely “Gone” after 2.5 Upgrade

  • Hi all!

    First post in the forum…which is a good sign, meaning that I’ve had VERY few problems using WordPress over the past six months.

    I upgraded from 2.3.3 tonight to 2.5, then after I carefully copied all of the files out of 2.5 to overwrite my old 2.3.3 files (taking care to NOT overwrite the critical files that needed to be preserved), I went to log in and upgrade the site, and the site is simply gone. Blank white screen…no errors or even page source! Just a “Done” message in my browsers when I try to load the site or login to the WordPress admin info (hosted on my web host’s server space).

    My host users MySQL version 5.0.45, and PHP version 4.4.7. The only thing I can think of is that I might not have logged out of the WordPress site admin one of my browser tabs before installing and uploading the new files on to my host server. Could that have messed things up?

    I’ve never had a problem upgrading versions before, but as of now, I have ZERO blog…so I would appreciate any help people might be able to offer. Thanks!

    Derek –

Viewing 15 replies - 1 through 15 (of 26 total)
  • Edited to add:

    It DOES occasionally give me a bare-bones login/password info set in a browser window, but when I enter my login and password info, it re-directs to the following URL:

    Still completely grounded, and unable to login to my WordPress Admin info.

    After reading a few more other threads, I thought I would try and delete the wp-admin folder off my web server and then re-load it, just to try and shake-out a few cobwebs and hope. That still did not correct the problem. Ugh. I’m sure it’s probably an easy fix, but I’m grounded until I figure out what’s gone wrong.



    Actually the uprgading instructions actually said to DELETE (not OVERWRITE) the old files (except those listed not to delete) completely and then re-upload the new ones.

    Also, seeing how you cannot access your Admin Panel as of now, trying backing up all the plugins file on your computer and deleting them off the server to see if it helps. I’m not sure whether you are aware but all plugins must be disabled before upgrading (well hope you did!).

    That’s all from me…I’m not that pro but plugins were my main cause when I experienced a blank page.

    Thanks for the ideas, fantasycrusader, but I’m still stuck with a blank white screen. Tried to completely delete all of the plugins off our web server, as well as re-installing plugin fills to the server after that didn’t work. Neither task lets me even see the ability to enter a login and password to access the dashboard. My next step today will be to completely remove the entire “/blog/” directory off my web server, then re-install everything from scratch. So much for the “five-minute” update for WordPress 2.5…. 🙁

    Whenever I do an upgrade, I use FTP (FileZilla).

    I deactivate all the plugins.

    I then upload the new WordPress right over top of the old one (I don’t delete anything except hello-dolly.php in the plugins directory). The only file that I’m aware of that needs to be preserved is the config.php file, but there usually shouldn’t be one in the new WordPress to overwrite the old one.

    Once the upload is complete, you goto http://…/blogname/wp-admin/upgrade.php and it will make any necessary changes to the database and you should be good to go.

    I would suggest you re-download WP 2.5 from the WordPress site and then re-upload it over top of whatever is on your site to make sure all the files got transfered properly.

    If it still doesn’t work after you try re-doing WP 2.5 I suggest going back to WP 2.3.3 until further troubleshooting can be used.

    I think its a problem with THEME or HTACCESS, try to remove them temporarily to see if it works, plus clear your browser cookies and cache.



    I’ve had blank-page problems with pre 2.5 WP installs after upgrading, and it’s usually been a problem with a theme. As in: no theme is active. 8-|

    If you can’t get to your admin page, get into the db however you normally do (command line, phpMyAdmin, etc) and set the theme to the default theme.

    Thanks for all the suggestions, everyone! Since posting my initial “S.O.S.” I have also gotten in touch with my web host as well. I use vDeck to manage files and such with them…and they told me today that they have been having significant problems related to MySQL and the recent 2.5 roll-over as well. They claim they are working on it…although sometimes that means it could take DAYS for me to hear back from them.

    In the interim, I am curious to learn how I could set a “default” theme and see if I can solve the problem myself. Quite honestly, the only time I go within a ten-foot-pole’s reach of MySQL at all is when WordPress is giving me problems related to upgrades (twice now, but the first time was a minor glitch). Even when I try and login to MySQL via vDeck, no luck. I think I am probably out of luck until my web host gets MySQL and 2.5 to play nice with one another…though if anyone can share other ideas and/or more specific instructions for re-setting my site’s theme (I use a significant hack to the wuhan-03 theme), I would greatly appreciate it. Thanks!




    Does your host offer phpMyAdmin?


    Truthfully, I don’t even know. I am VERY good at coding and image optimization (one of the very-best when it comes to optimizing imagery)…but make me have to deal with database administration when it comes to web development, and I am about as far from being an “expert” as they come. 🙂 WordPress is great because they make it pretty simple to blog using MySQL or ??? without really having to understand how it works behind the scenes. That is, unfortunately, until something “breaks.”

    I don’t see “phpMyAdmin” within my “Control Panel” of options available to me in vDeck. I am hoping to figure out a way in if I can…as it might take my web host days to get to the bottom of things on their end, as opposed to hours. I was connecting just fine with 2.3.3 though, pre-upgrade to 2.5. With all the problems I have experienced, however, it makes me wish I would have hung on to 2.3.3 for a while longer…

    I have one question for you? Did you by any chance “backup” your wp-config.php file? If you did, upload it and see if things work. If you wrote over that file or somehow deleted it – wp can no longer access your database.


    Thanks for the suggestion. That was one of the first things I tried last night…making sure that my wp-config.php file was not missing, damaged or overwritten. It looked the same to me as before, so I assumed this wasn’t the problem. However, the contents of that .php file can be found below (with me obviously removing account-sensitive information):

    // ** MySQL settings ** //
    define('DB_NAME', '**********'); // The name of the database
    define('DB_USER', '**********'); // Your MySQL username
    define('DB_PASSWORD', '**********'); // ...and password
    define('DB_HOST', '**********'); // 99% chance you won't need to change this value
    define('DB_CHARSET', 'utf8');
    define('DB_COLLATE', '');
    // You can have multiple installations in one database if you give each a unique prefix
    $table_prefix  = 'wp_'; // Only numbers, letters, and underscores please!
    // Change this to localize WordPress.  A corresponding MO file for the
    // chosen language must be installed to wp-content/languages.
    // For example, install to wp-content/languages and set WPLANG to 'de'
    // to enable German language support.
    define ('WPLANG', '');
    /* That's all, stop editing! Happy blogging. */
    define('ABSPATH', dirname(__FILE__).'/');


    Ok, let’s assume phpMyAdmin — or any db administration — is not possible.

    Get your old wp backup folder and upload it to your server at the same folder level as it was. Rename it “wp-old” before uploading so that you don’t upload over 2.5.

    Then access your WP admin panel — — via your web browser and set a theme.

    Disregard all this if the 2.5 db is significantly different enough to make this exercise impossible, i.e.: use of 2.3 web files with 2.5 db.

Viewing 15 replies - 1 through 15 (of 26 total)
  • The topic ‘Blog Completely “Gone” after 2.5 Upgrade’ is closed to new replies.