WP4.6 Backend Caching/Refresh issues.

I tried posting a few days ago but had trouble describing the problem exactly. Spending a few days with the issues I hope I can explain the problem better.

I can make new drafts and type in them just fine. After saving if I back out of the post by going to the post menu the new draft doesn’t appear on the main list, not unless I hit the refresh button.

Once refreshed the post shows up normal. But upon entering the new draft the latest revision does not appear unless, again, I hit the browser’s refresh button. I don’t know a lot about programming, or how WordPress works internally, but it seems like a caching issue?

This also makes it difficult for me and my wife to work together (signed in on different accounts) as it never properly refreshes when we exit posts and complains when she tries to revise my work, or vice versa, that I’m still working on the post and prompts her to wrestle control away. Even if she says click yes the prompt still doesn’t go away. This all makes it exceedingly difficult to work together on our posts.

The same thing happens with the plugin page. When I turn a plugin off or on it does not immediately show them as off, I have to refresh the browser to show the changes. And really, refresh any page to get the active icons for things like, say, Wordfence, to properly disappear. It’s like the whole thing is showing me an old cached version of the pages until I refresh. I’m confident it’s not a browser issue, as I have accessed the site from three different computers across Chrome and Safari.

I have disabled all plugins and that did not solve the issue. I cleared my browser’s cache and that didn’t fix anything. At this point the website is running on the 2016 theme (I turned off the Dynamic News child theme we’d been using since that was last updated before 4.6) and only has plugins active that are listed explicitly as 4.6 compatible.

Some help would be greatly appreciated. My service provider is stumped and, frustratingly, keeps passing the buck back to WordPress convinced it’s some kind of known bug.