From lang at b1-systems.de Mon Apr 19 09:23:23 2021 From: lang at b1-systems.de (Ralf Lang) Date: Mon, 19 Apr 2021 11:23:23 +0200 Subject: [horde] Horde CalDAV synchronization issue In-Reply-To: <20210416161900.35854193@mastermind> References: <20210416161900.35854193@mastermind> Message-ID: Hi Jan, Am 16.04.2021 um 16:19 schrieb Jan Teluch: > Hello! > > I have submitted a bug in July last year but so far nobody replied. Would there please be anyone who could take a look at it? > The bug report is here: https://bugs.horde.org/ticket/15027 > I was also consulting this with DavX5 authors and they recommended to open an issue with Horde, as it's clearly a Horde problem that drops the timezone from the tasks for some reason, so that's what I did. > If there is anything do to help sorting the issue, just let me know. > > Thanks! > Jan See my answer in the ticket: https://bugs.horde.org/ticket/15027 The produced iCalendar is valid and should be understood correctly. Which client are you using and which problem does this generate? I think it makes sense to add a timezone field to nag_tasks. kronolith_events also has a timezone field. But this would still mean that only one timezone would be used for all date fields (start, due, completed, alarm). -- Ralf Lang Linux Consultant / Developer Tel.: +49-170-6381563 Mail: lang at b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 From horde at 2600.sk Wed Apr 21 07:44:48 2021 From: horde at 2600.sk (Jan Teluch) Date: Wed, 21 Apr 2021 09:44:48 +0200 Subject: [horde] Horde CalDAV synchronization issue In-Reply-To: References: <20210416161900.35854193@mastermind> Message-ID: <20210421094448.52573ee8@2600.sk> Hello Ralf, On Mon, 19 Apr 2021 11:23:23 +0200 Ralf Lang wrote: > See my answer in the ticket: > > https://bugs.horde.org/ticket/15027 > > The produced iCalendar is valid and should be understood correctly. > Which client are you using and which problem does this generate? I am using DAVx5 (https://www.davx5.com/) and the problem is that when I create a task, when it's synced, the timezone information drops out and on the phone I see the task in the UTC timezone (the time of the task is correct, but for example if I then want to edit it, I have to either edit it with the UTC time, or I can change the timezone and set the time in my timezone, but the timezone information once again disappears after synchronization. > I think it makes sense to add a timezone field to nag_tasks. > kronolith_events also has a timezone field. > But this would still mean that only one timezone would be used for > all date fields (start, due, completed, alarm). That would be ok, I suppose that would solve my issue. > > > -- > Ralf Lang > Linux Consultant / Developer > Tel.: +49-170-6381563 > Mail: lang at b1-systems.de > B1 Systems GmbH > Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de > GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB > 3537 > P.S.: I have just realized that I have only sent this email directly to you (not sure if you have received it) so I'm resending it to the list now. Best regards, Jan Teluch From lang at b1-systems.de Thu Apr 22 05:45:21 2021 From: lang at b1-systems.de (Ralf Lang) Date: Thu, 22 Apr 2021 07:45:21 +0200 Subject: [horde] Horde CalDAV synchronization issue In-Reply-To: <20210421094448.52573ee8@2600.sk> References: <20210416161900.35854193@mastermind> <20210421094448.52573ee8@2600.sk> Message-ID: <48b1891f-8033-3ec8-ecb4-59a85089d641@b1-systems.de> Hi Jan, Am 21.04.2021 um 09:44 schrieb Jan Teluch: > Hello Ralf, > > On Mon, 19 Apr 2021 11:23:23 +0200 > Ralf Lang wrote: > >> See my answer in the ticket: >> >> https://bugs.horde.org/ticket/15027 >> >> The produced iCalendar is valid and should be understood correctly. >> Which client are you using and which problem does this generate? > I am using DAVx5 (https://www.davx5.com/) and the problem is that when I create a task, when it's synced, the timezone information drops out and on the phone I see the task in the UTC timezone (the time of the task is correct, but for example if I then want to edit it, I have to either edit it with the UTC time, or I can change the timezone and set the time in my timezone, but the timezone information once again disappears after synchronization. > >> I think it makes sense to add a timezone field to nag_tasks. >> kronolith_events also has a timezone field. >> But this would still mean that only one timezone would be used for >> all date fields (start, due, completed, alarm). > That would be ok, I suppose that would solve my issue. I will get back to you with a POC once I have that implemented. It may take a while, though. >> >> -- >> Ralf Lang >> Linux Consultant / Developer >> Tel.: +49-170-6381563 >> Mail: lang at b1-systems.de >> B1 Systems GmbH >> Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de >> GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB >> 3537 >> > P.S.: I have just realized that I have only sent this email directly to you (not sure if you have received it) so I'm resending it to the list now. > > Best regards, > Jan Teluch Going through the list is the right thing to do :) -- Ralf Lang Linux Consultant / Developer Tel.: +49-170-6381563 Mail: lang at b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 From horde at 2600.sk Thu Apr 22 11:40:56 2021 From: horde at 2600.sk (Jan Teluch) Date: Thu, 22 Apr 2021 13:40:56 +0200 Subject: [horde] Horde CalDAV synchronization issue In-Reply-To: <48b1891f-8033-3ec8-ecb4-59a85089d641@b1-systems.de> References: <20210416161900.35854193@mastermind> <20210421094448.52573ee8@2600.sk> <48b1891f-8033-3ec8-ecb4-59a85089d641@b1-systems.de> Message-ID: <20210422134056.1e1cefe3@mastermind> Hi Ralf, On Thu, 22 Apr 2021 07:45:21 +0200 Ralf Lang wrote: > >> I think it makes sense to add a timezone field to nag_tasks. > >> kronolith_events also has a timezone field. > >> But this would still mean that only one timezone would be used > >> for all date fields (start, due, completed, alarm). > > That would be ok, I suppose that would solve my issue. > I will get back to you with a POC once I have that implemented. It > may take a while, though. No problem, take your time, it's not really urgent :-) Best regards, Jan