BuddyPress.org

Thanks for further explaining yourself JJJ, and I like the general concept behind a lot.. But the idea that speaks to me the most is making BuddyPress in general more flexible and not “hook” into the group API but make a new one based on that which can not only be used for groups but also for users (and thus friends options).

The idea to make a general API which can be hooked in by the Core components and 3rd Party plugins seems to me the best solution. If you take the group API for example and use it’s functions for individual users:

– Add extra signup pages/fields

– Add new pages

– Add new navigational items etc

All these things are possible with the Group API but take lots of work with a regular profile. Like MrMaz said you could break these functions into smaller parts which can be called upon and extended upon for Groups, Users, Friends and the Activity stream.

The amount of possibilities for new plugins would be endless Once again I’m no programmer and this is coming from as a site admin/BP enthousiast/”Copy and Paste and pray to god I don’t get a white screen of death” kinda guy..

edit: I would also like to say that Mike perfectly summorized my exact ideas of what a group should be and what a group of friends means. Well spoken. I’m getting a Deja Vu here lol

I’d like to know as well. I’m not a php programmer. I’d noticed this function is specific for the members template, index I guess.

global $site_members_template;

I guess we need to add a global there. Or replace it in a separate function. I’ll try some things as soon as I have time.

Ideally I’d like to have a function that works anywhere in the theme…

I’m actually having the same issue as shaisimchi. I’ve been playing around with it, but haven’t found the solution. I only had some test users, so I tried deleting those and re-creating users. No dice. Any input would be great. Thanks!

@jamesyeah: I’m pretty sure the fields just need to be instantiated. I’m using a location field from the base group. It took me a while to figure out, but all I had to do was go into edit profile, add data to the field I wanted to use for the location, and select save. Then, that field will show up in the admin drop-down. (If you look at the PHP code, it checks that there is a value for that field. That’s how I figured out what I needed to do.)

Hope that makes sense. May not even be what you were talking about! : )

I got this solution here earlier. This in functions.php or bp_custom.php:

function bp_custom_member_list_xprofile_data( $field ) {

echo bp_custom_get_member_list_xprofile_data( $field );

}

function bp_custom_get_member_list_xprofile_data( $field ) {

global $site_members_template;

return xprofile_get_field_data( $field, $site_members_template->member->id );

}

And then this in the template:

<?php if ( $company = bp_custom_get_member_list_xprofile_data('Company') ) : ?>

<p><?php echo $company ?></p>

<?php endif; ?>

I didn’t come up with this myself. Forgot who deserves the credit…

EDIT:

BTW, this seems to work as well:

<p><?php echo bp_custom_get_member_list_xprofile_data('Company') ?></p>

Or am I missing something?

EDIT2:

Or further cleaned up:

function custom_xprofile( $field ) {

echo bp_custom_get_member_list_xprofile_data( $field );

}

function bp_custom_get_member_list_xprofile_data( $field ) {

global $site_members_template;

return xprofile_get_field_data( $field, $site_members_template->member->id );

}

In the template:

<p><?php custom_xprofile('Company') ?></p>

Sure, there’s a couple ways to do it.

If you want to turn off linking in specific profile fields (so that nothing in “About Me” gets linked, but locations in “Location” or “Hometown” do), you can use https://wordpress.org/extend/plugins/custom-profile-filters-for-buddypress/. Near the beginning of that plugin, there’s a spot for you to list fields that should NOT be linkable.

If you want to be more specific and look for certain words in a field, here’s how. Copy the original xprofile_filter_link_profile_data function from bp-xprofile-filters.php, paste it into functions.php or wherever you put the remove_filter code, rename it something unique (like henry_xprofile_filter_link_profile_data), then afterwards add the line

add_filter( 'bp_get_the_profile_field_value', 'henry_xprofile_filter_link_profile_data', 2, 2 );

At this point you’ll have to customize the filter to look for certain words. Use something like this (untested, but something like it should work):

if ( strpos( $field_value, 'Boston' ) ) {

$field_value = str_replace( 'Boston', '<a href="' . site_url( BP_MEMBERS_SLUG ) . '/?s=Boston">', $field_value);

}

In other words, if ‘Boston’ is found in the field, replace the plaintext ‘Boston’ with a link to a search on the word ‘Boston’.

This is my pet peeve with Buddypress! Wasted at least two weeks on this issue last Summer.

I use the same Beau Lebens email as login plugin that David Lewis found. So I wanted to get rid of username entirely and have basically only real name and email address on my registration form.

