Sites at Different WordPress versions

As a test, I just made a new site on the Network (I hadn’t thought to do so before). It was correctly identifying 3.9 as its version.

Are you running any server side caching, like memcached?

Have you gone to yourdomain.com/wp-admin/network/upgrade.php and run that? I know you said you reupgraded, but I want to be sure it was the right thing ??

I don’t think so and yes.

I’ve never set up server side caching myself but I’m on a shared host so I’ll see if they have anything set up once their live chat opens tomorrow morning and report back.

RE: updating, that is indeed what I did.

I checked-in with my hosting company and they’ve confirmed that there is no server-side caching going on.

Shared hosting, no memcached probably ??

Do these mapped domains have www in their URLs?

Nope. I mapped them all without the www subdomain. For reference, I also went into the site settings for each of them and unmapped them and re-ran the network updater and that didn’t do anything either and there were mapped domains on the Network that were updated, and some that weren’t. But, that’s my only clue; all unmapped domains worked fine.

I’m not sure, but have you try to “upgrade” the network as ipstenu mention?

Network Admin >
Updates > Upgrade Network?

Just tried right now. No joy; some sites still read as being at 3.8.1.

Silly idea…. Go into the DB and for the wp_x_options tables for these sites, delete ALL entries for _transient… including _site_transient_update_plugins if that’s there.

Nope. I deleted all transients in the wp_X_options tables and that didn’t change anything. Then, I did upgraded the network and that, also, did nothing. So, I deleted the transients from wp_options and that did nothing. Upgraded the network once more; still nothing.

I suppose you could try manually forcing it by going into wp_blogversions and making them all the same… though I’ve never seen the per-site versions be different, since that’s from a file and not the DB.

I might just backup, remove, and rebuild the offending sites. Some of them are unused at the moment; projects that never came to fruition or ideas had and lost, I suppose. Only one is truly important and that’s the one that’s causing Jetpack incompatibilities because of versioning. I’ll try to backup/remove/rebuild that one first and report results here. As for what went wrong, perhaps it’ll remain a mystery.

Take a look at /wp-includes/version.php on your server.

The $wp_db_version is what should be in wp_blog_versions so if you manually do it, that should kick ’em over, but I’ve honestly never seen that get out of sync. I didn’t think it was possible, since it’s pulled from that file!

version.php says 3.9 (I actually hadn’t known about that file before). Oddly, the other sites do still say 3.8.1 and I’m 100% sure they’re operating on the same set of WordPress code. It says that both in the At-a-Glance box on the Dashboard and in the Dashboard’s footer’s right hand corner.

Just for shiggles, I changed the value in version.php and the offending sites stayed at 3.8.1 while the other sites reported my altered version number.

I’m going to get back in touch with my hosting company because this makes it seem like there’s two versions of WordPress running somewhere but I can’t find a copy of that code so I wonder if my account is messed up somehow and some sites are … pointing (for lack of a better term) … to a different WordPress install to which I don’t or no longer have access.

I think I’ve figured it out, and it was the version.php issues that helped out so thank you very much. It looks like, for some reason, some of the sites are living on Server A (the one I can update) and others are living on Server B. There was a recent migration of my account and, evidently, it didn’t work perfectly. As such, some of the DNS for the sites on the network was never updated and so while the sites on Server A are probably working fine, the DNS still has people going back to Server B when they actually type in the URL.

Thanks for your patience and your help. I’ll be working with my hosting provider from here to sort things out. This is what I get for trying to fix what ain’t broken vis–à–vis hosting options.