BuddyPress.org

Are you aware of the include parameter for bp_has_members ?

Your use of the exclude parameter is very inefficient. It might be okay on sites with only a few hundred members, but would be a performance bottleneck for large numbers of members.

You could use this plugin: https://github.com/r-a-y/buddypress-usernames-only

Which extends across to the bbPress side of a BuddyPress install. Note that by default, display names are enabled in the member header on profile pages. If you prefer usernames to be shown everywhere, add the following snippet to your wp-config.php file:

define( 'BP_SHOW_DISPLAYNAME_ON_PROFILE', false );

@djpaul had a Like component in his BP Labs plugin that you might want to look at:

https://wordpress.org/plugins/bp-labs/

Between that and the BuddyPress Likes plugin that allows likes for other components, maybe you could develop something to help the broader community, or at least to fit your site’s needs.

One of the benefits of open source is the availability of code you can iterate upon to create something that fits your needs so you don’t have to continually start from scratch when developing a site. Note that many plugins are not built to appease the masses, as much as they are custom built for specific sites and specific purposes. The developers are then gracious enough to share that creation to the community, but I don’t believe that means they need to ensure that their plugin is a swiss army knife, when they had created it to merely open cans. You can’t always expect to find something that perfectly fits your needs (although it’s great when it happens, and it happens often).

There seems to be enough blocks out there for you to build/commision to have built, something that does what you need.

Hi @evitorino,

update to BP 2.2.0 first, than you can use the new member_type functionality.

Find a usage example here, based on what is written on Codex.

This will need some design work and maybe a custom filtered recently active members widget or a custom member directory template for this part of your homepage…

Design (be inspired) – Widget

@gina i’m not so sure about invite anyone i think there might Be a problem with BuddyPress. I need some time to Fully understand

Styling the WP Toolbar is not directly related to BuddyPress and a bit out of the scope of this forum.
Please ask better on a specialized CSS forum. 😉

In BuddyPress 2.1.1, when using this setting “Logged in users may register new sites” > registering new users is not available.
If you deactivate BuddyPress to only let WordPress, this setting doesn’t generate a registration link.
In BuddyPress 2.2 same behavior. So no bug.

This means the problem is coming from the plugin invite anyone. Since BuddyPress 2.2, the way this plugin was overriding BuddyPress site options is not working anymore. I’m going to inform the developer of the plugin.

Take a look through the template files here to see how things fit together. If you use the Template Hierarchy article as a starting block (read through that first), the way you should organise your templates should become clearer

Hope that helps?

@garrett-eclipse, @henrywright,

i added this dicussion here.

Another forum bug is related here.

hi @yosmc,

registration and activation are directly dependant of WordPress, that’s (i presume) the reason why BP doesn’t create those page for you automatically.
This is not a problem when you use a fresh install, but can be one if you’re installing BP on an existent WP install. In this case, some original settings may be slightly change i guess.
BP uses all those page for internal purpose. And this usage is somehow enforced with 2.2.0 version.(see here from trac)

There is anyway no alternative when BP is on. You have to create those page manually. Point.
I don’t think there is a way to get those page automatically created.
Creating them will take 1 mn, which is a less effort in regard of developing a custom function for an operation which is only done once. 😉

Hi @format19

You mention ‘the forum’. That’s bbPress and not BuddyPress functionality. Have you tried asking on their support forum?

Sometimes replies are maked as spam. That may have been the reason? Either way, it would probably have been better if the notification was cleared to avoid confusion at your end.

Feel free to open a Trac ticket to report the problem to our development team.

https://buddypress.trac.wordpress.org

Hello,

I am having the same problem also. It was fine until I updated Buddypress. “The following active BuddyPress Components do not have associated WordPress Pages: Search Page. Repair” Is the homepage notification. I choose the pages and the settings do not save.

Hi @betro99

Sorry you have this issue after upgrading. If you go in Settings > BuddyPress > Page are the registration and activate page set ? If you go in Settings > General > Anyone can register is activated ?

Hi @espyd,

Sorry you are having this issue after upgrading. Just to help us understand why it’s happening, could you reply to these questions:

WordPress version ?
WordPress configuation ? (Multisite or not)
If multisite: is BuddyPress activated on the main site or in a sub site ?
In the General settings of WordPress is the registration setting on ?
Are you using a cache plugin ?

Interesting discussion 🙂

First i’ll explain why i’m using bp_is_active( 'activity' ) : it’s just an extra check to be absolutely sure the activity component is active. I do it because BuddyPress is a set of components you can activate / deactivate from the BuddyPress settings. So if the activity component is not active, no need to add Post Type activities. And when you develop a BuddyPress plugin, you need to remember there can be configs that deactivated the component you are extending.

Second, about the contexts argument. In this codex page https://codex.buddypress.org/plugindev/post-types-activities/ i’m describing a bit his role
Here https://codex.buddypress.org/themes/activity-dropdown-filters-in-templates/ i’m talking about the way we are getting the activity types since BuddyPress 2.1 And finally reading this page https://codex.buddypress.org/developer/function-examples/bp_activity_set_action/ you will see the interest of the contexts argument.
In short the contexts argument is a way to control where you want an option (activity action) to be displayed. For instance if you want to include an option into the single group’s home page dropdown filter you do contexts => array( 'group' )

In the case of a post type, i think in most cases there’s not a great interest to have the activity filter in the group’s single home page because in most cases the post type have been created out of a BuddyPress group (mainly in WP Admin actually). That’s why in my example i suggest to use 'contexts' => array( 'activity', 'member' ), ‘activity’ means display the dropdown option into the activity directory and ‘member’ display it into the member’s profile. The ‘member’ context is interesting in the case of Post Types activities because a post type is always created by a user_id.

Now with the question “could it be possible to display Post type activities into a given group’s stream ?” we must understand this part 'component_id' => 'activity' Here you are defining the component you want the Post type activities to be linked to. So you could say cool! lets put ‘groups’ to have activities in groups. But here you’d be wrong because all generated activities would be displayed in the first group the one having the id #1 (If multisite it could give another illusion…) Why id #1, because it’s the id of the blog where was created the post type. So you would need to have a different value depending from which group the post type was posted. As in core we don’t include a feature to post a post type from a group, by default we are setting the item_id field to the current blog.

Unless you want to arbitrary display the activity in one particular group, i’d say this need should only concern Plugins extending the Groups component. Of course it’s possible, and i’ve done it for one of my plugin.

I hope my explanations will help you @youmin.

I am leaning toward Buddyblock but would like to wait for this functionality to be introduced to the core product to ensure compatibility and support down the road.

BuddyBlock is compatible with BuddyPress 1.7 or higher, including BuddyPress 2.2
BuddyBlock will be supported down the road.