BuddyPress.org

would this also work in members-loop?
i was to display a specific summary, including a link to the member’s own website (which is theoretically in a profile field if they fill it in) on the main member’s listing page.

not quite having success with the conditional display.

using

<?php if ( $data = bp_get_profile_field_data( 'field=Website' ) ) : ?>
         	<span class="activity"><a href="<?php echo $data ?>" target="_blank">Website</a></span>
<?php endif ?>

and it won’t display anything, even if there is data in the Website field…
but if i remove the if statement and just use
<span class="activity"><a href="<?php bp_member_profile_data( 'field=Website' ); ?>" target="_blank">Website</a></span>
i get a nice linked “Website” – except that EVERY one is linked, even if there isn’t an actual URL in the field. Empty profile fields just link it back to the member listing page.

any suggestions?

I think xprofile_data_value_before_save is the hook you want to use. So, if you add this to functions.php your xprofile fields will accept HTML:

remove_filter( 'xprofile_data_value_before_save', 'xprofile_sanitize_data_value_before_save', 1, 2 );

Note: Use this with caution. Not sanitizing incoming data is dangerous so you will need to add your own custom sanitization if you use this.

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?

What I did is I changed the form + validation stuff inside the template files to customize my own forms and validation process.

First of all I didn’t like the default validation process that BuddyPress is using where you have to push Submit and then the script checkes if every field is filled correctly, if not it pushes a text_message into the page through an Action.
Result, often the error message shows up at the top of the page where you aren’t looking and not at the form where the problem occurs, and even more important it’s an extra page-load to get this message into the page.

I didn’t like that so I left everything of that untouched as a back-up system and simply used my own ( Zurb’s ) validation JavaScript to check while writing if the fields are correct.
Plus this JavaScript disables the Submit buttons if a form or field is not valid.

This is a screenshot of the Profile Settings page but all forms work the same so you can just diff into the template files and add alter them.

The script I use is part of Zurb’s Foundation Framework so if you don’t like to work with Frameworks like me you have to strip all the needed code out of it.
http://foundation.zurb.com/docs/components/abide.html

There are probably also scripts like this one to be found online.

Doesn’t sound like you need to edit xprofile fields from within the Dashboard,
but this premium plugin allows you to view, edit and save xprofile field values from a User > Edit screen in the Dashboard:
http://www.philopress.com/products/bp-dashboard-user-profile-edit/

Nice. It would also be interesting to provide this on all timestamps.

One issue ‘tho – in this:
http://docs.taptappress.com/buddypress-add-time-zone-list-profile-field/

I think you’re inserting / updating all those xprofile fields on every page load.
Why not just do it once?

You could write a plugin that uses ‘register_activation_hook’ to run bp_add_custom_timezone_list() once.

And then use the filter hook in:
bp_get_message_thread_last_post_date()
to adjust the timestamp without requiring a template change.

And you could use other hooks to adjust other timestamp displays.

That would be a popular and very handy plugin.

@macpresss

Take a look at this page to see the parameters accepted:

Profile Fields Loop

Perhaps try using profile_group_id:

By default all groups and all fields will be displayed. If you provide the ID of a profile field group, then only the fields in this group will be displayed

So it would be:

if ( bp_has_profile( 'profile_group_id=2' ) ) :

Where 2 is the ID(s) of the group you’d like to include. I think it should take a comma separated list but I haven’t tested.

this is great help… but how do we do this with the s2member fields when we have s2member set to integrate with buddypress profiles???

You could try looking at https://wordpress.org/plugins/buddypress-xprofile-custom-fields-type/ to see how they do it. I think one of the profile field types is ‘number’ – so that might be the best place to start.

This code is just a start, I did not test to see if field groups will break it but you can get an example of spitting out fields as an object array variable on profile load and then using the variable to get the values instead of requesting each time.

put this in bp-custom.php

// creates global object array from profile fields
function bp_profile_fields_array() {
	global $fields;

	$fields = array();

	if ( bp_has_profile() ) :

		while ( bp_profile_groups() ) : bp_the_profile_group();

			if ( bp_profile_group_has_fields() ) :

				while ( bp_profile_fields() ) : bp_the_profile_field();

					if ( bp_field_has_data() ) :

							$field_name = bp_get_the_profile_field_name();
							$field_value = bp_get_the_profile_field_value();

							$field = array(
								'field_name' => $field_name,
								'field_value' => $field_value,
							);

							$fields[] =	$field;

					endif;

				endwhile;

			endif;

		endwhile;

	endif;

	return $fields;

}
add_action( 'bp_before_member_header', 'bp_profile_fields_array' );

// echoes value of field from object array based on param
function bp_get_single_profile_field( $param ) {
	global $fields;

	foreach ( $fields as $key => $val ) {
	   if ( $val['field_name'] === $param ) {
		   echo $val['field_value'];
	   }
	}
}

Then in your member templates:

<?php bp_get_single_profile_field('PROFILE FIELD NAME'); ?>

Hi @macpresss

What do you mean by ‘export all profile fields by a conditional tag’?

Doing what you’ve done above is good practice because if Country is an optional field and it has not been completed by the member then nothing will be outputted:

<?php if ( $data = bp_get_profile_field_data( 'field=Country ' ) ) : ?>
     <!-- do something -->
<?php endif ?>

If you’re doing something with a single profile field then there is no need to loop through them all. It’s basically wasted effort and slower performance.

hi @matt-mcfarland,

i’m not a dev but consider this, to get a user ID:

$user_id = bp_get_member_user_id();

To answer the sql question, here’s a function that doesn’t exist in buddypress, which let you get the xprofile_group name by it’s ID For inspiration…

function bpfr_get_xprofile_group_id_by_name( $name = '' ) {
	global $wpdb;
	
	$bp = buddypress();
	
	if( empty( $name ) )
		return false;
		
	return $wpdb->get_var( $wpdb->prepare( "SELECT id FROM {$bp->profile->table_name_groups} WHERE name = %s", $name ) );
}

For the output, you have to create another function containing at least:

	$user_id = bp_get_member_user_id();
	$xprofile_group_id = bpfr_get_xprofile_group_id_by_name( 'the groupe name' );

if( !class_exists( 'BP_XProfile_Group' ) )
		return false;
		
	$args = array(
		'profile_group_id'       => $xprofile_group_id,
		'user_id'                => $user_id,
		'fetch_fields'           => true,
		'fetch_field_data'       => true
	);

May this help you !

Hi @noizeburger, glad you finally got this working. I’m sure your tutorial will be helpful to many people too. I especially like the last snippet which shows you how to disable the editing of certain fields on the edit profile screen!

Still no easy solution to this one? It’s odd that BP has been around for so long and more people aren’t having an issue with the extra profile fields not being sent upon registration.

Could for instance add dropdown boxes with categories to users extended profile pages.
Get the value of those profile fields from your home template and use it in a query.

>Wow, so basically in order for members to have access to edit all of the fields that they entered while signing up, we have to pay for a custom plugin to get access to those fields?

Let me repeat:
They are accessed on the front-end on a member’s profile page.
your-site.com/members/peteratomic/profile/

If it’s your profile or you are an admin, you will clearly see an ‘Edit’ button.

>Utterly mind-boggling why this functionality isn’t built in to BP.
It is built into BP.