Using other login form with SWPM

Hi,

I want to use an Ajax login shortcode (another plugin) to avoid the information being cached.

Which plugin are you using?

Regards.

I try the Login With Ajax plugin.

I believe the best way to prevent the SWPM login shortcode displays being cached is to implement the shortcodes using AJAX. That will help a lot of users of SWPM and would attract a lot of new clients.

Hi,

I believe the best way to prevent the SWPM login shortcode displays being cached is to implement the shortcodes using AJAX.

If you are worried about your login form getting cached, the following instructions might help you.

W3 Total Cache plugin compatibility
WP Super Cache plugin compatibility
WP Rocket Cache Compatibility
WP Fastest Cache Compatibility

Kind regards.

Hi mbrsolution,
I do use W3 Total Cache and have entered the required text to prevent swpm login form and registration page being cache. My problem is something else.

I placed the swpm-mini-login shortcode in the sidebar.
When a non-logged-in user browses the public pages, the sidebar shows the logged-in link and the Join Us link. That is fine.
Then the same user logs in, the status on the sidebar of the public pages he/she visited earlier still shows not logged in. It appears to me that after a user logged in, the previous cached pages are still served. This is confusing for users who logged in but on the sidebar shows he/she is not.
If the swpm-mini-login and swpm_login_form shortcodes can be implemented with Ajax, then there would be not such problem. I think this is an important feature for any membership plugins. If implemented, it will be a big advantage for SWPM.

Thank you for providing more information. I have submitted a message to the developers to investigate further your request.

Kind regards.

Hi, are you still needing help with your issue?

Regards.

Yes I still need help with this issue. I have not heard from your developers yet. Please follow up with them, thanks.

For our simple plugin, it doesn’t have the architecture to handle what you suggested.

The login has to be handled by the login page of our plugin. Caching needs to be excluded/disabled on that login page for optimum result. I have added a bit of explanation for this below:

The membership functionality needs a dynamic page being shown to the members. A cached page simply shows a static cached page (our plugin doesn’t get a chance to apply the conditions to that page). When a cached page is being shown, the user is not actually being shown a page which can read the login status of the user then show/hide the page’s content accordingly. That’s what causes the issue with membership type setup because membership type site is not the same as a blog type site. Caching is normally fine with a Blog type site where there is no need to show content based on a member’s login status.

Thanks for the reply.