Libkolab plugin will contain Elastic style for all (or most) Kolab plugins
as we want to limit number of included stylesheets (and unify).
We're using less, so to build css file we require skins/elastic folder
in an appropriate place, i.e. aside of the plugins folder of this repository.
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
https://issues.kolab.org/show_bug.cgi?id=4067 and (Bifrost#TT20881)
It happens that IMAP folder may contain many objects with the same UID.
The precise reason for this is unknown, but it can be e.g. a faulty
client or an error between "create a new object instance" and "remove the
old one". It causes various issues when editing such objects.
With the change we assume that the most recent object (with max. IMAP UID)
is the one that should be used and all the older instances will be removed
automatically.
As libkolabxml does not support it at all it is a partial support.
We support most common cases of monthly recurrence with BYDAY specification,
e.g. "last/first weekday in a month", by converting BYSETPOS to BYDAY.
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
With disabled messages_cache and disabled kolab_notes plugin
Message-Id header is not FETCHed from the IMAP server.
So, in such a case member URI in the tag object will contain
message-id=mid:XXX, which causes problem when the message
is moved to another folder, because it cannot be found by this invalid message-id.
