Thread

Having some annoying problems with Date Fields & DST Settings.

After the clocks going back an hour on Sunday, we have turned DST ‘off’ to match the change. The problem is, the date/time updates and shows the correct time but every single date field on the system goes back 1 hour.

We have a massive list of events with ‘Start Times’ being one of the most important aspects. These are obviously being moved back 1 hour.

Any newly published entries have to be set 1 hour forward to accommodate the correct start time.

Am I wrong in thinking all Date fields should remain unaltered when switching DST settings? I’ve tried setting a Super Admin account as the master localisation and through the system-wide Localization settings, to no avail.

I’m either missing some glaringly obvious, or there’s an issue somewhere.

We are running 2.2.1, but didn’t notice anything in the changelog relating to this problem.

Hoping someone can shed some light on this, as I am lost with it as it stands.

Cheers,

-Wilko

Hi, Wilko.

DST is confusing for all of us.

Your date fields will change, what happens if you set the SuperAdmin to be in an altered time zone? In other words, change that member’s time zone twice a year. Not ideal, but I’d like to see if there is anything else we can offer.

I’ll ask the dev team to see if they have any workarounds.

Hi Sue,

Thanks for the response, very much appreciated.

If I alter a Super Admin account, the times still change as stated above.

As a temporary work-around we’ve had to set DST to ‘On’ and our Web Server time to -1 Hour. This keeps the date field times correct and also alters the time to the correct time on our website. This does however mean that our Web Server is running an Hour behind the ‘correct’ time.

I hope this makes sense?

This is obviously not an ideal work-around, but will do for the time being.

I’d appreciate any further advice.

Many thanks,

-Wilko

Hi cripcrop,

We’ve brought this issue up with our development team, as you can imagine, this time of year tends to stir the pot on DST. After so looking into the situation we came to understand that ExpressionEngine may not be handling this properly. I apologize that you have had to come up with a kludge of workaround, but that appears to be the best course for you at this time.

Is there anything else I can help you with?

Thanks!