| Summary | Task synchronization from DavX5 causes DTSTART rewrite to UTC |
| Queue | Horde Groupware |
| Queue Version | 5.2.22 |
| Type | Bug |
| State | Unconfirmed |
| Priority | 2. Medium |
| Owners | |
| Requester | horde (at) 2600 (dot) sk |
| Created | 07/22/2020 (1822 days ago) |
| Due | |
| Updated | 04/19/2021 (1551 days ago) |
| Assigned | |
| Resolved | |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
It rewrites the whole task caldav item from database content. The
database does not currently save the event's timezone(s).
So it reads in DTSTART;TZID=Europe/Vienna:20200722T160000 and saves
that - correctly, if I understand your report.
And it writes out DTSTART:20200722T140000Z, which is also correct.
This is form 2 https://tools.ietf.org/html/rfc5545#section-3.3.5
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Task synchronization from DavX5 causes DTSTART rewrite to UTC
Queue ⇒ Horde Groupware
Milestone ⇒
Patch ⇒ No
tasks to UTC and disregards the original timezone, for example:
data sent to Horde:
...
DTSTART;TZID=Europe/Vienna:20200722T160000
...
gets immediately rewritten to:
...
DTSTART:20200722T140000Z
...
and then synced back to the external client
I don't understand why Horde rewrites the timezone.
The timezone set in Horde settings matches the timezone of the
external calendar.
Is it possible for horde to leave the timezone as is when synchronizing tasks?