mirror of
https://github.com/aluxnimm/outlookcaldavsynchronizer.git
synced 2026-04-25 11:05:56 +03:00
[GH-ISSUE #46] wrong determination of monthly recurrence rule #513
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#513
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 @aluxnimm on GitHub (Jul 14, 2015).
Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/46
Originally assigned to: @aluxnimm on GitHub.
The following recurrence rule generates wrong incidence when synced from server to client by CalDavSynchronizer:
RRULE:FREQ=MONTHLY;BYSETPOS=4;BYDAY=MO
The recurrence pattern which is produced in Outlook shows the last Monday of the month, not the 4th.
The last Monday would be:
RRULE:FREQ=MONTHLY;BYDAY=-1MO
Steps to reproduce:
Original comment by: mawinkler
Original Ticket: outlookcaldavsynchronizer/46
@aluxnimm commented on GitHub (Jul 14, 2015):
Further information: The whole thing works if you use Sogo as server.
Sogo produces the following rule:
RRULE:FREQ=MONTHLY;BYDAY=4MO
whereas GroupOffice creates this one:
RRULE:FREQ=MONTHLY;BYSETPOS=4;BYDAY=MO
I think both are valid.
Original comment by: mawinkler
@aluxnimm commented on GitHub (Jul 14, 2015):
Since SOGo doesn't use that, I didn't implement it. Will be fixed in next commits.
Original comment by: aluxnimm
@aluxnimm commented on GitHub (Jul 14, 2015):
Original comment by: aluxnimm