Support » Plugin: LiteSpeed Cache » visual composer post grid and galleries not loading after a time period

  • Resolved KentAjans

    (@kentajans)


    Hi all,

    I have really liked that Litespeed cache but nowadays I found that some pages with photo galleries or post grid via visual composer, not loading, when you purge the cache they loading/show correctly again.

    I read about wp nonce properties for visual composer but could not find out how can I solve that problem.

    I had set Default Public Cache TTL to 86400 (which hope 1 day long) but nothing changed. Any suggestions?

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

Viewing 14 replies - 1 through 14 (of 14 total)
  • Plugin Support Hai Zheng⚡

    (@hailite)

    If there is nonce in frontend page, it will get cached too. Wile this may not be the ideal way. Can you tell the name of that plugin?

    Thread Starter KentAjans

    (@kentajans)

    plugin name is Visual Composer (very popular)

    They have many built-in elements to show different kind of content (galleries, post query, etc). With litespeed, they are working great but after a day these parts are not visible (to see again I need to purge cache again)

    Bests

    Plugin Support Hai Zheng⚡

    (@hailite)

    Is this happening when you are editing page as a logged in user or just visit the page as a guest user?

    Thread Starter KentAjans

    (@kentajans)

    It’s happening as a guest user. When I logged in its works (cause no cache for admin users)

    Plugin Support Hai Zheng⚡

    (@hailite)

    Yes I noticed that issue. What is your TTL setting? I think its still larger than your nonce lifetime?

    Thread Starter KentAjans

    (@kentajans)

    I had set Default Public Cache TTL to 86400 ( 1 day long) but had nothing changed. Any suggestions or what amount of TTL I have to set?

    Plugin Support Hai Zheng⚡

    (@hailite)

    We didn’t get any copy from Visual Composer yet, so it’s hard for us to do the local test. You may need to ask them what their default nonce lifetime is. If same as default WP’s, I guess 86400 should work.

    Currently, can you try to set it to 3600, and see if it can work well? Test it step by step.

    Thread Starter KentAjans

    (@kentajans)

    I don’t know as well but I can send a copy of my valid plugin for the test purposes?

    I will set it up 3600 now and let you know tomorrow

    Bests

    Plugin Support Hai Zheng⚡

    (@hailite)

    Thanks. You can send the test copy to bug@litespeedtech.com

    Plugin Support Hai Zheng⚡

    (@hailite)

    We created a wiki page about how to improve the compatibility in https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:cache:lscwp:esi_nonce

    Also we noticed their twitter. Hope we can get in touch and make the perfect compatibility in our next week v1.2.4 release. We have improved our API call based on that wiki which will be available in v1.2.4.

    Thread Starter KentAjans

    (@kentajans)

    Great to hear that! Thanks and looking forward the next update…

    Plugin Support Hai Zheng⚡

    (@hailite)

    We tried to contact them, and they got our solution and said they will forward to their developer. That is the only thing we can do. They have to improve their plugin to get cache work. Till now, even we asked again, we didn’t get any further response.

    I guess you may want to contact them as a customer.

    Best regards,
    Hai

    I thought I would jump in and indicate that I too have the same problem. I’ll contact Visual Composer as well. Thanks for all the work you have done so far. Much appreciated.

    Steve

    A new Visual Composer version (3.4) was just released.

    I contacted WPBakery asking if it included the LSCache fix, here’s their reply:

    I am afraid, our recent release does not include the litespeed cache code. The suggested enhancement is still on our list and it will be added while revamping the grids.

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘visual composer post grid and galleries not loading after a time period’ is closed to new replies.