Syncing event with exclusion date in recurrence

ed44 2020-08-25 14:44:39 UTC #1

Hi,
I’m experiencing problem with exclusion dates in a recurrent event.
The recurrent event sync well (Thunderbird or DavX5), but when I delete one occurrence of the serie, this one is not properly synced.
I’m using Egroupware Community 20.1.20200818 and Thunderbird 78.1.1 (32bits) , DavX5 2.2.1
Have you experienced the same problem and how can I fix it ?
Best regards.
ED

RalfBecker 2020-09-01 18:26:05 UTC #2

Where did you delete the exception when it does not sync, on TB or EGroupware?

Ralf

ed44 2020-09-02 09:06:44 UTC #3

Hi Ralf
I delete the exception in Egroupware.
Eric

ed44 2020-12-17 16:17:37 UTC #4

Hi,
I upgrade to Community 20.1.20201202 and the problem still occurs. But with an “all day” recurrence, the problem disappear. The exception date is well treated.
I suggest it’s due to a mismatch start value of “EXDATE” ?
Here is a .ICS export :
[…]
BEGIN:VEVENT
EXDATE;TZID=Europe/Paris:20201216T143000
NOTIFY_EXTERNALS:no
SUMMARY:recur 2
DTSTART;TZID=Europe/Paris:20201215T133000
DTEND;TZID=Europe/Paris:20201215T143000
RRULE:FREQ=DAILY;UNTIL=20201218T133000Z
PRIORITY: 5
[…]
Is it a bug ?
Eric

StefanU 2020-12-17 19:31:44 UTC #5

Hi Eric.

Please try with

Stefan

ed44 2021-01-13 13:06:04 UTC #6

Hi,
I’m happy to say my problem is solved. It was due to TimeZone configuration.
Now this config works well

lattest community version,
host timezone = UTC
docker container = UTC
php.ini = Europe/Paris
phpgwapi.server_timezone = Europe/Paris in egw_config table
préferences = Europe/Paris
Tested with Thnuderbird 78.1.1 ans DavX5 3.3-ose
Thanks
Eric

StefanU 2021-01-13 20:35:11 UTC #7

Hi Eric,

I’m glad it’s working correctly for you now. Yes, the time zone(s) must be set correctly. Otherwise there will be strange effects.

Please mark the answer as solution. I have described how to do this:

Stefan