BuddyPress.org

Re: 2. Importing s2member custom fields to buddypress fields
Instead of, for now, editing the codex page, please note the args parameter for add_action.

So the ‘2’ here is the arguments parameter. add_action('wp_login','s2_profile_field_update',10,2);
So the hook provides 2 arguments – very handy & useful.
But your example doesn’t use them in the function s2_profile_field_update.
You can use the $user arg instead of $current_user and thereby get rid of that global.
Use this to see the data in $user:

function hook_arg_display( $user_login, $user ) { 
   var_dump( $user ); 
}
add_action('wp_login','hook_arg_display',10,2);

imo: There is no Option 1.

@myg0t Thanks for sharing that with the community, S2 Member has wide use so this ought to be useful to people.

One point though it’s best not to advise that people edit a core file /buddypress/bp-templates/bp-legacy/..etc BP has a fairly well defined template hierarchy overload allowing files to be copied to the theme or child theme, those are the copies one should edit.

Another minor point rather than have to edit & pass the arguments in the template could bp_parse_args() perhaps work for this?
Using bp_parse_args() to filter BuddyPress template loops

In respect of the profile data would not setting the user visibility options on the profile field/s in the backend not work to provide the privacy for address fields, just a thought but I may have missed the point of this aspect.

Lastly this could make a nice user example guide for the BP codex if you’d care to post it there and we’ll slot it under a section appropriate.

Hey @qmai! I have setup a system before to link BuddyPress Profile Fields to SalesForce, but it takes a good amount of custom work. The method I ended up doing was to add a piece of custom meta to the Profile Field edit screen that allows you to specify a SF field id. Unfortunately, the process of adding custom meta to a BuddyPress Profile Field is a lot harder than it sounds, but it is doable.

Let me know if you have any further questions. I can’t seem to find the code that I wrote for this, but I’d be happy to work through this with you.

I believe it only runs when a profile is updated.
Try doing a ‘save’ on a BP profile – edit screen.

If it works, at least you know the sync is working going forward.

That doesn’t address your real issue re all your existing users.
You’ll probably need to write some code that loops thru your users and creates xprofile fields for them.

Take a look at function xprofile_set_field_data in
bp-xprofile/bp-xprofile-functions.php

Hi @navinachettri

1. Have you searched the plugin directory?
2. This can be done via hooks. It will need some custom code (not much, just a few lines).
3. You could hide or show xProfile fields according to role. How exactly roles are created and managed will be dependent on point 1
4. Again, to distinguish business users from ‘normal’ users, you’d use the roles created via the plugin you’re using from point 1. The jobs and adverts could each have their own custom post type
5. This will need to be custom coded

Hope that helps?

hi @kristinrutten,

have you imported users from an older wp site ?
Are you hosted on wpengine ? (toc toc @hnla ? )

Try to use the repair tool: dashboard > tools

What about avatar settings ? dashboard > general > discussion

About plugins
buddypress toolbar was intended for 1.5/1.6/1.7 – outdated now.
BuddyPress Members Import did you use it more as 1 time ?
On a default install, WP and BP users are in the same table: wp_users
In BP settings you can sync WP and BP users. Extended profile fields are stored in 4 other tables: _xprofile_somename
And WP has is own import tools…
IMO you can deactivate them.

Deactivate all plugins, but BP and activate 2013 theme. At this stage the avatars should appear.

1) https://codex.buddypress.org/getting-started/configure-components/

2) https://codex.buddypress.org/buddypress-components-and-features/extended-profiles/edit-xprofiles-admin-screen/

https://codex.buddypress.org/getting-started/guides/displaying-extended-profile-fields-on-member-profiles/

3) is built in on members directory. Each profile item becames clickable by default, letting users find others having entered the same information.
Example:
User A = City -> New York (NY is clickable)
User B = City -> New York (NY is clickable)
User C = City -> San Francisco (SF is clickable)

When user B click on NY he will see user A as search result
When user C click on SF he will only see himself

4) He use the buddy menu. This menu can be installed by going to dashboard > apparence > menu. If BP menu is not in the left side, under the other menus, open the screen option (top right corner) and check BuddyPress. Now you can set your BP menu like any other WordPress menu.
https://codex.wordpress.org/WordPress_Menu_User_Guide

When you’re new to something, you must read the documentation first. Also before asking on a help forum, you must search if your question wasn’t already asked and answered.

Happy install ! 😉

hi @roddaut,

don’t thought to much, a theme can influence over all a site, including the admin. This happens in 90% of the issues handled on this forum.

Thought the latest Canvas was 2014.10.14 – version 5.8.5

Members are the heart of BuddyPress. When a user register on a BP activated site, this user is automatically a “member”.

