DateTimeDatelistWidget isn't resilient to additional date orders

Created on 24 March 2017, over 7 years ago
Updated 31 January 2023, over 1 year ago

Problem/Motivation

While working on #2823764: Add granularity options β†’ , I uncovered #2863896: Followup: Add granularity options β†’ . We need to make date order more resilient to extensibility.

Steps to reproduce

TBA

Proposed resolution

TBA

Remaining tasks

Explain the bug

User interface changes

API changes

Data model changes

Release notes snippet

πŸ› Bug report
Status

Active

Version

10.1 ✨

Component
DatetimeΒ  β†’

Last updated about 1 hour ago

Created by

heddn Nicaragua

Live updates comments and jobs are added and updated live.
  • Needs issue summary update

    Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • heddn Nicaragua

    DateTimeDatelistWidget assumes that there are only 3 date orders possible. If someone extends the widget and provides a setting value that isn't one of the values it allows, then no default value is provided and the switch on $time_type has an undefined `$date_part_order` variable. A default should be added to set $date_part_order = 'YMD'.

Production build 0.71.5 2024