BP xProfile WordPress User Sync
Donate link: https://www.paypal.me/interactivist
Tags: buddypress, xprofile, profile, sync
Requires at least: 3.9
Tested up to: 5.7
Stable tag: 0.6.7
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html
IMPORTANT: Do not install this plugin if you already have BuddyPress 8.0.0 or greater.
Replaces the default BuddyPress xProfile Name field with First Name and Last Name fields and keeps these in sync with WordPress user profile fields.
IMPORTANT: This plugin is not needed if you have BuddyPress 8.0.0 or greater. If you are upgrading to BuddyPress 8.0.0 and already have this plugin installed, please upgrade and then visit this plugin’s “Migration Page” to switch to using built-in BuddyPress xProfile Fields.
Please note: this is the development repository for BP xProfile WordPress User Sync. It can be found in the WordPress Plugin Directory, which is the best place to get it from if you’re not a developer.
The BP xProfile WordPress User Sync plugin is useful when you have a BuddyPress network in which you want users to enter values for First Name and Last Name rather than rely on the more freeform default Name field that BuddyPress provides.
The plugin replaces the default BuddyPress xProfile Name field with two fields called (surprisingly) First Name and Last Name. These field values are kept in sync with the corresponding WordPress user profile fields as well as the BuddyPress xProfile Name field itself.
There are two ways to install from GitHub:
If you have downloaded BP xProfile WordPress User Sync as a ZIP file from the GitHub repository, do the following to install and activate the plugin:
Unzip the .zip file and, if needed, rename the enclosing folder so that the plugin’s files are located directly inside
- Activate the plugin on the main BuddyPress site
- You are done!
If you have cloned the code from GitHub, it is assumed that you know what you’re doing.
When upgrading this plugin, it is strongly recommended that you run
git pull to replace the plugin directory directly. This is preferable because it avoids the deactivate-activate process that happens when upgrading via the WordPress updater.