If you can revert back to a clean version before you upgraded BP or this plugin and upgrade this plugin to v:0.5.3 which can be found in the revision logs for this plugin and (then) upgrade to BP 2.3 you should be fine. I had a similar issue. Then keep this plugin at v:0.5.3 until author has a chance to comb through issues caused by broken v:0.6 update that was reversed in v:0.6.1
Backups are king, never upgrade without backups. There are just too many factors that can change. This author is great at support but recent changes in all of the plugins associated will be a challenge to address.
I was able to get database access and manually deleted the fields that had been spawned. The site doesn’t have live users yet, so no harm done. Lesson learned!
@crawfocl Happy to hear no harm was done. The issue that leads to this happening on some websites is that BuddyPress xProfile fields can’t be “disabled” during upgrades. So this plugin has to try and reconnect the orphaned data with the new post-upgrade fields – and sometimes it fails. At minimum, I’m going to see if I can make it fail more gracefully.
@VentureCore The 0.6.1 and 0.5.3 code are essentially the same. I reverted the code and bumped the version so that others wouldn’t encounter the problem you encountered. If I could burn “backup first” into people’s retinas, I might just consider doing so 😉
I will look at BuddyPress 2.3 issues when I can. In the meantime (and until xProfile fields can be disabled) the safest way to upgrade this plugin is simply to replace the plugin’s directory with the new one. At least that avoids the deactivate-reactivate procedure.
Hi. I have the exact same issue with 17 duplicate empty “first name (required)” fields. Can you please tell me how to sort this out? Unfortunately, I don’t have backups of my database – rookie error.
@mandilpradhan You need to find the field IDs of the actual “first name” and “last name” fields from the **_bp_xprofile_data table, then sync the fields in **_bp_xprofile_fields so that you only have one of each for “first name” and “last name” and so that their IDs match the IDs of the entries in the data table.
I know it’s a PITA, but there’s little I can do – especially because I have not seen this effect in my installs. FWIW, the best way to upgrade this plugin is just to replace the existing plugin directory with the new plugin directory, rather than using the WordPress updater.
Thank you Christian. It got a little stressful when I accidentally deleted a couple of fields to make up for the new primary fields, but all good in the end.
