• Resolved overismdtm

    (@overismdtm)


    Hello!

    I used Members to create an online reader for my book – each chapter has its own members-only page. If someone who hasn’t purchased and registered tries to go to a page (beyond the introduction), it takes them to the lockout page you see at the included link and prompts existing members to login.

    This worked well for a while, but I recently discovered an odd bug: When a user tries to go to the chapter page they initially logged in through, it will “forget” that they have already logged in and show them the lockout page, leading to an endless cycle of logging in and never getting to view that page. Any other chapter page besides the one they initially logged in through will work fine.

    After digging into this for a while, I discovered that simply refreshing the page will cause the site to “remember” that they are logged in and will let them in. I put the refresh suggestion on the lockout page, but this is obviously a temporary fix.

    Does anyone know why this would be happening or how to fix it?

    Thanks so much in advance!
    Ryan

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Caseproof

    (@caseproof)

    Hi @overismdtm

    It sounds like this might be related to some website or browser cache. Could you disable caching and see if that helps?

    Best

    Thread Starter overismdtm

    (@overismdtm)

    Thanks so much for the reply @caseproof. Unfortunately, disabling the cache did not seem to have any effect. I tried purging the cache as well and this didn’t affect it either. Let me know if you have any other ideas!

    Plugin Author Caseproof

    (@caseproof)

    Our developer noticed that you included a link for the user to log in. Can you tell me how the user gets back to the original chapter page after logging in.
    If the user has to do something like hit the back button, the page will usually just restore itself to how it was before logging in – thus why refreshing it works. It may be a good idea for you to figure out how to automatically redirect the user back to the page after logging in (e.g. with a redirect URL parameter on the login page).

    Hopefully, that helps.

    Thread Starter overismdtm

    (@overismdtm)

    Let’s say the user is on the unlocked introduction page and they click chapter 3. It will take them to the lockout page and direct them to the login page. Logging in currently always redirects back to the introduction page.

    If they then click chapter 3 again, it will take them to the lockout page again and make them go through the login process again. If they click any other chapter, it will know they’re logged in and let them read it.

    Thanks for the suggestion on redirecting back to the page they clicked. I’m not sure how to set that up but I’m sure I could figure it out if I knew it would solve the problem.

    Plugin Author Caseproof

    (@caseproof)

    That’s odd. It definitely sounds like a caching thing, but it’s hard to say for sure without troubleshooting directly on your site.

    That said, Members doesn’t really handle the login/redirect portion – this would be WordPress itself. Members only checks the current user’s privileges against the page’s settings. It sounds like this is correct, but only after reloading the page. A simple page refresh correcting things says that the validations are working properly, and that the first page load after log-in is cached.

    Kind regards

    Thread Starter overismdtm

    (@overismdtm)

    I’d be happy to grant you access to all the pages if you’re willing to check it out and see if you can get to the bottom of it. I would really appreciate it.

    It seems like a bit of a crossover issue between WordPress and Members, and I’m sure most WordPress forums would send me back here since it has to do with people not staying logged in through the Members plugin.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Site Selectively Forgets that User Is Logged In’ is closed to new replies.