BuddyPress.org

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.

I struggled with this for weeks. It never worked out well for me.
I used the Register Helper add-on plugin to add custom fields to the PMPro registration. I tried the above mentioned fixes, but nothing I tried let the PMPro registration process communicate with the BuddyPress (basically, I wanted one registration page to fill out the BuddyPress profile AND the necissary PMPro info).
Whichever way I tried it, they remained seperate. Of course, the PMPro registration process did add the user to BuddyPress, but with an empty profile, regardless of the custom fields that I added.

FINALLY, after MANY hours of working with this, I tried s2Member. This plugin is much more involved to configure, BUT it works perfectly AND integrates well with MailChimp. So now, I not only have integration with BuddyPress (specifically the profile, although the display is a bit off), but also with Mailchimp. And, this means that I can have different mail-lists or mail-list groups within Mailchimp! Perfect 🙂

Basically, what I am saying is that if you want a better integration, go with s2Member.

Note: I did not pay the $300 / year for paid membership pro support (too expensive for me), maybe they would have been able to help me resolve this issue. I did scour the forum and glean every bit of info I could to solve this without paying, but to no avail. BUT, with s2Member, it is free AND only $80 one time for the Pro version of the plugin.

Good luck!

And, if anyone sees this and has a solution, please add. As people (I assume because I was) are still looking for a solution.

Thanks so much for the solution above. How can I modify the code to apply only to a specific page:

.field-visibility-settings-toggle {
display: none !important;
}
.field-visibility-settings-notoggle {
display: none !important;
}

In my case, I’d like “This field can be seen by Anyone” removed from the registration page (#371), but still be visible on a users profile, thus giving users some control over the privacy levels of their fields.

Thanks in advance for the assistance.

You can save extra things manually on the bp_core_signup_user hook:
https://buddypress.trac.wordpress.org/browser/tags/2.9.1/src/bp-members/bp-members-functions.php#L1900

But I imagine that the simpler answer would be to use Profile Fields. If you add profile fields to the base group, then they appear on the registration form and are saved at signup. https://codex.buddypress.org/administrator-guide/extended-profiles/

Best,

-David

Put it all in one column:

/* Aligns Registration Profile Details fields to the left */
#buddypress .standard-form #basic-details-section,
#buddypress .standard-form #blog-details-section,
#buddypress .standard-form #profile-details-section {
    width: 100%;
}
#profile-details-section {
    margin-top: 20px;
}

And the finish button too (recommended):

#buddypress .standard-form#signup_form div.submit {
    float: left!important;
    margin: -12px 3px 3px 3px!important;
}

That should line it all up in 1 row. Congrats on not paying someone $1000 for that info 🙂