| Summary | shared calendars: users' timezones are not really respected |
| Queue | Kronolith |
| Queue Version | HEAD |
| Type | Enhancement |
| State | Resolved |
| Priority | 1. Low |
| Owners | jan (at) horde (dot) org |
| Requester | andrew.nau.ua (at) gmail (dot) com |
| Created | 01/04/2008 (6413 days ago) |
| Due | |
| Updated | 10/22/2008 (6121 days ago) |
| Assigned | |
| Resolved | 10/22/2008 (6121 days ago) |
| Milestone | |
| Patch | No |
Assigned to Jan Schneider
State ⇒ Resolved
a bug. I was sure we already had a ticket for this in the tracker,
but obviously not.
Times and dates are stored timezone dependent in the backend. This is
legacy cruft from old Kronolith versions that didn't even have
timezone support at all. With Kronolith 3 this is going to change,
dates will be stored in UTC.
Thanks, but this does not appear to work properly yet in 3.0-cvs. I
have downloaded kronolith-HEAD-2008-01-04.tar.gz, installed it and
found old behavior unchanged; the limitation is still there. Are there
any release plans publicly available?
Priority ⇒ 1. Low
State ⇒ Accepted
Type ⇒ Enhancement
a bug. I was sure we already had a ticket for this in the tracker, but
obviously not.
Times and dates are stored timezone dependent in the backend. This is
legacy cruft from old Kronolith versions that didn't even have
timezone support at all. With Kronolith 3 this is going to change,
dates will be stored in UTC.
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ shared calendars: users' timezones are not really respected
Queue ⇒ Kronolith
State ⇒ Unconfirmed
collection on freebsd. it seems i've found a bug in shared calendar
feature: users' timezones are not really respected. suppose a user
with timezone America/New_York creates a new event that lasts from 7am
till 8am. when another user, whose timezone is Europe/Prague, looks at
the calendar, he sees 7am-8am, which is not correct. It should be
1pm-2pm. timezone of the user who creates an event and timezone of the
user who views an event must be respected.