Hmm,
thanks for the info ... so the question is what's the problem with the original event (why it is processed incorrectly by your server) ...
Cheers,
JM
On 9 Mar 2018, at 20:56, Johan Vromans jvromans@squirrel.nl wrote:
Hi Jan,
On Thu, 8 Mar 2018 12:19:34 +0100, Ján Máté jan.mate@inf-it.com wrote:
When I download the calendar ics directly from the DAViCal server (788 events), the missing event is there:
BEGIN:VEVENT CREATED:20170103T111640Z LAST-MODIFIED:20171221T212825Z DTSTAMP:20171221T212825Z UID:a80d59e0-a0a8-47d8-a6d1-2bf4d5cefa48.1483442200530 SUMMARY:Inhalers vervangen RRULE:FREQ=DAILY;INTERVAL=30;UNTIL=20181231T000000Z EXDATE;VALUE=DATE:20161203 TRANSP:OPAQUE STATUS:CONFIRMED CLASS:PUBLIC DTSTART;VALUE=DATE:20161203 DTEND;VALUE=DATE:20161204 DURATION:P1D SEQUENCE:1 END:VEVENT
I tested the RRULE value using https://jakubroztocil.github.io/rrule/#rfc-input https://jakubroztocil.github.io/rrule/#rfc-input and it ("FREQ=DAILY;INTERVAL=30;UNTIL=20181231T000000Z") looks OK, but what is confusing for me is the "DTEND;VALUE=DATE:20161204" ... so the question is whether the problem is in your server or in the DTEND value (I'm not sure). Please try to check the RFC and if the DTEND is the problem you can fix it manually, if not then please contact the server developer.
Using InfCloud, I created a new event. This is how it looks:
BEGIN:VEVENT CREATED:20180307T162953Z LAST-MODIFIED:20180307T163021Z DTSTAMP:20180307T163021Z UID:iq1kydmv-4iuf-0tpv-lirk-vws61ol5xaee SUMMARY:Inhalers vervangen RRULE:FREQ=DAILY;INTERVAL=30 TRANSP:OPAQUE CLASS:PUBLIC DTSTART;VALUE=DATE:20180307 DTEND;VALUE=DATE:20180308 END:VEVENT
It has the same DTEND value.
(This event *does* show on all clients.)
-- Johan