Home › Forums › Calendar Products › Events Calendar PRO › The Daylight Savings Issue has returned
- This topic has 4 replies, 3 voices, and was last updated 9 years, 2 months ago by
Chris.
-
AuthorPosts
-
February 20, 2017 at 8:56 pm #1242665
Chris
ParticipantHi Team,
At the change of Daylight savings time in Australia last year, we had a lengthy discussion on fixing the Daylight Savings disparity of times on recurring events.
Well, we’re a month away from the change over going back to normal time and the issue is re-appearing. Here’s the scenario.
In the month of March 2017, Australian Eastern Daylight Time (AEDT) March 2017, events set at 9.30am and are showing up in Australian Eastern Standard Time (AEST), April 2017 at 10.30am.
The setting on the client’s WordPress system hadn’t changed until I started testing.
Here’s what they were set at…
General Settings Time Zone > Sydney, Australia.
The Event Calendar Settings > use the Local Timezone, in this case Sydney, Australia.
When we create a recurring event, or for existing recurring events we select the local time zone, in this case >Sydney, Australia.So I tested a few things on some separate events that recur:
Test Event 1 that recurs:
1. I set the General Settings Time Zone > UTC-10….. I refreshed the calendar, no changes.
2. I went into the parent recurring event for the series and changed the timezone to Sydney and refreshed the calendar, no changes.
3. I went back into the parent recurring event for the series and changed the timezone to UTC-10, no changes.
4. I went back into the parent recurring event for the series and changed the timezone to Sydney and refreshed the calendar, and it changed the dates correctly on AEST, April 2017 onwards.Test Event 2 that recurs:
1. No changes to the General Settings Time Zone still UTC-10.
2. I went into the parent recurring event for the series and changed the timezone to Sydney and refreshed the calendar, no changes.
3. I went back into the parent recurring event for the series and changed the timezone to UTC-10, no changes.
4. I went back into the parent recurring event for the series and changed the timezone to Sydney and refreshed the calendar, and it changed the dates correctly on AEST, April 2017 onwards.(It looks like I’m onto something…..)
Test Event 3 that recurs:
1. No changes to the General Settings Time Zone still UTC-10
2. I went into the parent recurring event for the series and changed the timezone to Sydney and refreshed the calendar, no changes.
3. I went back into the parent recurring event for the series and changed the timezone to UTC-10, no changes.
4. I went back into the parent recurring event for the series and changed the timezone to Sydney and refreshed the calendar, and it changed the dates correctly on AEST, April 2017 onwards.(It’s looking consistent)
Test Event 4 that recurs:
1. No changes to the General Settings Time Zone still UTC-10
2. I went back into the parent recurring event for the series and changed the timezone to Sydney and refreshed the calendar, and it changed the dates correctly on AEST, April 2017 onwards.So there you have it.
I also checked Dec 2017 and it seems all the Test Events I regenerated seem correct.
So at the end of the testing session we have the following configuration settings:
No changes to the General Settings Time Zone still UTC-10
The Event Calendar Settings > use the Local Timezone, in this case Sydney, Australia.
When we create a recurring event, or for existing recurring events we select the local time zone, in this case >Sydney, Australia.Would love your feedback and advice.
February 21, 2017 at 2:45 pm #1243344Andras
KeymasterHello again Chris,
WOW!!! Kudos to you, man! Amazing testing.
I tried to recreate the issue with the summer time change but couldn’t. Here is what I did:
- General Settings Time Zone > Sydney, Australia.
- The Event Calendar Settings > use the Local Timezone
- Create an event for March 31, from 8am to 9am, with daily recurrence that stops after 5 days.
- On the front-end all recurrences show start time as 8am and end time as 9am as expected.
I even tried this with General Settings Timezone as UTC, same result.
Changed event timezone from locality to utc and back, no changes.
So I’m a bit clueless at the moment. Are you / were you doing anything different when setting up the recurring event? Maybe different type of recurrence rule? That is the only thing I can think about at the moment.
Let me know, please. I’m just about as eager to get to the bottom of this as you are. I do hope we find something and we will be able to fix it.
Cheers,
AndrasFebruary 27, 2017 at 7:23 pm #1246606Chris
ParticipantHi Andras,
The events creator has made some new recurring events for the site. She has checked the records across the the change of Daylight Savings times for 2017 and they all seem OK.
The plan is to go back through existing events and fix them.
So as it stands, it seems like its all working OK.
Happy to close the ticket off.
Thanks again for your assistance.
Chris
March 1, 2017 at 3:48 pm #1248047Andras
KeymasterChris, my pleasure!
I’m happy to hear that the newly created events are working as expected, through the timezones and the daylight saving / wasting times.
I am going to close this ticket. Good luck with your project down the road, and if you need anything else related to this topic or another please post a new one in the forum and we will be happy to help you out.
Cheers,
Andras -
AuthorPosts
- The topic ‘The Daylight Savings Issue has returned’ is closed to new replies.
