• Resolved allstarsft

    (@allstarsft)


    Hi Guys,

    Using Super Page Cache for Cloudflare and Elementor (Webpage editing) + Litespeed Cache (LSCache)

    Today the CSS not loading issue has happened again though I’m 100% sure there were no changes today.

    Screenshot is from my colleague in office/retail shop and reported by customer too : https://snipboard.io/Slu0Xo.jpg — and from my end, it was working when I tested it on Mobile browser outside. So as usual I have to use Clear Cache for Me plugin to clear Elementor cache then its back to normal.

    I have asked earlier via the contact@themeisle.com email and Stefan has replied me on how to set Auto clearing of cache, and I have done that but it still happened today. — screenshot of the said setting : https://snipboard.io/71irqF.jpg — Do I keep it to related pages only or should Purge whole cache be enabled too?

    Elementor side – CSS loading is External (previously was internal embedded) — was told in Global Elementor FB group earlier that I should set it to External but this still happened.

    — I just checked — the CSS loading became internal embedding again… have just switched back to External as per screenshot : https://snipboard.io/uO3jwh.jpg

    LScache – screenshot — have disabled cache since am using Super Page Cache for — Disk Page cache : https://snipboard.io/S2YHWR.jpg

    Are there any other settings I should be aware of so that Super Page Cache will work properly with Elementor and WordPress (with LScache as well)?

    Thank you.

    Regards

    Faustine

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Robert Soare

    (@soarerobertdaniel7)

    Hello,

    One thing you can try is to set Cache-Control max-age (on Advanced > Cache Lifetime Settings) to value lower than or equal to 12 hours (like 43200). For e-commerce sites, the default value of 1 year might be too much since the website has a lot of dynamic content along with CSS snippets via WPCode.

    The Disk Cache save a copy of the HTML page on the disk, thus any change might not be immediately reflected. With a lower cache age, the cache will refresh more often.

    Do I keep it to related pages only or should Purge whole cache be enabled too?

    You should keep them both.

    Thread Starter allstarsft

    (@allstarsft)

    @soarerobertdaniel7 Thanks for your reply. The Cache-Control Max-age is at 31536000 — which is 1 year. — Gonna change that to 43200 — for 12 hours… .

    Cache Lifespan (seconds) — 172800 — does that matter too?

    Cloudflare Cache Behavior — Will enable Purge Whole cache as well.

    Edit : After changing the above settings other than the Cache Lifespan — the issue still happening : https://snipboard.io/LjfzDr.jpg — but did some changes to the Elementor Elements etc earlier. However it just peeves me that the Auto cache clearing is not happening.

    Thank you.

    Regards

    Faustine

    • This reply was modified 3 months, 2 weeks ago by allstarsft.
    • This reply was modified 3 months, 2 weeks ago by allstarsft.
    Robert Soare

    (@soarerobertdaniel7)

    In the Browser Console, what errors do you see? And if it is possible to send a screenshot and link for a manual check.

    Also, the plugin might be not aware of all Elementor cases of save. Our automatic purge cache is linked to WordPress native hooks for saving posts and pages. Anything else might need a manual purge.

    Also, if you can, you can also post the settings via Export Settings (sensitive data will not included) – it will be a .json file to which you can copy the content and paste it here.

    Cache Lifespan (seconds) you can can also set it under 12 hours. This one determine how much it can keep the saved HTML file on the disk (it does not affect Cloudflare).

    Thread Starter allstarsft

    (@allstarsft)

    @soarerobertdaniel7 Sorry for getting back this late.

    Was in the midst of solving issues of migration to new server then realised Cloudflare has integration issue — after clicking Test Purge

    Resolved that by removing all Manually created rules and retain Super Page Cache’s own Cache rules in Cloudflare.com

    I noticed an issue when trying Preloading at Live site. It caused the same issue as per this thread and I have to disable that to get the site back to normal CSS styling loading as well. I thought Preloading is supposed to help with loading speed etc but its causing problems.

    I’m now going to push to live from my staged site dev-s3.allstars.com.sg (since I have been troubleshooting some backend loading issue there) and will keep monitoring if this problem (mentioned in this thread) — still happens….

    Last week, my boss and colleagues told me they were unable to load the website front end as well…. but webhost is not able to pin point any issue. Not sure if its related to Cloudflare cache as well? (in relation to the usage of Super Page Cache?)

    What is the best settings for a dynamic website such as Woocommerce?

Viewing 4 replies - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.