[Tickets #11767] Kolab backend: All day events are not handled correctly
bugs at horde.org
bugs at horde.org
Tue Nov 27 17:12:41 UTC 2012
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/11767
------------------------------------------------------------------------------
Ticket | 11767
Created By | Thomas Jarosch <thomas.jarosch at intra2net.com>
Summary | Kolab backend: All day events are not handled correctly
Queue | Kronolith
Version | Git master
Type | Bug
State | Unconfirmed
Priority | 2. Medium
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------
Thomas Jarosch <thomas.jarosch at intra2net.com> (2012-11-27 17:12) wrote:
Hi,
all day events are not handled correctly, at least not according to
the Kolab format specification.
The Kolab definition of all day events:
--------------------------------------
<event>
<start-date>(date or datetime)</start-date>
<end-date>(date or datetime)</end-date>
</event>
-> So "start-date" and "end-date" allows "date" or "datetime" values.
Later on the format specification clarifies:
"An event without a time but with a date associated is a full day
event. Such a full day event may span
over multiple days and may have recurrences."
The earlier section "Common in Tasks and Events" is even more specific:
"The start-date is optional for tasks. For events, it is required. If
they are there, they can either have a date or a datetime as the type.
Parsing this is just a matter of looking at the length of the date
string. In the case of an all day event (floating event) the end-date
MUST be in date only format."
--------------------------------------
-> Right now kronolith saves all day events with a timestamp. Also it
fails to parse all day events from other Kolab clients correctly. We
should write out all day events with an "end-date" as "date" only.
Thomas
More information about the bugs
mailing list