BuddyPress.org

great!
thannks

LOL
Duh on me.

Thanks, again!

If you use slugs you’ll need to enclose them in ‘, like `is_page( ‘terms-of-service’ )`

Sure. Here’s the code:

`function sh_walled_garden()
{
global $bp;

if( bp_is_register_page() || bp_is_activation_page() || is_page(terms-of-service) || is_page(privacy-policy) )
return;

if( ! bp_is_blog_page() && ! is_user_logged_in() )
bp_core_redirect( $bp->root_domain .’/’. BP_REGISTER_SLUG );
}
add_action( ‘get_header’, ‘sh_walled_garden’ );`

The activity stream, member directory … the whole nine shows up to not-logged-in users if i add anything to the exclusion line.

What do you mean with everything? Can you post your complete code here?

@travel-junkie

Thanks heaps!
The only issue is that if I add
`is_page(slug)` or `bp_is_page(slug)`
it makes everything visible again.

Any ideas?

@abomb1977
You’ll have to create that TOS page yourself. It’ll be a normal WP page. Then you can exclude that page like this:
`is_page(23)`

23 in this case is the id of the page, so substitute with the proper id. You can use the page slug as well instead of the id.

@Travel-Junkie

I absolutely adore this code you’ve posted. It’s clean and easy to install, and there’s no extraneous junk that needs to be done. A simple copy/paste does the trick amazingly well for me.

But here’s a question:

I know that
`if( bp_is_register_page() || bp_is_activation_page() )’
is where I add slugs that make particular pages available to the public.

I’m also using the bp-xtra-signup, which I think you contributed to. On my registration page, there’s a checkbox to check that says one agrees to the site TOS, but one has to open a link to see the TOS. When that link is clicked, it redirects to the front page of the site that logged out users are redirected to.

I’m wondering two things: (1) I haven’t made a TOS page, so where is it? Does one come with that plugin? (Cause I have yet to find it. LOL) and (2) Where do I get that slug to add to the visible pages code line?

Thanks!
ABomb

Why Docs Tab is active in private group for users that are not member of it?
is it possible to hide it and make not accessible for nonmembers?

can you fix pagination also?

One possible fix or workaround might be to remove ‘favourites’ from public screens i.e only display this if logged in user is equal to displayed user.

imho a lot of a members account/profile information is essentially private to them, I do not really need to see another members favourite list.

@thetoolman

1) s2member. You’ll likely need to download the zip and upload to your site via ftp ‘cuz it’s a huge plugin.
http://www.primothemes.com/post/product/s2member-membership-plugin-with-paypal/
2) Buddypress includes a private messaging system (kinda like internal email) but there are a few chat plugins available too. See this post:
https://buddypress.org/community/groups/miscellaneous/forum/topic/chat-rooms-chat-scripts-any-recommendations/

Hope this helps!

I think you might be barking up the wrong tree. Since you want to repurpose an existing query (the ‘my groups’ query) you don’t really need to alter the querystring. Instead, you should be altering the behavior of the query itself, which happens at the level of the bp_has_groups() function, as found in bp-groups/bp-groups-templatetags.php. One of the arguments for that function is user_id; when one is passed, you know you are looking at a my-groups loop.

Ideally, you would be able to filter bp_has_groups() to detect when a my-groups-type query was being requested, and then hijack it and do a query just for hidden groups. Unfortunately, I don’t believe that there is going to be an easy way to do that in this version of BuddyPress. For one thing, while there is a filter on bp_has_groups, the original arguments (like user_id) are not passed along to the filter in BP 1.2.7 (it’d be a good enhancement request). Second, there is no way to filter groups by status (public, private, hidden) at the moment (that too would be a good enhancement request).

One quick and dirty way to do something like what you want to do is to filter bp_has_groups, grab the content of the group query out of the groups_template global, and remove the ones that are *not* hidden. It’s not an ideal solution for a number of reasons (for one, it screws up pagination) but it can work. Here’s an example off the top of my head (untested!)

`function bbg_hidden_groups_only( $has_groups ) {
global $groups_template;

// when we are looking at a my-groups page…
if ( bp_is_user_groups() ) {
foreach ( $groups_template->groups as $key => $group ) {
if ( ‘hidden’ == $group->status ) {
unset( $groups_template->groups[$key] );
}
}

// reset the keys so you don’t end up with blank spaces
$groups_template->groups = array_values( $groups_template->groups );
}

return $has_groups;
}
add_filter( ‘bp_has_groups’, ‘bbg_hidden_groups_only’ );`

This is your THIRD post you have made on this problem.

@tradiart
I´m also going to use BuddyPress as an intranet. Its for a company and it is going to be completely locked down if users arent logged in.
Can you please share some experiences with your intranet solution. The biggest question i have is to “lock down” the site when users are logged out. No information is allowed to be exposed. Do you have the same setup? That the user have to be logged in before accessing any information?
I´m thinking about RSS feeds. How can i restrict access to them? I want to have BP email updates instead.
What plugis/hacks are you using to achieve your intranet solution?
What modules/functions do you have active? Groups? Forum? more?
Do you have a solution for sending email updates to users when someone reply to a forum post?

@joshua_d Some other options include
https://wordpress.org/extend/plugins/bp-profile-privacy/
https://wordpress.org/extend/plugins/buddypress-profiles-manager/
and/or making the site private for members only via script or a plugins like
https://wordpress.org/extend/plugins/s2member/
https://wordpress.org/extend/plugins/hs-membership/

I know that there are other devs who are interested in developing the plugin. Just don’t know when it will happen and whether or not it’ll be free or premium.

Check out the messages loop:
https://codex.buddypress.org/developer-docs/custom-buddypress-loops/the-private-messages-loop-bp_has_message_threads/

Are you looking for something like “all messages will be deleted after __ days”?

Hi, I should preface this by saying that I’m not a BuddyPress developer as such, but have been coding WordPress themes professionally for a couple of years, and have been researching BP and putting together a BP-based startup for the past couple of months, so have been through these questions myself, and my own early steps may prove useful.

1. See https://wordpress.org/extend/plugins/bp-profile-privacy/

2. https://wordpress.org/extend/plugins/buddypress-private-community/ might be interesting. There’s another, more granular, privacy plugin that the community has its fingers crossed for, for further details see http://bp-privacy.com/

3. All of that should, and does, happen as a matter of course.

4. Semantics aside, they are all “subscribers” as far as WP is concerned, ie. members and commenters are one and the same.

5. BuddyPress themes contain extra template files for the parts of BP that are an extension on the WP template system (eg. activity, groups, user profile etc.) plus various css and javascript files. Running a regular WP theme with BP running won’t give you the framework to display that BP functionality. In order to achieve that, your WP theme needs the extra template files. You have two options, each with benefits and drawbacks:

a) Extend your existing theme with the required template files, javascript and css to enable and display the BuddyPress sections and functionalities. See https://wordpress.org/extend/plugins/bp-template-pack/ The drawback is that next time BuddyPress is updated, you might be faced with quite a fair amount of development getting your site aligned with the latest code base, new features etc.

b) Constructing a child theme. This relies on running the Default theme, and then adding your own css overrides and theme hacks as a non-destructive layer on top. The principle is that you can strip away your own additions, and you’ve still got the Default theme running beneath it, so in a sense it’s “unbreakable” and whilst you may need to modify your additions once BP is next updated, the underlying template will always function. With a decent caching strategy, unless you’ve expert level php behind you, I think it’s the way to go.