BuddyPress.org

One option is to do as @embergermedia stated. To catch everyone, you could hook in a profile edit action and check to see if all the fields you require have been completed. If they have, then you could add something in their usermeta saying they’ve completed everything. Then you could hook into bp_init, check that usermeta field, and if you don’t get the correct response, then you can redirect them to their profile, or display an error telling them they need to complete their profile. However, as both @embergermedia and @brooker said, it wouldn’t be the most user friendly way to go.

It’s still the same answer. There is a way, but it would take code. You would need to use hooks from the AD Intergration plugin and hooks/functions from BP to handle this. The reason I said talk to the plugin author is because you might be able to request the the plugin author adds this as a feature.

That would be something to ask the authors of the AD Integration plugin, but I would suspect that you would need to use a plugin provided hook, and the write you’re own custom function to do this.

Hi,

Under profile field group i have name permanently in there. Is there a way that I can remove that field?

thank you.

This would be a great plugin. Anyone created it? Especially useful for getting people to enter location details for mapping.

Seems there may have been a country list in version 1.0 : https://svn.buddypress.org/branches/1.0/bp-xprofile/prebuilt-fields/

In early BP versions, there used to be a few handy pre-populated profile fields – including a country list (I think).

Would be nice to have them back. As @djpaul suggests, some SQL and a bit of plugin coding should do the trick…. Paul: is there a nice schematic of the xprofile tables available?

I found a much easier solution for this….

Line 59 of the register.php file contains this code when it’s forming the query to get all the signup fields…
“

The ‘profile_group_id=1’ restricts the query to only the base fields. Delete that argument and it should display all the fields. The code looks like:
“

I am having the same problem, but are you sure this isn’t a bug in the plugin? It shouldn’t need 33MB of RAM just to activate the plugin. I got the same error trying to activate Buddypress 1.2.8 on a fresh install of WordPress 3.1.1 on a high-quality host. There are a huge number of warnings that come before the memory error. Here’s the full output with debug on (I cut out another ~50 warnings on call-time pass-by-reference).

