Summary | Syncml sync with funambol/outlook does not respect excludeDates |
Queue | Synchronization |
Queue Version | FRAMEWORK_3 |
Type | Bug |
State | No Feedback |
Priority | 2. Medium |
Owners | jan (at) horde (dot) org |
Requester | mephisto (at) gmx (dot) net |
Created | 01/27/2010 (5615 days ago) |
Due | |
Updated | 03/19/2011 (5199 days ago) |
Assigned | 10/24/2010 (5345 days ago) |
Resolved | 03/19/2011 (5199 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
State ⇒ Feedback
Version ⇒ FRAMEWORK_3
bug #8835.New Attachment: diff.txt
exchange data. If this is done, exclude dates are being sent in the form
EXDATE:20100301T170000Z;20100308T170000Z;20100315T170000Z
within the vCalendar entry.
This is similar to the format current Nokia mobiles seem to use (see
bug #8835), and is not correctly understood by Horde.I have written a patch against current cvs that transforms a string
like the above into
EXDATE:20100301T160000Z
EXDATE:20100308T160000Z
EXDATE:20100315T160000Z
which is the format Horde uses.
Note that the time setting must be changed to the beginning of the
event for horde to accept the exclusion, whereas outlook/funambol seem
to send the DTEND time.
The patch is rather dirty, but a first test shows it to be functional for me.
The reverse direction (from horde to outlook/funambol) is still missing.
Assigned to Jan Schneider
State ⇒ Assigned
New Attachment: outlook-funambol-excludedate-example.txt
State ⇒ Feedback
Milestone ⇒
State ⇒ Unconfirmed
Patch ⇒ No
Queue ⇒ Synchronization
Summary ⇒ Syncml sync with funambol/outlook does not respect excludeDates
Type ⇒ Bug
Priority ⇒ 2. Medium
when sending recurrent events to horde from outlook via funambol
(8.0.5) that have certain dates excluded, the exclude dates are not
passed to horde.
They appear in the data sent by the server, /tmp/sync/data.log states
<Exceptions>
<ExcludeDate>20090513T110000Z</ExcludeDate>
</Exceptions>
as part of the event in question.
However, as far as I can see, Device/Sync4j.php does not contain
anything processing this information.