BuddyPress.org

@member11 – rather than enclosing your website URL in brackets (and making your users do the same) you’d be better off specifying the website URL field in the config file as @r-a-y suggests, so that it’s not linked to the search facility:

Open up the custom-profile-filters-for-buddypress.php file and in the $no_link_fields array (starting on line 14) add in your field, so mine looks like this:

$no_link_fields = array( // Enter the field ID of any field that you want to appear as plain, non-clickable text. Don’t forget to separate with commas.

‘Skype ID ‘ ,

‘Phone’ ,

‘IM’ ,

‘Web Site’

);

– where my web site field is called Web Site.

Also you may want to add in any social networking URLS that your site uses in the $social_networking_fields array that’s below this array. Same principle.

I use a plugin by Boone Gorges called Custom Profile Filters:

http://dev.commons.gc.cuny.edu/2009/06/21/updated-version-02-of-custom-profile-filters-for-buddypress/

Needs some manual configuration in the $social_networking_fields array, but you should be able to do what you need.

Give that a shot.

Is that a premium theme ?,I don’t have access to it,so my opinion may not be good enough.But I hope,you can achieve it using the following approach.

1.Do some css modification,that can help you to make it 2 column

if not then.

Look at the function

bp_get_the_profile_field_options in bp-xprofile-templatetags.php, Here resides the logic for what you are looking for.

But Note,editing this is not a good idea,so better try it using css.

Try the custom filters for BP plugin – https://wordpress.org/extend/plugins/custom-profile-filters-for-buddypress/

Allows you / your users to be more prescriptive about what BP ‘auto-links’. Don’t think it will completely stop BP auto-linking some things – though you could, if you wished, tell the plugin to exclude ALL fields from being auto-linked.

You / users can also use the square brackets ‘[ ]’ in profile fields to specify words or phrases they do want linking.

The plugin’s pretty handy for specifying fields like web site / twitter that shouldn’t be auto-linked.

I had a similar issue, and this is how i fixed it. Maybe it will help.

BTW, using WPMU 2.8.4a and BP 1.1.1.

bp-core-classes.php: around line 224:

$total_users_sql = apply_filters( ‘bp_core_users_by_letter_count_sql’, $wpdb->prepare( “SELECT DISTINCT count(u.ID) FROM ” . CUSTOM_USER_TABLE . ” u LEFT JOIN {$bp->profile->table_name_data} pd ON u.ID = pd.user_id LEFT JOIN {$bp->profile->table_name_fields} pf ON pd.field_id = pf.id WHERE u.spam = 0 AND u.deleted = 0 AND u.user_status = 0 AND pf.name = %s AND pd.value LIKE ‘$letter%%’ ORDER BY pd.value ASC”, BP_XPROFILE_FULLNAME_FIELD_NAME ), $letter );

$paged_users_sql = apply_filters( ‘bp_core_users_by_letter_sql’, $wpdb->prepare( “SELECT DISTINCT u.ID as user_id FROM ” . CUSTOM_USER_TABLE . ” u LEFT JOIN {$bp->profile->table_name_data} pd ON u.ID = pd.user_id LEFT JOIN {$bp->profile->table_name_fields} pf ON pd.field_id = pf.id WHERE u.spam = 0 AND u.deleted = 0 AND u.user_status = 0 AND pf.name = %s AND pd.value LIKE ‘$letter%%’ ORDER BY pd.value ASC{$pag_sql}”, BP_XPROFILE_FULLNAME_FIELD_NAME ), $letter, $pag_sql );

For me, it was the pf.name in the WHERE that was coming back with nothing. I understand the MYSQL, but not understanding the logic behind that. I changed it to what I was hoping to nail in the first place:

$total_users_sql = apply_filters( ‘bp_core_users_by_letter_count_sql’, $wpdb->prepare( “SELECT DISTINCT count(u.ID) FROM ” . CUSTOM_USER_TABLE . ” u LEFT JOIN {$bp->profile->table_name_data} pd ON u.ID = pd.user_id LEFT JOIN {$bp->profile->table_name_fields} pf ON pd.field_id = pf.id WHERE u.spam = 0 AND u.deleted = 0 AND u.user_status = 0 AND pf.name = ‘Last Name’ AND pd.value LIKE ‘$letter%%’ ORDER BY pd.value ASC”, BP_XPROFILE_FULLNAME_FIELD_NAME ), $letter );

$paged_users_sql = apply_filters( ‘bp_core_users_by_letter_sql’, $wpdb->prepare( “SELECT DISTINCT u.ID as user_id FROM ” . CUSTOM_USER_TABLE . ” u LEFT JOIN {$bp->profile->table_name_data} pd ON u.ID = pd.user_id LEFT JOIN {$bp->profile->table_name_fields} pf ON pd.field_id = pf.id WHERE u.spam = 0 AND u.deleted = 0 AND u.user_status = 0 AND pf.name = ‘Last Name’ AND pd.value LIKE ‘$letter%%’ ORDER BY pd.value ASC{$pag_sql}”, BP_XPROFILE_FULLNAME_FIELD_NAME ), $letter, $pag_sql );

