[Syncevolution-issues] [Bug 1180] Funambol, Memotoo, ...: workaround for detached recurrences
https://bugs.meego.com/show_bug.cgi?id=1180
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends on| |23761
--- Comment #2 from pohly <patrick.ohly(a)intel.com> 2011-10-26 14:46:49 UTC ---
(In reply to comment #0)
We've had the same problem with Funambol. At that time I
didn't have an
idea, but after writing down the explanation above and thinking some
more about it, here's something that might work: when a new VEVENT gets
added in Evolution with RECURRENCE-ID for an existing, unmodified
recurring event, then modify the recurring event by adding an exception.
Then sync both the main event and the child to the server.
The CalDAV backend does this for the Maemo Calendar backend, see
"[SyncEvolution] Recurrences in Maemo 5".
The problem is that this transformation really belongs into the engine. I don't
want to add such hacks also to the EDS calendar backend. The only sane way to
solve this issue is improving the Synthesis engine so that it works with a set
of items internally, see bug #23761.
--------
Product: SyncEvolution
Component: SyncEvolution
MeeGo Release: unspecified
Severity: enhancement
Priority: Medium
Keywords:
Status: ASSIGNED
Who: patrick.ohly(a)intel.com
Assigned To: patrick.ohly(a)intel.com
Target Build: ---
Flags:
Changed: Depends on
--------
https://bugs.meego.com/show_bug.cgi?id=1180
--
Configure bugmail: https://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.