BuddyPress.org

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.

Hi.
I am looking to create a site similar to the one you propose.
Did you find a solution?
Harty

@dwenaus, the code above gives me duplicate topics, as well as topics misplaced in different groups.

@dwenaus Great code.
Quick question, would it be possible to show it in the activity tab, regardless of tab? Currently it only shows if using the “My Groups”.
Thanks mate.

There is an epic thread on this that is worth a read – https://buddypress.org/community/groups/creating-extending/forum/topic/securing-components-from-non-logged-in-users/

That thread has lots of examples and discussion.

Here’s an example:

`
function restrict_access(){
global $bp, $bp_unfiltered_uri;

if (!is_user_logged_in() &&
(
BP_MEMBERS_SLUG == $bp_unfiltered_uri[0] ||
BP_GROUPS_SLUG == $bp->current_component ||
BP_BLOGS_SLUG == $bp->current_component ||
‘forums’ == $bp->current_component ||
is_page_template(‘private-page.php’)
)
) {

bp_core_redirect( get_option(‘home’) . “/private/” );

}
}

add_action( ‘wp’, ‘restrict_access’, 3 );
`

You can put that in bp-custom.php in the `wp-content/plugins/` directory. https://codex.buddypress.org/extending-buddypress/bp-custom-php/

Thanks, that did the trick!

Deleting `$bp->is_directory &&` from the line above should do it. That means that all the links that have the links directory slug in the URL are excluded.

Look over “Configuring BuddyPress Components” https://codex.buddypress.org/getting-started/configure-buddypress-components/
In dashboard menu BuddyPress > Components, do not enable private messaging. Other than that, anyone can request for and possibly get a response for contact information whether they post in forums or blog posts.

Thanks guys, thanks to @Travel-Junkie ‘s code, I am now able to make an exception for the Links Directory, based on the ‘links’ slug.

However, I’ve now also been asked if we can’t get the individual link page (www.website.tld/links/…) to be an exception too… Can I count on you again?

There are lots of CSS hooks so you can customize the look of your messages pages. It would be easiest to just use some creative theming and create the effect. You could hide most profile information/avatar using CSS.

Or you could also try creating a custom page template using the private messages loop and adjust the parameters to suit your needs.

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

I use BP-Registration-Options and also Members Only between them this keeps out the non registered users and presents the registration page by default (which I have set as my redirect in Members Only). I hope this helps.

@joshua_d
As far as I know there were a couple rounds of private beta for a select few.

@suchaqd
That’s an interesting idea, but I doubt Automattic would go for it. kickstarter.com is great, but so far only available in the US

Thanks @dwenaus. This code is great!
Exactly what i looked for!!!

@acaps2007
@ScottWatson
the post linked below says how to display the number of unread messages.

https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/how-to-moverelocate-the-links-in-the-admin-bars-my-account-individuallyseparately-to-the-sidebar/

But I would prefer the idea @acaps2007 has proposed, that’s the “notification” item and the mouse over effect, since in a buddypress community, we would have
1. private messages
2. friend requests
3. group requests
4. group invites
5. mentions

Although the last one is not included in the default bp notification count, combining the previous four in one place would still help a lot.

Nope, doesn’t matter in this case, cause the && gets tested before the ||, but you can use parentheses. Doesn’t hurt.

If your site has open registration like you say, then users shouldn’t be redirected to the register page when they’re trying to read a post.

Do you have any redirection or private BuddyPress plugins installed?

@travel-junkie

Shouldn’t that line be:

`if( bp_is_register_page() || bp_is_activation_page() || ($bp->is_directory && $bp->current_component == ‘your-links-directory-slug’) )`

The added param should be between parentheses ‘cuz the “&&” applies only to the “is_directory”, no?

Well, just add that page to the first if statement in the function. Something like this:

`function sh_walled_garden()
{
global $bp;

if( bp_is_register_page() || bp_is_activation_page() || $bp->is_directory && $bp->current_component == ‘your-links-directory-slug’ )
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’ );`

@Travel-Junkie and @iamjoshfrank I’ve just implemented your ‘sh walled garden’ code to shield my community pages from prying eyes, and it works great.

I was wondering however if you knew a way I could make an exception for the BuddyPress Links Directory (it’s a plugin, so there is no kind of conditional tag for this, as far as I know).

Any help would be greatly appreciated.