BuddyPress.org

That’s normal: page can’t walk, as they have no feet ! 🙂
ça ne marche pas n’a pas le même sens en anglais. Ils disent ça ne travaille pas (does not work).

You have to create these page manually. This is explained in Getting started guide, configuration section.

Configure BuddyPress

If you feel better in french, visit bp-fr.net

Yes indeed, there is a way.

Step by step tutorial with example code which you add to bp-custom.
Note: use this code as is and follow the instruction. Once you understood what it does and how it works, you will be able to modify it to your needs.

First, create a new xprofile field in the first group field (aka Base Group and containing Name as default field). Only fields created in that group are visible on the register page. Call it Type, enter description and choose multiselectbox as field type. Add operator, vendor, coach as select option.

That’s all for the register part handled by BuddyPress.

Now we need to declare the whole thing to get it work on front-end.
Member-type is an additionnal functiony to select members by… type ! Not by role, not by latest, mst popular or anything else. Just (for the moment) by a custom type of your choice.

We have to built a member directory for our types. We have 3 types and they will be shown on 3 new tabs on that directory.

1) we formally declare the member types
2) we count members by type (to stay correctly informative on the directory)
3) we display the tabs

function using_mt_register_member_types() {
	bp_register_member_type( 'operator', array(
		'labels' => array(
			'name'          => __( 'Operators', 'using-mt' ),
			'singular_name' => __( 'Operator', 'using-mt' ),
		),
	) );

	bp_register_member_type( 'vendor', array(
		'labels' => array(
			'name'          => __( 'Vendors', 'using-mt' ),
			'singular_name' => __( 'Vendor', 'using-mt' ),
		),
	) );

	bp_register_member_type( 'coach', array(
		'labels' => array(
			'name'          => __( 'Coaches', 'using-mt' ),
			'singular_name' => __( 'Coach', 'using-mt' ),
		),
	) );
}
add_action( 'bp_init', 'using_mt_register_member_types' );

function using_mt_count_member_types( $member_type = '', $taxonomy = 'bp_member_type' ) {
	global $wpdb;
	$member_types = bp_get_member_types();

	if ( empty( $member_type ) || empty( $member_types[ $member_type ] ) ) {
		return false;
	}

	$count_types = wp_cache_get( 'using_mt_count_member_types', 'using_mt_bp_member_type' );

	if ( ! $count_types ) {
		if ( ! bp_is_root_blog() ) {
			switch_to_blog( bp_get_root_blog_id() );
		}

		$sql = array(
			'select' => "SELECT t.slug, tt.count FROM {$wpdb->term_taxonomy} tt LEFT JOIN {$wpdb->terms} t",
			'on'     => 'ON tt.term_id = t.term_id',
			'where'  => $wpdb->prepare( 'WHERE tt.taxonomy = %s', $taxonomy ),
		);

		$count_types = $wpdb->get_results( join( ' ', $sql ) );
		wp_cache_set( 'using_mt_count_member_types', $count_types, 'using_mt_bp_member_type' );

		restore_current_blog();
	}

	$type_count = wp_filter_object_list( $count_types, array( 'slug' => $member_type ), 'and', 'count' );
	$type_count = array_values( $type_count );

	if ( empty( $type_count ) ) {
		return 0;
	}

	return (int) $type_count[0];
}

function using_mt_display_directory_tabs() {
	$member_types = bp_get_member_types( array(), 'objects' );

	// Loop in member types to build the tabs
	foreach ( $member_types as $member_type ) : ?>

	<li id="members-<?php echo esc_attr( $member_type->name ) ;?>">
		<a href="<?php bp_members_directory_permalink(); ?>"><?php printf( '%s <span>%d</span>', $member_type->labels['name'], using_mt_count_member_types( $member_type->name ) ); ?></a>
	</li>

	<?php endforeach;
}
add_action( 'bp_members_directory_member_types', 'using_mt_display_directory_tabs' );

We also need to sort the members list on each type tab using the loop scope.

function using_mt_set_has_members_type_arg( $args = array() ) {
	// Get member types to check scope
	$member_types = bp_get_member_types();

	// Set the member type arg if scope match one of the registered member type
	if ( ! empty( $args['scope'] ) && ! empty( $member_types[ $args['scope'] ] ) ) {
		$args['member_type'] = $args['scope'];
	}

	return $args;
}
add_filter( 'bp_before_has_members_parse_args', 'using_mt_set_has_members_type_arg', 10, 1 );

And we finally clean the cache to stay up to date with the output

function using_mt_clean_count_cache( $term = 0, $taxonomy = null ) {
	if ( empty( $term ) || empty( $taxonomy->name ) || 'bp_member_type' != $taxonomy->name )  {
		return;
	}

	wp_cache_delete( 'using_mt_count_member_types', 'using_mt_bp_member_type' );
}
add_action( 'edited_term_taxonomy', 'using_mt_clean_count_cache', 10, 2 );

That’s all for a members directory page showing All Members and tabed Members by type.

If you want to show the type of a member on his profile header, use this:

function using_mt_member_header_display() {
	$member_type = bp_get_member_type( bp_displayed_user_id() );

	if ( empty( $member_type ) ) {
		return;
	}

	$member_type_object = bp_get_member_type_object( $member_type );
	?>
	<p class="member_type"><?php echo esc_html( $member_type_object->labels['singular_name'] ); ?></p>

	<?php
}
add_action( 'bp_before_member_header_meta', 'using_mt_member_header_display' );

Or if you want to display the type under each user avatar on the member directory, you can use this snippet. Note: was originally made to add a geoloc shortcode below the member type. I let it as is, so you can see how it’s done.

function who_are_you_directory() { // by member_type name + geoloc (wpgeo me)
$user = bp_get_member_user_id();
$terms = bp_get_object_terms( $user,  'bp_member_type' );

	if ( ! empty( $terms ) ) {
		if ( ! is_wp_error( $terms ) ) {		
				foreach( $terms as $term ) {
					echo '<p>' . $term->name . '</p>'; 					
					echo do_shortcode('[gmw_member_info]');
				}		
		}
	} 

}
add_filter ( 'bp_directory_members_item', 'who_are_you_directory' );

Anything inspired by Codex and heavy topics reading.

Member Types

Members Loop

May this help.

May be useful:

2.2 Member Types – Setting user member types during registration (xProfile)

You can remove the creation option from the template. You have to do this from within a child theme by using a template overload.

Concerned file is bp-templates/bp-legacy/buddypress/groups/create.php

Part to remove for the “hidden” option is

<label>
	<input type="radio" name="group-status" value="hidden"<?php if ( 'hidden' == bp_get_new_group_status() ) { ?> checked="checked"<?php } ?> /> 
	<strong><?php _e('This is a hidden group', 'buddypress' ); ?></strong>
</label>
	<ul>
		<li><?php _e( 'Only users who are invited can join the group.', 'buddypress' ); ?></li>
		<li><?php _e( 'This group will not be listed in the groups directory or search results.', 'buddypress' ); ?></li>
		<li><?php _e( 'Group content and activity will only be visible to members of the group.', 'buddypress' ); ?></li>
	</ul>

I’m experiencing the same issue. After I visit BuddyPress pages and then navigate to any standard or template page, except the homepage, but including the blog, I get a 404. Sometimes a simple refresh will work. Sometimes navigating to a new page will work. Sometimes the issue will not be fixed unless I refresh Permalinks or log-out and log-in again.

WordPress 4.2.2
BuddyPress 2.2.3.1
bbPress 2.5.7 (though, the issue continues even when bbPress is deactivated)

This issue was asked on another post that was closed before an answer was provided:
https://buddypress.org/support/topic/buddypress-iis-and-randomreoccurring-404-errors/

This post had a resolution:
https://buddypress.org/support/topic/page-not-found-error-on-static-pages/

I have checked and Mod_Rewrite is enabled through htaccess as defined here:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /higher/
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /higher/index.php [L]
</IfModule>
# END WordPress

Am I missing anything here? This appears to be an issue with BuddyPress. Does anyone have a resolution?

This comment was kind of on the right track but as most of the people pointed out in that topic, editing core files is a very bad idea.

Instead, you should take a look at this article to familiarise yourself with the Template Hierarchy. That way, you can remove the ‘reply’ link and be sure your modifications will remain after you upgrade BuddyPress.

@ashket That could be related to a theme or a plugin issue because that’s not normal at all. What are your WP/BP versions for that installation? If you change to Twenty Fifteen theme and deactivate all plugins except BuddyPress, is the issue you reported resolved?

Answered on similar question of yours
https://buddypress.org/support/topic/install-issue-menu-hrefs-dont-work/#post-239502

Read the manual …

Configure BuddyPress

@amalsh

None of what you have here relates to redirecting HTTP to HTTPS. I’m assuming you know that?

Nothing ready to use avaible at the moment. Depends of your coding level…

New Plugin Adds Taxonomies to BuddyPress Groups

An old plugin, don’t know if it is still working: bp group reviews
A different one, maybe: buddypress groups extras
And a little read of the codex:

Group Extension API

Good luck !

Have you tested this plugin ?
https://wordpress.org/plugins/buddypress-upload-avatar-ajax/

Depends where wp is installed ! Usually at site root.
See your WP settings (settings > general) if unsure.
Remember also that BuddyPress does not work on installations where you give WordPress its own directory.

Getting Started

@minglonaire,

i’m part of the one percenter who cares about well formed urls and a basic system which is working on 23% of www’s sites !

If you have enhancement ideas, feel free to post in the appropriate forum or open a ticket on Trac.

BP is only a WP plugin and doesn’t handle registration. On the other hand, WP use a very short registering form, containing 3 fields: username, email and password.

First and last name are optionnal fields on the standard WP user profile. These fields are not mandatory, never appear on the registration page and it’s in the freedom of everyone to use them or not. When BP is installed, he provides a mandatory Name field, which can be used to enter a username or a first/last name.

Even if i have no percentage to give you, i’m pretty sure that almost all users are satisfied to use a CMS which doesn’t ask them for real names at first ! And why not their address, blood group, gran’mother nickname or their mom’s phone number ?

This are privacy options, and WP is smart enough to not abuse of such things, by default. Smart enough also to use the simpliest existing register routine, like all other major web operators, a username, a valid email and an encrypted password.

Anything else is matter of flexibility, one of the major interrest to use BuddyPress. And definetly no, not all communities have members who knows each others. Don’t make you the spokeman of such behalf speculation. 😉

I think you’re confused by system requirements and your own desires. To get it clear for the register aspect, read here please.

Oh, and the answer to your question is here:

Customizing Labels, Messages, and URLs

Hi @minglonaire

This whole username, name system in Buddypress is weird

What do you think is weird about it?

Hi @imath

I am sort of loosing my hair since I updated to the latest version of buddypress.
had searched the forum a few months back and put a LOT of time into custom coding that the activity will read my custom post types. I put that code in my functions.php file and was really happy with everything- each activity had it’s own text and it was really nice.

I am not a coder, just building my site, and now, since this update, all my work is gone- all I get is the generic “posted a new item”, and a link to the post- not even the name of the post. I have 3 custom post types, and I need them all to be unique.
I don’t know what to do now, how to start over?

Can I just cancel the new custom post support and go back to my own code?
Please help.