Issue with Lite speedcache plugin

  • Resolved djwilko12

    (@djwilko12)


    4 months, 1 week ago

    Hi

    We’ve encountered an issue where any changes made to the sliders are not reflected on the front end unless we manually purge the cache. We use Litespeed cache plugin. We contacted their support and they replied the following:

    • please check with smart slider support, if their plugin has any hook we can useor kindly ask them to add this code to their save actionif ( defined('LSCWP_V')) {
      do_action( 'litespeed_purge_post', $post_id );
      }      I assume it is saved like custom post type ,if it’s other type , can also try with the URL purge , e.g.do_action( 'litespeed_purge_url', '/slider-page/' );

    Could you please check the above suggestions? How can we do to make both plugins work together correctly?

    Thanks

Viewing 1 replies (of 1 total)
  • Plugin Support Laszlo

    (@laszloszalvak)

    Hi @djwilko12

    Actually what is happening is the expected behavior when you use a cache plugin. Since the cache plugin stores the cached HTML of your post. When you publish a slider to the post and you save the post, then by doing that, you did a modification in that post which triggers the “save_post” action:

    that most cache plugins respect hence the cache for the post will be cleared.

    But when you modify the slider, then you won’t modify the actual post, thus the post should still display the earlier cached results, unless you clear the cache manually.

    On our end it is not possible to tell where you will display the sliders. But the good news is that, you can let us know by adding the ID of the corresponding post into the “Post IDs (One Per Line)” field on the Developer tab of each slider:

    by doing this, we will trigger the “edit_post” and “save_post” actions on the posts with the IDs you entered, so if LiteSpeed Cache respects those actions, then those posts would start displaying the new results of your sliders each time you make modifications, without having to clear the cache manually!

    Best regards,

    Laszlo.

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.