Skip to Main Content
Customer Feedback

We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.

Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.

Categories Content Manager
Created by Guest
Created on Sep 4, 2024

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