`Warning: Call-time pass-by-reference has been deprecated; If you would like to pass it by reference, modify the declaration of apply_filters(). If you would like to enable call-time pass-by-reference, you can set allow_call_time_pass_reference to true in your INI file in /sites/www.mysite.org/web/content/wp-content/plugins/buddypress/bp-core.php on line 565

Warning: Call-time pass-by-reference has been deprecated in /sites/www.mysite.org/web/content/wp-content/plugins/buddypress/bp-core/bp-core-classes.php on line 228

[many more errors on call-time pass-by-reference…]

Warning: Call-time pass-by-reference has been deprecated; If you would like to pass it by reference, modify the declaration of apply_filters(). If you would like to enable call-time pass-by-reference, you can set allow_call_time_pass_reference to true in your INI file in /sites/www.mysite.org/web/content/wp-content/plugins/buddypress/bp-friends.php on line 433

Notice: Undefined offset: 0 in /sites/www.mysite.org/web/content/wp-content/plugins/buddypress/bp-core/bp-core-catchuri.php on line 85

Notice: is_page was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. (This message was added in version 3.1.) in /sites/www.mysite.org/web/content/wp-includes/functions.php on line 3422

Notice: Undefined offset: 2 in /sites/www.mysite.org/web/content/wp-content/plugins/buddypress/bp-core/bp-core-catchuri.php on line 158

Notice: Undefined property: stdClass::$loggedin_user in /sites/www.mysite.org/web/content/wp-content/plugins/buddypress/bp-forums.php on line 530

Notice: Trying to get property of non-object in /sites/www.mysite.org/web/content/wp-content/plugins/buddypress/bp-forums.php on line 530

Notice: Undefined property: stdClass::$displayed_user in /sites/www.mysite.org/web/content/wp-content/plugins/buddypress/bp-core.php on line 1070

Notice: Trying to get property of non-object in /sites/www.mysite.org/web/content/wp-content/plugins/buddypress/bp-core.php on line 1070

Notice: Undefined index: user-avatar-default in /sites/www.mysite.org/web/content/wp-content/plugins/buddypress/bp-core.php on line 160

Notice: Undefined property: stdClass::$profile in /sites/www.mysite.org/web/content/wp-content/plugins/buddypress/bp-xprofile/bp-xprofile-classes.php on line 816

Notice: Undefined index: bp-xprofile-base-group-name in /sites/www.mysite.org/web/content/wp-content/plugins/buddypress/bp-xprofile.php on line 101

Notice: Undefined index: bp-xprofile-fullname-field-name in /sites/www.mysite.org/web/content/wp-content/plugins/buddypress/bp-xprofile.php on line 102
WordPress database error: [Table ‘z_mysitewp.wp_bp_xprofile_data’ doesn’t exist]
SELECT value FROM wp_bp_xprofile_data WHERE field_id = 1 AND user_id = 1

WordPress database error: [Table ‘z_mysitewp.wp_bp_xprofile_fields’ doesn’t exist]
SELECT * FROM wp_bp_xprofile_fields WHERE id = 1

WordPress database error: [Table ‘z_mysitewp.wp_bp_xprofile_fields’ doesn’t exist]
SELECT id FROM wp_bp_xprofile_fields WHERE id = 1

Notice: Undefined index: bb-config-location in /sites/www.mysite.org/web/content/wp-content/plugins/buddypress/bp-forums.php on line 23

Notice: Undefined index: bp-xprofile-base-group-name in /sites/www.mysite.org/web/content/wp-content/plugins/buddypress/bp-xprofile.php on line 101

Notice: Constant BP_XPROFILE_BASE_GROUP_NAME already defined in /sites/www.mysite.org/web/content/wp-content/plugins/buddypress/bp-xprofile.php on line 101

Notice: Undefined index: bp-xprofile-fullname-field-name in /sites/www.mysite.org/web/content/wp-content/plugins/buddypress/bp-xprofile.php on line 102

Notice: Constant BP_XPROFILE_FULLNAME_FIELD_NAME already defined in /sites/www.mysite.org/web/content/wp-content/plugins/buddypress/bp-xprofile.php on line 102

Notice: Undefined index: fileupload_maxk in /sites/www.mysite.org/web/content/wp-content/plugins/buddypress/bp-core/bp-core-avatars.php on line 35
WordPress database error: [Table ‘z_mysitewp.wp_bp_groups_members’ doesn’t exist]
SELECT COUNT(DISTINCT m.group_id) FROM wp_bp_groups_members m, wp_bp_groups g WHERE m.group_id = g.id AND m.user_id = 1 AND m.is_confirmed = 1 AND m.is_banned = 0

Notice: Undefined property: stdClass::$current_group in /sites/www.mysite.org/web/content/wp-content/plugins/buddypress/bp-groups.php on line 223

Notice: Trying to get property of non-object in /sites/www.mysite.org/web/content/wp-content/plugins/buddypress/bp-groups.php on line 223
WordPress database error: [Table ‘z_mysitewp.wp_bp_messages_recipients’ doesn’t exist]
SELECT unread_count FROM wp_bp_messages_recipients WHERE user_id = 1 AND is_deleted = 0 AND sender_only = 0

Notice: Undefined variable: count_indicator in /sites/www.mysite.org/web/content/wp-content/plugins/buddypress/bp-messages.php on line 115

Notice: Undefined index: action in /sites/www.mysite.org/web/content/wp-content/plugins/buddypress/bp-core/bp-core-signup.php on line 571

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 122880 bytes) in /sites/www.mysite.org/web/content/wp-admin/includes/media.php on line 1963`

@onyx808

Oops… my comment about “Required” fields is a bit (a lot?) misleading

Users will not be able to save their profile settings until all required fields are filled out… that’s what I meant by “trapped”

@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.

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
`

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.