- This topic has 3 replies, 2 voices, and was last updated 2 years, 12 months ago by
.
-
Posts
-
The Simple Membership PLugin works really well on my site when it’s working, but frequently goes wrong (details below). I am wondering if this is caused by caching on the server, as I have seen other threads on this forum which suggest that’s sometimes an issue. My hosting company uses a caching system called Varnish. Is there a compitibility issue? Last time the plugin went wrong, I tried clearing the Varnish cache, and it fixed the problem, at least for now.
Here are details of the problems that occur when it goes wrong:
On my PC I log in as SteveE and get access to protected pages.
I use the widget to log out and it shows that I am logged out (the widget reverts to ‘Login here’) but I can still access protected pages.On my phone, I use the widget link to ‘Login here’ but the login page shows that I’m already logged in as SteveE.
I click the Logout link, it redirects me to the correct page, but I remain logged in.Other users on other devices – if they log out of their user account, the widget shows that they are logged in as SteveE, they can access my profile, and they cannot log out of this.
The login state is maintained with cookies. So, as a minimum, your browser must accept cookies. Additionally, there are only 4 caching systems SWPM supports:
- W3 Total Cache
https://support.tipsandtricks-hq.com/forums/topic/emember-mailpoet-newsletter-addon-problem#post-84913
- WP Super Cache
https://simple-membership-plugin.com/wp-super-cache-compatibility-simple-membership/
- WP Rocket Cache
https://simple-membership-plugin.com/wp-rocket-cache-compatibility-for-simple-membership/
- WP Fastest Cache
https://simple-membership-plugin.com/wp-fastest-cache-compatibility-for-simple-membership/
If you are using a non supported caching system; please study the compatibility requirements for the supported caching plugins, and try adjusting your settings accordingly.
Thanks for this. Is it likely that the problems I have described are caused by the caching system on the server as I suspect? Or are there other likely causes?
- W3 Total Cache
- You must be logged in to reply to this topic.