msmithers

My sincere apologies. I wasn’t clearing the Safari cache properly. (There are a few different options.) Now cleared, the tables are showing correctly now on Mojave.

After some more testing, the Safari layout problems appear to be only on the latest macOS 10.14 (Mojave) and the latest iOS (iPhone).

Is it possible to downgrade to 2.6 or has the database been changed in a way that makes the downgrade impossible?

Thank you so much for your reply.

I’m using Pingdom tools to check the website from different locations around the world. So I have no control over browser caching, but from experience, each Pingdom request seems to not involve local caching.

I followed your instructions re WP Super Cache. Interestingly when I specifically delete the homepage from the “List all cached files” list, the 1st web query (from a non-EU country – e.g. Australia) does NOT do a reload, which is great. However any subsequent web queries from a non-EU country does do a reload. I can replicate this reliably be deleting the file from the cache, then doing requests from Australia, USA, etc.

I’m not sure what else to do at the point except just not use WP Super Cache. From your notes under Country Caching for WP Super Cache support, I confirmed that “Cache delivery method” is set to Simple, and “Cache HTTP Headers with page content” is checked.

Happy to move this to email if it helps. Got to https://southerlychange.net/ fill out the contact form and I’ll reply.

Kind regards,
Michael

• This reply was modified 6 years, 4 months ago by msmithers.
• This reply was modified 6 years, 4 months ago by msmithers.

Sorry for a followup question.

After success with the CCA fix above, we enabled WP Super Cache and Country Caching for WP Super Cache, and the reload returned for non-EU countries. We then turned off both plugins, and the single load returned – as per your fix.

Any ideas as to what is happening? Are there particular settings we should apply to Country Caching for WP Super Cache to ensure the double load doesn’t occur? We followed the instructions for Cookie Notice users…

Thanks,
Michael

Wonderful. This works. Thank you VERY much!!!

Hi wrigs1,

Thank you for the URL line cn-reloaded=1 fix in 1.2.3 for non-EU visitors.

We’re still experiencing the page reload, for non-EU visitors, and I’m confused why this is the case. I would have thought that the web server could see the non-EU visitor from the initial web page query and as such the first page delivered to the visitors browser would include everything – and thus NOT need a page reload (for CN to install the Google analytics and Facebook pixel information).

Am I missing something here? Is it just the way CN works? The page reload is causing an unnecessary ~50% increase in page load time for our non-EU visitors (who are close to 100% of our customers).

Kind regards,
Michael