Time zone issue affecting published Date
|
| When publishing content we are experiencing an issue with the published date displayed on site consistently being one day earlier than the date the content is actually published. We have the following request to enable us to resolve this issue.
Is it possible to use the .Net 6 built in type DateOnly in CMS 12+ ? Setting time zone on the server as suggested does not help in scenarios where we don't want to neither use nor display a date at all because the internal timezone conversion places dates on the day before in some cases. This can be solved by using DateOnly which is a type that has no date component, has an equivalent in SQL Server and would be a welcome contribution to the CMS. After all, it IS a feature that would fix a decade old problem with the CMS, see Henrik Fransas request from 2015 and we see this for every single customer that wants to use an actual date object but without the time component.
https://world.optimizely.com/forum/legacy-forums/Feature-requests/2015/3/built-in-uihint-for-dateonly/
I can't use DateOnly because there's no PropertyTypeDefiniton for it and I get an exception in the startup phase of the site:
TypeMismatchException: Type 'System.DateOnly' could not be mapped to a PropertyDefinitionType |
|
Selena Smith-Taylor
shared this idea
-
Ted Nyberg
commented
Editors often need to specify dates without a specific time.
Today we solve this with a DateTime property and an editor descriptor to display a date picker without time in the CMS UI, meaning we'll have a date at midnight.
However, this can easily lead to gotchas when working with multiple time zones.
Support for the DateOnly type (introduced in .NET 6) would solve this.