Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restrict visibility of BuddyPress pages to a user's BuddyPress friends? #4

Closed
adambreen opened this issue Jul 17, 2016 · 1 comment
Closed

Comments

@adambreen
Copy link

Hey there,

I'm hoping restrict-user-access can really help us avoid writing code!

We are building a Wordpress Multisite network, with BuddyPress network-activated (thus its toolbar is visible on all sites in the network).

However, we want to ensure similar privacy levels to Facebook, in the sense that our users' BuddyPress profiles should be (able to be) private, except to other users who they have a BuddyPress relationship with (eg. followers).

So there are two key use cases:

  1. Public internet (not logged in to BuddyPress): do not show any BuddyPress member profile details, especially their Sites page (ie. the old "blogs" page).
  2. Logged-in user: only show BuddyPress "Sites" page and "Activity" to other users who are logged-in and, say, following the profile in question.

Please let me know if Restrict User Access can achieve the above? I apologise for using a GitHub issue to ask this question — I couldn't find a better way to contact you!

Warm regards,

Adam

@intoxstudio
Copy link
Owner

intoxstudio commented Aug 6, 2016

Sorry for the delayed response here.

Some of the functionality you are describing is not built into the plugin, but it is possible to restrict access to specific BuddyPress pages to users that are not logged in (Use case 1).
Hiding only parts of a page can also be done with a shortcode or by using rua_has_user_level($user_id:int,$level_id:int) in the theme templates.

I think BuddyPress already has built-in functionality to hide profile posts/statuses to friends/followers, so I would recommend you look into expanding that for use case 2. At this point, I think it would be too much work to try to implement that use case with this plugin, but if you plan on doing it, I would be more than happy to answer any questions and see the result.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants