BuddyPress.org

If I understand properly, you need conditional profile fields. Try BuddyDev’s Conditional Profile Fields for BuddyPress.

Conditional Profile Fields for BuddyPress

It’s not possible to use a regular BP profile field to keep track of data changes over time. BP doesn’t keep records of old profile field values – it only stores the most recent one.

There are a number of ways you could accomplish it. If you had the technical know-how, you could build a tool that hooks into XProfile and syncs user-entered data to another system (maybe an array in usermeta or something like that). Another option is to manually created new fields every 3 months, but then you’d need to do some customization to the way fields are displayed on the front end so that the profile doesn’t show all past entries as separate items. Either way, some customization would be required.

Maybe someone on this forum knows of an existing tool that will help.

BuddyPress’s Register page is a special kind of page that cannot be edited via the Dashboard. That’s why it’s blank when you view it in the normal way.

To add additional fields to the registration process, go to Dashboard > Users > Profile Fields. Add one for Address and one for Phone Number. Make them required and/or private, if you’d like. As long as they are part of the ‘Base’ profile field group, they will appear as part of the registration process.

Hi @Sander – Thanks for reporting this. It looks like a legitimate bug. I’ve opened a ticket to track it: https://buddypress.trac.wordpress.org/ticket/7631

While we try to figure out a way to make this work better, you can work around the issue by disabling autolink for the field in question. Dashboard > Users > Profile Fields > Edit, and look for the Autolink metabox at the right.

You may be able to disable the linking in the admin. Go to Dashboard > Users > Profile Fields. Find the Email field, and click Edit. On the right-hand column, find the “Autolink” metabox. Switch it to ‘Disabled’ and save.

> i created customed fields for the inner-page of the user, but they don’t show in the members list page.

The details depend on how you created these “customed fields”. If they are xprofile fields, then the simplest way is to do this:

$user_id = bp_get_member_user_id();
$data = xprofile_get_field_data( 'Custom Field Name', $user_id );
if ( $data ) {
    echo $data;
}

If you stored it in user meta, do something similar:

$data = get_user_meta( $user_id, 'custom_field_name', true );

Either way, bp_get_member_user_id() is how you get the ID of the current user in the loop.

Hi @barkins – BP doesn’t have a built-in tool for this (though it should – see https://buddypress.trac.wordpress.org/ticket/7393, https://buddypress.trac.wordpress.org/ticket/408). If you know that user IDs will remain the same between the local WP install and the live install, then you can do a simple database export/import, something like:

$ mysqldump -u db_user -p db_name wp_bp_xprofile_groups wp_bp_xprofile_fields wp_bp_xprofile_data > ~/xprofile-export.sql

$ mysql -u db_user -p db_name < ~/xprofile-export.sql

If the user names will not be the same, you’ll need to write a script to handle this, but the details will depend on how you plan to identify users (email address, etc).

Hi @willallen83 – I’m afraid I haven’t integrated with s2member in many years, so I can’t provide exact advice. But briefly, it appears that the code above is meant to sync the $s2member_fields fields – which I assume are defined somewhere in s2member – to the corresponding members of the $xprofile_fields array. The latter fields are created in Dashboard > Users > Profile fields; make sure the names (like ‘Last Name’) match exactly, or the lookup will fail.

Note also that it may be more reliable to fetch user info from the values passed by the ‘wp_login’ hook to the function. So something like this:

function s2_profile_field_update( $user_login, $user ) {
  //Array of xprofile field names
  $xprofile_fields = array('Last Name','Country','Introduce yourself to Aisha Salem');
  //Array of s2member field slugs
  $s2member_fields = array('last_name','user_country','member_letter_aisha');
  //Populates BP with S2 info
  get_currentuserinfo();
  // if( current_user_is("s2member_level1") ) {
       for($i = 0; $i < sizeof($xprofile_fields); $i++) {
          if(xprofile_get_field_data($xprofile_fields[i], $user->id) == '' && get_user_field($s2member_fields[i]) != '' )  {
              xprofile_set_field_data($xprofile_fields[i], $user->id, get_user_field($s2member_fields[i]) );
           }
       }
  // }
}

Note that, according to this code, it’ll only update the BP xprofile fields if they’re empty. You’ll have to remove that check if you always want s2member values to take precedence.

Beyond this, your best bet for figuring out why this is not working is to place some debug statements at various points. Use error_log() or good old-fashioned var_dump() to make sure (a) the function is actually firing at ‘wp_login’, (b) the xprofile field values are actually being fetched properly, (c) the get_user_field() function is fetching data properly, and from the correct user https://s2member.com/kb-article/user-custom-fields-via-php-code/#toc-460a2dd2, etc.

Sure, I’m happy to point you in the right direction.

The BuddyPress Custom XProfile Field Type plugin is probably a good one to start with. It uses the BP_XProfile_Field_Type class to register its fields. It even has an existing Datepicker field that you can use as a starting place: https://github.com/donmik/buddypress-xprofile-custom-fields-type/blob/master/classes/Bxcft_Field_Type_Datepicker.php

There are a few changes you’ll need to make in order for this to show two datepickers instead of one.

– The set_format validation regex expects a single date. This will need to be modified for your new format. https://github.com/donmik/buddypress-xprofile-custom-fields-type/blob/1126cf093bd2b6e9f917b5c15f52e203f17cbb9e/classes/Bxcft_Field_Type_Datepicker.php#L14
– You’ll need to modify the edit_field_html method so that it loads two separate input fields, and then write some JavaScript that assigns a jquery-datepicker to each one of them. Then you’ll need to write a little bit of extra JS that combines the two datepicker inputs into a single (probably hidden) field, which is the one that BP will actually save to the database. https://github.com/donmik/buddypress-xprofile-custom-fields-type/blob/1126cf093bd2b6e9f917b5c15f52e203f17cbb9e/classes/Bxcft_Field_Type_Datepicker.php#L29
– If you decide to store the start and end date in a single row in the profile field, you’ll also need some logic that splits it into start and end when you load the edit_field_html. Another option is to store the concatenated display text – say, April 2017 - May 2017 – in BP’s native xprofile field, and to store the start and end date separately, as xprofilemeta. You’d need a custom save routine for this, but it may be a bit cleaner.

Good luck! Sounds like a fun project.

Hi @amitrwt – The ‘Start’ and ‘End’ fields in the BP admin settings define the start and end dates of a single datepicker. That is, if you want to have a datepicker, but you only want to show dates between the years 1970 and 1990, you’d use those dates as the Start and End.

If you want your users to be able to select start and end times, my best suggestion is to create two separate xprofile fields, and name them accordingly: ‘Start Date’, ‘End Date’ or something like that.

Hi @redcompolitica – I’ve built multi-page registration processes for clients in the past, but unfortunately, it’s not very easy to do – BP’s registration system is not built in such a way as to make it easy.

If your main goal is to make registration less overwhelming, you might consider moving some or most of your registration fields out of the “Base” group. This will mean that they don’t show up during the registration process, and users will have to fill them in by editing their profile after signing in.

If your goal is to have *conditional* registration steps – where, for example, step 2 depends on a specific value provided in step 1 – then I’m afraid it’d have to be custom-built. Much of the work could be done with a custom theme template members/register.php and by modifying the way that registration data is saved and validated https://buddypress.trac.wordpress.org/browser/tags/2.9.2/src/bp-members/bp-members-screens.php?marks=113#L72

Some Trac tickets that are somewhat related that you might want to follow:
https://buddypress.trac.wordpress.org/ticket/1842
https://buddypress.trac.wordpress.org/ticket/4278

Good luck with your project!

BuddyPress Xprofile Custom Fields Type plugin is what I use to do this.

It shows up on the profile as age. If you want it on the members page that takes some code editing. I saw a tutorial on BPDev site.