• Resolved alanwpeasy

    (@alanwpeasy)


    Hello,
    I love the features and performance of LSCache for my WordPress sites.

    The one huge frustration is how often I look at sites using CSS optimisations, and they look broken. Simply logging and doing a “purge all” resolves the issues.

    I have tried this with several basic sites and different themes. Currently, most of our sites use Elementor and Hello Elementor.

    Super frustrating. In the meantime is there a nightly CRON I can run to purge all cache?

    Thanks,
    Alan.

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

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support qtwrk

    (@qtwrk)

    Hi,

    could you please do me a screenshot for how it looks broken ?

    and also please provide the report number , you can get it in toolbox -> report -> click “send to LiteSpeed”

    Best regards,

    Thread Starter alanwpeasy

    (@alanwpeasy)

    Thanks,
    It is no longer broken as I purged the cache. I will have to wait until it happens again.

    So if I understand correctly, you want the report number while it is broken, not after the cache is purged, and it gets fixed?.

    What happens is the layout breaks and some page elements disappear. This happens randomly on any site that I enable CSS minify and CSS Combine. The reason I picked https://www.wpget.net to ask about is that it has very few plugins and uses the basic “Hello Elementor” theme. The only plugins that would have any effect on CSS is Elementor Pro and Happy Add-ons Pro.

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    yes, please provide the report number

    and also , when that happens , please check the developer tool (you can open it by press F12 on your browser) -> network -> request list , see if CSS file request ended up in error or not

    Best regards,

    I must say I love this plugin as well, but this happens to my clients websites all the time. Usually after an update. The last update, I just went to all of my clients websites that were using it and I’d say 4 out of 5 had to be purged to fix this issue.

    The site looks like all text, no background images, sometimes no images at all. It just needs to be “purged all”. But it’s very frustrating when a client calls me that their website isn’t looking right. I have uptime software checking it, but it doesn’t always work as some only check for text.
    Is there a way to purge nightly?
    Thank you
    Will

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    you can create a php file like this

    <?php
    define( 'WP_USE_THEMES', false );
    require( './wp-load.php' );
    
    do_action( 'litespeed_purge_all' );
    

    save it somewhere in the site , then set up a cron job to access like curl -I -XGET https://domain.com/script.php to trigger the purge all

    and please create a separated topic for your issue , meanwhile please check and make sure you have serve stale set to OFF

    Best regards,

    Thread Starter alanwpeasy

    (@alanwpeasy)

    Thanks for that script.

    Strangely, I have not seen this issue occur since asking this question.

    I currently have about 40 sites with LSCache. Months ago I disabled the CSS minify and combine on all, because it was just too unreliable.

    Around 2 months ago I re-enabled on 5 of my own sites to test. I was seeing this issue intermittently occurring across all 5, which is why I asked the question.

    When the issue does occur, I don’t see any 404 errors. The combined JS and CSS files load just fine, they are just broken until I purge.

    I have just checked my sites and “Serve Stale” is off, I never change this, so it must be the default.

    I will keep it enabled on my own sites for now and report back if it does break again.

    If it does occur,
    – I will get the LSCache report number for you.
    – I’ll download a copy of the CSS while it is broken
    – I’ll download a copy of the CSS after the purge.

    Thanks,
    Alan.

    Thank you!

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘LSCache breaks CSS often’ is closed to new replies.