Conversation
supportSo it doesn’t affect everyone, but I think its affecting my UK shoppers because they are unable to add things to the cart. I tested deactivating each plugin with one of them and we narrowed it down to WP Supercache. However, my site is extremely slow and laggy without it and crashes because so many folks visit it, so I need this plugin. What can I do to fix this issue? I also want to add I also have cloudflare set up, not the plugin but the website. My supercache settings are on expert mode but I also switched to simple/basic caching and still the same issue. This topic was modified 8 months, 1 week ago by fyrakins . The page I need help with: [ log in to see the link]
Hi @fyrakins , Just to narrow things down, have you already excluded your cart, checkout, and account pages from WP Super Cache settings? Under Rejected URLs in Settings → WP Super Cache → Advanced , add your cart/checkout/account pages (for example: /cart/, /checkout/, /my-account/). Also, under Misc settings in Settings → WP Super Cache → Advanced, select “Disable caching for visitors who have a cookie set in their browser.” Those usually need to be bypassed to avoid unexpected behaviour with your dynamic pages. Also, be sure to clear the cache after each change so the new rules take effect. Let us know!
Hello I have all of that added but it still does not work.
Thanks for the update @fyrakins , From the curl response, your site looks to be running LiteSpeed in some form. Since LiteSpeed includes its own caching, which can overlap with WP Super Cache and/or Cloudflare, it’s best to avoid running multiple cache layers at the same time. Also, to make sure we’re on the same page, could you confirm how you ran the plugin conflict test earlier? Ideally, the conflict test looks like the following: Pause Cloudflare so it isn’t caching. If LiteSpeed caching is enabled at the plugin or host/server level, please pause that too. In WordPress, leave only WooCommerce and WP Super Cache active. Test add-to-cart on a single product. If testing this live is risky, you can do the same on a staging site. We have more on that here: https://jetpack.com/support/troubleshooting-plugin-and-theme-conflicts/ . As an extra check, after pausing Cloudflare and LiteSpeed, try loading a product page and viewing the page source at the very bottom. WP Super Cache usually adds a footer comment like this if it’s handling the cache for that specific content. <!-- Cached page generated by WP-Super-Cache ... --> That helps confirm whether WP Super Cache is really serving the cache or if something else (like LiteSpeed/Cloudflare) is stepping in. Look forward to your updates.
I tested it by deactivating all plugins and activating one by one while my customers tested it until we found the conflict. I just did rewrite mod rewrite rules and that seemed to have fixed the issue. I don’t have Lightspeed, the only caching plugin I have is wp supercache. This reply was modified 8 months, 1 week ago by fyrakins . This reply was modified 8 months, 1 week ago by fyrakins .
Hi @fyrakins , Just to narrow things down, have you already excluded your cart, checkout, and account pages from WP Super Cache settings? Under Rejected URLs in Settings → WP Super Cache → Advanced , add your cart/checkout/account pages (for example: /cart/, /checkout/, /my-account/). Also, under Misc settings in Settings → WP Super Cache → Advanced, select “Disable caching for visitors who have a cookie set in their browser.” Those usually need to be bypassed to avoid unexpected behaviour with your dynamic pages. Also, be sure to clear the cache after each change so the new rules take effect. Let us know!
Hello I have all of that added but it still does not work.
Thanks for the update @fyrakins , From the curl response, your site looks to be running LiteSpeed in some form. Since LiteSpeed includes its own caching, which can overlap with WP Super Cache and/or Cloudflare, it’s best to avoid running multiple cache layers at the same time. Also, to make sure we’re on the same page, could you confirm how you ran the plugin conflict test earlier? Ideally, the conflict test looks like the following: Pause Cloudflare so it isn’t caching. If LiteSpeed caching is enabled at the plugin or host/server level, please pause that too. In WordPress, leave only WooCommerce and WP Super Cache active. Test add-to-cart on a single product. If testing this live is risky, you can do the same on a staging site. We have more on that here: https://jetpack.com/support/troubleshooting-plugin-and-theme-conflicts/ . As an extra check, after pausing Cloudflare and LiteSpeed, try loading a product page and viewing the page source at the very bottom. WP Super Cache usually adds a footer comment like this if it’s handling the cache for that specific content. <!-- Cached page generated by WP-Super-Cache ... --> That helps confirm whether WP Super Cache is really serving the cache or if something else (like LiteSpeed/Cloudflare) is stepping in. Look forward to your updates.
I tested it by deactivating all plugins and activating one by one while my customers tested it until we found the conflict. I just did rewrite mod rewrite rules and that seemed to have fixed the issue. I don’t have Lightspeed, the only caching plugin I have is wp supercache. This reply was modified 8 months, 1 week ago by fyrakins . This reply was modified 8 months, 1 week ago by fyrakins .