Summary | Attendees not synced |
Queue | Kronolith |
Queue Version | Git master |
Type | Enhancement |
State | Accepted |
Priority | 1. Low |
Owners | |
Requester | toenjes.neuhaeusser (at) klst (dot) com |
Created | 02/15/2008 (6298 days ago) |
Due | |
Updated | 06/28/2013 (4338 days ago) |
Assigned | |
Resolved | |
Milestone | |
Patch | No |
suppose. If this feature is of high importance to you or your
organization you could consider sponsoring the feature.
Since this topic is accepted as enhancemet for a long time ago could
we get an update or state info about the plans to implement this (or
where is the problem not to get it into kronolith)?
Tanky you!
Kronolith_Driver ->fromiCalendar() is the place where is iCal embedded
in the SyncML message is decoded and saved. The function is looking
for the X-ATTENDEE element instead of ATTENDEE. I don't know if that
depends in the SyncML client implementation.
Another weird thing is that toiCalendar() build the iCal message using
ATTENDEE.
I've fixed the problem replacing X-ATTENDEE with ATTENDEE. What do you
think about? Shall we look for both elements?
If not, I'll start to work on it.
ticket #3965.Version ⇒ Git master
State ⇒ Accepted
Type ⇒ Enhancement
Priority ⇒ 1. Low
happen. The creator field that we currently have is bound to horde
user names.
Queue ⇒ Kronolith
State ⇒
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Attendees not synced
Queue ⇒ Synchronization
State ⇒ Unconfirmed
Kronolith and Outlook 2003 in terms of Funambol 6.5.7. It does not
matter whether the event is transfered from outlook to horde or vice
versa.