[GH-ISSUE #388] Issue on recurring events with COUNT != 0 ? #370

Closed
opened 2026-02-25 20:31:30 +03:00 by kerem · 5 comments
Owner

Originally created by @armoisan on GitHub (Apr 5, 2023).
Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/388

Hello,

by playing with sabre/dav server and caldavsynchronizer 4.4.0 on outlook (Microsoft® Outlook® LTSC MSO (16.0.14332.20478) 64 bit) , the recurring events with RRULE:FREQ=DAILY;COUNT=xxx seem to be considered with no end date in outlook.

Could it be a problem of the format of the events or an issue from to the latest modification done in 4.4.0 related to the NoEndDate ?

Originally created by @armoisan on GitHub (Apr 5, 2023). Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/388 Hello, by playing with sabre/dav server and caldavsynchronizer 4.4.0 on outlook (Microsoft® Outlook® LTSC MSO (16.0.14332.20478) 64 bit) , the recurring events with RRULE:FREQ=DAILY;COUNT=xxx seem to be considered with no end date in outlook. Could it be a problem of the format of the events or an issue from to the latest modification done in 4.4.0 related to the NoEndDate ?
kerem closed this issue 2026-02-25 20:31:30 +03:00
Author
Owner

@aluxnimm commented on GitHub (Apr 5, 2023):

You are right, we fixed the UNTIL handling but broke the COUNT it seems. Need to look into it. Thanks for reporting!

<!-- gh-comment-id:1497299058 --> @aluxnimm commented on GitHub (Apr 5, 2023): You are right, we fixed the UNTIL handling but broke the COUNT it seems. Need to look into it. Thanks for reporting!
Author
Owner

@aluxnimm commented on GitHub (Apr 6, 2023):

fixed in 4.4.1.

<!-- gh-comment-id:1498847007 --> @aluxnimm commented on GitHub (Apr 6, 2023): fixed in 4.4.1.
Author
Owner

@armoisan commented on GitHub (Apr 6, 2023):

hello, thanks a lot for this quick fix

<!-- gh-comment-id:1498986531 --> @armoisan commented on GitHub (Apr 6, 2023): hello, thanks a lot for this quick fix
Author
Owner

@Jisco commented on GitHub (Sep 26, 2024):

Hi,
I don't know exactly whether my error is related to this, but if I create a recurring appointment and set it to end after X appointments, it now works (with Version 4.4.1). But as soon as I edit this appointment somehow, this information is lost and the appointment becomes "infinite" again.

<!-- gh-comment-id:2376829708 --> @Jisco commented on GitHub (Sep 26, 2024): Hi, I don't know exactly whether my error is related to this, but if I create a recurring appointment and set it to end after X appointments, it now works (with Version 4.4.1). But as soon as I edit this appointment somehow, this information is lost and the appointment becomes "infinite" again.
Author
Owner

@Jisco commented on GitHub (Sep 30, 2024):

Created new Issue: #434

<!-- gh-comment-id:2382184777 --> @Jisco commented on GitHub (Sep 30, 2024): Created new Issue: #434
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/outlookcaldavsynchronizer#370
No description provided.