The Event Calendar PRO – Daylight Saving Time Issues

[Frederick Brockmann]

I have seen several threads – and also the encouragement to add my own if I was having the same issue – so here it is.

New recurring events (and old one, too, for that matter) are shifting an hour earlier after the DST change on March 13. I have my WP timezone set to local (Denver) and I have run all the troubleshooting steps – changed my theme to “twenty-fourteen,” disabled all plugins except those needed for the calendar, cleared my browser cache, etc.

I am running 4.0.6 and here is a link to an event that I just created – http://www.firstluth.org/blog/event/test-event/2016-03-11/

I am going to reset my theme and reactive my plugins because it is a live site that people are using, so it needs to be working. I know that this could still be a setting, but I cannot seem to find anything that makes it work.

Thanks for the help.

Gus

[Nico]

Hey Gus,

Thanks for reaching out and also for opening a new thread for this!

I found a bug ticket for this, but seems the fix has been released in maintenance release 4.0.1. I guess you fall under a different use cas (which is still buggy) or maybe this issue is back in a newer release.

From what I see in the Denver timezone description (http://www.timezoneconverter.com/cgi-bin/zoneinfo?tz=America/Denver), DST will take effect in March 13, right? We are still a couple of weeks ahead of that. So for now it should be equal to UTC-7, makes sense?

Please let me know about it, I might be getting this wrong,
Best,
Nico

[Frederick Brockmann]

Yes – right now Denver is UTC-7 and will change on March 13. So there are a few weeks before it is critical that these events are correct on the calendar.

Do you need other information from me at this point?

Thanks

Gus

[Nico]

Thanks for following up Gus!

I guess I’m clearly missing something here, because I’m not sure what’s the problem now before the DST change?

Are you just preparing for the change in March 13? Also, the test event you previously sent what should I be looking for in there?

Sorry for the many questions on this, I’m still not getting this issue!

Have a great weekend,
Nico

[Frederick Brockmann]

The test event that I sent you shifts an hour earlier after March 13. It should stay at 10:00 am, but it shifts to 9:oo am.

Here, might be easier to see what I mean in this view -http://www.firstluth.org/blog/event/test-event/all/

All of my recurring events are doing this, and I have tried all the troubleshooting tips I can find both on your site and on WP. Like I said, not a big issue right now, but soon every recurring event on my calendar will be wrong by one hour, and that will be a big issue.

I am clearing missing something, too, because not everyone is having this problem, but I cannot seem to fix it. Please help.

[Frederick Brockmann]

Any new information on this DST issue? In less than two weeks I am going to have many, many events that are the wrong time by 1 hour.

Again, doesn’t matter if it is an event that I added 3 months ago (about when I starting using The Events Calendar) or a brand new event added with the most recent release of the software.

Thanks

[Frederick Brockmann]

I do see the note that you are all at an annual meeting of sorts, and I hope that it goes well.

I do, also, hope that this Daylight Saving Time issue can be taken care of soon! In a little more than a week many of my current events will be wrong by an hour. Yes, I know that I can re-enter them after the DST change and make them correct again, but I shouldn’t have to!

Please let me know the status of this issue. Here is a link a “test event” that I made that clearly shows the event moving 1 hour earlier after March 13.

http://www.firstluth.org/blog/event/test-event/all/

Thank you,

Gus

[Frederick Brockmann]

Just to make sure – I also just created another “test event” after installing the latest update – still have the same issue.

http://www.firstluth.org/blog/event/test-2/all/

[Nico]

Hey Gus,

Sorry for the delay on this! Most of the team, including me, was out last week and part this one as well. I’m catching up with all my threads, thanks for the patience whioe I work on this one.

I’ll take a close look on this one later, because I’m not sure on the top of my head what could be affecting this and also as you say we are not seeing occurrences of this in other customers threads.

Cheers, I’ll be back to you soon,
Nico

[Nico]

Hey Gus,

I still feel that’s there something we are understand differently. Let’s re-cap:

• If you don’t want events to be adjusted/changed to match the offset of the DST then go to WP-Admin > Settings > General > Timezone and set it to UTC-7 instead of America/Denver.
• If it’s ok for the events to be changed accordingly to the DST offset, but if this is not changed correctly please indicate what would be the correct adjustment made.

Please let me know about it,
Best,
Nico

[Frederick Brockmann]

Not only is OK if the events adjust, I WANT them to adjust and they are not!

Here is the link again -http://www.firstluth.org/blog/event/test-event/all/

This event should stay at 10 am.

It is not staying at 10 am.

My timezone is set to Denver, so should have DST settings enabled.

Help.

[Nico]

Thanks for clarifying Gus, I get you know and I’m sorry this is still an issue because it was fixed in version 4.0.1 but seems that it has been reintroduced by some other changes in the code. It’s has already been logged as a high priority bug so it gets fixed as soon as possible, I see this is slated to be out in the next maintenance release. I don’t have a date for it but I guess it will be after the release of version 4.1 (which is already in the QA process) coming out soon.

For now please try editing the events, and hopefully we can have the fix out soon!

Thanks for your patience and sorry I was having a hard time to get what was wrong here.

Best,
Nico

[Frederick Brockmann]

I look forward to the patch.

[Nico]

Thanks for confirming Gus! We will update the thread when it’s out.

Have a great week,
Cheers,
Nico

[Leah]

Hello,

Thank you for reporting this issue. We weren’t able to get a fix for it into our upcoming release (4.1). However, please know that the problem is still on our radar and is ticketed within our system to be addressed in a future maintenance release. We’ll do our best to keep you posted when we are able to get a solution in place. Thank you for your patience while we improve and expand our plugins.

Best,
Leah

[Author]

Posts