5 Mar
2014
5 Mar
'14
2:52 p.m.
Am 05.03.2014 13:41, schrieb Johan Vromans:
Marten Gajda <marten(a)dmfs.org> writes:
So it's the same file that has been retrieved by CalDAV-Sync. I'll have
to think about what's the best way to handle an event like this. I
wonder how iOS was able to determine the right event. Maybe they just
ignore additional VEVENTs with UIDs that don't match the original UID. I
guess that would be the best way. But I wonder which of those UIDs was
the original one. None of them matches the file name.
Which client created the event initially?
cheers
Marten
--
Marten Gajda
Schandauer Straße 34
01309 Dresden
Germany
tel: +49 177 4427167
email: marten(a)dmfs.org
twitter: twitter.com/dmfs_org
VAT Reg. No.: DE269072391
the file you sent me is definitely broken. It
contains two VEVENTs
with different UIDs, which is not allowed in CalDAV:
BEGIN:VEVENT
...
UID:8xgll0ja-tmwa-uubj-n5fo-cnngv7hgkx5w
....
END:VEVENT
BEGIN:VEVENT
...
UID:jgp2g2m2-yc1t-bgl4-817g-s3ynu2aub2sr
...
END:VEVENT
PRODID:-//Inf-IT//CalDavZAP 0.10.0.2//EN
How exactly did you export/download that file?
wget --password 'xxxx'
http://jv@davical.squirrel.nl/caldav.php/jv/joan/e8a9ff60ab4f01ce92cde275d9…
I got the url by using the HTML element inspector of Google-Chrome.
-- Johan