[Tickets #2530] Importing vCal saves to wrong calendar

[bugs@bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/?id=2530
-----------------------------------------------------------------------
 Ticket             | 2530
 Updated By         | tevans at tachometry.com
 Summary            | Importing vCal saves to wrong calendar
 Queue              | Kronolith
 Version            | HEAD
 State              | Assigned
 Priority           | 2. Medium
 Type               | Bug
 Owners             | Horde Developers
+New Attachment     | kronolith_import_patch.txt
-----------------------------------------------------------------------


tevans at tachometry.com (2005-10-18 19:49) wrote:

This patch corrects the calendar import problem in our environment.

I believe the $kronolith global variable gets clobbered at some point during
the import loop, although I could not track it down to actual offending line
of code. Moving the $kronolith->open(...) call into the import loop fixes
the problem by restoring the target calendar name from the session variable
just prior to constructing the new event instance.

The open(..) method appears to have some defensive code that will allow it
to reuse an existing DB connection whenever possible, so I expect only a
minor performance penalty.  While I admit this approach is a bit
heavy-handed, such is the price of using globals.

Comments and feedback welcome.

Tom Evans
Tachometry