[buddypress-trac] [BuddyPress Trac] #5589: Duplicated fields using Buddypress Xprofile Custom Fields Type and custom theme not from buddypress

[buddypress-trac]

#5589: Duplicated fields using Buddypress Xprofile Custom Fields Type and custom
theme not from buddypress
--------------------------+---------------------
 Reporter:  atallos       |       Owner:  djpaul
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:  2.0.1
Component:  XProfile      |     Version:  2.0
 Severity:  normal        |  Resolution:  fixed
 Keywords:  has-patch     |
--------------------------+---------------------
Changes (by djpaul):

 * owner:   => djpaul
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"8336"]:
 {{{
 #!CommitTicketReference repository="" revision="8336"
 xProfile: prevent duplicate profile field templating when using pre-2.0
 custom field types.

 Prior to the xProfile field type overhaul in 2.0, plugins that added
 custom field types had to do so with a variety of actions.
 One such plugin is "Buddypress Xprofile Custom Fields Type" and the
 changes in 2.0 caused an issue where the plugin's custom
 templating was being rendered, alongside BuddyPress' profile field
 fallback type, the textbox.

 BuddyPress uses a fallback field type to handle situations when extra
 profile types/data are provided by another plugin, and
 then that plugin is removed. The original idea was that everything would
 fallback to rendering a textbox if a field type was
 unregistered to give at least some kind of access to that profile field's
 data, but in practice this has caused a couple of
 issues with templating, as this commit addresses.

 This change essentially reverts the fallback behaviour to the pre-2.0
 implementation: if a custom field type is unknown to
 BuddyPress, that field simply won't be rendered.

 Fixes #5589
 }}}

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