[buddypress-trac] [BuddyPress Trac] #6685: XProfile name field created through multiple triggers

[buddypress-trac]

#6685: XProfile name field created through multiple triggers
----------------------------------+----------------------
 Reporter:  Rourke                |       Owner:
     Type:  defect (bug)          |      Status:  closed
 Priority:  high                  |   Milestone:
Component:  Component - XProfile  |     Version:
 Severity:  major                 |  Resolution:  invalid
 Keywords:                        |
----------------------------------+----------------------
Changes (by boonebgorges):

 * status:  new => closed
 * resolution:   => invalid
 * milestone:  Awaiting Review =>


Comment:

 Thanks for checking back in, Rourke.

 I would like for BuddyPress to be more discriminating about this, but our
 hands are kinda tied. On the one hand, we could keep track of which field
 is the 'name' field - something we used to do, via the
 `xprofile_name_field_id` option (or something like that) - but this
 creates problems with syncing and performance. We hardcode the `1` as a
 way of ensuring consistency, and we try to enforce this by setting
 `can_delete` to `0` on that field, but obviously there are workarounds :)
 Given that we already attempt to enforce the deletability, and given that
 we don't have any other great solutions on hand, I'm going to close the
 ticket.

--
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/6685#comment:4>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac