BuddyPress.org

@ch1n3s3b0y – there are options to create your own profile fields, so you could add a new profile field with a radio button eg – choose customer or expert.

There are also different membership plugins and stuff that might enhance that a bit more – plugins like s2member.. maybe even something like press permit…

as far as having a different profile page for each – I think that is going to take some fancy custom coding.. some if then statements and such.. you will likely have to post on a job board to get someone with some skills on that.. it may be tempting to custom code a theme like this – but ultimately I think it would be better to custom code a couple of plugins and drop those into a sidebar or something – eg – “if bp_profile-field-2=customer” then display these fields / this code…

IF you custom mod up a theme and things change in the future where you theme has issues with new buddypress, or you want something different for another reason – then it will be more custom coding to bring over your custom profiles stuff..

just some random thoughts from a BP user – I am not an expert on any of this.

Hi @ndh01,

I think you could do this just with buddypress.

(just please backup database before….. etc)

Go to Profile Fields—> (Click) Add New Field Group

Add New Field (text) say Field Name virgin

Then add the following to your functions.php

function vub_login_redirect($redirect_to, $set_for, $user){

	global $current_user, $bp, $wpdb;
	$val = 'no';
	if (bp_get_profile_field_data (virgin, $user -> ID )!=""){
	$redirect_to = bp_core_get_user_domain($user->ID) .'/groups/';	
}else{
	xprofile_set_field_data( 'virgin', $user -> ID, $val);
	$redirect_to = bp_core_get_user_domain($user->ID) .'/profile/change-avatar/';
}

	wp_redirect( $redirect_to );
	exit();

}

add_action('login_redirect', 'vub_login_redirect', 20, 3);

Alternatively you could as you have suggested create a new meta.

A useful plugin for that would be User Meta Manager

Add Custom Meta say a text field Name — firsttimer

then add the following (instead of the above) to your functions.php

function vu_login_redirect($redirect_to, $set_for, $user){

	global $current_user, $wpdb;
	$firsttimer = get_usermeta($user -> ID, 'firsttimer',single);
	$val = 'no';
	if (!empty ($firsttimer)) {	
	$redirect_to = bp_core_get_user_domain($user->ID) .'/groups/';
}else{
	update_user_meta( $user -> ID,'firsttimer',$val);
	$redirect_to = bp_core_get_user_domain($user->ID) .'/profile/change-avatar/';
}
	
	wp_redirect( $redirect_to );
	exit();

}

add_action('login_redirect', 'vu_login_redirect', 20, 3);

Obviously change the redirects to wherever you want the user to go.

@sbraiden – I recently helped migrate a site off of wpengine because of performance issues and the price wpengine wanted for more horse power under the hood. Their next level of service was going to cost $3200 a month. I suggested linode.com and was also amused by the fact that wpengine runs on top of linode.

The page generation times for wordpress/buddypress/bbpress along with various plugins (gravity forms, buddypress xprofile custom fields type, gravity forms upload rules, gravity forms wysiwyg, gd bbpress toolbox, cloudflare…) was not good. It is still not where we want it either, unfortunately.

The site is quite active, pushing 30,000 members and over 1.3+ million rows in the posts table. On average the page generation times are about 1.5 seconds for logged in users. Adding a new bbpress topic/reply can time out sometimes though. (still on the list to track down and fix)

We utilize Cloudflare out front for a CDN and their threat/spam protection. Their service is free but if you need more page rules to balance out caching the pro service level is $20 a month.

On linode we have a node balancer in front of two 4 core app server nodes. The app server nodes each connect directly to their own 8 core database nodes in a master master setup. This will be changing down the road once the database indexes are trimmed down with some denormalization. The cost for the node balancer, two 4 core and two 8 core nodes is $260 a month but that’s also allowing for some room to grow, capacity wise.

Server software is a combination of nginx, apache (threaded), php-fpm, glusterfs (upload directory only), memcache, zend opcode cache and mariadb. Nginx is the web server in front of apache which serves up static files from the glusterfs file system. Nginx is caching the static content being served up by apache along with full page caching (fastcgi) for anonymous visitors. Cloud flare is also caching the static content and to date we aren’t having any performance issues with IO and glusterfs.

I hope this helps. It can be done but it takes some effort (and money) to do so.

This will hide fields on the profile edit page and on the register page.
You need to add the field IDs.
Put the function in bp-custom.php.

