-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] (CalDav): Last occurrence date is not calculated properly on recurring events #45489
Comments
Confirmed. Tested using a every 2 days event that was recurring for two weeks, then cancelling the event after the second occurrence had passed. |
Determined Cause. The cause is the parseEventForOrganizer function in sabre/vobject/lib/ITip/Broker class that generates the iTip messages. The function does not include the RRULE parameter as part of the iTipMessage->message->VEVENT that is sent to the scheduler. Therefore the last occurrence cannot be calculated properly. Possible fixes...
|
#47998 is in so this can be resumed |
Confirmed fixed with #48583 RRULE is now present when cancelling an event series after the first occurance. |
The last occurrence date is NOT calculated properly on recurring events causing notification emails for changes and cancellation not to be sent.
server/apps/dav/lib/CalDAV/Schedule/IMipPlugin.php
Lines 149 to 154 in 500a9cb
The text was updated successfully, but these errors were encountered: