[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.4
Component:  Component - XProfile     |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |
-------------------------------------+------------------

Comment (by boonebgorges):

 Replying to [comment:24 sooskriszta]:
 > At the moment year/no-year checkbox literally does exactly what it says
 on the tin.
 > If year shows 1 Jan 2016 (based on WordPress date format), then no year
 shows 1 Jan.

 Yes. But what I'm suggesting is that this checkbox is too specific to your
 use case for us to adopt in BuddyPress. What if I only want to show years?
 Only months? Only month + year? There are valid use cases for all of
 these. So I'm suggesting one of the following:

 1. A curated list of format options. Maybe a radio button of options like:

 {{{
 * February 23, 2015
 * February 23
 * February 2015
 * February
 * 2015
 }}}

 2. A parameterized system for defining your desired format. Perhaps we'd
 define some subset of PHP's `date()` syntax, maybe something like this:

 {{{
 Enter your desired date format. Use the following placeholders for various
 parts of the date:
   - %F - Full month name (eg, January)
   - %m - Month number, with leading zeroes (eg, 04)
   - %d - Day number, with leading zeroes (eg, 13)
   - %j - Day number, without leading zeroes (eg, 4)
   - %Y - Year number
   etc

 Format: [ %F %d, %Y ] (February 23, 2015) // this would maybe update
 dynamically as a preview
 }}}

 These are just some ideas. It would be very valuable to see what existing
 form-building plugins do. We don't necessarily need (or want) to build a
 full date-format system, but perhaps looking at examples would give us a
 sense of what would be a useful subset of such a system.

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