Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
0013804: Timezone Issues with TbSync #6827
Reported by estradis on 21 Mar 2018 19:30
Version: 2018.02.2 Community Edition
This issue is forwarded from another issue at jobisoft/TbSync#45 (comment).
Here is the summary from the other issue:
"Tine will use the LOCAL time of the event in the global view, which is not clever. Thunderbird always calculates the time of the event in the default timezone of the user and only displays the timezone specific time in the edit window (as Tine does)."
Steps to reproduce: Steps to reproduce this issue can be seen at jobisoft/TbSync#45 (comment)
Additional information: If you want to test with tbsync Plugin, always use the newest version at https://github.com/jobisoft/TbSync/releases. The author did a lot of changes which are not published at mozilla yet.
Comment posted by pschuele on 19 Apr 2018 14:26
hi estradis, thanks for the report. what is the advantage of using tbsync over the stock thunderbird/lightning sync?
I'm not sure about this:
i'll pass this to Cornelius as TZ is his special area ;)
Comment posted by jobisoft on 27 Apr 2018 07:54
Hi, I am the author of TbSync.
Lightning is using the CALDAV protocol to sync, TbSync is using EAS. For me, the advantage is the simplified setup process, you get task, events contacts in one go. Also I do not like the SOGo connector (which you need to get contacts via CARDDAV).
"Tine does not obey incoming timezones" means, that it will set incoming events (synced from client to Tine) always to the default timezone of the user (set up in the Tine 2.0 webinterface) and does not use the timezone of the event itself. This is not limited to TbSync but any EAS cleint I used to test Tine.
Comment posted by jobisoft on 27 Apr 2018 11:15
Let me give more details.
First of all, in the view layer, tine can do whatever it wants. If it wants to display an event, which is set to Moscow timezone in Berlin timezone, because that is the default timezone of the user, it can do that.
However, it should not CHANGE the timezone data field of the event from Moscow to Berlin. This is what tine is doing. If I sync an event with timezone set to Moscow from a client to Tine, and than look at another client, how this event comes back, it will have the timezone set to Berlin. I think, this is wrong.
The other issue is more within tine itself. If you create an event in Tine, it is using the default timezone, This way you can create multiple events with different timezone settings by changing the default timezone for each event. In the global view, all those events are shown in their LOCAL timezone, and not in a common timezone. Since the global view does not have any timezone identification, you cannot tell, when an event is actually occurring.
This image is an example: https://user-images.githubusercontent.com/5830621/37649582-822f2da6-2c32-11e8-9b61-ae4015a5c4e4.png
The two events have different timezones, which is fine. One at 9:00 Moskow time (5:00 UTC) and one at 11:00 Rome time (9:00 UTC). The global view is misleading. Both times should be converted to a common timezone (for example the default timezone) .
I think the title of this issue is not correct, both issues are issues with Tine 2.0
If you need further information, I will be happy to assist.