BuddyPress.org

Hi @navinachettri

1. Have you searched the plugin directory?
2. This can be done via hooks. It will need some custom code (not much, just a few lines).
3. You could hide or show xProfile fields according to role. How exactly roles are created and managed will be dependent on point 1
4. Again, to distinguish business users from ‘normal’ users, you’d use the roles created via the plugin you’re using from point 1. The jobs and adverts could each have their own custom post type
5. This will need to be custom coded

Hope that helps?

For me also not:

I tried it with

Mitglieder-Kategorie (Team oder Fan?)

instead of

'name of your field'

as well as with

'Mitglieder-Kategorie (Team oder Fan?)'

But my users can still change the values for this field. –

I tried as well – already before and now again – this code of @noizeburger:

//hide the user role select field in edit-screen to prevent changes after registration
add_filter("xprofile_group_fields","bpdev_filter_profile_fields_by_usertype",10,2);
function bpdev_filter_profile_fields_by_usertype($fields,$group_id){
//only disable these fields on edit page
if(!bp_is_profile_edit())
return $fields;
//please change it with the name of fields you don't want to allow editing
$field_to_remove=array("User Role");
$count=count($fields);
$flds=array();
for($i=0;$i<$count;$i++){
if(in_array($fields[$i]->name,$field_to_remove))
unset($fields[$i]);
else
$flds[]=$fields[$i];//doh, I did not remember a way to reset the index, so creating a new array
}
return $flds;
}

It works neither with

"Mitglieder-Kategorie (Team oder Fan?)"

nor with

Mitglieder-Kategorie (Team oder Fan?)

nor with:

'Mitglieder-Kategorie (Team oder Fan?)'

@jessicana,

The field NAME in the field group BASE is required. This group is used for the registration page to work. As you already know, it’s also this group who allows you to show custom fields on the registration page.
The NAME field in BuddyPress is intended to receive first and last name and replace the two original fields (first name, last name) coming with WordPress.

That said, you can hide this field to users, but you can’t give them the choice to show/hide it.

The above snippet will hide the field NAME to all visitors/members, but not to site admin and the concerned profile.

function bpfr_make_name_members_only( $retval ) {	
	//hold all of our info
	global $bp;
	
	// is xprofile component active ?	
	if ( bp_is_active( 'xprofile' ) )
	
    // The user ID of the currently logged in user
    $current_user_id = (int) trim($bp->loggedin_user->id);
	
    // The author that we are currently viewing
    $author_id  = (int) trim($bp->displayed_user->id);
	
	// user can see only his name && admin can see everyone 
	if ($current_user_id !== $author_id && !current_user_can('delete_others_pages') ) {
		$retval['exclude_fields'] = '1';	
	}
	return $retval;	
}
add_filter( 'bp_after_has_profile_parse_args', 'bpfr_make_name_members_only' );

Add this to your child-theme functions.php or to bp-custom.php

I wouldn’t rely on messing with visibility settings.
To make a profile field only editable by admins, do this in bp-custom.php or a plugin:

// only admins can edit the Skills field
function chief_hide_profile_fields( $retval ) {
	
	if( is_super_admin () )
		return $retval;

	if(  bp_is_profile_edit() || bp_is_register_page() )
		$retval['exclude_fields'] = '3';	//profile field ID's separated by comma

	return $retval;

}
add_filter( 'bp_after_has_profile_parse_args', 'chief_hide_profile_fields' );

Note that you need to add the correct id(s) for exclude_fields.
And that ‘ || bp_is_register_page() ‘ keeps the field(s) off the register page – which you may not need to do.

Re how to create profile fields in code, there a couple of ways to do it depending on the kind of field and how it will be used.
Take a look at these plugins for more info:
https://wordpress.org/plugins/buddypress-xprofile-custom-fields-type/
https://wordpress.org/plugins/buddypress-xprofile-image-field/

Another snippet, more accurate with the suggested way above. Snippet goes into bp-custom or functions.php

The field/field group is only shown to site admins. A small bug in the current BP version(.0 -> 2.0.2) prevent of completely remove the group tab from the edit screen. Bug is fixed and this will work with BP 2.1.

function bpfr_hide_profile_field_group( $retval ) {
	if ( bp_is_active( 'xprofile' ) ) :	
	
	// hide profile group/field to all except admin	
	if ( !is_super_admin() ) {		
		//exlude fields, separated by comma
		$retval['exclude_fields'] = '60';  
		//exlude groups, separated by comma - this may work with BP 2.1
		$retval['exclude_groups'] = '7'; 			
	} 
	return $retval;		
	
	endif;
}
add_filter( 'bp_after_has_profile_parse_args', 'bpfr_hide_profile_field_group' );

