Same DST Issue on Recurring Events as Others

[Shay]

Recurring events that started before DST ended on November 5 now show incorrect time (one hour ahead). All timezones are set to America/New_York. This is only an issue with recurring events. One-time events show correct time.

WP timezone: America/New_York
Server timezone: America/New_York
Timezone handling of TEC (Events > Settings > General tab: Local
Timezone setting of the specific events: America/New_York

========================
PLEASE LEAVE FOR SUPPORT
Reporting the same issue as: https://theeventscalendar.com/support/forums/topic/daylight-savings-time-displays-incorrectly-in-future/

[Cliff]

Hi, Shay. Sorry you’re experiencing this.

This was an old bug that should have been resolved quite a while ago. Is it possible the recurring events that are off were created while running a considerably-older version (months ago) of PRO?

One way to double-check is to create a brand new event, such as recurring weekly from October 1 – December 1 and see how that works.

Please let me know what you find out.

[Shay]

Just tested and same error. Time before DST ended is OK, but events after DST appear an hour later than they should. Correct time only displays when editing the event.

Recurring events that start after DST ended are working OK though.

• This reply was modified 8 years, 5 months ago by Shay.

[Cliff]

Thanks for testing.

Here are the steps to reproduce from one of our staff who was able to reproduce this bug (they are from prior to Nov 5, 2017, so you might have to test after March 11, 2018):

The timing of your events after the DST change date will be off by 1 hour if all of these conditions are met:

• Under Events > Settings > General tab > Timezone mode is set to ‘Use sitewide timezone everywhere’
• The site timezone under Dashboard > Settings > General > Timezone is set based on UTC (e.g. UTC or UTC-8) — (I don’t think this applies in your case)
• The timezone of the event itself is set city / GMT based, e.g. Los Angeles

Here’s a screenshot: https://cloudup.com/cvk26JgEfDY

You will also get this if:

• Under Events > Settings > General tab > Timezone mode is set to ‘Use sitewide timezone everywhere’
• The site timezone under Dashboard > Settings > General > Timezone is set based on GMT (e.g. Los Angeles)
• The timezone of the event itself is set UTC based, e.g. UTC-8 — (I don’t think this applies in your case)

I found 2 solutions based on your Calendar Timezone mode:

1. Set the Events > Settings > General tab > Timezone mode to ‘Use the local timezones for each event’. Then you should be able to use whatever combination for your site and the events. — (Don’t you already have this set?)

2. If you want to keep Events > Settings > General tab > Timezone mode on ‘Use sitewide timezone everywhere’, then make sure that you use the same type of timezone setting for both your site and the events. So both either UTC based, or city / GMT based.

===

Please send a screenshot of one of your event’s date, time, and recurrence details.

[Shay]

The only way I could get events to display correctly was to make them UTC -4 and in TEC settings use sitewide, not local. This is going to be a problem because this spring I will need to back and change all recurring events again, since they will be off an hour then too when DST starts.

For example, the screenshot attached shows an event that actually starts at 9:30 AM, but since it started before DST, the time shows an hour ahead now. The ONLY way it will work on the calendar is to keep it like this and use UTC-4. Any other configuration throws it off an hour.

Is there going to be a fix for this bug or do we need to rely on these workarounds? If the latter, I need to look for another calendar solution because this isn’t good.

[Cliff]

We always recommend setting a city-based timezone, not a manual UTC offset.

If it’s not working when the same city-based timezone is used for both the event timezone and WordPress timezone, everything should work correctly; if it doesn’t, it’s definitely a bug.

However, I can’t replicate this on my own site. Here’s my attempt: https://cl.ly/3q3p3m1N241L

I’d suggest following our recommended troubleshooting steps:

There might be some new updates available. Could you please make sure all your Modern Tribe plugins (and WordPress core) are at their latest versions?

• Downloads / Version Numbers
• License Keys
• TEC Automatic Updates
• or TEC Manual Updates
• WordPress core updates

Once you verify you’re on the latest versions, please test to see if the issue is still happening for you.

If it is, please follow our Testing for Conflicts Guide (basically switch to Twenty Seventeen theme and deactivate all plugins and custom code other than Modern Tribe plugins) and see if that helps narrow down the cause of this.

Of course, we always recommend restorable database and file backups before modifying anything on your site.

If it doesn’t, please enable WP_DEBUG and WP_DEBUG_LOG (which will create a file on your server at /wp-content/debug.log if there are any WP_DEBUG messages) and share any debug messages you see while trying to replicate this issue and doing other things on your site relevant to this ticket (such as visiting your site’s home page, events page, single-event pages, and anything else you can think to do).

Then, please share your System Information (while in Testing for Conflicts Mode) in a Private Reply. That will give me a lot of extra information to help troubleshoot this.

You might also see if you can spot any console errors at your site. (If needed, you may reference our KB article Using Google Chrome Developer Tools.)

Let us know what you find out.

Thanks.

[Shay]

You are not seeing the error because your test event did not begin before DST ended, which was on November 5. This issue impacts recurring events that started BEFORE November 5 and continue after that date only. As I mentioned in the my last reply, events that begin after November 5 are OK.

I’d rather not use UTC either! That’s the problem! It is the ONLY way the correct time will display on the calendar, so I am left with no other choice at the moment.

I have already sent system info and completed testing before submitting the original ticket, which seems to be an issue with many other users as well. It is clearly not an isolated incident. There are no other errors on the site.

[Cliff]

I agree you shouldn’t use a manual UTC offset or the UTC timezone. I was just sharing what another team member discovered.

At the time of creating my previous recording to you, it was not DST so I created an event that went through the start of DST.

Here’s another recording for an event started during DST through non-DST, again unable to reproduce this on the latest versions of our plugins and WordPress core: https://cl.ly/192R2k0b3k2v

[Support Droid]

Hey there! This thread has been pretty quiet for the last three weeks, so we’re going to go ahead and close it to avoid confusion with other topics. If you’re still looking for help with this, please do open a new thread, reference this one and we’d be more than happy to continue the conversation over there.

Thanks so much!
The Events Calendar Support Team

[Jaime Marchwinski]

Hi There!

Just wanted to share with you that a new release of our plugins is out, including a fix for this issue 🙂

Find out more about this release —> https://theeventscalendar.com/maintenance-release-week-25-march-2018/

Please update the plugins and let us know if the fix works for your site.

Best,
Jaime

[Support Droid]

Hey there! This thread has been pretty quiet for the last three weeks, so we’re going to go ahead and close it to avoid confusion with other topics. If you’re still looking for help with this, please do open a new thread, reference this one and we’d be more than happy to continue the conversation over there.

Thanks so much!
The Events Calendar Support Team

[Author]

Posts