6.0.0-beta6
▾
Tasks
New Task
Search
Photos
Wiki
▾
Tickets
New Ticket
Search
dev.horde.org
Toggle Alerts Log
Help
4/10/26
H
istory
A
ttachments
C
omment
W
atch
Download
Comment on [#1365] end date for recurring events not supported
*
Your Email Address
*
Spam protection
Enter the letters below:
. .. ,.__ . .. . |\ | \./ [__)|\/|| | | \| | | | ||__|
Comment
> When importing from ICalendar files, Kronolith ignores the end date > 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
Attachment
Watch this ticket
N
ew Ticket
M
y Tickets
S
earch
Q
uery Builder
R
eports
Saved Queries
Open Bugs
Bugs waiting for Feedback
Open Bugs in Releases
Open Enhancements
Enhancements waiting for Feedback
Bugs with Patches
Enhancements with Patches
Release Showstoppers
Stalled Tickets
New Tickets
Horde 5 Showstoppers