Maybe there are some of you out there, still using ownCloud 8.2.9 with the ownCloud Calendar 0.8.2. I would like to ask if you could reproduce the following behaviour. And at all users on a newer release I would like to ask you, if you could confirm the expected behaviour which is described at the end of this post.
Steps to reproduce
First, import the ics file with the following content:
BEGIN:VCALENDAR VERSION:2.0 PRODID: tronde whatsoever X-WR-CALNAME:OpenSSH2 BEGIN:VEVENT CREATED:20170311T102027 UID:firstname.lastname@example.org DTSTAMP:20170311T102027 DESCRIPTION: Testing SUMMARY:OpenSSH2 LOCATION:Chemnitz / Reichenhainer Str. 90 / Raum V4 CLASS:PUBLIC DTSTART:20170311T160000 DTEND:20170311T170000 GEO:50.813889;12.93 URL:https://chemnitzer.linux-tage.de/2017/de/programm/beitrag/274 END:VEVENT END:VCALENDAR
Please notice that DTSTART and DTEND is given in floating time according to https://icalendar.org/iCalendar-RFC-5545/3-3-5-date-time.html.
Second, export this event from ownCloud Calendar to ics file. A
diff of the original and the exported file shows:
diff OpenSSH.ics OpenSSH_oc_export.ics 3c3 < PRODID: tronde whatsoever --- > PRODID:ownCloud Calendar 0.8.2 14c14 < DTEND:20170311T170000 --- > DTEND:20170311T170000Z 18c18 < END:VCALENDAR --- > END:VCALENDAR \ Kein Zeilenumbruch am Dateiende.
Now, DTEND is suddenly given in utc time.
I guess the change happens during the import, already. Because if the imported event is synced with tunderbird lightning the event shows the wrong end time in the lightning calendar.
The expected behaviour is, that DTSTART and DTEND are not modified during import or export. I would like to know if newer versions of the ownCloud Calendar show the expected behaviour.
Because I'm not a native speaker, bear with me, please. If there is anything hard to understand, please ask and I would try to improve my explanation.