Thank you Sam.
I am glad it worked.

I sincerely appreciate you upgrading to our Membership.

I will push another update tomorrow with the option to have the tab visible to admin/super admins.

Regards
Brajesh

Hi Sam,
Thank you for the patience. I have released 1.1.6 which fixes it. Your last post helped greatly to find and resolve the issue.

Thank you
Brajesh

Hi,

Please put this code in your bp-custom.php (or theme’s functions.php)
It will hide the I Research field on Registration/Edit profile and update its value from the “I am” field.

I have used the field id from your site.

/**
 * Update value of the dest field when source is updated.
 *
 * @param BP_XProfile_ProfileData $object data object.
 */
function buddydev_sync_to_field_data_to_other_field_on_update( $object ) {
	// Field id, whose value we use to determine the calculated value for the synchronized field.
	$sync_source_field_id      = 3; // field when change, triggers change to the sync field.
	// this is the field whose value will be updated based on the calculation.
	$sync_dest_field_id = 6;// field we will update.

	// If it is not the source field id, don't do anything.
	if ( $object->field_id != $sync_source_field_id ) {
		return;
	}

	$value       = $object->value;
	$value       = maybe_unserialize( $value );
	$other_value = '';

	if ( empty( $value ) ) {
		// delete.
		xprofile_delete_field_data( $sync_dest_field_id, $object->user_id );

		return;
	}
	// Determine, what value we should set.
	// This is the block that we use to calculate
	// you will need to update for your use case.
	if ( 'Un Homme' == $value ) {
		$other_value = 'Une Femme';
	} else {
		$other_value = 'Un Homme';
	}
	// If the sync_destination field is select/radio, make sure the calculated value is what you have
	// added as option the the field add/edit screen. Should match exactly.
	// set teh value.
	xprofile_set_field_data( $sync_dest_field_id, $object->user_id, $other_value );
}
// On update.
add_action( 'xprofile_data_after_save', 'buddydev_sync_to_field_data_to_other_field_on_update' );

// On delete.
function buddydev_sync_to_field_data_to_other_field_on_delete( $object ) {
// Field id, whose value we use to determine the calculated value for the synchronized field.
	$sync_source_field_id      = 3; // field when change, triggers change to the sync field.
	// this is the field whose value will be updated based on the calculation.
	$sync_dest_field_id = 6;// field we will update.

	// If it is not the source field id, don't do anything.
	if ( $object->field_id != $sync_source_field_id ) {
		return;
	}

	xprofile_delete_field_data( $sync_dest_field_id, $object->user_id );
}
add_action( 'xprofile_data_after_delete', 'buddydev_sync_to_field_data_to_other_field_on_delete' );

/**
 * Hide the synchronized field from Registration/Edit profile fields. Its value is set programatically.
 * @param $args
 *
 * @return mixed
 */
function buddydev_exclude_sync_profile_field_in_edit_context( $args ) {

	if ( ! bp_is_user_profile_edit() && ! bp_is_register_page() ) {
		return $args;
	}

	$sync_to_field    = 6;
	$exclude_fields   = isset( $args['exclude_fields'] ) ? explode( ',', $args['exclude_fields'] ) : array();
	$exclude_fields[] = $sync_to_field;

	$args['exclude_fields'] = join( ',', $exclude_fields );

	return $args;
}

add_filter( 'bp_after_has_profile_parse_args', 'buddydev_exclude_sync_profile_field_in_edit_context' );

Regards
Brajesh

Hi Max,

Thank you for clarifying.

We haven’t tested it. We can certainly test and make compatible with our activity autoloader plugin in future.

Thank you
Brajesh