| Summary | creation of events: events with daily interval + range defined end two days early |
| Queue | Kolab |
| Type | Bug |
| State | Duplicate |
| Priority | 1. Low |
| Owners | wrobel (at) horde (dot) org |
| Requester | m.gabriel (at) das-netzwerkteam (dot) de |
| Created | 02/15/2008 (6352 days ago) |
| Due | |
| Updated | 03/12/2008 (6326 days ago) |
| Assigned | 02/15/2008 (6352 days ago) |
| Resolved | 03/12/2008 (6326 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Duplicate
Bug #6377State ⇒ Assigned
Queue ⇒ Kolab
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ creation of events: events with daily interval + range defined end two days early
Queue ⇒ Kronolith
State ⇒ Unconfirmed
this is an example for a systematic error:
try to create an event, starting on the 28th of july (11am-12am),
define recurrence: daily (every day) and let it end (by date) on the
3rd of august.
this action results in the following kolab-xml file (:
<?xml version="1.0"?>
<event version="1.0">
<uid>97dbb9068aefb060e4d19e1034b527ea</uid>
<body><!--a75c305b1c0a6022--></body>
<categories></categories>
<creation-date>2008-02-15T08:28:29Z</creation-date>
<last-modification-date>2008-02-15T08:28:29Z</last-modification-date>
<sensitivity>public</sensitivity>
<product-id>Horde::Kolab</product-id>
<summary>Test</summary>
<organizer>
<display-name>Mike Gabriel</display-name>
<smtp-address>m.gabriel@das-netzwerkteam.de</smtp-address>
</organizer>
<start-date>2008-07-29T10:00:00Z</start-date>
<recurrence cycle="daily">
<interval>1</interval>
<range type="date">2008-08-01</range>
</recurrence>
<show-time-as>busy</show-time-as>
<end-date>2008-07-29T11:00:00Z</end-date>
</event>
i think, the recurrence should rather look like this:
<recurrence cycle="daily">
<interval>1</interval>
<range type="date">2008-08-03</range>
</recurrence>
something similar happens on weekly recurrences: the last recurrence
of an event is often left out, only the last-but-one event is
displayed in the calendar / stored in the xml-file.
any ideas?
mike