What is the URL?
Relevant URL: https://corpsite.admin.datocms.com/editor/item_types/HN31cI9gRVSkEcFQKCZ9pA/items
What is the issue?
I need help with: The date that shows in list view is always one day off from the actual date in the record.
Relevant URL: https://corpsite.admin.datocms.com/editor/item_types/HN31cI9gRVSkEcFQKCZ9pA/items
I need help with: The date that shows in list view is always one day off from the actual date in the record.
Hmm, this is probably a time zone issue — the default date field is saved in UTC/Zulu time, but the list view is probably using your browser time.
I’ll file a bug report about it!
In the meantime, if you want more explicit control, this might be another instance where the Zoned DateTime Picker - Plugins — DatoCMS plugin can help (that you’re already using elsewhere).
Since we’re dealing with a date field, not a date/time field, I’m surprised that timezones would even come into the picture.
But also, our configured timezone is Eastern, and the display shows a day off even for people in Eastern time, unless it should be set differently because of DST?
I don’t want to use the Zoned DateTime Picker for this if I can help it, because we aren’t including times currently.
Understood. I have a tentative patch for this awaiting code review.
The concept of a “timezone-less date” is a bit difficult to represent across our backend, the frontend, and the browser, so we have to kinda coerce it to something behind the scenes (usually your defined site API time zone in the environment config, as distinct from each user’s UI time zone set in their localization settings). In this case, it looks like a UI bug to me — we are using two different logic paths and “secret” time zones in the record view vs the list view.
A dev will take a look at my PR soon and I’ll let you know if it either gets fixed or rejected.
(Edit: Quick update: Still discussing this internally. Hopefully soon.)
(Edit: This response was wrong — I misread our API shape, my bad. Anyway, an official patch has been deployed.)
@fitzage This should be fixed now!
Yes, it’s fixed! Thanks.