Conflict With Litespeed Cache Plugin (Loader Loop)

  • Resolved ???? ????

    (@vandanojan)


    3 years, 3 months ago

    Hi,
    I am having an issue with LoftLoader that has been recently reported by some others.
    The problem is that the loader gets stuck in an infinite loop, unless the user starts to interact or the whole content has been fully loaded (though I have set the max time at 5 seconds). This problem has been appearing on a website which is using a combination of Litespeed Cache and WP Meteor plugins, so that the former just minifies JS files while the latter delays scripts. I excluded LoftLoader JS files path in both plugins (/wp-content/plugins/loftloader/assets/js/(.*).js) and cleared the cache, but this failed to solve the issue.
    so would you mind helping me find a solution? Thanks in advance.

    • This topic was modified 3 years, 3 months ago by ???? ????.
    • This topic was modified 3 years, 3 months ago by ???? ????.
Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author loftocean

    (@loftocean)

    Hi @vandanojan ,

    Thank you for contacting us.

    Could you please share your website URL, so that I can check it for you?

    Thank you very much.

    Best regards,
    The Loft.Ocean Team

    Thread Starter ???? ????

    (@vandanojan)

    Thank you @loftocean for your response. I’d already mentioned the website url above, but again you can check it out from HERE. It’s better to simulate a slow internet connection for testing.

    Plugin Author loftocean

    (@loftocean)

    Hi @vandanojan ,

    Thank you for your reply.

    I checked your website and tested the plugins mentioned on our testing site. Please put the keyword “loftloader” to the exclusion text field and enable the option “Exclude scripts matching regexp from optimization”, then the loader will work properly. Please see the screenshot for details: https://d.pr/i/F9qLOd

    Thank you very much.

    Best regards,
    The Loft.Ocean Team

    Thread Starter ???? ????

    (@vandanojan)

    Thanks @loftocean
    I excluded LoftLoader from WP Meteor, but the problem now is that its loading gets over soon when the rest scripts have not yet been executed and the slider is being lazy loaded. So there is kind of Flash of Unstyled Content (FOUC) that by LoftLoader I was to hide, but now I fail to do. To get my point, please check the url again.

    • This reply was modified 3 years, 3 months ago by ???? ????.
    • This reply was modified 3 years, 3 months ago by ???? ????.
    Plugin Author loftocean

    (@loftocean)

    Hi @vandanojan ,

    Thank you for your reply.

    Because you have optimized the loading process of the assets on your website, the CSS related code has been deferred and loaded by JavaScript. But for browser, the loading process is completed ( although the JavaScript is trying to load CSS, images … ), so the loader stops displaying.

    The pro version has a feature “Minimum Load Time”, by using this feature you can set a minimal time to show the loader during the page loading process. You may like to check the online documentation for details.

    However, I think the best solution for your website is to find out the cause of FOUC and then fix it.

    Thank you very much.

    Best regards,
    The Loft.Ocean Team

    Thread Starter ???? ????

    (@vandanojan)

    Thank you for your time. I’ll try to do so.
    All the best

    Thread Starter ???? ????

    (@vandanojan)

    The slider was using a jQuery plugin named Owl Carousel. I just amended owl.carousel.jscode and changed the value of lazyload to false.
    So seems that the FOUC problem has been resolved for the time being.
    @loftocean

    • This reply was modified 3 years, 3 months ago by ???? ????.
    • This reply was modified 3 years, 3 months ago by ???? ????.
    Plugin Author loftocean

    (@loftocean)

    Hi @vandanojan ,

    Glad to hear that.

    Best regards,
    The Loft.Ocean Team

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Conflict With Litespeed Cache Plugin (Loader Loop)’ is closed to new replies.