Header version / render problems across browsers

[giffc]

How does Pro render and cache itself?

I’m seeing very odd behavior as I work on my header in Pro. For context, I had built my site in X-Integrity, and then switched it to Pro. However, that migration seemed to break the header nav (it was working differently on the home page versus other pages).

But I’m also seeing really odd behavior as I make changes with different browsers while editing the header in Pro. I’ve made a global header. But the changes I’m making, which show up on my Chrome logged-in browser, and also seem to be showing up in Firefox, are not showing up in my incognito Chrome browser.

Earlier as I was fighting with this, I thought it might be a browser cache issue but I’ve cleared the cache (and event totally reset Chrome) and I’m still seeing “old” design+behavior in Incognito. It’s more than just css – I’ve seen different content as well. I was also seeing inconsistent behavior in other browsers between the home page and other pages, with the home page showing the Integrity nav while other pages had flipped to the Pro nav (but I had made the header a global header).

So what is going on in how changes get rendered, and how can I force browsers during my testing to render the most recent, accurate versions?

p.s. your training video on Pro headers shows “Integrity” as a preset, but it’s not a preset in the customer facing version.

[friech]

Hi There,

Thank you for writing in, but I can not identify the issue, I’ve checked all the pages on your site in both Chrome and Firefox (see screenshots below) and the header looks the same.

Please clarify how we can see the issue.

Cheers!

[giffc]

I should have taken screenshots. I was hoping others had reported this problem, or that you could explain how the system renders. I’ve never seen this kind of behavior before in creating websites, but I can promise you that I would make a change (working in Chrome), make sure the Pro builder had saved, and then try to look at the result in an incognito browser, but the incognito browser would not reflect the changes on all pages. I might see it on one of my pages, but not on all.

I saw this same behavior testing on firefox and safari. Clearing caches did not help. Nor did restarting MBP or the browser. I even saw this on my iphone browser. And it wasn’t just CSS – if I changed the main nav menu for example, the new element might show up on certain pages and certain browsers but not on others. Same if I took an element away.

This is going to sound really strange, but it is almost like there is a time delay that was inconsistent across browsers.

Has no one else faced this issue before? Is there something I should know in how Pro renders changes?

[rad]

Hi @giffc,

Please note that there is a server cache and a browser cache, what you’re just clearing is your browser cache. You have to clear both. And the reason why the changes appear when the user is logged in is due to server cache (caches generated by plugin, host, or CDN like Cloudflare) and not the browser cache. And I see that most often when there is an active server cache (some plugin have user logged in caching option like W3 Total Cache). Using incognito has no effect on server side cache, it will still serve the same cache.

And have multiple caches, minification, CDN will make it more complex. Though, if it’s not the case, I would love to see a video recording of this issue, maybe it’s something we need to fix.

Thanks!

[giffc]

Thanks Rad. I do not yet have a caching plugin working, and i did hit the purge cache link within the theme. But I’m about to build another site with Pro, and I’ll make sure to capture it this time if it happens again.

[ruenel]

No problem. As always you are most welcome.
If you need anything else we can help you with, don’t hesitate to open another thread.