To integrate a mailinglist script I needed separate firstname + lastname. Buddypress doesn’t store them out-of-the-box. This is NOT a WPMU issue; WP/WPMU has firstname + lastname in wp_usermeta, but Buddypress simply refuses to synchronize those fields, so you can’t count on the data being there for other scripts (mailinglist, events, etc.).

Here’s my solution:

How to synchronize firstname+lastname between xprofile field_1 and wp_usermeta upon registration

And

How to autogenerate blogname (url) from Blog Title (or username from fullname!)

The Javascript I use for fullname->username looks like this

function copyinputuser()

{

var tmp = document.getElementById('field_1').value;

tmp = tmp.toLowerCase().replace(/^s+|s+$/g, "").replace(/[_|s]+/g, "");

tmp = tmp.replace(/[^a-z0-9-]+/g, "").replace(/[-]+/g, "").replace(/^-+|-+$/g, "");

document.getElementById('signup_username').value = tmp;

}

Unfortunately a lot of people sign up with only one name in the Fullname (field_1) field. Question:

Would anyone know how to validate/check the input for a two-part (minimum) name? You’d probably have to check for a space, make a space required. How would that script look?

No firstname/lastname because this does not work for a lot of international users.

Which countries are you talking about?! Name them.

With all due respect, this is such a bizarre argument. Not only the western world, but India, China, etc. all have no problem whatsoever using two or more names. Countries that use only one name or more than four can write their own plugins, along with the language pack etc.

More than two names is no problem; separating first and last name is primarily about having a first name available. Users can put their other two, three, four names in the second field.

If Facebook, LinkedIn, etc. have no problem requiring separate firstname and lastname, why is this such a controversial issue for Buddypress? Why make life difficult for 80-90 percent of Buddypress users just to prevent offense to 10 percent with different customs?

Just had a quick look. You might be able to just get away with changing the group_id field in wp_bp_xprofile_fields to the id of the new group. The data table only seems to be looking for the id field. You can do that in phpMyAdmin. Try it locally, though, first if at all possible.

@Bowe

setting up different group types is fairly easy. You just have to attach some groupmeta to the group, that basically let you add as many types as you’d like. Then you just check the metadata to figure out what type of group you’re in. Using the groups API you can then add different functionality for different groups.

I’ve written a types-plugin for one of my sites. It doesn’t have an interface, though. The 3 types I needed are hardcoded into it, so it’s really not suited for a release at the moment. There’s also a lot of more stuff, like a shopping cart, part of that plugin. So, I’ve stripped the functions needed for group types out (hopefully al of them).

First we need to add the addtional fields to our registration form:

function sv_add_registration_group_types()

{

?>

<div id="account-type" class="register-section">

<h3 class="transform"><?php _e( 'Choose your account type (required)', 'group-types' ) ?></h3>



<script type="text/javascript" defer="defer">

jQuery(document).ready(function(){

jQuery("#account-type-normal_user").attr("checked", true);

jQuery("#group-details").hide();

jQuery("#account-type-type_one,#account-type-type_two,#account-type-type_three").click(function(){

if (jQuery(this).is(":checked")) {

jQuery("#group-details").slideDown("slow");

} else {

jQuery("#group-details").slideUp("slow");

}

});

jQuery("#account-type-normal_user").click(function(){

if (jQuery(this).is(":checked")) {

jQuery("#group-details").slideUp("slow");

} else {

jQuery("#group-details").slideDown("slow");

}

});

});

</script>



<?php do_action( 'bp_account_type_errors' ) ?>

<label><input type="radio" name="account_type" id="account-type-normal_user" value="normal_user" checked="checked" /><?php _e( 'User', 'group-types' ) ?></label>

<label><input type="radio" name="account_type" id="account-type-type_one" value="type_one" /><?php _e( 'Type 1', 'group-types' ) ?></label>

<label><input type="radio" name="account_type" id="account-type-type_two" value="type_two" /><?php _e( 'Type 2', 'group-types' ) ?></label>

<label><input type="radio" name="account_type" id="account-type-type_three" value="type_three" /><?php _e( 'Type 3', 'group-types' ) ?></label>



<div id="group-details">

<p><?php _e( 'We will automatically create a group for your business or organization. This group will be tailored to your needs! You can change the description and the news later in the admin section of your group.', 'group-types' ); ?></p>



<?php do_action( 'bp_group_name_errors' ) ?>

<label for="group_name"><?php _e( 'Group Name', 'scuba' ) ?> <?php _e( '(required)', 'buddypress' ) ?></label>

<input type="text" name="group_name" id="group_name" value="" />

<br /><small><?php _e( 'We suggest you use the name of your business or organization', 'group-types' ) ?></small>



<label for="group_desc"><?php _e( 'Group Description', 'scuba' ) ?></label>

<textarea rows="5" cols="40" name="group_desc" id="group_desc"></textarea>

<br /><small><?php _e( 'This description will be visible on your group profile, so it could be used to present your mission statement for example.', 'group-types' ) ?></small>



<label for="group_news"><?php _e( 'Group News', 'scuba' ) ?></label>

<textarea rows="5" cols="40" name="group_news" id="group_news"></textarea>

<br /><small><?php _e( 'Enter any news that you want potential members to see.', 'group-types' ) ?></small>

</div>

</div>

<?php

}

