Revisit Date/Time fields

[JoryHogeveen]

• Combine the three fields into one
• I18n JS (should be here, not in i18n component: Translate Pods and fields #3641)
• Validate existing options for JS and HTML5
• Enhance options for JS and HTML5
• Check/extend output options (surgestions please!).
  • Date Field needs additional formatting options for UNIX Time String and other Date Formats #3927
  • Maybe allow a custom input for format?
• Feature: HTML5 Date options for date and datetime fields
  (From Slack)
  @yourpcmagician14
  Ok so Safari and IE apparently don't honor minDate. I changed the code slightly to remove the minYear and maxYear options and did $args[ 'yearRange' ] = '1900:2016';

Also see https://github.com/pods-framework/pods-code-library/blob/master/example/hooks/filters/pods_form_ui_field_date_args/examples/date-range.php

[JoryHogeveen]

Maybe also just combine datetime.php, date.php and time.php into one field type where the user has the option to enable/disable time and date functionality.

[JoryHogeveen]

Also change HTML input type datetime to datetime-local for browser support. datetime is removed.
See "datetime" input at: http://www.w3schools.com/html/html_form_input_types.asp

The input type datetime is removed from the HTML standard. Use datetime-local instead.

[JoryHogeveen]

Also add week & month in there

[jimtrue]

Fuzzy date input logic? Next week, 3 weeks from today

[jimtrue]

Some people also use just 'parts' of the field (ie Year). To me a full datetime string is always more useful. It's just what it 'stores' that matters.

[quasel]

putting that on the DFV list for 2.8 to comb through all the field issues ...

[sc0ttkclark]

Date/time/datetime fields have been rewritten for DFV in React, we should review what's left to be done here at some point soon.