Support » Fixing WordPress » Upgrade from 3.1 to 3.2: Endless "Your WordPress database is already up-to-date"

  • Resolved gboudreau


    I updated (automatically, then manually) to WordPress 3.2, from 3.1.4.
    Now, when I try to go in /wp-admin/, I get redirected to:
    which says:

    “No Update Required
    Your WordPress database is already up-to-date!”

    Clicking Continue sends me back to my blog’s homepage, and trying to access wp-admin again does the same.

    Any idea how I can debug what’s happening ?


    Blog URL:

Viewing 15 replies - 1 through 15 (of 18 total)
  • esmi


    Forum Moderator

    – switching to the Twenty Ten theme by renaming your current theme’s folder in wp-content/themes using FTP or whatever file management application your host provides.

    resetting the plugins folder by FTP or phpMyAdmin.

    Also flush your browser cache.

    I excluded the possible browser cause by using curl:

    $ curl -i ""
    HTTP/1.1 302 Found
    X-Powered-By: PHP/5.3.3

    I tried to rename my theme folder, but that didn’t help.
    I tried to rename my plugins folder too, and that didn’t help either.
    I’m always redirected to upgrade.php

    I also tried emptying the active_plugins options in MySQL (to a:0:{}), and that didn’t help either.
    I guess I’ll debug the PHP code to find why it redirects, when it shouldn’t (or why it thinks there’s nothing to update when there is).
    I use another prefix that wp_ for my tables; maybe it’s related.

    Are you also using MultiSite?


    I found that in ./wp-admin/admin.php:42
    get_option(‘db_version’) == 17516
    $wp_db_version == 18226

    But in ./wp-admin/upgrade.php:58, both get_option( ‘db_version’ ) and $wp_db_version == 18226

    I’ll continue to investigate why get_option(‘db_version’) in admin.php seems to be wrong… (MySQL options table where option_name = ‘db_version’ == 18226)

    Try re-applying the upgrade manually. You may have caught a bad download.

    I already did. I did an automatic upgrade first, and when I noticed that issue, I manually downloaded the tgz from the website, and unpacked over.

    I now found that the values returned by wp_cache_get( ‘alloptions’, ‘options’ ) seems to be outdated.
    Not sure what should trigger the cache to become invalid, but that seems to have failed… Continuing debugging.

    I’m pretty sure the problem comes from the memcached plugin I have installed…
    No idea why the problem would persist even with the plugins folder renamed though!

    Ah, I see… Part of the memcached plugin install was to copy a file into ./wp-content/object-cache.php!
    Renaming this file to object-cache.php.bak fixed the issue.

    I guess I should contact that plugin’s author, to tell him his cache wasn’t properly reset when it should have been?

    Also, a simple restart of the memcached process fixed this permanently, since that empty the memcache cache!

    Yeah, do let the plugin dev know 🙂

    Which one is this? I’m keeping a running list 😉

    Plugin Name: Memcached
    Description: Memcached backend for the WP Object Cache.
    Version: 2.0
    Plugin URI:
    Author: Ryan Boren

    You may want to upgrade to 2.0.1

    Indeed. Just did when I noticed I was using an older version.
    Thanks for your time.

Viewing 15 replies - 1 through 15 (of 18 total)
  • The topic ‘Upgrade from 3.1 to 3.2: Endless "Your WordPress database is already up-to-date"’ is closed to new replies.