add_action( 'bp_before_registration_submit_buttons', 'sv_add_registration_group_types' );

Then we have to validate things and add some usermeta when a regitration happens:

/**

* Add custom userdata from register.php

* @since 1.0

*/

function sv_add_to_signup( $usermeta )

{

$usermeta['account_type'] = $_POST['account_type'];



if( isset( $_POST['group_name'] ) )

$usermeta['group_name'] = $_POST['group_name'];



if( isset( $_POST['group_desc'] ) )

$usermeta['group_desc'] = $_POST['group_desc'];



if( isset( $_POST['group_news'] ) )

$usermeta['group_news'] = $_POST['group_news'];



return $usermeta;

}

add_filter( 'bp_signup_usermeta', 'sv_add_to_signup' );



/**

* Update usermeta with custom registration data

* @since 1.0

*/

function sv_user_activate_fields( $user )

{

update_usermeta( $user['user_id'], 'account_type', $user['meta']['account_type'] );



if( isset( $user['meta']['group_name'] ) )

update_usermeta( $user['user_id'], 'group_name', $user['meta']['group_name'] );



if( isset( $user['meta']['group_desc'] ) )

update_usermeta( $user['user_id'], 'group_desc', $user['meta']['group_desc'] );



if( isset( $user['meta']['group_news'] ) )

update_usermeta( $user['user_id'], 'group_news', $user['meta']['group_news'] );



return $user;

}

add_filter( 'bp_core_activate_account', 'sv_user_activate_fields' );



/**

* Perform checks for custom registration data

* @since 1.0

*/

function sv_check_additional_signup()

{

global $bp;



if( empty( $_POST['account_type'] ) )

$bp->signup->errors['account_type'] = __( 'You need to choose your account type', 'group-types' );



if( empty( $_POST['group_name'] ) && $_POST['account_type'] != 'normal_user' )

$bp->signup->errors['group_name'] = __( 'You need to pick a group name', 'group-types' );



if( ! empty( $_POST['group_name'] ) && $_POST['account_type'] != 'normal_user' )

{

$slug = sanitize_title_with_dashes( $_POST['group_name'] );

$exist = groups_check_group_exists( $slug );

if( $exist )

$bp->signup->errors['group_name'] = __( 'This name is not available. If you feel this is a mistake, please <a href="/contact">contact us</a>.', 'group-types' );

}

}

add_action( 'bp_signup_validate', 'sv_check_additional_signup' );

And then we set up the group for the user (there are some constants in this function, so you’ll need to change that):

/**

* Create custom groups for skools, biz and org accounts

* @since 1.0

*/

function sv_init_special_groups( $user )

