Support » Fixing WordPress » Why auto-updating to 3.3.1 does not work?

  • Hi,

    I can’t seem to auto-update to 3.3.1 – after I click on that option, I just get a blank admin page (the side menu still show and I can go back to the dashboard and all works fine, just not update being performed)

    I really don’t want to get this done manually since I might break it in the process!

    Any help in getting this to work will be appreciated 😉

Viewing 3 replies - 1 through 3 (of 3 total)
  • Mine is doing the same thing. I’ve deactivated all plugins, etc. I’m attempting the manual update now…



    I’m experiencing this issue as well. I’ve got about 10 self hosted sites and only happening on one site. Has me stumped. I’ve tried working with the host and they suggested I reinstall the wordpress files. No luck.

    This will fix for you

    Step 1: Replace WordPress files
    1.Get the latest WordPress zip (or tar.gz) file.
    2.Unpack the zip file that you downloaded.
    3.Deactivate plugins.
    4.Delete the old wp-includes and wp-admin directories on your web host (through your FTP or shell access).
    5.Using FTP or your shell access, upload the new wp-includes and wp-admin directories to your web host, overwriting old files.
    6.Upload the individual files from the new wp-content folder to your existing wp-content folder, overwriting existing files. Do NOT delete your existing wp-content folder. Do NOT delete any files or folders in your existing wp-content directory (except for the one being overwritten by new files).
    7.Upload all new loose files from the root directory of the new version to your existing wordpress root directory.
    NOTE – you should replace all the old WordPress files with the new ones in the wp-includes and wp-admin directories and sub-directories, and in the root directory (such as index.php, wp-login.php and so on). Don’t worry – your wp-config.php will be safe.

    Be careful when you come to copying the wp-content directory. You should make sure that you only copy the files from inside this directory, rather than replacing your entire wp-content directory. This is where your themes and plugins live, so you will want to keep them. If you have customized the default or classic themes without renaming them, make sure not to overwrite those files, otherwise you will lose your changes. (Though you might want to compare them for new features or fixes..)

    Lastly you should take a look at the wp-config-sample.php file, to see if any new settings have been introduced that you might want to add to your own wp-config.php.

    Step 1.5: Remove .maintenance file
    If you’re upgrading manually after a failed auto-upgrade, delete the file .maintenance from your WordPress directory using FTP. This will remove the “failed update” nag message.

    Step 2: Update your installation
    Visit your main WordPress admin page at /wp-admin. You may be asked to login again. If a database upgrade is necessary at this point, WordPress will detect it and give you a link to a URL like Follow that link and follow the instructions. This will update your database to be compatible with the latest code. You should do this as soon as possible after step 1.

    Step 3: Do something nice for yourself
    If you have caching enabled, your changes will appear to users more immediately if you clear the cache at this point (and if you don’t, you may get confused when you see the old version number in page footers when you check to see if the upgrade worked).

    Your WordPress installation is successfully updated. That’s as simple as we can make it without Updating WordPress Using Subversion.

    Consider rewarding yourself with a blog post about the update, reading that book or article you’ve been putting off, or simply sitting back for a few moments and letting the world pass you by.

    Final Steps
    Your update is now complete, so you can go in and enable your Plugins again. If you have issues with logging in, try clearing cookies in your browser.

    Linl for this topic

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Why auto-updating to 3.3.1 does not work?’ is closed to new replies.