[buddypress-trac] [BuddyPress Trac] #5500: Date xprofile field enhancement

[buddypress-trac]

#5500: Date xprofile field enhancement
----------------------------------+------------------
 Reporter:  sooskriszta           |       Owner:
     Type:  enhancement           |      Status:  new
 Priority:  normal                |   Milestone:  2.6
Component:  Component - XProfile  |     Version:
 Severity:  normal                |  Resolution:
 Keywords:  needs-patch           |
----------------------------------+------------------

Comment (by boonebgorges):

 Replying to [comment:39 sooskriszta]:
 > Replying to [comment:35 boonebgorges]:
 >
 > > If the date_format selected doesn't include year (or month or day), we
 shouldn't include it in the front-end interface.
 >
 > @boonebgorges I don't have a specific use-case in mind, and this may be
 inapplicable for this particular ticket, but I'd like to see in BuddyPress
 a decoupling of the input data and the output information.

 I see this point, and I guess I don't feel strongly about my suggestion.
 My main thinking is that it's awkward to ask someone for, say, their
 birthday, knowing that you're not going to show the year on the front end,
 but requiring that the user provide it when editing the profile. I guess
 in some ideal world (though is this really ideal? seems like a potentially
 very confusing interface) the site admin would be able to say "collect the
 year, but don't display it", or "make the year optional" or "require the
 day and month, make the year optional, and only display the month and
 year" or whatever. Maybe, as a compromise, the validation should work like
 this: fields that are not going to be displayed on the front end should be
 de facto optional - that is, the validation routine will not throw an
 error if you don't include a Year, if the year is not part of the display
 format.

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