Hi @correiar
That often happens when the cache was outdated for that particular request. So, it often clears up once you visit the plugins or updates page. But if its reappearing, it might be a situation where its again using a stale cache somehow.
Do you know what your hosting setup looks like? Whether you use any sort of caching – persistent object caching in a master/slave setup? Could be that one of the read-only nodes hasn’t sync up. Or maybe just a database server running in a master/slave setup, where slaves are probably out of sync?
When you see the option, does it go away on its own, if you do nothing and just reloads the page a bunch of times? Does it reappear while doing so before disappearing again?
I assume you are referring to server level caching. I am not familiar with how the server side is configured.
I do use W3TC plugin on my site and clear cache regularly. Issue still exists.
I do have a plugin called WP Safe Mode that I sometimes use when troubleshooting conflicts. Just by activating that plugin but not enabling it, causes the plugin updates to appear and remain visible so that I can deal with the plugin updates.
I then deactivate the plugin…
I have both a production site and a development environment (in a sub-domain) and they both exhibit this issue. I did clone the development site from production using Duplicator Pro.
So you are saying when you enable this “WP Safe mode” plugin but doesn’t tell it to do anything (disable any plugin for example), the updates that were being shown, are now actually shown and you can go ahead and update them?
If so, then its not a cache issue as I was describing. Then something prevents them from showing up. A clue would be to figure out how WP Safe Mode works and make out how that can affect this. Perhaps a plugin that prevents communication with external hosts by restricting HTTP requests or something?
That is correct. I sent a note off to the makers of the WP Safe Mode plugin to see if they can shed some light on it. Will update the post with anything I find out.
Sure! Let see if they can indeed provide a clue.
BTW, if you have CLI/SSH access, can you try verifying integrity of core files? https://developer.ww.wp.xz.cn/cli/commands/core/verify-checksums/
Also, I take it you are running the latest WordPress 5.8?