@csimpson,

oh crossposting ! haven’t seen henry’s answer.

nobody visibility doesn’t exist. This setting is called “only me“. This means that only the member can see this field – and the site admins. Such fields are not for site admins, but for the members !

I don’t really understand what is not working for you, as what you’re looking for doesn’t exist in BuddyPress. Sorry if i’m misunderstanding you.

When you create such a field visibility, you should also set “Enforce the default visibility for all members“, so the member cannot modify it later on his profile settings.

Little weird side effect, when a “only me” field is used and member A wrote hello, this word becames clickabke, by default. When member B write also hello, it becames also clickable. And if A or B clcik on Hello, it shows a list of all members who wrote the same word. In this case A and B !

Not really confidential, isn’t it ? The solution is to remove the clickable link.
Here’s a snippet which let you do that selectively.

function my_xprofile_filter_link_profile_data( $field_value, $field_type = 'textbox' ) {
    // Access the field you are going to display value.
    global $field;
	
    // In this array you write the ids of the fields you want to hide the link.
    $excluded_field_ids = array(2,9,54); // field ID separated by comma
	
    // If the id of this $field is in the array, we return the value only and not the link.
    if (in_array($field->id, $excluded_field_ids))
	return $field_value;

	if ( 'datebox' == $field_type )
	return $field_value;
	
	if ( !strpos( $field_value, ',' ) && ( count( explode( ' ', $field_value ) ) > 5 ) )
	return $field_value;
	
	$values = explode( ',', $field_value );

	if ( !empty( $values ) ) {
		foreach ( (array) $values as $value ) {
			$value = trim( $value );
			
			// If the value is a URL, skip it and just make it clickable.
			if ( preg_match( '@(https?://([-\w\.]+)+(:\d+)?(/([\w/_\.]*(\?\S+)?)?)?)@', $value ) ) {
				$new_values[] = make_clickable( $value );
				
				// Is not clickable
			} else {
				
				// More than 5 spaces
				if ( count( explode( ' ', $value ) ) > 5 ) {
					$new_values[] = $value;
					
					// Less than 5 spaces
				} else {
					$search_url   = add_query_arg( array( 's' => urlencode( $value ) ), bp_get_members_directory_permalink() );
					$new_values[] = '<a href="' . $search_url . '" rel="nofollow">' . $value . '</a>';
				}
			}
		}
		
		$values = implode( ', ', $new_values );
	}
	
	return $values;
}

/**
 * We remove the buddypress filter and add our custom filter.
 */
function remove_xprofile_links() {
    // Remove the old filter.
    remove_filter( 'bp_get_the_profile_field_value', 'xprofile_filter_link_profile_data', 9, 2 );
    // Add your custom filter.
    add_filter( 'bp_get_the_profile_field_value', 'my_xprofile_filter_link_profile_data', 9, 2);
}
add_action('bp_setup_globals', 'remove_xprofile_links');

Would it matter that I have my group_order (i.e., the order in which my field groups are displayed) arranged in a specific order?

No !
Anyway, i was wrong myself. Apologize. My snippet hides groups from viewing, not from editing. But you can get another trick on this post. And this one works realy. 😉

Hi @simpleone,

you can actually only hide xprofile fields. Hiding field groups is not possible, due to a bug.
But it is corrected for 2.1 and you’ll find a patch on the trac.

You can already apply the patch to 2.0.2 bp-xprofile-classes.php and the above snippet will work. Add it to bp-custom.php or theme’s functions.php

To hide an xprofile group, use bp_parse_args like this:

function bpfr_make_profile_tab_members_only( $retval ) {
	// hide to non members
	if( !is_user_logged_in() ) {
           // exlude groups, separated by comma
		$retval['exclude_groups'] = '4,5';
           // exclude fields, separated by comma
       		$retval['exclude_fields'] = '1,39';			
	} 
	return $retval;	
}
add_filter( 'bp_after_has_profile_parse_args', 'bpfr_make_profile_tab_members_only' );

sorry to bump this old topic. I use both BP 2.0.1 and BP custom fields type and i got the the links removed with:

