[buddypress-trac] [BuddyPress Trac] #8455: Fixes for xProfile field support for WordPress Profile Fields

buddypress-trac noreply at wordpress.org
Mon Apr 12 17:46:20 UTC 2021

#8455: Fixes for xProfile field support for WordPress Profile Fields
 Reporter:  needle            |      Owner:  (none)
     Type:  defect (bug)      |     Status:  assigned
 Priority:  normal            |  Milestone:  Awaiting Review
Component:  Extended Profile  |    Version:
 Severity:  normal            |   Keywords:  has-patch
 This patch provides a couple of fixes for #7162:

 1. Skips caching existing data for an xProfile field when it is a
 WordPress field
 2. Fixes a minor bug where the empty item's `table_name` is cleared

 Part 1 allows existing xProfile fields to be converted from `textbox` to
 `wp-textbox` format by ignoring any pre-existing values retrieved by the
 uncached data query.

 This allows people using the [https://wordpress.org/plugins/bp-xprofile-
 wp-user-sync/ BP XProfile WP User Sync] plugin to simply change the
 xProfile field type and then deactivate it in favour of the new BuddyPress
 sync functionality. There will be orphaned field data left in the
 `*_bp_xprofile_data` table, but I think this is of little practical
 consequence since the field IDs are still in use.

 Part 2, as the summary says, simply prevents the WordPress xProfile field
 `table_name` property from being cleared prior to priming the cache.

Ticket URL: <https://buddypress.trac.wordpress.org/ticket/8455>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac

More information about the buddypress-trac mailing list