Recurring scheduling didn't work with non-UTC timezone
Bug #377126 reported by
Joe Tippetts
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Xibo |
Fix Released
|
High
|
Dan Garner |
Bug Description
I'm in US and had Denver time zone selected. When I tried to schedule events from AM to PM (i.e. 0800 to 1700) it was converting the times to their opposites (i.e. 2000 to 0500). When I changed my settings to use UTC, recurring event scheduling worked fine.
Using:
xibo-client-
xibo-server-
LAMP server with Apache 2.0, Ubuntu 8, mysql 5, php 5
Related branches
lp:~dangarner/xibo/bug-377126
- Xibo Maintainters: Pending requested
-
Diff: 11 lines1 file modifiedserver/lib/js/schedule.js (+0/-2)
description: | updated |
Changed in xibo: | |
status: | Confirmed → Fix Committed |
Changed in xibo: | |
status: | Fix Committed → Fix Released |
Changed in xibo: | |
status: | Fix Released → Confirmed |
status: | Confirmed → Fix Released |
To post a comment you must log in.
Hi tipjoe,
Could you just confirm something for me?
- Your Ubuntu server is set to the Denver time zone
- Your Xibo admin interface is set to the Denver time zone
- Your client PC is set to the Denver time zone
I think there may be a few inconsistencies in the way Xibo is working with dates...
The Start and End time you enter for an event will be recorded in the DB with no conversion at all (meaning the dates you put in will be considered as the same time zone as the server).
The Start and End times of all the recurring events you set will be compared against the time zones of the server and the Xibo time zone setting.
On the way out (when you look in the calendar) these dates are pulled back out and presented exactly as they were recorded - therefore highlighting the problem.
I'll be looking into this further - with a view to improving it for the 1.0 Series - hopefully its not a massive change!
If you could confirm your exact settings for the above that would be very helpful! Thanks