mirror of
https://github.com/aluxnimm/outlookcaldavsynchronizer.git
synced 2026-04-26 03:25:48 +03:00
[GH-ISSUE #388] Issue on recurring events with COUNT != 0 ? #370
Labels
No labels
1.0
1.0
1.0
2.0
Feature
Feature request
Google
Google Calendar
async
attachement
auto-migrated
auto-migrated
auto-migrated
bug
critical
enhancement
help wanted
implemented
pull-request
solved
solved
sourceforge
sourceforge
sourceforge
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/outlookcaldavsynchronizer#370
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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 ?
@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!
@aluxnimm commented on GitHub (Apr 6, 2023):
fixed in 4.4.1.
@armoisan commented on GitHub (Apr 6, 2023):
hello, thanks a lot for this quick fix
@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.
@Jisco commented on GitHub (Sep 30, 2024):
Created new Issue: #434