BuddyPress.org

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?

@natetheaverage –

an outline solution (there are lots of areas where you’d have to work to implement it):

When a group is created, you could write a hook that creates a corresponding xprofile field group (remember to hook on delete group as well to remove the profile field group)
In the member’s profile screens, you would hide that xprofile field group if the member is not a member of the group
In a hook on Join Group, you’d want to display an additional screen that prompts for the user fields, and when that is submitted use the xprofile API to write the data to the user’s profile
I guess finally, you’d also want to modify the members loop inside the group to show that information

There’s a lot of code for you to trawl through

You’ll need to do something like wrap the custom xprofile loop section in a check for a specific field name ‘birthdate’ and do something like ‘if not’ ‘birthdate’ go ahead and display field item or display if is_admin if you want to be able to see users data as a site admin.

To remove a field you could do:
`

<tr>

`
in the profile loop; equally if you wanted to remove a complete field group you can copy the approach seen in the file for ensuring that the base group is not shown `if ( 1 != bp_get_the_profile_group_id() ) ` adding an OR followed by a check on the group id to hide.

Profiles are by default public, you can also extend them by creating your own custom xprofile fields, these and any profile fields can be further modified if wished to show or hide some based on whether the displayed user is also the logged in user.

Hey @davidveldt this should do it if you are using the default theme. Otherwise you should integrate as you see fit.

theme/registration/register.php

You can add any groups or fields as you require. The groups and fields here are arbitrary.

` ‘player’, 4 => ‘coach’, 5 =>’parent’, 6 => ‘instructor’); ?>

`

Create some profile groups to cater for each role. You can find the group id within the BuddyPress admin… In the url bar or investigate your database.

You should set-up the $roles array above to match your requirements.

Within the loop you can show any fields you have created within that xprofile group. If you have a select box within that group you would add the following code as outlined in the bp-default register.php

`

<label for="”>

<select name="” id=””>

`

Finally add the following jQuery where you house any other code of similar ilk.

`
jQuery(“.role-fields”).hide();
$roles = jQuery(“#roles”);
jQuery(“#field_2”).change(function()
{
$role = jQuery(this).val().toLowerCase();
jQuery(“.role-fields”).hide();
jQuery(“#” + $role).toggle();
});
`

Here’s a pastebin for all that above. http://pastebin.com/QFdTdstz

No need for tabs or accordion this time.

Hope that helps you on the Road.

Just an example here, running with Paul Gibbs start point.

Create xprofile fields as normal.

Each career group would also have its own xprofile group.

Player would have his / her own set of fields.
Coach would have his / her own set of fields.
Parent would have his / her own set of fields.
Instructor would have his / her own set of fields.

None of the above would be required fields. (as far as BuddyPress is concerned (unless you roll some PHP codes))

You’d have another xprofile group specifically for required fields (this would be your first group).

You would make the “type” part of the required group and set it as a select box.

You could then write your registration form mark-up matching the requirements of jQuery tabs or jQuery accordion.

The “type” would be the last item on the required fields. Once that was selected you could then show or hide the corresponding jQuery ui-tab-panel that holds those form fields.

You could then on-the-fly make those fields then required using some jQuery also but a bit hacky.

Just read you don’t want to edit home.php. There isn’t a filter for privacy like there is with messages for showing profile sections. Messages and xprofile fields has logic for output and can be filtered but the actual page needs a code edit.

Tested just now, works for me.
You need to use the profile id #.

Go to your profile field setup and check the ID by putting your mouse over the “Edit” field. The ID # is field_id.
For example, “Name” is 1.

Either that or go to your DB and manually look up the profile field id in the wp_bp_xprofile_fields table.

You can also use any profile template tag and do your conditional.

If you wanted to use the profile name, use bp_get_the_profile_field_name() instead.

@thelandman, in my solution I use javascript to generate the username from the weird semi-optional xprofile fullname field, hide the username field on the form, use the email login plugin so members don’t need the username to log in, add more custom code to synchronize the fullname and the fullname-derived username to all the various similar fields in the database, etc. It’s messy, but somewhat workable.

The point is that it should not be that hard. Using full names, Firstname Lastname, should be part of the core. Seeing that none of this is fixed in 1.2+ and probably will never be fixed, I have no plans to upgrade to newer versions of Buddypress and will continue developing my version as a fork, more suited for professional and business use. If anyone is interested in working with me on that, please contact me directly.

So it works? Tag the topic as resolved.

It becomes just string manipulation. Create a new function (my_funky_function) and do something like this:

function my_funky_function() {

echo str_replace( "username","", bp_get_the_profile_group_field_ids() );

}

Then replace the bp_the_profile_group_field_ids() call in edit.php (in your child theme of course) with my_funky_function().

I think that will work but it’s not tested.

Edit:

Oh, sorry, I’m sort of wrong. This is what I get in my edit.php form in the HTML:

<input type="hidden" name="field_ids" id="field_ids" value="1,3" />

Field_id 1 is the Username for me. You just need to filter that out so the str_replace call should be “1,” instead of “username”.

<input type="hidden" name="field_ids" id="field_ids" value="<?php bp_the_profile_group_field_ids() ?>" />

That line is your problem. Well, more specifically, the call to bp_the_profile_group_field_ids() which creates a list of the expected field names.

Unfortunately it doesn’t have a filter so you’d have to clone and own the function into your functions.php file and manually filter out the “username” field from the string that gets generated.

Make sense?

Oh, nope, it probably means that the code is actually checking that the field ‘username’ should be getting updated. I was sort of wondering if that would happen.