(solved) UTC in Content Studio

Enonic version: 7.16.1

Content Studio: 5.3.6 (yes, we’re a bit behind)

We’re having a weird UTC issue. Some editors get UTC+2 when selecting a date and time (see screenshot). I’ve tested myself and get the correct UTC+1.

When I ask the editor who sent attached screenshot to visit https://myutcoffset.com, they get UTC+1 as well. They have confirmed that the correct timezone “sentraleuropeiske normaltid” and Oslo - Norway is set in settings.

I know there was a UTC issue that was fixed in CS, so I’m mostly keen to know if there are related fixes waiting in newer CS versions?

Is this related to this issue that was fixed in 5.3.5?

Actually, I realize this is working as intended. We’re switching to daylight saving time on the 29th, which would put us in UTC+2. The date in the example is April 9th.

Sorry!

2 Likes

Working with dates is always such a headache, as there are so many side cases!

I was listening to this podcast episode from Igalia about the Temporal API yesterday, so it feels topical to share it here! :slight_smile: If you are interested in web standards, give it a listen!

From Wikipedia about Igalia:

Igalia is a major contributor to each of the major Web engines (Blink, Gecko/Servo and WebKit). In 2019 they were the #2 committers to both the WebKit and Chromium codebases