Exclude checkout page and plugin entirely from being cached

  • Resolved joshgreg

    (@joshgreg)


    3 years, 8 months ago

    I recently installed and configured Litespeed Cache, after which I noticed an issue with my checkout page and another plugin (Paystack WooCommerce Payment Gateway) on my website.

    When a returning customer enters login information on the checkout page and clicks the login button, the product and payment information keeps loading (see screenshot – https://snipboard.io/Ijs7Ki.jpg). Not until the page is manually refreshed would the customer be able to checkout. And when the customer eventually clicks the checkout button (after accepting terms and conditions), the payment option (powered by Paystack WooCommerce Payment Gateway plugin) doesn’t pop up as before and as expected.

    I have excluded the checkout page from being cached (see screenshot – https://snipboard.io/TWlzX1.jpg) through the tuning option in Page optimisation but this doesn’t help. I also wanted to exclude
    Paystack WooCommerce Payment Gateway plugin entirely from being cached but I’m unable to find any option that could enable me to achieve this.

    Please assist.

    PS: I disabled all plugins and found that the Litespeed cache was causing the issue.

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

    (@qtwrk)

    Hi,

    by default checkout and cart page are NOT cached , you can verify it by HTTP response header , you should see x-litespeed-cache-control: no-cache on these pages

    have you tried with default setting ?

    do you see any warning or error message shows up on dev tool ?

    Best regards,

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    I’m going to mark this topic “Resolved”, due to lack of activity.

    If you still need help, please feel free to re-open it.

    When re-open it, please also change the topic status to “not solved”

    Best regards,

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Exclude checkout page and plugin entirely from being cached’ is closed to new replies.