function remove_xprofile_links() {
    remove_filter( 'bp_get_the_profile_field_value', 'xprofile_filter_link_profile_data', 9, 2 );
}
add_action('bp_setup_globals', 'remove_xprofile_links');

I was wondering if you could use this to only hide the links from certain profile fields, like only for profile field 2, 6 & 7 ?

@simpleone,

Can you show how you solved your problem? danbp‘s code did not work for me. As you, I also wanted to hide some xprofile fields and tabs that I don’t want users to be able to edit.

Since BP 2.0, you can use bp_parse_args to customise template loops and on a much easier way as never before.

The example function below will hide profile groups with ID 1 and profile fields IDs 6, 18 & 39 on the public profile screen of each member and stay visible on the edit screen. Tested & approved 2.0.1

If you get some php warning while using this function, be aware that there is a bug in 2.0.1 bp-xprofile-classes.php (fixed. See ticket). Simply apply the lattest patch to get rid of this error.

function flegmatiq_profiles( $retval ) {	
   // conditionnals to set accordingly to your purpose
	if( !is_user_logged_in()  && !bp_is_profile_edit() ) { 
		$retval['exclude_groups'] = '2';	
		$retval['exclude_fields'] = '6,18,39';	
		
	} 
	return $retval;
	
}
add_filter( 'bp_after_has_profile_parse_args', 'flegmatiq_profiles' );

In your particular case, you have to play with the conditionnals

The example below is to give you an idea how to handle this. Not tested !

function flegmatiq_profiles( $retval ) {
$myfield = xprofile_get_field_data( 'Faculty', $user_id );
if( empty( $myfield ) )
return; // or echo

   if( $myfield == "Faculty" ) 
      if( bp_is_profile_edit() ) { 
		$retval['exclude_groups'] = '1,56';	
		$retval['exclude_fields'] = '6,18,39';	.
      }
   if $myfield == "field_name_2";
     // do something other...

return $myfield;

add_filter( 'bp_after_has_profile_parse_args', 'flegmatiq_profiles' );

Hi @SimpleOne,

read from line 154 in bp-xprofile-classes.php file. It contains many information for what you want to do.
See also on Codex here and here

You can also revert your changes back and use this kind of function (goes into theme’s functions.php or bp-custom.php):

function simple_one_hide_some_profile_fields( $retval ) {	
	
	if(  bp_is_profile_edit() ) {		
		$retval['exclude_fields'] = '48';	//field ID's separated by comma
		
	}	
	
	return $retval;
	
}
add_filter( 'bp_after_has_profile_parse_args', 'simple_one_hide_some_profile_fields' );

May this help ? 😉

Hi have a very similar issue and I think it may be related to the same cause.

I have set up a xprofile group where I have a bunch of different radio fields like so…

About You Widget
Show | Hide

Display Avatar On Profile
Show | Hide

Subscribed Member Badge
Show | Hide

etc.

I have put code all around my website to show or hide things according to a users settings and it all works as it should BUT, the only problem is that the settings don’t take effect until a user goes to edit the particular profile group and clicks the ‘Save Changes’ button.

Even though the defaults are set as they should be initially, they do not actually work until the user saves them.

Any help on this issue would be much appreciated.

Thanks

You’re not attempting to hide anything, if you have created xprofile field groups other than the default ‘Base’ then anything in those groups for user profile input will not show on the standard BP registration form only on the users account profile screen. If you are following that principle and those fields are showing on the main registration form then something is going wrong and likely you have third party plugins at work?

I think a better bet is to collect that info on the BP registration page and then not display it on the user profile (that way you’ll still be able to use it in other ways). With BP 1.6. you can change the visibility of each xprofile field to friends only, logged-in users, or public (and force that level or allow the user to override your selection). (Visible to admin only is coming in BP 1.7, btw, which would totally fix you up.) At the moment, you can modify your theme template file (themes/yourtheme/members/single/profile/profile-loop.php) to hide some fields like this:
`about line 17:

<?php $no_display_fields = array( // Enter the field name of any field that you don't want to appear on the user profile.
‘E-mail’,
‘Name of Field Hide’,
‘Another’
);

if ( bp_field_has_data() && !in_array( bp_get_the_profile_field_name(), $no_display_fields ) ) : ?>`

It’s a hack, but it works for me (until BP 1.7).

I need to be able to show / Hide XProfile groups based on select value during the registration phase. I’m a newbie to all this so could someone please help on how accomplish this.

Is that possible with buddypress? Has this plugin been created?