Login and Content Protection issues

[outpost33]

Hi,

Just following up on this, and the issues described in this thread

Dreamhost responded to my Dreampress support request regarding this issue as follows:

The response from the plugin’s support team is very helpful; thank you for providing that. DreamPress indeed does NOT serve cached pages if a cookie is present.

This last sentence of theirs: “If your hosting provider has an option where they don’t serve cached page if a cookie is present, then we can devise a solution for that.”

If I understand it correctly, since it is the case that DreamPress by default does not serve cached pages if a cookie is present, please let them know this is the case so that they can devise a solution to adjust the plugin.

[outpost33]

Hi,

Just wondered what if you have anything further on this, following the information above supplied by Dreamhost support? I am still seeing this issue – here’s a typical email from a member:

Dear Team,

I’m a new member of your platform, but unfortunately membership access doesn’t work. I’m always asked to sign in again (which I already did a few times).

Can you please check what’s going wrong ?

Many thanks in advance for your help

[admin]

Something else is conflicting somewhere but I have no idea where that is coming from. Different people use different plugins, themes and server configuration. So conflicts are really hard to identify (that is just beyond the scope of the free support we can offer). Try a different plugin and hopefully you won’t have the same conflict on your site with the other plugin.

[outpost33]

Many thanks for your response.

In your previous reply, you mentioned that if my hosting provider has an option where they don’t serve a cached page if a cookie is present, then you could devise a solution.

I have confirmed that my hosting provider does not serve cached pages if a cookie is present. Does this help you resolve the problem?

Furthermore, this does very much look like a cache problem. For example, when the user is caught in the redirection loop (i.e. the website tells them they need to log in when they just did) a simple refresh of the page reveals that they are indeed logged in.

[denimbluebiz]

This is doing the exact same thing to me. I’ve installed the WP Total Cache plugin, followed instructions above, saved and purged the cache. Still getting the same thing. Prompting me to login again no matter what. This seems to be a big issue and I can imagine affecting a lot of sites. Hopefully Simple Membership can solve this problem on their end soon.

[denimbluebiz]

Also, just followed the instructions deactivating all plug-ins, and changing themes. Same issue. I am just going to delete the WP Members plugin and find another membership plug-in. Too bad as I liked this one.

[admin]

Hi, I have checked and re-checked everything. The plugin itself has no issue with the login system. The issue is going to come from one of the following sources:

#1) PHP session on the server is not functioning 100%.

#2) Some kind of caching issue. Could be a caching solution you are using or your hosting provider using caching. I have seen instances where the hosting provider said they are not doing any caching but then when I jumped on a site to investigate, I found that there were using some caching. On the cheaper hosting plans, some hosting companies just do some caching on the server end and they don’t tell you about it.

#3) You may have another plugin that is conflicting our user login functionality. I have seen plugins that just breaks the PHP Session functionality on the site and then when another plugin tries to use the PHP session, it doesn’t work for that plugin.

#4) Sometimes, I have found people to mix up the HTTPS and HTTP pages on their sites. So they have mixed pages on the same site. If a user logs in from the HTTPS page then goes to a non-https page, the authentication will drop due to security reasons. So if your members are login in from a HTTPS page for example and then you have specified an after login redirection that takes them to a non-https page, that is just not going to work. So pick HTTP or HTTPS then stick to that, don’t mix them up in the same site.

#5) The same goes for mixing “www” and “non-www” on the same site. Pick one and stick to it throughout that site.

etc.

It is totally fine to try a different plugin which may be using a different technique and hopefully you won’t have the same issue.

If you want me to jump on your site and investigate the issue related to your particular site and setup, then you can use the following option:
https://simple-membership-plugin.com/paid-support-simple-membership-plugin/

[Author]

Posts