Marten Gajda <marten(a)dmfs.org> writes:
Which client created the event initially?
From the OP:
The appointment is a repeating event, to repeat every
Starting tomorrow. Ending 2014-12-31. The appointment exists on all
clients. It is displayed in weeks 10, 12, and so on.
Using CalDAVzap I edit the first occurrence of the appointment and
change all occurrences: change the starting date to one week later. It
is now displayed in weeks 11, 13, and so on.
So the suspect is CalDAVzap. But it could very well be the case that the
appointment already was corrupt (in some way) at that time and that the
changes I made just made the corruption apparent.
Anyone has a tool to verify ics files for correctness?
Also, it would be very helpful if there was an (easy) was to show the
raw event (ics) data (or copyable url) from CalDAVzap...