After update using svn and trying to just download full app and over write files I still get a message in admin that says a update is avaliable. wp-includes/verson.php shos 2.3.3 and a svn sw to 2.3.3 says i'm at the correct revision. Any sugguestions?
[resolved] 2.3.3 upgrade still says update avaliable in admin (15 posts)
-
sparkyewu
Posted 4 years ago # -
Jeremy Clark
Posted 4 years ago #Have you tried clearing your browser cache?
-
Posted 4 years ago #Yep, and different browsers.
-
Then you didn't upgrade properly. Make sure all the files were uploaded to your site.
-
Posted 4 years ago #Ok, I just did a full download of latest.tar.gz, renamed my blog folder to wordpress and did a tar -xvzf latest.tar.gz, then watched it go into wordpress. Renamed my blog directory back to what it was and guess what, still says 2.3.2. How is that not upgrading properly?
-
Posted 4 years ago #Well view the source of your blog and look for the meta tag called generator and see what it says the version is there.
-
Posted 4 years ago #Is there any other file that dictates version?
-
Posted 4 years ago #2.3.2
But here is a direct copy of wp-includes/version.php, oh and I have disabled all plugins to test as well.
<?php
// This holds the version number in a separate file so we can bump it without cluttering the SVN
$wp_version = '2.3.3';
$wp_db_version = 6124;?>
-
Is there any other file that dictates version?
No, just version.php. All the other files get their version numbers from there.
So, perhaps your site isn't actually where you think it is? Or maybe you have a cache interfering?
-
Posted 4 years ago #How about give a link to your blog and we can tell if it is a cache issue.
-
Posted 4 years ago # -
Both the feed and the main site still say 2.3.2. I'm thinking that you uploaded the files to the wrong place. I can't think of anything else that makes any sense.
-
Posted 4 years ago #Yea i wish that was the case. I've been running wordpress since 1.1 so I've done a update or two. What is weird is that svn sw ..../2.3.3/ says i'm at the right revision, and all the files check out against 2.3.3 with a diff meaning i'm at 2.3.3 for all intents and purposes. I think i'm going to do a backup of the db, and just try to start fresh. Maybe svn got me in some weird state.
-
Posted 4 years ago #Did any of your files have conflicts when you used svn. I've run into this problem with the version.php file before. Check your wp-includes folder and make sure there aren't and files with odd extensions like .R6723 (just an arbitrary number.)
-
Posted 4 years ago #Yep that was the problem, as soon as I cleaned up any svn conflicts the upgrade was fine. Thanks for you help everyone. :) I'm sure the next upgrade will go great
Topic Closed
This topic has been closed to new replies.
