David Dashifen Kees

Honestly, I have no idea why it’s happening in the first place, so I can’t figure out how to recreate it. For now, let’s consider this one a mystery and if I figure anything out, I’ll come back to update this thread in case it helps y’all identify a change on your end or if someone else finds there way here.

Riza,

Thank you for getting back to me. The post type was public but was not hierarchical. I switched it so that it was hierarchical, but its checkboxes are still disabled. With respect to the screenshots, the second one indicates an entire row of disabled checkboxes for the post type that begins with the letter “A.” In the first screenshot, you can see that we’ve marked every single post type to try and control them via the plugin, but despite this, the “A” post type doesn’t let us do so.

If you have any advice, it would be most appreciated. We have been trying to fix this on and off for about a year now. For a few more details, we are running 2.13.0 of this plugin WordPress 6.5.5.

Thanks,
Dash

Looks like the screenshots didn’t work; here are they’re URLs:

• https://www.dropbox.com/scl/fi/8pnvkfh0mayy5mmkpzayr/Screenshot_1.jpg?rlkey=gwa49q42zn9t588uc517y813p&dl=0
• https://www.dropbox.com/scl/fi/cn0t0p7ogorbekgm74xo1/Screenshot_2.jpg?rlkey=20bcf8b8rzlovscolwv4srts6&dl=0

nevermind, i’m a moron. If you see this before you post the above, feel free to discard it.

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.

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 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.

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.

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

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 checked-in with my hosting company and they’ve confirmed that there is no server-side caching going on.

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.

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.

With a Network of over 1200 sites, it would take us quite some time to try and swap plugins and repair any settings or display issues so we’re hoping to try and find something to help warn site owners about impending changes empowering them to deal with things and saving us time and work. We already use your plugin to hide the deprecated plugins from sites not already using it, but we’d like a way to tell those who are using it that it’s going to go away and to contact us if they have questions. If you’re not interested in the feature, no worries. We can probably add it ourselves with our own plugin since it is likely to be a outlaying case.

This is also happening to me. I’ve tried disabling and re-activating the plugin, removing it and reinstalling it, and deleting and re-creating the site within my Network on which I’d like to use the plugin and the same error continues to happen. I’m running WordPress 3.3.1 with version 1.7 of the plugin.

Thanks,
David