BuddyPress.org

the only fields which show on the register page are the ones that belong to the “base” (unless you have renamed it) profile field group.

the non optional fields cannot be split you might be able to rename them however. you will find the option to add/define fields is under admin (network admin for multisite) > users > profile fields

@jcollier Tested your site registration in IE 10 and getting the same issue. Made a Responsive child theme in my test install, used default page template for register and had no issues registering/activating new account.

Could be the custom template used for register page – noticed that there’s “Posted in” text just before footer in your register page. Change register page template back to default page template, clear cache, check if issue is resolved. if that doesn’t work, deactivate plugins batch by batch to check which is causing the timeout.

Always perform a quick search first, sort of topic that has come up a few times.

https://buddypress.org/support/search/?bbp_search=profile+fields

keep scrolling down through them, you’ll find example code to work from.

No they wouldn’t as you are working in a child theme.. aren’t you! if not you should be.

I’m not sure but scanning your post possibly suggests smething amiss in your understanding of BP, as modemlooper points out hiding fields is easy and along with the privacy controls on BP profile fields you can ensure that they are set to both required and only editable by admins so not sure why you need your custom form, but may have overlooked the reason.

If you guys mean the the sites from the navigation, then you can use the following code in either your theme’s functions.php or bp-custom.php

function bpdev_remove_blogs_nav(){
    global $bp;

    bp_core_remove_nav_item($bp->blogs->id);//

}
add_action('wp_loaded','bpdev_remove_blogs_nav');

Hope that helps.

Leofitz, WangGuard will check your user base for spammers and delete them.

See https://wordpress.org/plugins/wangguard/

The author says that “WangGuard not only protect your site from sploggers, spam users or unwanted users, WangGuard cleans your database from them. No plugin or service does this, only with WangGuard you will get this feature,” and I believe him. His English may not be too good, but the plugin is really outstanding.

There’s just one consideration for you: In order to have your database cleaned up, you will have to submit far more than 500 queries the first month. Perhaps you can arrange to pay for a month?

Here’s my suggestion to reduce database queries after that. (It worked for me.) Buddypress allows for the customization of User Profiles. Add a couple of questions that require a certain amount of intelligence to answer and make them required. That means the form will not be submitted either to WordPress or to WangGuard if the required fields are not filled out. It’s not fool-proof, but it decreased queries on my very busy site to just a few a day.

Incidentally, I added a question, “How do you plan to participate?” Among the choices offered the user are these:
“I want to increase my online presence.” and
“I want to sell my stuff.”

We don’t need anyone not bright enough to figure out that these replies do not make the user desirable. Now all I need is a script to automatically kick out users who choose these replies. 😉 (As it is, they can be manually deleted if other users report them.)

I don’t know what happens to a group when all the users are unsubscribed, so this may not be precisely what you are looking for. But WangGuard will make your site secure against almost all sploggers. (One registrant passed all tests on our site, and we had to delete manually, but that person must have registered manually too.)

Good luck!

Inge (http://ssnet.org)

Good one man… Post here if you come with the solution.

You can hide fields from being edited easy. in members/single/edit.php you can exclude fields by ID. Use comma separated list.

if ( bp_has_profile( 'profile_group_id=' . bp_get_current_profile_group_id() . '&exclude_fields=2,3,4' ) ) :

full code example https://gist.github.com/modemlooper/5816548

BuddyPress profile fields are searchable.

any one here to help me
installed and activated plugin and in widget area it is asking to put Birthday field Name (or ID)

from where i can get this ?

and as said in plugin page Birthday field must have been previously created in the Buddypress profile page so i opened USERS >Profile Fields >Add New Field

here i user date selector to create it and after that in registration page user have to put their date of birth .but from where i can get Birthday field Name (or ID) please help .Thankyou

@4ella one bump is sufficient!

@henrywright-1I think this is going to have attendant issues difficult to deal with. Gravity forms allows for forms with repeater fields and you can then tie submissions into existing functionality but profile fields are going to be hard to deal with, if they aren’t created. The repeater fields are created via JS on submission you have to tie it in to creating new profile field label etc then if you can do that you create those extra for all users.

What may be a better approach is to add in advance all the fields you may need then on front end hide them with JS and allow user to show them as and when needed, public profile would be set to ignore any empty fields & labels.

nice idea, bump

Check the value of the “bp-xprofile-fullname-field-name” entry in the WordPress “wp_options”-table.

SELECT * FROM wp_options WHERE option_name LIKE 'bp-xprofile-fullname-field-name'

Its value should match the name of the profile field containing the Member-Name. Usually the same as whats returned by

SELECT name FROM wp_bp_xprofile_fields WHERE id = 1

If the value in bp-xprofile-fullname-field-name is invalid (for example: in my case it contained “Name” but I renamed the first profile field to “Lastname, Firstname”), BuddyPress goes bonkers and tries to execute an invalid SQL-query resulting in an empty memberlist.

The main problem is the code located in “plugins\buddypress\bp-core\bp-core-classes.php” around line 260:

				} else {
					$fullname_field_id = $wpdb->get_var( $wpdb->prepare( "SELECT id FROM {$bp->profile->table_name_fields} WHERE name = %s", bp_xprofile_fullname_field_name() ) );

					$this->uid_name = 'user_id';
					$sql['select']  = "SELECT DISTINCT u.{$this->uid_name} as id FROM {$bp->profile->table_name_data} u";
					$sql['where'][] = "u.field_id = {$fullname_field_id}";
					$sql['orderby'] = "ORDER BY u.value";
					$sql['order']   = "ASC";
				}

$fullname_field_id is empty if the value in bp-xprofile-fullname-field-name points to an non-existing fieldname.

Hope this helps others with the same problem.

@reacton What kind of modifications did you make on your BP Default child theme? Note that if made changes in the HTML markup in the template files of the BP-specific pages, you might also have to copy over and revise the JS files of BP Default theme.

You maybe right, and i’m unsure too. The best way to know, is to give a try. But do you absolutely need to ask twice for the user email ?
Or you could simply name the email fields differently.
Private mail
Work mail