[kronolith] Recurring events with RDATE
Jan Schneider
jan at horde.org
Mon Jan 22 10:54:45 UTC 2018
Zitat von Jens Wahnes <wahnes at uni-koeln.de>:
> Michael J Rubinsky wrote:
>>
>> Quoting Jens Wahnes <wahnes at uni-koeln.de>:
>>
>>> When trying to import an event from an ICS file that uses RDATE to
>>> define multiple occurrences of that event, only the "first" event
>>> is shown in Kronolith. That is, the later dates where the event
>>> is to reoccur are silently dropped upon import. It seems that
>>> Kronolith does not support recurring events that do not follow a
>>> regular scheme (e.g. weekly or bi-weekly, defined via RRULE in an
>>> ICS file). Is that observation correct? I couldn't find a way to
>>> create such events (non-RRULE reoccuring events) in the GUI, so it
>>> might be obvious that Kronolith does not support this, but then I
>>> also might be missing something.
>>
>> This is correct. Kronolith, and the underlaying Horde_Date library,
>> do not currently support these type of arbitrary occurrences.
>
> Thanks for your clarification. Unfortunately, Lotus Notes seems to
> convert all recurring events (even the ones with very simple
> repetition rules, e.g. weekly) into RDATE recurring events upon
> export. So that's really annoying if one uses Kronolith and has to
> arrange a series of events with Lotus Notes users.
I'm not surprised. Notes is traditionally one of the worst pieces of
groupware available.
>>> On a side note, I noticed that when IMP displays an email with an
>>> invitation to a recurring (RRULE) event, there is a printf
>>> placeholder "%x" in the event preview that is not filled. See the
>>> attached image for an example. Is this a known bug or should I
>>> report this to the bug tracker?
>>
>> Yes, please report this bug in the tracker and be sure to include
>> the version numbers of the installed applications.
>
> https://bugs.horde.org/ticket/14768
>
>
>
> Jens
--
Jan Schneider
The Horde Project
https://www.horde.org/
More information about the kronolith
mailing list