This feature has ever had many limitations and inconsistent
behaviour depending if the user is logged in or not.
Also in meantime, PHP's mail() support has been removed
from Roundcube Framework.
Now to enable the feature you have to set calendar_itip_smtp_server option.
Summary:
When a recurring event start date does not match a recurrence pattern
(e.g. an event recurring on Fridays is created on Thursday),
we move the start date to the date of the first occurrence.
There's also a checkbox to keep the old behavior where the
start date was not modified.
Reviewers: vanmeeuwen
Reviewed By: vanmeeuwen
Differential Revision: https://git.kolab.org/D536
Summary: With Roundcube version 1.3, the default Larry theme receives a small face-list. This change adapts the styles of the calendar and tasklist plugins to tat.
Reviewers: machniak
Differential Revision: https://git.kolab.org/D423
When handling an iTip request for an updated event where
start or end date has been changed, user will be able to change
his participant status.
In such cases we display RSVP buttons instead of "Update in my calendar"
button and highlight the event date.
So, e.g. if you accepted the event and then its time has been
changed by the organizer, you will be able to decline it or vice-versa.
A participant can accept an invitation via link. This works fine
for initial invitation. However, if there is any update for the event
in another invitation request, the event in participant's calendar
was not updated.
Example scenario:
- an organizer invites a participant for specified date/time
- a participant declines the invitation (he's busy on that time),
the event in participant's calendar will be created
- an organizer updates the event with another date/time
- a participant now accepts the modified event, the event should
be updated with the new date/time.
- In event preview display organizer (if its different than the current user)
- In event edit make sure the organizer is listed on organizer identities selector
in Attendees tab
Fixes bug where exceptions could be lost when editing
non-first occurence of a recurring event.
Also fixes bug where recurrent event update could
unintentionally change start date of the main event
when non-first occurence was selected for edition.
