BuddyPress.org

This only takes effect for other created profile fields, not the “Name” field.

Try creating a new profile field and then you should be able to access the options you are looking for.

Hi, you can rename it.
Go to Users=>Profile Fields=>Edit Group.

Hi @dave8528

Please, you can use this plugin…

Buddypress Xprofile Custom Fields Type

Hope this will help.

Thanks.

Read this conversation in its entirety.

The plugin author was kind enough to guide me through the process of making that work. If you follow those instructions, your users will be able to upload their profile photo during registration.

Although this method works, it causes a slight problem: The users won’t be able to update their photo in the future, because the default Buddypress “Change avatar” function refers to a different file, or location, than the xprofile custom fields type location.

If you find a way to fix that problem, please let me know.

You can get the value of an xProfile field in BuddyPress quite easily but you will need to use code. Take a look at this article to get started:

Displaying Extended Profile Fields on Member Profiles

Extended Buddypress profile fields demands an additional name / username field. This is the case whether you are using Buddypress Usernames Only plugin or not.

This is only relevant if you require extended profile fields. If you don’t, then go into Buddypress settings and turn off extended profiles. That will remove the requirement for a second name on the registration / profile area.

If you want to use extended profile fields on BP, but you don’t want the second username / name field uglying up your registration flow, you can do the following.

You have to be careful with this, because if you hack it, remove the second required name / username field, or any of a dozen other solutions I’ve found – the registration will break down. You will get 500 errors, missing confirmation emails etc.

The solution I used for this is as follows.

1. Assuming you just want to use a singular Username for your site – install the Buddypress Usernames Only plugin. It says the plugin is old but it is still working as of WP version 4.7.4 (for me at least). This deals with the display / access of various username / name / fullname / nickname issues throughout the WP / Buddypress install.

2. Next you’ll need to hide the extra name / username field on the registration area, and the BP profile area. Stick this CSS into your theme custom CSS under Appearance > Customize:

#profile-edit-form .field_1 { display: none;}
#signup_form .field_1 { display: none;}

(I have seen a 3rd line of CSS on other solutions – #register-page p { display: none;} – all this did for me was to hide the confirmation message after the user registers. You probably want that so I’d leave that line out).

3. The fields should now be hidden, but the system still requires that information to process properly. So next create a file in notepad and save it as name_remove.js

In that file put the following javascript:

document.getElementById("signup_username").onchange = function() {myFunction()};
function myFunction() {
 var x = document.getElementById("signup_username");
document.getElementById("field_1") .value = x.value
}

Save that file and upload it to your theme folder (same folder as functions.php etc). This javascript automatically populates the hidden field with the username, so the system does not complain or fall over.

4. Finally you need WordPress to pick this javascript file up. You can do that with a function, using file enqueing. Copy and paste this function into your themes functions.php file Appearance > Editor

function wpb_adding_scripts() {
wp_register_script('name_field_remove', get_stylesheet_directory_uri() . '/name_remove.js', array('jquery'),'1.1', true);
wp_enqueue_script('name_field_remove');
}

add_action( 'wp_enqueue_scripts', 'wpb_adding_scripts' );

You have to be careful about the path. If it’s not working at this point, you can view the page source of your register page, and search for “name_remove.js” – look at the path on that script line. If the path is wrong, tweak it in the function above (you might need to change the get_stylesheet_directory_uri() part, or the path part after it. You can check if the path is correct by clicking the link to the .js file in the page source. If the path is wrong, you will get a 404 error. If the path is right, you should see the script code contained in the js file. Fiddle around with the path until it’s correct.

At that point, you have hidden the fields with CSS, and populated the second hidden username / name field automatically with javascript. Test your registration / confirmation email etc to make sure everything is working. But you should be good to go.

Hope that helps someone. Thanks to the folks I cobbled this solution together from.

Try going to .../wp-admin/users.php?page=bp-profile-setup.
If the fields appear there, you should be able to delete them.

I was dealing with this problem too. It might not be exactly what you’re looking for, but in my case I just decided to hook into the BP signup, extract the full name, split it at the first space and then update the WordPress ‘first_name’ and ‘last_name’ user metadata fields with the results.

Here is the code you can add to your functions.php or custom plug-in:

// define the bp_core_signup_user callback 
function ac_bp_core_signup_user( $user_id ) { 
    // make action magic happen here...
    $fullname = bp_get_member_profile_data( array( 'field' => 'Name', 'user_id' => $user_id ) );
   //split the full name at the first space
   $name_parts = explode(" ", $fullname, 2);

   //set the firstname and lastname for WordPress based on the BP name
   //firstname
   if( isset($name_parts[0]) )
        update_user_meta( $user_id, 'first_name', $name_parts[0] );

   //lastname
   if( isset($name_parts[1]) )
       update_user_meta( $user_id, 'last_name', $name_parts[1] );

   //not needed for an action, but I always like to return something
   return $fullname;
}

// BuddyPress save first name last name to WP profile on signup 
add_action( 'bp_core_signup_user', 'ac_bp_core_signup_user', 10, 1 );

When I go in administration menu users, there is no profile fields entry and i dont have a multisite, but the component is activated in the component section what can I do ?

View this guide to create your own profile fields:

User Extended Profiles

That’s an interesting plugin. Do you know if the location fields are xProfile fields?

Do you mean you have created additional profile fields? If so BP Profile Search plugin would allow you to do that.

I would suggest https://wordpress.org/plugins/buddypress-xprofile-custom-fields-type/ to create your profile fields. There also conditional field plugins that would allow you to set up different fields to members and doctors.

First, you need to figure out how to fetch the Active Directory data for a user and how to display it. This isn’t dependent on BuddyPress.

Once, you’ve figured that out, you’ll need to hook into the BuddyPress profile template to add those fields.

If you are a WordPress developer, there are various hooks you could use. View the profile template:
https://buddypress.trac.wordpress.org/browser/tags/2.8.1/src/bp-templates/bp-legacy/buddypress/members/single/profile/profile-loop.php

And hook into any of the do_action() hooks to display your AD data. To get the current user’s ID on a profile page, use bp_displayed_user_id().

@johanna75 – We do need some kind of universal “display public ok” field perhaps?

Some people have fields set to ‘friends only’ – so things in search should only display to them.

Bp has a thing in it when a user is marked as spam, then they are only visible to admins – so I think this kind of functioning is half in there already.

Would be nice for the buddyblock and rtmedia plugins to also consider this visibility thing, and for buddyblock to be able to conditionally affect that as well.

I could see the need for someone to hide certain things from the public and from specific people – what a nightmare it is when things that were assumed secret pop up in search results.. I had this happen with a wp install – pages published but password protected – well either the theme, or the post teaser plugin pulled data from those non public pages and put them smack in the public search results.

Luckily the bp profile search pluing (that I also use – it’s great!) – is under active development – (I see the author has responded to the support forum on wp repo saying it is an issue that is under consideration, but bp does the same thing – so it’s no different in the privacy regard) wonder if we could ping the other bp peeps and rtmedia and buddyblock peeps tp put some heads together on this..

I have a similar problem right now with rtmedia not meshing with buddyblock. When a user blocks and enemy on my site – that enemy can not message them or comment on their activity – but they can harass the sh*t out of them via comments on their media.