Thank you for reaching out to us. We don’t really have any documentation in regards to LiteSpeed Cache plugin. However the following forum post has a solution by one of the users.
https://ww.wp.xz.cn/support/topic/register-form-input-boxes-too-long/#post-15709345
Let me know if this helps you.
Kind regards.
Thread Starter
GregW
(@gwmbox)
@mbrsolution thanks for the reply but that does not cover what I am wanting to verify. I expect there are specific urls I need to tell LiteSpeed to not cache, which may be all pages listed in the simple membership page list (login, register etc)
I have submitted a message to the developers to investigate further your request.
Kind regards.
Hi, the best approach for caching situation is to use the ‘Exclude Caching Based on a Cookie’ condition whenever possible.
Try the following to see if that gives a good result or not. Let me know how this goes for you:
- Go to: LiteSpeed Cache > Cache > Excludes in your WordPress dashboard.
- Scroll down to the “Do Not Cache Cookies” option.
- Enter the cookie name you want to exclude. Use the following cookie name for our plugin:
wp_swpm_in_use
- Save Changes.
Next, exclude the login page and any payment related pages from caching
To maintain the proper functionality of your membership site, it’s important to exclude certain pages from caching. Specifically, make sure to exclude the following pages:
- Login Page: This page is used by the members to log into the site.
- Join Us Page: This page contains the payment buttons and should not be cached to ensure that payment processing and membership sign-up work correctly.
- Thank You Page: This page is displayed after a successful payment and should not be cached to ensure that the correct information is shown to the user after they complete their payment.
- Pages Containing Payment Buttons: If you have placed the payment buttons on other pages, these pages should also be excluded from caching to prevent any issues with the payment process.
Thread Starter
GregW
(@gwmbox)
Thanks, I will give this all a try.
@gwmbox Just wanted to check and see if this worked for you.
Thread Starter
GregW
(@gwmbox)
Hi @wpinsider-1 , sorry I have been away, I am still to fully test this. I will let you know next week how it goes.
Thread Starter
GregW
(@gwmbox)
Thanks. With removing the cookies, does that means they need to login every time they revisit the website?
What about pages that are set to be fully restricted, should I set it to not cache them as well?
What do you mean by ‘removing the cookies’? Are you referring to ‘cookie exclusion’ as outlined in the steps above, or is this something different? Please note that cookie exclusion and cookie deletion are not the same. In the context of caching, cookie exclusion means that if a specific cookie is present, the cache will be bypassed for that user.
I don’t personally use this specific caching plugin, so I can’t say for certain whether it will work. In theory, it should—but it needs to be tested on a live site using the plugin. Some trial and error will likely be necessary to get it working correctly.
Thread Starter
GregW
(@gwmbox)
Sorry I meant “Do Not Cache Cookies”
Could you provide more information, or an example about “cookie exclusion means that if a specific cookie is present, the cache will be bypassed for that user.”
Yes I am still testing, but I know cache plugins and member access restrictions can cause issues where a member only page full content can be cached and displays that page.
Sorry to be a pain, I just need clarification to be sure I have it working as needed.
Sure! When a member logs in using our plugin’s login form, it sets a cookie with the following name:
wp_swpm_in_use
By using cookie exclusion, we’re instructing the caching plugin to skip serving a cached page if this specific cookie is present. The idea is to ensure that logged-in members see dynamic content based on their membership access level, rather than a cached version. Regular visitors who are not logged in won’t have this cookie and will continue to see the cached version of your site.
Thread Starter
GregW
(@gwmbox)
“Regular visitors who are not logged in won’t have this cookie and will continue to see the cached version of your site”
But can’t see member restricted content correct?
What if they disable/reject all cookies?
If they disable or reject all cookies, then this cookie exclusion won’t work for them unfortunately. I’ve also responded to your question in the following post, which includes some additional details:
https://simple-membership-plugin.com/forums/topic/ls-cache-and-sm-how-do-i-cache/
Thread Starter
GregW
(@gwmbox)
Can I just check should the urls be exact match, e.g.
mydomain.com/page/
or
mydomain.com/page
or both just in case?
and no need for http(s)://
@gwmbox, check the following documentation. This explains what URL’s format is permitted by their plugin, service.
https://docs.litespeedtech.com/lscache/lscwp/cache/
Let us know if this helps you.
Kind regards.
