Nov 13 2019
https://github.com/sabre-io/vobject/pull/476 fixes the issue for me.
Oct 4 2019
Fixed in d05e11f145cf.
Oct 1 2019
Sep 29 2019
Fixed in 3841f63fbd42 [roundcubemail master] and eee719e6d2f87 [roundcubemail-plugins-kolab master].
This issue is a bug in Roundcube sql cache, so is reproducible with $config['imap_cache'] = 'db' and of course only when using MySQL engine. No issue if it's set to memcache, redis or disabled.
I'm unable to reproduce on current git-master.
Sep 27 2019
Fixed in 1ddbb2bcaa1b2.
Fixed in b3b695b66d6d15.
Fixed in 58d9ed122718c.
Sep 25 2019
Fixed in ad33b48521d7.
Sep 12 2019
this is the problem. It's not reproducable at all. Nearly all of our users can do all the stuff. Only very few encounter these problems. So maybe it's a caching issue - and the settings are not repsponsible but special settings together with some special circumstances in caching.
I'm unable to reproduce any of these issues.
Sep 11 2019
Here are the preferences which cause the error. I have shortened the folder list for privacy reasons. But I think it doesn't cause the error.
Sep 10 2019
Could you provide the faulty preferences?
Sep 9 2019
In the meantime I got another issue - not with calendar but wit task plugin.
Aug 29 2019
In my case it was sufficiant to switch from German to English date format and back. Then it's possible to save events but the pop up window doen't close. It remains but without content.
For those useres affected, we could fix the problem by setting the roundcube standard date format from the German to the Englisch version. Then the save button works again. Nevertheless, those users, who did not have this problem, continue to use the German date format setting without a problem. All this on the same server and same domain.
Aug 20 2019
We are also affected.
Jul 5 2019
Confirmed with current version.
Confirmed with current git-master. On export event recurrence is not resolved to match the date filter.
Jun 11 2019
This version does not work with Roundcube 1.3.
with this version, i got error 500 to open calendar UI:
with the repo
git clone https://git.kolab.org/diffusion/RPK/roundcubemail-plugins-kolab.git
Indeed, using today's master from roundcube is working fine
You're using the outdated fork repo. The official one is here https://git.kolab.org/diffusion/RPK/repository/master/
these versions may require Roundcube from git-master.
Jun 10 2019
The issue persist for me:
Jun 7 2019
May 31 2019
I'm reopening this as there are more related issues. E.g. the Check Calendar button points to the wrong date.
This was hard to track, but fixed.
May 30 2019
This is working out of the box, but requires long-press. After a long press you can move the event. After a long press event also a handle to resize the event appears, so you can also resize the event.
I don't think we can control that with current design. For me scrolling in the dialog is consistent. Problems start when a virtual keyboard appears.
May 29 2019
exactly, this bug only occur in "all day" events.
The date and time format under Settings in Roundcube can be identical between user that have this problem and user that don't. At least at this level that does not seem to make a difference.
What is the user date and time format? You could also check what are the input arguments to parseDate() in line 169 of libcalendaring.js file. Just add console.log(this.datepicker_settings.dateFormat, date, this.datepicker_settings) a line before.
I think I saw this before, but never had time to work on this. Probably the date is handled as date-time and converted to user timezone, but should not for all-day events.
May 27 2019
I don't see it on current beta.kolabnow.com withiPone SE iOS 12.1.4. Could you re-test and provide screenshot if it's still an issue?
May 22 2019
The package was created by Thomas, but it looks he's not interested in working on this currently (or just have no time). Problem is that current calendar plugin version will probably not work with Roundcube 1.3. It also requires some manual packaging work for Elastic skin support. Also there are some known issues in the database driver noone have time to work on. From Kolab perspective we could spend that time better on other things. Maybe after the final 1.4.0 release I'll do something about the situation, but I can't promise anything.