Works fine for me. I’ve heard the latest edge version of BuddyPress fixes this somehow… but this worked at install for me so something must of changed. I have ALOT of custom profiles and the member import was a-typical so maybe in my case that had something to do with it.

I installed WPMU and buddypress and all work great but blogs subdomains dont work – blank page

My Apache error:

[Tue Nov 17 21:21:52 2009] [error] [client 83.16.234.122] WordPress database error Table ‘aa11935_pozy.wp_bp_xprofile_data’ doesn’t exist for query SELECT * FROM wp_bp_xprofile_data WHERE field_id = 1 AND user_id = 1 made by require_once, require_once, require_once, require_once, do_action, call_user_func_array, bp_core_setup_globals, bp_core_get_user_displayname, xprofile_get_field_data, BP_XProfile_ProfileData->get_value_byid, referer: http://trzebiatow.eu/wp-admin/plugins.php

[Tue Nov 17 21:21:52 2009] [error] [client 83.16.234.122] WordPress database error Table ‘aa11935_pozy.wp_bp_xprofile_fields’ doesn’t exist for query SELECT id FROM wp_bp_xprofile_fields WHERE id = 1 made by require_once, require_once, require_once, require_once, do_action, call_user_func_array, bp_core_setup_globals, bp_core_get_user_displayname, xprofile_set_field_data, BP_XProfile_ProfileData->save, BP_XProfile_ProfileData->is_valid_field, referer: http://trzebiatow.eu/wp-admin/plugins.php

[Tue Nov 17 21:21:52 2009] [error] [client 83.16.234.122] WordPress database error Table ‘aa11935_pozy.wp_bp_groups’ doesn’t exist for query SELECT id FROM wp_bp_groups WHERE slug = ‘plugins.php’ made by require_once, require_once, require_once, require_once, do_action, call_user_func_array, groups_setup_nav, BP_Groups_Group->group_exists, referer: http://trzebiatow.eu/wp-admin/plugins.php

can you help me? whats wrong… install was OK

hi Phillip

Yes yo can.

By default your registration page will show only the fields from first profile field group.

You can change it.

You will have to edit registration/register.php

Look for the code

and replace it with

Now your register page will show all the fields.

But stop,This is not enough,you need to aggregate all the field ids and put it as hidden field.

So Take a look at the the line

remove it from the profile loop.Now create some code inside the profile loop,aggregate all profile ids and then

put this code outside the profile group loop,

where I ssume you have aggregated all profile fields in the variable $all_pf_fields.

Please note,all $all_pf_fields should be the comma separated list of all profile ids(say 1,2,3,)

This will make it work,and your registration page will show all profile groups fields

Each field group has an ID value. You can modify the registration.php file to include additional groups by repeating the following and changing “1” to “2”:

<?php if ( function_exists( ‘bp_has_profile’ ) ) : if ( bp_has_profile( ‘profile_group_id=1’ ) ) : while ( bp_profile_groups() ) : bp_the_profile_group(); ?>

to

<?php if ( function_exists( ‘bp_has_profile’ ) ) : if ( bp_has_profile( ‘profile_group_id=2’ ) ) : while ( bp_profile_groups() ) : bp_the_profile_group(); ?>

i installed it… and it is the best example possible for the suggestion i made for a /bp-plugins/ directory… we can not actually install this plugin on the fly with the installer, we need to move files around. we also have to replace two files… that could be a problem if we have another product that need to overwrite these 2 files again. (adding actions into these files is needed though)

suggestion:

bp-profile-setup : when we setup some custom field, would be good to have a checkbox “is searchable”… so we can filter or search thru these fields only when possible. this could be good if we want to avoid some details to be trackable…

suggestion: popular keywords. similar to auto-tags based on post content, would be amazing for big sites to have the same for profile fields, so we have a cloud (or a dropdown) of popular profile field answers.

challenging i suppose.. lol

I believe the xprofile fields are the fields like “name”, so basically your users their account details.

I like the fact that you can order your users like this, A to Z is kinda… lame and outdated. I’ll definately try this out later. Thanks JJJ.

Edit: JJJ was 51 seconds faster then me.

I want to thank you for this, but I don’t even know what ‘xprofile fields’ refers to!

This is a free, open source project primarily powered by volunteers’ efforts. So don’t expect to get instant results.

As r-a-y has stated, there used to be several pre-built fields and site developers also had the option to create their own pre-built fields by importing their list via a .cvs file. But, as Andy states in this thread, that feature is no longer available:

https://buddypress.org/forums/topic/making-prebuilt-profile-fields

So, you either have to code a solution yourself or hire a developer to do it.

By the way, up until two-weeks ago, there was only one official BuddyPress developer. Now there are two. The rest of us are unpaid volunteers–some of us with coding experience, some of us with design experience, and some of us just interested in running social networking sites.

You can ask for additonal insights on the #buddypress-dev IRC channel. But even there, it is simply a group of developers with their own projects and responsibilities. Only Andy and jjj are the official voices of BuddyPress development.