Users directed to WP log in rather than buddypress login if protected content

When users (or "strangers") run into protected content, they are being redirected to the WordPress login rather than the buddypress login widget. Is this a setting in buddypress? I am running Membership Pro plugin to protect certain content.

  • Tyler Postle

    Hey again Barb :slight_smile:

    By default the protected content page should just have this on it:

    The content you are trying to access is only available to members. Sorry.

    You can edit the protected content page by going to:

    Membership > Settings > Membership pages. Then clicking "edit page" beside the protected content page.

    Whatever you have on that page is what users should see when they try to visit protected content.

    Is that not what is happening for you? Do you have a link to your site so we can see what happens when someone tries to visit protected content? :slight_smile:

    Look forward to hearing back!

    All the best,
    Tyler

  • Barb

    The default language for protected content is working great for the areas I have filtered through the Access Levels section of Membership. I really wish there were filters from the Events plug in there that I could drag to the positive and negative rules portions. That would make this a lot easier.

    I want public users to see events. It may even be ok with me if they see who has RSVPd for an event. But the problem is that they can then click on the people who have RSVPd and see their profile information. That is no good. I need the profiles to be protected content. I do not see a way to do that through either Events or Membership. Any ideas? On top of that, any areas inside of Events that I do have marked as protected content are sending my users to the Word Press login in site, not the "protected content" page. Seems like it would be easily resolved if we connected the dots between Event and Membership somehow. Right?

  • Michelle Shull

    Hi, Barb!

    I think the secret sauce we need here is URL groups, which allows you to drill down and protect just about anything on your site, even if it's not included in the drag 'n' drop.

    So, for example, to protect member profiles, you could create a URL group like so:
    http://yoursite.com/members/profile/*

    Using your URL, obviously, this will protect any content with a URL that starts http://yoursite.com/members/profile

    You can do the same for Events pages, just grab the URL from the front end of your site for the page you want to protect. If it's a single page, like http://yoursite.com/events/aspecificevent, you can use the URL as is. If it's a group of pages that are in the same directory (all events pages, for example) you can use the wildcard * to provide blanket protection.

    Hope this helps!

Thank NAME, for their help.

Let NAME know exactly why they deserved these points.

Gift a custom amount of points.