function oazar_hide_profile_fields( $retval ) {
	
	if( is_super_admin () )
		return $retval;

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

	return $retval;

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

@mariovisie – you say after you choose the radio button for man, when you login you always see the other fields… you mean when viewing a profile you see all the filed option? OR you mean if you click “edit profile” you see all field option?

I have not seen all fields show when viewing profiles that are already created, so I am confused if you are seeing this in this way.

as far as “Only an administrator must have the option to change this.” – I don’t know about setting permissions for that, another bp expert may be able to chime in on that – or maybe the “press permit core” plugin can lock that down somehow. Not sure on that one.

under “users” -> “profile fields”

add new field.

I choose “field type” radio buttons – you might use checkboxes or something.

put “guy” in the field option under radio buttons.
then click “add another option” text under that.
put “girl”
click add another option
“couple”

I cannot duplicate your issue.
In wp-admin, Users > Profile Fields, are your fields part of the ‘Base’ group of fields?
Or are they under another group, in another tab to the right of ‘Base’?

btw: instead of bp_get_profile_field_data, you should use bp_get_member_profile_data
That tutorial is for BP 1.5, very old.

but not in the admin menu profile fields section

What exactly are you referring to?
The adminbar at the top of each page? If so, member-header.php does not affect that.

How will the ‘tags’ be used?
As the basis for filtering members?
Or just as ‘notes’ about each member?

If the former, see the BP_User_Query codex page.

If the latter, you could use this premium plugin: BuddyNotes

Or you could simply create template overloads of these 2 files:

buddypress\bp-templates\bp-legacy\buddypress\members\single\profile\profile-loop.php
buddypress\bp-templates\bp-legacy\buddypress\members\single\profile\edit.php

And check the fields via their id or name and then decide, based on who the logged-in user is, whether the fields should be displayed.

Sorry to answer you with a big laught, it’s not html but php. 😀
You should also find the time to read more attentively the forum, or search by keywords.
in this case: hide xprofile fields

https://buddypress.org/support/search/hide+xprofile+fields/

You’re welcome. Glad you got it. 😉

Hi @amic58, @tecca

When BP is installed and xProfile is activated, the original WP profile settings are not accessible to user.

The WP register process use only username, password and email and BuddyPress add by default a Name field as base for other extended profile fields.

In short this means that username and name fields can contain a same information(a name, a pseudonym, a first or/and a last name). The plugin you mention is best for a WP install where user had choosen first/last name as output on post, comments, etc Once BP is activated, this became a little different.

Now to the initial question.
The CSS trick is a very inelegant solution as it lets everybody knowing how BP works to surround this invisibility. You’re also loosing any flexibility if you want to show some fields privately for example.

You can do this properly with a little snippet, as explained here:

Using bp_parse_args() to filter BuddyPress template loops

Here’s an example which let you hide fields or fiels group to members, but not to site admin

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'] = '1';  
		//exlude groups, separated by comma
		$retval['exclude_groups'] = '1'; 			
	} 
	return $retval;		
	
	endif;
}
add_filter( 'bp_after_has_profile_parse_args', 'bpfr_hide_profile_field_group' );

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

Of course you can also choose to show a field or group, but remove the possibility for the user to edit it later. Simply add more conditionnal to the function.

Here another example:

function bpfr_hide_profile_edit( $retval ) {	
	// remove field from edit tab
	if(  bp_is_user_profile_edit() ) {		
		$retval['exclude_fields'] = '54'; // ID's separated by comma
	}	
	// allow field on register page
	if ( bp_is_register_page() ) {
		$retval['include_fields'] = '54'; // ID's separated by comma
		}		
	
	// hide the field on profile view tab
	if ( $data = bp_get_profile_field_data( 'field=54' ) ) : 
		$retval['exclude_fields'] = '54'; // ID's separated by comma	
	endif;	
	
	return $retval;	
}
add_filter( 'bp_after_has_profile_parse_args', 'bpfr_hide_profile_edit' );

Hope to be clear.

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

function bpfr_hide_profile_edit( $retval ) {	
	// remove field from edit tab
	if(  bp_is_profile_edit() ) {		
		$retval['exclude_fields'] = '2'; // field ID's separated by comma
	}	
	// allow field on register page
	if ( bp_is_register_page() ) {
		$retval['include_fields'] = '2'; // field ID's separated by comma
		}		
	
	// hide the field on profile view tab
	if ( $data = bp_get_profile_field_data( 'field=2' ) ) : 
		$retval['exclude_fields'] = '2'; // field ID's separated by comma	
	endif;	
	
	return $retval;	
}
add_filter( 'bp_after_has_profile_parse_args', 'bpfr_hide_profile_edit' );

The BuddyPress codex is your friend:

Filtering by Xprofile fields

Read this for a better approach to your issue: Filtering by Xprofile fields

Another approach: bp_user_query

Is there any way to make the icons following the privacy rules of the related profile fields?

Hi @danbp

I tried the way you suggested and it works.

I would like to ask if there is any way the social media icons to follow the privacy rules of the related custom profile fields.

Thank you!

hi franklinkevin321,

I have disabled all of my xprofile plugins

For our understanding, can you tell which plugins you’re speaking about ?
The snippet is intended for BP, so if you use another source to generate your profile fields, it maybe possible that it screws your template.