Support » Requests and Feedback » WP dashboard tells me to upgrade to 2.3.3. Why?

  • Hi everyone,

    I just downloaded (what I thought was the 2.3.3) on March 5, 2008. After I unzipped WP, my folder title stated it was WP 2.3.3. However, when I log in to my dashboard, and at the bottom, it tells me my 2.3.2 is out of date and I need to upgrade.

    How can it be 2.3.2 when my file title says 2.3.3 and I just downloaded it 10 days ago? Should I just ignore this? Can I remove it from WP? Do I have the latest version?



    P.S. Thanks to everyone who helped on my install. And thanks in advance to any who might help me on this.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The location of the file that contains the version number is,

    Somehow that file was not properly overwritten/upgraded during the upload process. That said, I think it’s safe to assume there are other files that may not have uploaded properly either. To play it safe you may want to re-up everything.

    Unfortunately ftp-ing is not an exact science and I’ve seen many strange things happen during the procedure.

    Are you using any plugin or other method to remove the WordPress version identification from your site?

    The only reason I ask, is that I had an identical issue on a WordPress installation where the owner was using the bs-wp-noversion plugin to prevent the WordPress version number from being viewed. When I updated his site from 2.3.2 to 2.3.3, I encountered the same issue you are having. WordPress was reporting that it needed an upgrade, although I had just completed it. Deactivating the plugin eliminated the issue. Here is a similar comment I came across on the BlogSecurity website. I realize that it may not apply to your situation, but It’s a strikingly similar symptom.

    “…interestingly enough, it seems that wordpress itself is dependent on the availability of its version number – with the plugin activated, it reports (just below the menubar): A new version of WordPress is available! Please update now, although i have updated already…”

    Just more food for thought.

    You also may need to simply clear your browser’s cache.

    Hi everyone,
    Thanks for all the responses. Below is what I did.

    I thought I would take your suggestion first, since it does not require me to really think. 🙂 But, that did not work. And thanks for the suggestion.

    Nope, not using a plugin, but I’ll remember that suggestion if I want to ever use bs-wp-noversion plugin. Thanks much.

    Yepper, that was it. The wp-includes/version.php file on my server said 2.3.2 and the (supposed) same file on my desktop said 2.3.3. So, I just overwrite the file and it works perfectly now.

    However, how did that 2.3.2 file even get on my server ? I completely deleted the 2.3.2 WP off of my computer, server and database. And I started with a completely new mysql database for this new install of 2.3.3. Could it have picked up a shadow file off of my hard drive?

    I know you said I should start all over and re-up, but to be honest, I would rather visit my dentist than FTP this honker again. Do you have any other suggestions?

    Thanks to everyone who helped me and made suggestions. This is such a wonderful community.


    I thought you merely overwrote existing files which could explain where an errant old file came from but if you actually deleted everything then reupped (which is the proper way, I delete everything except for the config and htaccess files and wp-content folder) then I don’t know where that file came from.

    You should be aware though that an exploit was identified in 2.3.2 which was supposedly fixed in 2.3.3 The upgrade from 2.3.2 to 2.3.3 involved only a few changed files – at the very least make sure you have the current versions of those files. You can read more info in this thread where whooami packaged the changed files and offers them for download.

    Hi LenK,

    Okay, I’ll visit that thread where whooami packaged the changed files. And I’ll make sure the files are current with 2.3.3.

    I’ll mark this thread as resolved.

    Thanks so much for your help!!


    Where is the resolved tag for this?


Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘WP dashboard tells me to upgrade to 2.3.3. Why?’ is closed to new replies.