| Summary | Exception Support in recurrent types |
| Queue | SyncML |
| Type | Enhancement |
| State | Resolved |
| Priority | 1. Low |
| Owners | Jan Schneider <jan (at) horde (dot) org> |
| Requester | almarin (at) um (dot) es |
| Created | 03/10/09 (372 days ago) |
| Due | |
| Updated | 10/01/09 (167 days ago) |
| Assigned | 03/10/09 (372 days ago) |
| Resolved | 10/01/09 (167 days ago) |
| Attachments | Sync4j.php.patch ![]() |
| Milestone | 3.3.6 |
| Patch | Yes |
State ⇒ Resolved
Milestone ⇒ 3.3.6
Assigned to Jan Schneider
State ⇒ New
New Attachment: Sync4j.php.patch
Patch ⇒ 1
Milestone ⇒
Queue ⇒ SyncML
Summary ⇒ Exception Support in recurrent types
Type ⇒ Enhancement
Priority ⇒ 1. Low
Current Sync4j device doesn't support <Exceptions> in recurrent
events. That makes duplicate events very often. It would be desirable
translate Exceptions to EXDATE iCalendar fields and vice versa.
I attach a working patch to do that at least with <ExceptionDate> xml
fields. I have addapted sif2array and array2sif to allow at least 2
levels, because <Exceptions> could contain more than one ExceptionDate.
The patch includes the one that I attached to
bug 4487