• Resolved shawnwyatt

    (@shawnwyatt-1)


    I recently updated from v2.1.8 to v2.1.9 and in doing so noticed that the page I had previously protected using this plugin was accessible to non-members. Going to the page in Dashboard, checking the the “No, Do not protect this content.”, saving, then checking “Yes, Protect this content.” again enabled the membership requirement.

    https://www.ads-software.com/plugins/simple-membership/

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support mbrsolution

    (@mbrsolution)

    Hi shawnwyatt are you saying that updating the plugin to the latest version, your protected content was automatically changed by the update to “No, Do not protect this content.”?

    Thread Starter shawnwyatt

    (@shawnwyatt-1)

    Sorry for any confusion. After the update, the page I had protected still had the Yes, Protect this content checked, but it wasn’t actually protecting it. I could see the page fine using three different browsers, even after logging out and dumping history/cache. Disabling it, then re-enabling it fixed it fine.

    Plugin Support mbrsolution

    (@mbrsolution)

    Okay thank you for sharing.

    The plugin sometimes can cause a bit of a hiccup but a refresh or a re-enable of an option or a feature can fix the problem. There are various factors that can cause this to happen. One of them could be related to a cache plugin, if not configured correctly could cause this to occur.

    If your issue is resolved can you mark it as resolved.

    Thank you

    Thread Starter shawnwyatt

    (@shawnwyatt-1)

    I have WP Super Cache, as installed and preconfigured by the Host during WP installation.

    Thanks!

    Plugin Support mbrsolution

    (@mbrsolution)

    Is it still working well for you?

    Thread Starter shawnwyatt

    (@shawnwyatt-1)

    Oh, it works fine (now). Just that after the upgrade I had to disable, then re-enable protection for the one page where I’m using it. The confusing part that I saw was that I still had it enabled, yet it “didn’t work”. I can understand a cache plugin or other plugins might interact with something like a membership plugin after a change like this. After an update, you might want to put a message in Dashboard for the Admin to check their pages as a “public user” to ensure protection is still enabled. My hope is that this is only happened to me for some odd reason.

    Plugin Support mbrsolution

    (@mbrsolution)

    Thank you for letting me know. That is a good suggestion about the admin message. The plugin authors will look into this further.

    Regards

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Protected Page Stopped Working’ is closed to new replies.