Forum Replies Created
-
Posts
-
I had someone else on our team take a look and this is something that they found which hopefully is helpful:
“I can see the HTML is actually different between the working version and the broken versionThe working version has a lot of utility classes that don’t mean anything to me “mjm-3q mjm-3r mjm-3s mjm-3t” BUT it is those utility classes that get the CSS to where it needs to go. The styles seem to be in there, but they aren’t being engaged because they are cascading from some of those utility classes.
The HTML is present in the raw source, not added with javascript, so this looks like a server issue, and the way it sort of hangs out and then disappears makes it looks like a transient server issue which gets cached first broken then fixed.”
My settings already match what you have shown above.
I’ve attached the console log. This is the only thing in the console log before and after.
The one thing I did find that, at least for me, using Chrome in incognito mode never gets past the broken render view of the page even after refreshing, forcing to clear the cache, or visiting the page in another browser. If I view it first while in incognito mode I can’t get the correct result. Same sort of behavior I’ve seen in Safari. Still though if I view the page first in normal Chrome and refresh the page it looks fine in those browsers.
It does seem like I am unable to totally disable caching on my hosting provider WP Engine. And if I clear the cache on the server side it fixes the issue for just the page that has been viewed. Same can be done by adding a cache buster to the URL like “?foo=bar”
Still though if I deactivate the Ajax Search Pro plugin this issue goes away.
interesting. I’ve attached what is the behavior I’m seeing when I visit a page for the first time. The CSS only partially loads and then if I refresh I get the full CSS. Then any subsequent views to the page will render correctly for myself any anyone else. It seems to be much worse for our users on Safari which seems to hold on to client side cache of page a bit more aggressively.
