• Hello,
    due to Thrive Comments incompatibility with LSCache I had to disable caching of my blog pages by filtering “/blog/” in LSCache settings. However, this also uncaches main blog archive which isn’t necessary (comments don’t load there). I was wondering if it’s possible to uncache only subpages after “/blog/” with regex or “*”?

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Hai Zheng?

    (@hailite)

    It isn’t supported yet. Noted.

    Plugin Support Hai Zheng?

    (@hailite)

    BTW, the best way I think is not to exclude the page but to fix the compatibility on utility app level.

    Thread Starter szmigieldesign

    (@szmigieldesign)

    I’m aware of that and that would be an ideal solution as there’s a tremendous difference in loading times between cached and uncached pages (0.3s vs 1.5s). However, it’s a commercial product and making it compatible with LSCache is a matter of Thrive Comments developers willing to invest their resources in extra work. Modifying it by myself is not an option as it will make the product incompatible with future releases.

    On 15th of January I got a reply from their support:
    “A feature request with this issues has been logged and will be available in one of our next releases

    We will have to see how to prioritize the problem, usually the incompabilities with another plugin are treated based on how the widspread usage of the other plugin.”

    You can follow the issue on their comment system here:
    https://thrivethemes.com/forums/topic/comments-wont-load-after-certain-time-giving-403-on-wp-json/

    It requires an account though.

    Plugin Support Hai Zheng?

    (@hailite)

    Ideally each page should be stored, full page cache or ESI. Basically ESI can fix all these kind of compatibility. You are right, lets see.

    Thread Starter szmigieldesign

    (@szmigieldesign)

    Yes, on a separate thread you’ve noticed it shouldn’t be handled with nonces but with proper implementation of ESI instead. I’ve read LSCache documentation and it doesn’t look hard to implement ESI in this case. We’ll see.

    Thread Starter szmigieldesign

    (@szmigieldesign)

    I was thinking about this issue also in regard to APM (if AMPs are also cached with LSCache). The best way to approach my issue regarding Thrive Comments at present would be to only uncache posts. Main blogroll, tags, categories archives and amp pages don’t use Thrive Comments so they can be cached normally.

    So the plugin would have to uncache only pages that follow /blog/ but only on the first path level after (so that /blog/post/amp/ are cached ok). Would that be even possible without being too hard to implement?

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘How to disable caching for every subpage of a certain page’ is closed to new replies.