Loading...
 
Features / Usability

Features / Usability


Calendar problems - Daylight saving time?

posts: 92

Two errors are observed when I enter events after March 8, 2015:

If entered as a single-day, all-day event (e.g. start March 9, end March 9, all-day box checked), after hitting "Save" the start date changed to the day before, creating a two-day event. If I open the event while logged in as admin, it reads start March 8, end March 9. If I open the event while logged in as anonymous, it reads start March 8, end March 8.

If entered as a single-day event spanning two hours (e.g. 10am-12pm), the calendar shows the even staring one hour later (e.g. 11am). If I open the event it still reads 10-12, but the display after it is closed says 11am.

http://www.hrsms.org/home/calendar

I am filing a bug report, but am also writing in the forum to see if anyone else has encountered this. Anyone?

I have 12.3svn.
I am running on a shared host (Bluehost).

Thanks,

Greg

posts: 400

Hi,

What do you have set as the time zone and "displayed time zone" in the General admin panel in the Date & Time tab?

Thanks,

lindon


posts: 92

Time zone is America/New_York

Displayed time zone was set to "auto detect".

The problem goes away when I change to "site default", so thank you for mentioning this setting.

Now that we have entered daylight savings time, I can no longer reproduce the problem (using "auto" or "system") in March, as in my description.  But if I enter events in December (a standard time month) I can reproduce the problem with is set to "auto" and resolve the problem by setting it to "system".

Using "system" is acceptable for me, but it appears to be a bug worth reporting.   I filed one already, and will copy this information there.  I tried to reproduce with TikiShow instance, but when using FullCalendar, nothing was displayed.

Thanks again,

Greg


posts: 400

I have backported a fix for 12x with r54288. The fix will also be in version 14.

The problem with "auto" was that it was using the time zone abbreviation (like EDT) detected from the browser by javascript. This abbreviation was applied no matter what time of year an event was set for so daylight savings time problems resulted.

The fix tries to convert the abbreviation into the full timezone name (like America/New_York), which changes along with daylight savings time and so should resolve this issue.

Regards,

lindon