{

global $bp;



// get account type

$type = get_usermeta( $user['user_id'], 'account_type' );



if( $type == 'normal_user' )

{

// Do nothing

}

elseif( $type == 'type_one' || $type == 'type_two' || $type == 'type_three' )

{

// get some more data from sign up

$group_name = get_usermeta( $user['user_id'], 'group_name' );

$group_desc = get_usermeta( $user['user_id'], 'group_desc' );

$group_news = get_usermeta( $user['user_id'], 'group_news' );



$slug = sanitize_title_with_dashes( $group_name );



// create dive skool group

$group_id = groups_create_group( array(

'creator_id'	=> $user['user_id'],

'name'			=> $group_name,

'slug'			=> $slug,

'description'	=> $group_desc,

'news'			=> $group_news,

'status'		=> 'public',

'enable_wire'	=> true,

'enable_forum'	=> true,

'date_created'	=> gmdate('Y-m-d H:i:s')

)

);

// add the type to our group

groups_update_groupmeta( $group_id, 'group_type', $type );



// delete now useless data

delete_usermeta( $user['user_id'], 'group_name' );

delete_usermeta( $user['user_id'], 'group_desc' );

delete_usermeta( $user['user_id'], 'group_news' );



// include PHPMailer

require_once( SV_MAILER . 'class.phpmailer.php' );



$mail = new PHPMailer();

$mail->IsSMTP();

$mail->Host = SV_SMTP;



$auth = get_userdata( $user['user_id'] );

$profile_link = $bp->root_domain . '/' . $bp->groups->slug . '/' . $slug . '/admin';



$message = sprintf( __( 'Hello %s,



we have created a group for your business or organization. To get more out of your presence on Yoursitenamehere please take some time to set it up properly.



Please follow this link to fill in the rest of your profile: %s



We wish you all the best. Should you have any questions regarding your new group, please contact us at support@yoursitenamehere.com.



Your Yoursitenamehere Team', 'group-types' ), $auth->display_name, $profile_link );



$mail->SetFrom("support@yoursitenamehere.com","Yoursitenamehere");

$mail->AddAddress( $auth->user_email );



$mail->Subject  = __( 'Your new group pages on Yoursitenamehere', 'group-types' );

$mail->Body = $message;

$mail->WordWrap = 75;

$mail->Send();

}

}

add_action( 'bp_core_account_activated', 'sv_init_special_groups' );

When you write a group extension we’ll have to swap the activation call with a function like the one below to be able to check for group types.

/**

* Replacement activation function for group extension classes

*/

function activate_type_one()

{

global $bp;

$type = groups_get_groupmeta( $bp->groups->current_group->id, 'group_type' );

if( $type == 'type_one' )

{

$extension = new Group_Type_One;

add_action( "wp", array( &$extension, "_register" ), 2 );

}

}

add_action( 'plugins_loaded', 'activate_type_one' );

The last thing we need to do is add our group type names to group and directory pages:

/**

* Modify the group type status

*/

function sv_get_group_type( $type, $group = false )

{

global $groups_template;



if( ! $group )

$group =& $groups_template->group;



$gtype = groups_get_groupmeta( $group->id, 'group_type' );

if( $gtype == 'type_one' )

$name = __( 'Type 1', 'group-types' );



elseif( $gtype == 'type_two' )

$name = __( 'Type 2', 'group-types' );



elseif( $gtype == 'type_three' )

$name = __( 'Type 3', 'group-types' );



else

$name = __( 'User Group', 'group-types' );



if( 'public' == $group->status )

{

$type = sprintf( __( "%s (public)", "group-types" ), $name );

}

elseif( 'hidden' == $group->status )

{

$type = sprintf( __( "%s (hidden)", "group-types" ), $name );

}

elseif( 'private' == $group->status )

{

$type = sprintf( __( "%s (private)", "group-types" ), $name );

}

else

{

$type = ucwords( $group->status ) . ' ' . __( 'Group', 'buddypress' );

}



return $type;

}

add_filter( 'bp_get_group_type', 'sv_get_group_type' );



/**

* Modify the group type status on directory pages

*/

function sv_get_the_site_group_type()

{

global $site_groups_template;



return sv_get_group_type( '', $site_groups_template->group );

}

add_filter( 'bp_get_the_site_group_type', 'sv_get_the_site_group_type' );

It’s quite a bit of code, but it should get you started. This hasn’t been tested with 1.2 btw.

Basically, you could extend the registration form by using one of the many hooks provided there. The data your user inputs there can then be saved as usermeta and it won’t show on their profile. Something like this:

/**

* Add xtra input field to registration form

* @since 4.0

*/

function tj_add_to_registration()

{

?>

<div id="tos" class="register-section">

<h3 class="transform"><?php _e( 'Don\'t forget...', 'traveljunkie' ) ?></h3>



<?php do_action( 'bp_accept_tos_errors' ) ?>

<label><input type="checkbox" name="accept_tos" id="accept_tos" value="agreed" /> <?php _e( 'Check this box to accept our <a href="/terms-of-service" target="_blank">Terms Of Service</a> (required)', 'traveljunkie' ) ?></label>

</div>

<?php

}

add_action( 'bp_before_registration_submit_buttons', 'tj_add_to_registration' );



/**

* Add custom userdata from register.php

* @since 4.0

*/

function tj_add_to_signup( $usermeta )

{

$usermeta['accept_tos'] = $_POST['accept_tos'];



return $usermeta;

}

add_filter( 'bp_signup_usermeta', 'tj_add_to_signup' );



/**

* Update usermeta with custom registration data

* @since 4.0

*/

function tj_user_activate_fields( $user )

{

update_usermeta( $user['user_id'], 'accept_tos', $user['meta']['accept_tos'] );



return $user;

}

add_filter( 'bp_core_activate_account', 'tj_user_activate_fields' );



/**

* Perform checks for custom registration data

* @since 4.0

*/

function tj_check_additional_signup()

{

global $bp;



if( $_POST['accept_tos'] != 'agreed'  )

$bp->signup->errors['accept_tos'] = __( 'Please make sure to read our Terms of Service and then check this box!', 'traveljunkie' );



}

add_action( 'bp_signup_validate', 'tj_check_additional_signup' );

I haven’t tested the above code much so there might be some bugs…

This is the default behaviour. Have a look at https://wordpress.org/extend/plugins/custom-profile-filters-for-buddypress/

Are you asking whether a realtor community, storing and fetching realtor information is possible with BP? Or are you asking whether you could have that layout with additional member field data?

I agree with Peter in that, the data displayed here is coming out of a complex realty system. But the layout is nothing special. You could do that with BP. You’d just add the extra fields to the member directory layout (user meta) and the members themselves would have to supply that data in their profiles.

I’d like to use this on a current project I have, but being a BP/WPMU newbie, I’m a little lost about setting it up. I have it installed, I’m just not sure about what goes in the following fields:

“Which group contains the location information?”

“Which field represents each user’s location?”

“Which field represents a description for each user (i.e. ‘About Me’)?”

Any chance any one else has used this and could give me a quick breakdown of what they’re for, and how I’d go about setting them up. I would’ve posted on the BraveNewCode forums, but I guess those are down for a while. Also, I can’t find any documentation on the site for it.

I’m now using another 3rd party plugin for membership to the site (WP eMember). While it has its own table, it also creates a matching WP user for each of the members it creates. I was thinking of adding some code to add users to a group on creation of their profile, and then using this group as the group that “contains the location information”. Am I on the right track?

Thanks in advance for any help!

@Teebes: you can already do what you want with auto group join: http://brentandmary.net/2009/10/24/bn-auto-join-group-plugin/

I’m planning to do the same for my site. Based on certain profile fields they are put in different groups after signup!

I love the idea of as an admin, creating a relationship between profile fields (not necessarily required ones) and groups. In fact, I was scouring around my new 1.2 install hoping this feature was already live I see it as a good way to get folks involved in their specific demographic while always having the ability to leave the group if they want.

I see this as an option when defining a group, keeping the current public/private options intact, just adding another criteria or ‘group profile rule’.

The name field was previously split into “First Name / Last Name” fields, but this is an issue for internationalization. In future versions it may be possible to apply rules to profile fields that will determine the content allowed.

That is such a silly argument. 90 percent of the civilized world uses firstname + lastname. Why make life difficult for the rest of us just because theoretically a few places in the world use only one name or three names or whatever? Why not let them hack a workaround it?

My issue with this is also not just about that field, but more about what it says about Buddypress’ priorities. If you want to register members in your company or sports club with name, address, phone number, etc. there is no easy way to do it, you’ll have to hack core files and later you’ll have to use custom functions to retrieve the data from several different tables in the database.

Also, BuddyPress will automatically synchronize profile fields with the WP profile fields. Check the function xprofile_sync_wp_profile()

No it doesn’t. Version 1.0 only added first name and last name to wp_usermeta if a user updated his account data after signup. You couldn’t count on the data to be there for every member. I had to write a custom function, based on xprofile_sync_wp_profile, to force that synchronization to happen upon registration.

Also, BuddyPress will automatically synchronize profile fields with the WP profile fields. Check the function xprofile_sync_wp_profile()

The name field was previously split into “First Name / Last Name” fields, but this is an issue for internationalization. In future versions it may be possible to apply rules to profile fields that will determine the content allowed.

To me the biggest barrier to more professional use of Buddypress is the lousy member/user management. Everything is based on username/password. There isn’t even a built-in way to get people to sign up with their real name, first name + last name. There is a required custom field for “Name”, but with the way the sign-up form is structured new users are almost encouraged to enter a garbage name – lowercase, one word anonymous nickname bs.

After lots of painful hacking in core files I now have a form with one Real name field on top. My custom code in the back splits the real name and stores it in various places in the database, so at least I have synchronized data in wp_usermeta etc. Buddypress does none of this out of the box and in general BP developers don’t seem to see this as a problem. But the one field for real name still doesn’t really force new users to enter a full two-part name.

In a previous version of my site I did have separate first name and last name fields. I NEVER had people sign up with cutesy one name names. Sure, you can create custom fields in xprofile, but synchronizing the input with all the other username, nickname, name etc. fields in the datebase and integrating them with other member management scripts businesses will have on their server requires serious database and php programming skills.

Just add the profile fields in the backend.

No worries. Glad I could help