-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Events wrongly synchronized #41
Comments
Addtionally it looks like a synchronized thunderbird shows the appointment at the right time, but the reminder is shown 2h after the appointment. |
It really looks wired what happens here and the appointments get moved and shown at the wrong times. |
it looks like some calendar things come from caldav sync with thunderbird:
I've checked the lines in tine20_cal_attendee - there is a user_id; so I don't really understand the meaning of this log |
I've compared what Outlooks sends for timezone and what is generated by tine:
tine:
old tine genarted sth similar to outlook:
|
patching vendor/metaways/timezoneconvert/lib/TimeZoneConvert/VTimeZone.php with hardcoded old values solves the problem with thunderbird, OpenSync, ... The newer strange definition does not work correctly! |
what exact version of tine are you using? our unittests look normal, here the output from
|
this is Version: Ellie (2023.11.8) (latest official release) it worked in Version 15.3 which I used before and broke after the update. |
from the other ticket i learned you're using php 8.2. tine supports 8.1 only atm.
|
if you want to try: |
fix is incoming ... |
I'm facing the fact, that some appointments, created in tine are wrongly synchronized.
If the appointment is at 13:00, the synchronized time is set to 14:00 (e.g. opensync on android).
This happens since the update to the newer versions.
Looking into the caldav entry, the data looks good so far, but I can see, there is a timezone definition added to every calendar entry.
Due to RFC7809 4.3:
3. Clients can expect servers not to include standard time zone
definitions in any iCalendar data they receive from the server,
if there is no "CalDAV-Timezones" request header field in the
HTTP request. Clients MUST retrieve standard time zone
definitions either from its own cache of standard time zones or
from the set of time zone distribution servers advertised by the
CalDAV server (see Section 3.1.2).
The calendar entry should not contain this data.
The text was updated successfully, but these errors were encountered: