allyouranime

Thanks for the help, Pacicio, but after speaking to my service provider it doesn’t seem this will be a fix for me. Pair doesn’t use Apache, and I’ve been told there’s no .htaccess file to speak of/won’t have an impact on the Nginx servers.

Guess it’s back to the drawing board for me.

Yeah and like I said, I don’t really know how to do that.

Hey Pacicio, complete newbie here:

So our website’s servers and such are run by pair. How would I go about making these changes myself or do I need to direct Pair’s tech support to this potential solution?

Thanks,
-Tom

I’ve accessed the site through both Chrome and Safari (don’t use/have Firefox) and either browser suffered the same issue.

Right now I’ve only got Child Theme Editor, Wordfence, and Yoast turned on, as they’re listed as 4.6 Compatible.

What’s turned off currently, but not deleted are: Disqus Conditional Load, Google AdSense, Insert Headers and Footers, Patreon Button, Post Views Counter, Varnish HTTP Purge, and W3 Total Cache (although this has always remained off since a caching bug when we first launched the website back in March)

Everything listed there has yet to be marked as compatible with 4.6, so I thought maybe it was one of them, but after having been off for several hours there’s no change.

Thanks for the help btw,
-Tom

Update:

I’ve attempted to pinpoint/better describe exactly what the issue is. I think it’s a caching issue on the backend.

I can revise posts (by myself, I haven’t tried letting my wife log in and us swap between posts yet) and it’ll tick the Revision number up. However, if I enter the post again a second time it won’t recognize the new revision right away (Let’s say I save and it marks it as Revision 14, when I enter back in it’ll still be 13) until I refresh the page.

This goes for Plug ins too. I can deactivate plug ins, but it won’t immediately tick them as off, not until I refresh the page.

After backing up my site again, I’ve deactivated all the plug ins, deleted every plug in we hadn’t been using anyway, and when that didn’t fix it I turned on plug ins that are listed as 4.6 compatible for sure.

This makes me think it’s a weird kind of backend caching issue (<– total newb here) that’s causing the backend to not properly refresh and immediately display the most recent changes.

Again, any help would be appreciated as we’re losing a lot of work time having to deal with this. =/