eMember – erratic behavior after login, protected content not displaying

[billj_5150]

I have leveraged WP eMember to create a partner portal on my website. When a user navigates to a protected page within this portal section, they will see the “Please login to view this content” message. I do not have login redirection enabled, so after logging in via the inline login widget, the protected page content does display properly. However, that login status is not persisting across the other protected pages featured in this section.

After successfully logging into a page, if I then immediately navigate to any other protected pages in the portal, the “Please login to view this content” message is displayed again. If I then click on the “Login” link, the inline login widget appears, with the message “You have been logged out because another user has logged into this account from another browser.” I have noticed that if I then stay on this page and wait a minute or two, then attempt to navigate to another page (without logging in again), the protected pages seem to be displaying properly. This behavior is occurring across different browsers and devices.

I feel like this may be tied to some sort of caching issue, however, I am not using any type of caching plug-in. I am using GoDaddy Managed WordPress Hosting.

I can provide user login credentials for you to do a test login on my staging site:

hpk.49c.myftpupload.com/partner-portal-home/

[admin]

Go to the settings menu and turn off (uncheck) the following checkbox:

Disable Simultaneous Member Login

Then test the login again.

Do you have any caching on this site?

[billj_5150]

The “Disable Simultaneous Member Login” box is already turned off/unchecked.

Per my original post, I am not using any type of caching plug-in. However, it is possible that GoDaddy may have some form of server-side caching in place.

[admin]

Can you please ask the hosting provider about caching? The issue you explained seems to be caching related. A cached page is being served which is why you are seeing a page different than what you are expecting to see as a logged-in member. When a cached page is served, it doesn’t check the user’s status since it is just sending the cached version of the page to the browser.

[Author]

Posts