Tickets :: [#950] iCalendar export problems with recurring events

6.0.0-beta1

7/11/25

Summary	iCalendar export problems with recurring events
Queue	Kronolith
Queue Version	2.0-RC2
Type	Bug
State	Resolved
Priority	1. Low
Owners	chuck (at) horde (dot) org
Requester	kevin_myer (at) iu13 (dot) org
Created	12/08/2004 (7520 days ago)
Due
Updated	11/04/2007 (6459 days ago)
Assigned	12/18/2004 (7510 days ago)
Resolved	12/18/2004 (7510 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

11/04/2007 05:11:28 PM	thomas (dot) vogel (at) power-waves (dot) net	Comment #7	Reply to this comment
Hi there, I still experienced problems with importing ics Files into Kronolith (also non-all day events). It seems that all end dates are set to "never" - looking at today's calendar lets me see all recurring events I ever had on a Sunday or on a 4th of November... Greetings, Tom Looks like this was only with all day events - should be fixed now. If that doesn't match your experience, there may be something else to look in to - let me know.

12/18/2004 04:38:44 AM	Chuck Hagenbuch	Comment #6 State ⇒ Resolved	Reply to this comment
Looks like this was only with all day events - should be fixed now. If that doesn't match your experience, there may be something else to look in to - let me know.

12/18/2004 02:00:50 AM	Chuck Hagenbuch	Comment #5 State ⇒ Assigned	Reply to this comment
I haven't found the pattern yet, but I can still find some bad dates also. Re-opening, will investigate.

12/17/2004 03:22:48 PM	kevin_myer (at) iu13 (dot) org	Comment #4	Reply to this comment
I believe there is still an issue somewhere, with RC3. I exported my calendar from my main site, created a fresh database (because the main site has been migrated from HEAD to ALPHA to RC1, 2, and 3 and datatree and categories stuff is all messed up) and imported the calendar. Each day in December has 11 recurring events. Some recurring events in December don't show at all because they've got exported values like: BEGIN:VEVENT DTSTART;VALUE=DATE:00000000 DTEND;VALUE=DATE:00000000 DTSTAMP:20041217T124915Z UID:kronolith:4b9ad418f4a7b9ec6cfe96c0c8ad890a SUMMARY:Exchange Day DESCRIPTION: CATEGORIES:Business LOCATION: TRANSP:OPAQUE ORGANIZER;CN=Kevin M. Myer:MAILTO:kevin_myer@iu13.org EXDATE;VALUE=DATE:00000000 END:VEVENT That particular event has no recurrence, starts on December 27 at 12:00AM and ends on December 28 at 12:00AM but the iCalendar file does not reflect that at all. At one point, the Horde Framework code was distributed separately but that appears to have been rolled back into the release. I thought perhaps old calendar code was getting included but it looks like the include path is set to search the local Horde install, and then whatever include_path is set to, so it should find new code first, right?

12/11/2004 04:11:30 PM	Chuck Hagenbuch	Comment #3 State ⇒ Resolved	Reply to this comment
It appears I did. Resolving!

12/11/2004 03:40:26 PM	Jan Schneider	Comment #2 Assigned to Chuck Hagenbuch State ⇒ Assigned	Reply to this comment
Chuck, did you fix this with the pre-RC3 iCal fixes?

12/08/2004 02:41:25 PM	kevin_myer (at) iu13 (dot) org	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ iCalendar export problems with recurring events Queue ⇒ Kronolith State ⇒ Unconfirmed	Reply to this comment
Wanted to submit this earlier but didn't get around to it. I see RC3 is out now but I haven't had a chance to download all compontents and test. If you export your calendar in iCalendar format, and the calendar contains recurring events, the DTSTART, DTEND, and UNTIL options under RRULE have a date value of 00000000. This breaks recurrence when importing it into something like Apple's iCal, or importing back into Kronolith. Example output: BEGIN:VEVENT DTSTART;VALUE=DATE:00000000 DTEND;VALUE=DATE:00000000 DTSTAMP:20041208T142939Z UID:kronolith:28f194619b2db9a82498920e1a9c66f5 SUMMARY:Floater Holiday DESCRIPTION:Choice of 27th, 28th, 29th, or 30th. CATEGORIES:Business LOCATION: TRANSP:OPAQUE ORGANIZER;CN=Kevin M. Myer:MAILTO:kevin_myer@iu13.org RRULE:FREQ=DAILY;INTERVAL=1;UNTIL=00000000 END:VEVENT Will test with RC3 as soon as I can - not sure if this is handled in Kronolith or in one of the framework classes.