So i guess “they are not registering for the site, just the members area” is just impossible. Don’t know what you already did to get a “private” member area, but if you have an issue, it’s mostly because you did something wrong. 😉

To confirm to readers what you already get to work:

To modify the registration page, on which appears the login fields belonging to WP (user, username, email & password), BP adds his own additionnal fields, under condition you activated the xProfile component.

By default, BP add only one field in the mandatory field group “Base”: NAME.

When the admin add a new field, he can choose between different field status, and depending this status, you will see phrase such as “This field can be seen by: “.

These settings are avaible in Dashboard > Users > Profile Fields

hi @tac28,

as you’re a first timer, i would suggest that you read attentively the Codex, and try to understand how BuddyPres works.

I am using a child theme based on Headway Base and have no need of a bp theme.

You can use any theme you want with BuddyPress.

Modifying the registration page is explained here.

xProfile fields settings is explained here.

A less elegant, but working solution regarding locations within states you can find on my registration page (section: ‘Profile Details – Teil III: Geographisches’):

http://1a-spielwiese.de/registrieren/

You can ask at first:

• In which state (USA or UK?) do you live?

and then:

• In which US-federal state respec. in which UK-county to you live?
• and finally you can introduce the names of the federal states of the USA with ‘US-‘ and the names of the counties of the United Kingdom with ‘UK-‘.

(You can ask this questions within the ‘base group’ of your xProfile fields – then they get displayed on your registration page automatically. Or you can make your further xProfile fields displayed on your registration page as well:

https://buddypress.org/support/topic/reshaping-the-registration-page/#post-203615 [section 2nd].)

Yes, there should be a way, but I was not able to follow the instructions / to realise that way.

The basic idea is:

• Create two (or more) new WordPress user roles, e.g.: Users-UK and Users-USA.
• Then you can assign one xProfile-field, ‘In which [federal] state do you live?’, exclusively to your users with the user role Users-USA; and another x-Profile, ‘In which county do you live?’, to your users with the user role Users-UK.

—

The instructions for that solution you find there:

https://buddypress.org/support/topic/resolved-different-profile-types-and-different-user-roles/

(The user roles there are ‘bands’ and ‘fans’).

And my report about my attempt to apply that instructions you find there:

https://buddypress.org/support/topic/different-profile-types-and-different-user-roles-part-ii/

My user roles are (sport) ‘teams’ and ‘fans’.

—

But unfortunately, I was not able to hinder, that ‘fans’ get displayed the questions (xProfile-fields) for ‘teams’ was well; and the ‘teams’ the questions for ‘fans’…

—

Further problem:

Even if there is a solution regarding later profile edits – even complicate seems to be, to make already the registration page “input senstive”, because during registration the new user isn’t yet registered (i.e.: has no user role yet).

Cfr. there:

http://forum.wpde.org/buddypress/133961-registrierungsseite-umgestalten-anleitung-und-fragen.html (section 4. – unfortunately in German).

To make a field uneditable, you can remove it from the edit page of each profile.
You just have to enter the file ID, separated by coma if necessary to hide more than one.

Add snippet to child-theme functions.php or bp-custom.php

function bpfr_make_profile_field_uneditable( $retval ) {	
	
	if( is_user_logged_in()  && bp_is_profile_edit() ) {
	
	$retval['exclude_fields'] = '20,21,22';	// field id's
	
	} 
	return $retval;
	
	}
add_filter( 'bp_after_has_profile_parse_args', 'bpfr_make_profile_field_uneditable' );

Reference:

Using bp_parse_args() to filter BuddyPress template loops

For me also not:

I tried it with

Mitglieder-Kategorie (Team oder Fan?)

instead of

'name of your field'

as well as with

'Mitglieder-Kategorie (Team oder Fan?)'

But my users can still change the values for this field. –

I tried as well – already before and now again – this code of @noizeburger:

//hide the user role select field in edit-screen to prevent changes after registration
add_filter("xprofile_group_fields","bpdev_filter_profile_fields_by_usertype",10,2);
function bpdev_filter_profile_fields_by_usertype($fields,$group_id){
//only disable these fields on edit page
if(!bp_is_profile_edit())
return $fields;
//please change it with the name of fields you don't want to allow editing
$field_to_remove=array("User Role");
$count=count($fields);
$flds=array();
for($i=0;$i<$count;$i++){
if(in_array($fields[$i]->name,$field_to_remove))
unset($fields[$i]);
else
$flds[]=$fields[$i];//doh, I did not remember a way to reset the index, so creating a new array
}
return $flds;
}

It works neither with

"Mitglieder-Kategorie (Team oder Fan?)"

nor with

Mitglieder-Kategorie (Team oder Fan?)

nor with:

'Mitglieder-Kategorie (Team oder Fan?)'