November Happy Hour will be moved to Thursday December 5th.
November Happy Hour will be moved to Thursday December 5th.
Hi Ian,
Is it causing an issue?
As I understand datetimes should be converted to utc datetime when storing in the database.
Paul
@Paul - no, it does not seem to be converting date/time fields to UTC. For example, a raw value from the Epi DB is 2023-01-26 05:00:00.000. We're on v11.14.0 for what it's worth.
Hi Ian
The date/time picker only shows the time based on the timezone on the user's system. It does not store the date in that timezone.
In the database it is stored in UTC, by default. And the content properties will also return UTC dates.
Changing editor UI to always use a certain time zone is not so easy.
@Stefan - understood. I'm looking to always show the same time for all users, regarldess of time zone. The fact that it changes the date/time based on time zone is what is causing us issues. Are there any solutions that might always show the date/time picker in UTC vs converted to the user's local time zone?
The use case here is we have pages that show events that need to be set to a fixed date/time as we manage the event's time zone in a separate field. Since editors in different time zones are shown different values, it causes much confusion.
There are no configuration for this. So you would need to "get your hands dirty" with overriding two Dojo classes:
But I don't know whether exactly those two classes can be overridden.
Thanks Stefan. It seems a little strange that this isn't functionality available out of the box.
We have multiple content editors in different time zones and I'm looking for a way to show all content editors the same date/time picker in the CMS, regardless of time zone. Currently, the date/time picker adjusts for the user's local time zone, which makes it impossible for editors to select a consistent date/time for fixed event dates.
We're looking to make the dates in the CMS admin UI consistent for all users. Is that even possible?
The date/time property we're currently using is as follows: