You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a weird Daylight Saving Time anomaly for recurring events across DST time changes.
Events (including Event Registration?) are based on a single event record with begin and end times set to 'offset from unixtime 0' and also one or more eventdate records with their date set to 'beginning of day'. Therefore each event on the calendar is established by adding the eventdate date with the event begin/end time.
One symptom of this anomaly is that events on the day of the time change will be 1 hour off. One solution is to change the 'beginning of day' to 60 minutes earlier...however this moves the events on the day of the time change to the previous calendar day.
The BEST solution would be to completely revise the entire event system/module using the new PHP DateTIme class/package which is more timezone/daylight-savings friendly...however, there should be a less intensive work-around for this anomaly.
The text was updated successfully, but these errors were encountered:
There is a weird Daylight Saving Time anomaly for recurring events across DST time changes.
Events (including Event Registration?) are based on a single event record with begin and end times set to 'offset from unixtime 0' and also one or more eventdate records with their date set to 'beginning of day'. Therefore each event on the calendar is established by adding the eventdate date with the event begin/end time.
One symptom of this anomaly is that events on the day of the time change will be 1 hour off. One solution is to change the 'beginning of day' to 60 minutes earlier...however this moves the events on the day of the time change to the previous calendar day.
The BEST solution would be to completely revise the entire event system/module using the new PHP DateTIme class/package which is more timezone/daylight-savings friendly...however, there should be a less intensive work-around for this anomaly.
The text was updated successfully, but these errors were encountered: