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

bugs at bugs.horde.org bugs at bugs.horde.org
Fri Dec 17 07:22:49 PST 2004


DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=950
-----------------------------------------------------------------------
 Ticket     | 950
 Updated By | kevin_myer at iu13.org
 Summary    | iCalendar export problems with recurring events
 Queue      | Kronolith
 Version    | 2.0-RC2
 State      | Resolved
 Priority   | 1. Low
 Type       | Bug
 Owners     | Chuck Hagenbuch
-----------------------------------------------------------------------


kevin_myer at iu13.org (2004-12-17 07:22) wrote:

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 at 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?





More information about the bugs mailing list