[buddypress-trac] [BuddyPress Trac] #6347: XProfile fields used for signup should be configurable

[buddypress-trac]

#6347: XProfile fields used for signup should be configurable
----------------------------------+------------------
 Reporter:  johnjamesjacoby       |       Owner:
     Type:  enhancement           |      Status:  new
 Priority:  normal                |   Milestone:  2.3
Component:  Component - XProfile  |     Version:  1.0
 Severity:  normal                |  Resolution:
 Keywords:                        |
----------------------------------+------------------

Comment (by johnjamesjacoby):

 [https://buddypress.trac.wordpress.org/attachment/ticket/6347/6347.01.patch
 6347.01.patch] simply moves the `bp_has_profile()` and its arguments out
 of `register.php` and into a custom function.

 The additional `bp_parse_args()` call allows explicit filtering of
 `bp_before_signup_fields_parse_args` to more easily target the arguments.

 How I plan to approach this:
 * New "Signup" metabox for all fields (including base?) with a checkbox to
 opt-into including
 * Checkbox is linked to profile field meta similar to field visibility
 * Custom query cached to `bp_xprofile` group to determine if any custom
 sign-up fields have been set
 * If so, use them and *not* the old base-group approach
 * If not, use the old base-group approach

 UX Goals:
 * If a user sets any profile fields as sign-up fields, they have opted
 into customizing the experience, and will naturally want to continue to
 pick others
 * If a user has not set any profile fields yet, the status quo continues
 as is for backwards compatibility
 * Consider improving visual distinction of which fields are: required,
 primary, sign-up

 Stretch goals:
 * Maybe begin to think about removing BuddyPress's dependency on the
 "Base" profile group and field. They aren't really hurting anything, but
 they start to make less sense when fields and groups become increasingly
 more flexible.
 * We can create another new metabox for telling BuddyPress which profile
 field to use for the "Base" field, which BuddyPress traditionally uses as
 another "Display Name" field, which I think is pretty confusing.

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