BuddyPress.org

Regarding my caveat above (that BP activities were not showing up in the BP news feed of a non-admin user), I have discovered that two other plugins I have been using are effecting the behavior here:

1. BuddyBoss Wall: this is not breaking anything, but it does change what the activity stream looks like to the user. In particular, it adds a “news stream” view, similar to Facebook. So for anyone reading this later wondering what I meant by “news stream” above, that’s apparently a BuddyBoss Wall specific view.
2. BuddyPress Activity Privacy: It was when I disabled this plugin that the non-admin user started seeing the activity updates in his news feed as I would have expected. And I’m not saying that this plugin was breaking anything necessarily—could easily have just been some configuration mixup on my part. But it was time for me to remove this plugin anyway because it was adding unnecessary complexity to my site.

So removing the Activity Privacy plugin resolved the caveat. Scenario 4 is now working for me just as I need it to.

Thanks for the suggestion, @earl_d. I had tried it already, but at your suggestion, I tried again. I did find one user error on part that was partially responsible for the fact that it didn’t work previously (the root group forum had a visibility of “Hidden”, which breaks makes the topic inaccessible to non-admin users). But still, your suggestion didn’t work for me.

TLDR: I got it working, mostly, though not entirely, and not using the approach you suggested, but your suggestion sent me down a fruitful path that ended up working out. See Scenario 4 below. Posting all of this for the benefit (hopefully) of others that may come along some day trying to work through the same issue.

(BTW, the way I interpreted your suggestion was that I should set the top-level group forum to have type=category instead of type=forum. In any case, here are my results…)

Versions

1. WordPress: 4.6
2. bbPress: 2.5.10
3. BuddyPress: 2.6.2

Scenario 1:
(a) Create the BP Group without an associated forum.
(b) Separately, later, create a forum with type=category
(c) Go to the BP Group’s settings to try and associate the Forum to the BP Group

Fail: The forum drop-down has the category forum greyed out, probably because it’s type=category.

Scenario 2:
(a) Create the BP Group *with* an associated Forum (which will automatically have type=forum)
(b) Separately, later, go edit that new Forum’s type, setting type=category
(c) Navigate to the forum’s page within the group. Say’s “the forum is empty.”
(d) Add a new sub-forum type=forum
(e) Create Topic A in the sub-forum
(f) Navigate to the group’s forum again (as a non-admin user)

Expected: Topic A should appear
Actual: Topic A does not appear

(g) How about directly linking to Topic A? Maybe Topic A is accessible to the user, but somehow the template simply isn’t outputting it under (f) above?

Expected: Topic A should be accessible
Actual: Topic A is accessible

Therefore: the user can see and interact with Topic, but BuddyPress doesn’t know about it as being part of the forum.

In retrospect, what seems to have actually happened here is that the original group of type=forum was regenerated and associated with the BP Group. So our topic is probably not showing up in the Group because it’s parent is the sub-forum of a forum the forum that is no longer associated with the group.

Scenario 3:
I thought: If sub-forums don’t work, then maybe multiple sibling forums could work. The Settings page for BuddyPress obviously only allows you to attach one forum, though the data model seems to allow for multiples. However, after slogging through the code, it’s clear that the current version of bbPress thwarts the adding of multiple forums. In at least two places that I saw in the code (like includes/extend/buddypress/groups.php), you have something like this:

// No support for multiple forums yet
$forum_id = (int) ( is_array( $forum_ids ) ? $forum_ids[0] : $forum_ids );

So even if you were to completely bypass the user interface and do a hack of some kind to attach multiple forums to the group, this sort of code would thwart the hack.

Scenario 4:
So what if we go back to Scenario 1, but set up the initial group-associated forum with type=forum, instead of type=category. It would then be selectable in the admin UI, or could just be created automatically upon creation of the group.

(a) Create a new private group with an associated forum
(b) Go create a new private forum and set its parent to be that initial group forum
(c) Create a topic in the sub-forum
(d) Navigate to the forum within the group as a non-admin user

Expected: The sub-forum should be visible and navigable
Actual: It is! The user can click through, see the topic within the sub-forum, and reply on it.

Conclusion: Success! This is the best and most functional scenario thus far.

Key differences from what I’d tried and failed before:

1. All forums involved have to be set to Private visibility. If Hidden, then some aspects of this may success, but others will fail.
2. The forum that is associated with the group will have to be type=forum, not type=category. But I wrote a little plugin that disallows creation of new topics within a forum, without having to mark it CLOSED (thereby also disabling comments). So this will functionally turn this top-level group forum into a category/container forum anyway

Caveat: I have noticed that when my admin user replies on the topic within the sub-forum, the BP Activity is created as expected (seen in the admin screen under Activities), but it doesn’t show up in the BP news feed of my non-admin test user. The other way works, though: if my non-admin user posts a reply to that topic, then this activity shows up in the news feed of my admin user. I need to debug that.

I have the same need/concern.

Unfortunately, I think the suggestion from @openring to use https://wordpress.org/plugins/bbp-private-groups/ won’t work. I’ve looked closely at that plugin. It doesn’t seem to have anything to do with BuddyPress groups. Rather, it seems to have to do with creating it’s own role based access groups. So that’s a way of having more access control over your forums, which is valuable in and of itself, but it doesn’t pertain to BuddyPress.

If you like to keep using Yoast for WordPress pages and exclude BuddyPress from using Yoast, you may try this.

function wpseo_fix_title_buddypress($title) {
    // Check if we are in a buddypress page 
    if ( function_exists( 'buddypress') && ( !empty( buddypress()->displayed_user->id ) || !empty( buddypress()->current_component ) ) ) {
        $bp_title_parts = bp_modify_document_title_parts();

        // let's rebuild the title here
        $title = $bp_title_parts['title'] . ' ' . $title;
    }
    return $title;
}
add_filter( 'wpseo_title', 'wpseo_fix_title_buddypress');

It’s quite probable it just won’t work. BuddyPress intentionally interferes with the page that WordPress thinks its loading (when it’s a BuddyPress URL), and I suspect Yoast SEO will look at this page object, and because we’ve messed with it and because it doesn’t map to a real WordPress Page, it won’t work.

Sorry!

This won’t help your spam issue, that’s another matter, but it will remove the user registration updates on your activity stream (among other activity types, depending on how you configure the plugin)

https://github.com/lenasterg/buddypress-block-activity-stream-types-ls

Well any theme that i have bought for buddypress usage would be at least a year old (probably more) at this point and i not would generally recommend buying a theme that’s old since responsive design trends are still moving so fast. Sorry i cannot personally recommend anything but there are good ways to vet the newer themes as well.

🙂

As of right now, you would have to make a copy of the JS to make your required change:
https://buddypress.trac.wordpress.org/browser/tags/2.6.2/src/bp-templates/bp-legacy/js/buddypress.js?marks=530#L513

This file should reside in your theme’s buddypress/js folder.

Keep in mind that this is the source JS. When used in production environments, this JS is minified to buddypress.min.js.

It sounds like Specular has some built-in BuddyPress support, which is either incomplete or wrongly added.

See if there is a buddypress folder in the Specular theme folder. If this folder exists, rename it to buddypress-backup temporarily and see if the group creation page works again.

If there isn’t a buddypress folder, there is probably a code snippet in Specular’s functions.php that is interfering with the group creation screen.

this place has decent premium themes:
https://themeforest.net/search?utf8=✓&term=buddypress+bootstrap

you can also do a similar search query on the wp.org repository.

Our user details and activity goes into a massive database; however I don’t want this to be impacted by the forum users

If this is absolutely non-negotiable (don’t share the database), you are going to almost certainly have to set up a separate WordPress site, just for your community.

There is one users table in the database, provided by WordPress, and as BuddyPress is a plugin that runs on top of WordPress, we also use that users database table.

If you don’t want new community users mixed up with existing users, you need to put the community stuff on a separate WordPress. Or, write code to filter and customise various lists of users as/when/if you need. BuddyPress Member Types might help.

Look at https://codex.buddypress.org/developer/member-types/ and https://en-gb.wordpress.org/plugins/bp-member-type-generator/ and http://www.buddyboss.com/product/buddypress-member-types/

This is a better question for somewhere on the WordPress.org forums. More people over there, and this isn’t specific to BuddyPress. 🙂

Do other BuddyPress emails get sent?
Do WordPress emails get sent? (comment notification, new user registration, etc).

if you are a non coder would suggest you look at this paid plugin

BuddyPress User Blog

does what u need

“WP was finding it difficult to distinguish users on our current system with users of Buddypress”

correct cause bp adds additional profile fields…xprofile fields like name for example. rest gets stored in the wp_users database.

maybe u can try setting up different subdomains…bp on community.yoursite.com and forums on forums.yoursite.com

check the min requirements here

Getting Started

Basically, you’re trying to built a page menu. That’s WP territory

See here an example using wp_page_menu function which may help to going further:
https://buddypress.org/support/topic/notification-count-in-dynamic-menu/

Hi @jpry,

I noticed that you are using buddypress activity plus with apppresser. I am unable to get it to work together on mobile ( don’t see the photo upload icons) . I thought it was not compatible but wanted to check and see does it work for you out of the box.

Never modify original files.
Custom code for BP can be added to bp-custom.php