Fix support for fields of 'timestamp' type

Created on 15 March 2023, almost 2 years ago

Updated 18 January 2024, about 1 year ago

Problem/Motivation

When using the range datepicker widget for a field of timestamp type e.g. placed field from commerce order, it doesn't work as expected, because the module's processor is not applied to the facer.

Steps to reproduce

Proposed resolution

Update code of DatepickerProcessor::supportsFacet() and RangeDatepickerProcessor::supportsFacet() and add 'timestamp' in $allowed_types.

Remaining tasks

✨ Feature request

Status

Needs work

Version

1.0

Component

Code

Created by

🇺🇦Ukraine khiminrm

Live updates comments and jobs are added and updated live.

Comments & Activities

Issue created by @khiminrm
Comment almost 2 years ago →
🇺🇦Ukraine khiminrm
Status changed to Needs review almost 2 years ago5:05pm 15 March 2023
Comment almost 2 years ago →
🇺🇦Ukraine khiminrm
Status changed to Needs work about 1 year ago11:44am 18 January 2024
Comment about 1 year ago →
🇨🇦Canada jigarius Montréal
I tried the patch, but it doesn't seem to have any effect. I think the problem is deeper than that. Additionally, even for a regular datetime field, the module doesn't seem to work.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024