| Summary | end date for recurring events not supported |
| Queue | Kronolith |
| Queue Version | 2.0.2 |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | Horde Developers (at) , chuck (at) horde (dot) org |
| Requester | gauret (at) free (dot) fr |
| Created | 02/13/2005 (7454 days ago) |
| Due | |
| Updated | 04/22/2005 (7386 days ago) |
| Assigned | 02/14/2005 (7453 days ago) |
| Resolved | 04/22/2005 (7386 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
Assigned to
State ⇒ Assigned
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ end date for recurring events not supported
Queue ⇒ Kronolith
for recurring events. Example :
BEGIN:VEVENT
DTSTAMP:20050213T151539Z
CREATED:20050213T151408Z
SEQUENCE:2
LAST-MODIFIED:20050213T151536Z
SUMMARY:test recurring event
CLASS:PUBLIC
PRIORITY:3
RRULE:FREQ=DAILY;UNTIL=20050218;INTERVAL=1
DTSTART;VALUE=DATE:20050214
DTEND;VALUE=DATE:20050215
TRANSP:OPAQUE
END:VEVENT
This event is supposed to happen every day (INTERVAL=1) until
2005-02-18. The UNTIL statement is ignored by Kronolith, and thus the
events happens every day from day start.
This statement is part of the iCalendar standard as defined in RFC 2445 :
http://www.faqs.org/rfcs/rfc2445.html
See paragraph 4.3.10 about recurring events.
It would be nice if COUNT statements were also supported.
I'm not sure if this sould be filed as bug or enhancement, but since
those statements are part of the standard, I chose bug.
Thanks