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.
Use window.history.replaceState on folder selection, the same way
is in Roundcube core.
Conflicts:
plugins/kolab_files/kolab_files.js
plugins/kolab_files/lib/kolab_files_engine.php
There was already a code to do this, but it didn't work for all cases.
E.g. it didn't work when you created an event with resources assigned, but no other attendees.
Summary:
1. "Previous Slot" action moves the selection box to the beginning of the time slot not the end.
It looked to me as an obvious mistake.
2. Both "previous slot" and "next slot" move the selection box in intervals defined in calendar_timeslots
option instead of one hour. I.e. it will be one hour, 30 minutes, 20 minutes, 15 minutes or 10 minutes,
depending what's configured in Preferences > Calendar > Time slots per hour.
Reviewers: #roundcube_kolab_plugins_developers
Differential Revision: https://git.kolab.org/D207
Conflicts:
plugins/calendar/calendar.php
Summary:
Actually it sets the internal end time interval to 100 years for all kind
of events. Before it was 100 for yearly events, but only 10 for weekly.
Fixes T1268.
Reviewers: #roundcube_kolab_plugins_developers
Maniphest Tasks: T1268
Differential Revision: https://git.kolab.org/D203
The issue was caused by missing event uid. On client-side all events
have had the same _id property and calendar widget couldn't properly
merge changes.
Conflicts:
plugins/calendar/drivers/kolab/kolab_user_calendar.php
