• Resolved rolevine

    (@rolevine)


    Hi,

    It’s possible I’m missing a basic premise of UM. If I have “Global Site Access” set to “Site accessible to Everyone” and I have a WordPress page that is set to private and I try to access that page directly, by putting its URL into the browser window, the UM login screen does not appear and the page displays with no content.

    If, however, I set “Global Site Access” to “Site accessible by logged in users”, set the WP page to “Public” and access the page directly, the login page pops up.

    Is the second scenario the only way to force a login redirect on a page? It’s doable, but a pain in the butt to set the site up as “Site accessible by logged in users” and then exclude a bunch of pages that I want to be public.

    Thoughts?

    Regards,
    Rob

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Ultimate Member Support

    (@ultimatemembersupport)

    Hi @rolevine,

    What version of the Ultimate member plugin you have installed on your site?
    This issue can be due to some conflicts with your theme or other plugins or due to cache.
    Can you please try to do a quick conflict test and see if this issue goes away.
    Here is the doc on how to do a conflict test if you are not sure how to do it.

    Regards.

    Thread Starter rolevine

    (@rolevine)

    Hi @ultimatemembersupport,

    I’m running 2.0.33. While I do the conflict test, can you please confirm that my desired situation, “Site accessible to Everyone” with a private page that launches the login, is possible and a supported UM scenario?

    Regards,
    Rob

    Thread Starter rolevine

    (@rolevine)

    After further research, I think I’ve completely misunderstood the concept of a WordPress private page. I find it simply odd that a private page wouldn’t just force you to a login page, but I didn’t invent WordPress. :). So an alternative solution is to install some sort of content restriction plugin, such as “Paid Member Subscriptions”, and use the shortcodes to block out the sensitive content until the user is logged in. I might even try to make the page so that it has some condition js code to call the login page when the user isn’t logged in.

    As much as I hate to mark it as resolved, because it really should be marked as “ignored”, I’ll do it anyway.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Private pages not causing login when “Site accessible to Everyone”’ is closed to new replies.