@onyx808
That’s a basic feature of profile fields. Go to “Profile Field Setup” in your backend and you’ll see this:
“NOTE: Any fields in the first group will appear on the signup page.”
Simply click the “Add New Field Group” button and create the fields you want in that new group. They will not appear on the signup page, but will be available on the user’s Profile page.
Be careful with the “Required” setting though. If you set fields in new groups to “Required”, your users will be trapped on their profile page the first time they visit until they fill in all required fields.
Thank you for responding. I will check that. Unfortunately, a much larger error has cropped up that bumped this style issue back.
I will let you know how the test goes. (mostly I appreciate you letting me know I was in the right file. It was driving me nuts!)
Hi.
Thanks for the code Brajesh! I just had one question. I’ve defined different profile field groups for different user types. I want to restrict the visibility of these filed groups to only those users (e.g. users of type A get to see only those profile fields for user type A). My problem is that when I use your code
<?php global $bp;
if(bp_get_current_profile_group_id()==1)
bp_core_redirect($bp->displayed_user->domain.”profile/edit/group/2″);
?>
it shows the same profile fields for all user types. I guessed it was because 1 is the base profile group ID and tried changing the if loop to
if(bp_get_current_profile_group_id()==ID number of group)
bp_core_redirect($bp->displayed_user->domain.”profile/edit/group/ID number of group”);
but now it shows me only the ‘Editing base profile’ screen
Is this code correct?
Cheers
You are in the right file, so if you are not seeing your changes, then the file is not being overwritten.
Try something simple to see if your edited file is being loaded.
Change this:
`
`
To:
`
HELLO HELLO HELLO HELLO HELLO HELLO
`
Argh – much faster, coding and parsing-wise, to do this in members_single_profile/edit.php
as opposed to doing an add_filter on ‘bp_get_the_profile_field_options_select
Error caused by checking for ‘acceptable value’ before save.
See
/* Check the value is an acceptable value */
around Line 735 in bp-xprofile.php
I removed ‘selectbox’ from the ‘if’ and profile save now works.
you can delete those groups in your profile field setup panel 
what are you trying to achieve?Are you trying to display those based on user roles?
bp_get_the_profile_group_id() is returning only one ID you have to create an function that returns an array of id’s and then you need to loop over those and exclude 7 and 6.
you can try this
profile loop
`
<?php
if ( bp_profile_group_has_fields() && 6 != bp_get_the_profile_group_id() && 7 != bp_get_the_profile_group_id() ) :
?>
<div class="bp-widget “>
`
Not sure. I just downloaded and it worked. I did notice when I was in a member profile and looked at my public profile tab the fields showed up. When not logged in or logged in as another user, the fields were not visible. I am also using Role Manager plugin, not sure if that makes any difference.
@graq Yes into bp_xprofile_fields.
@ultimateuser Do you mean write values directly into bp_xprofile_fields ?
I wrote some dirty SQL to do just that.
` $insertsql = $wpdb->prepare(“INSERT INTO {$tablename} (group_id, parent_id, type, name, description, is_required, order_by, field_order, is_default_option, option_order ) VALUES (%d, %d, %s, %s, %s, %d, %s, %d, %d, %d )”, $group_id, $parent_id, $type, $region, ”, 0, ”, 0, 0, $option_order );`
To be honest, I was hoping there would be a better way.
@Mikey3D another thank you from me
It’s not entirely clear how you would integrate this into BuddyPress itself, since every installation will have different “links” between profile fields. What kind of interface would be used to allow site admins to dictate such dependencies? If anyone is interested in providing a patch, or building a plugin, it might be worth looking at something like Drupal to see if they’ve implemented similarly dependent metadata fields, and how they’ve done it.
Hmm I see, what you mean by to be done on the frontend is by editing the source code right?
I think this feature have been requested by others also and I think this is pretty basic functionality.
Hope this feature will be integrate to buddypress in the near future.
This will most likely have to be done on the frontend with javascript.
Brush up on your jQuery! Look up “jquery conditional form fields” on Google.
@Mikey3D Thank you very much!
have you considered moving some xprofile fields to the top of the middle column above the tabs? This area would make a lot of sense for some of the profile info maybe some of the ones you are having trouble with space.
@pcwriter,
Thanks for that. white-space:normal; helps with my x-axis fields and it works perfectly.
Now, however, I am trying to limit the height of my “about me” field. I’m using max-height:400px; but white-space causes the browsers to ignore the limit. What I really want is: white-space:normal; max-height: 400px; overflow-y:auto; but firefox is the only one that shows it properly. The others all revert to scroll bars, even safari.
Ugh.
I have the same question as well. I have created a couple more field groups in Buddypress profile fields section on the dash. Alas, none but the base group shows up in registration. Any help on how to get around this would be fantastic!
Did this ever get off the ground?
*puzzled* I contributed to some and have used various approaches of my own all post dating 1.1 or the transition to the 1.2 stream, but yes guess some are a little complicated but then BP isn’t that simple a thing to code for requiring as it does a little more than basic knowledge.
hnl: Yep.. I did that.. but they where all old and did not use the BP 1.2 method of displaying the profile fields and seemed to add a a lot of extra unneeded parameters to the snippet. Hopefully it’ll be easier for php noobs to find and implement now
A search of the forum would have thrown up a few posts on this subject that have this and alternative examples.
