| Summary | Exception Support in recurrent types |
| Queue | Synchronization |
| Type | Enhancement |
| State | Resolved |
| Priority | 1. Low |
| Owners | jan (at) horde (dot) org |
| Requester | almarin (at) um (dot) es |
| Created | 3/10/09 (6239 days ago) |
| Due | |
| Updated | 10/1/09 (6034 days ago) |
| Assigned | 3/10/09 (6239 days ago) |
| Resolved | 10/1/09 (6034 days ago) |
| Milestone | 3.3.6 |
| Patch | Yes |
State ⇒ Resolved
Milestone ⇒ 3.3.6
State ⇒ Assigned
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ Exception Support in recurrent types
Queue ⇒ Synchronization
Milestone ⇒
Patch ⇒ Yes
New Attachment: Sync4j.php.patch
State ⇒ New
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