Tickets :: [#4365] Make kolab driver use a UID if it already exists when saving an event

6.0.0-beta1

7/24/25

Summary	Make kolab driver use a UID if it already exists when saving an event
Queue	Kolab
Type	Bug
State	Resolved
Priority	1. Low
Owners	wrobel (at) horde (dot) org
Requester	michael.sheldon (at) credativ (dot) de
Created	08/30/2006 (6903 days ago)
Due
Updated	05/25/2007 (6635 days ago)
Assigned	09/27/2006 (6875 days ago)
Resolved	05/25/2007 (6635 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	Yes

05/25/2007 11:31:14 AM	Gunnar Wrobel	Comment #2 State ⇒ Resolved	Reply to this comment
Fix submitted by Thomas Jarosch <thomas.jarosch@intra2net.com>. Fixed in CVS. Thanks for the report.

04/19/2007 10:04:48 PM	Jan Schneider	Assigned to Gunnar Wrobel Taken from Horde Developers Taken from Jan Schneider

09/27/2006 11:07:45 AM	Jan Schneider	Assigned to Jan Schneider Assigned to Horde Developers State ⇒ Assigned

08/30/2006 11:59:43 AM	michael (dot) sheldon (at) credativ (dot) de	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ Make kolab driver use a UID if it already exists when saving an event Queue ⇒ Kolab New Attachment: kolab_uid.patch State ⇒ Unconfirmed	Reply to this comment
When importing an iCalendar the UID of the new kronolith event is set based on the UID of the iCal event, without this group dates can't be deleted or updated correctly and can be added multiple times to the same calendar. The Kolab implementation of the kronolith Driver class doesn't take in to account the UID being set explicitly when the event is created and so it gets overwritten with a new randomly generated UID whilst being saved. The attached patch should correct this, unfortunately I'm unable to work against CVS HEAD so the patch is against stable.