On Wed, 2012-07-04 at 12:50 +1200, Jane Atkinson wrote:
I think I've found a bug in the phone@webdav configuration - not
related
to yesterday's error, I'm fairly sure.
[...]
2012-07-04 11:39:48+1200 [-] [caldav-0] [-]
[twistedcaldav.method.put_common#error] Invalid calendar data: Calendar
data had unfixable problems:
2012-07-04 11:39:48+1200 [-] [caldav-0] [VEVENT] Missing or too
many required property: DTSTAMP
I believe that I fixed that together with setting LAST-MODIFIED for the
plain text to iCalendar 2.0 conversion. Let me check...
Yes, it works. I can reproduce the problem and the recent change fixes
it. It only occurs in combination with a peer (like your phone) which
does not already include DTSTAMP in the data that it sends. Therefore I
don't see it when testing with SyncEvolution itself (which adds it when
sending).
The fix will be in SyncEvolution 1.2.99.2, which is currently undergoing
a full test run.
Thanks a lot for trying out these new features in real-world scenarios.
I have double-checked the login details. :)
;-)
I don't often create new events on the phone, which is probably
why I
only just found this one. (Also, it doesn't affect Radicale calendars.)
Apple Calendar server is more strict about checking data for validity.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.