Could you confirm that this code works for you? I think it should work with SabreDAV 2.1 as well as any newer version.

$is_dir = !empty($props['{DAV:}resourcetype']) && count($props['{DAV:}resourcetype']->getValue()) > 0;

I'm trying to tell you that your patch is not acceptable because it does not work with Kolab's WebDAV server (and maybe others). From the debug you provided I see that it might be a Sabre compat. issue. For me it is different:

Sabre\DAV\Property\ResourceType::__set_state(array(
   'resourceType' => array (
      0 => '{DAV:}collection',
    ),
))

What version of SabreDAV do you have installed?

However, I don't get it. Does that mean that OwnCloud returns set-but-empty DAV:resourcetype for folders? Could you provide sample owncloud response? Or, is commit d1342141be6 working for you?

Proposed solution does not work with Kolab's WebDAV implementation (iRony). However, indeed standard says that files have no contenttype, so I'm going to fix it anyway.

Case 1 is already implemented.

It's part of Kolab 16.

Fixed in be2e3f21541 [roundcubemail master].

It looks good, but I don't really know it does what it looks like it should be doing ;)

This version does not work with Roundcube 1.3.

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.

Fixed.

Please, be more clear. I don't have owncloud installation. Are you saying that it returns full folders hierarchy event if we ask for "1,noroot"? My understanding of owncloud and other dav servers was that they do (may) not support "infinity", but "1,noroot" should be supported. And this is what the rest of the code expects.

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.

No such issue on CentOS with wallace-0.8.11-7.1.el7.kolab_16.

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.

Fixed in 668ca02c3f3d8 [roundcubemail master].

Confirmed. If I then try to start wallace, I got:

2019-05-29 11:36:24,741 pykolab.wallace WARNING [10320] Could not bind to socket on port 10026 on bind address localhost
2019-05-29 11:36:24,741 pykolab.wallace WARNING [10320] Could not shut down socket
2019-05-29 11:36:25,743 pykolab.wallace WARNING [10320] Could not shut down socket
2019-05-29 11:36:26,745 pykolab.wallace WARNING [10320] Could not shut down socket
2019-05-29 11:36:27,747 pykolab.wallace WARNING [10320] Could not shut down socket
2019-05-29 11:36:28,750 pykolab.wallace WARNING [10320] Could not shut down socket
...

and

# ps ax | grep wallace
 3595 ?        S      0:00 /usr/bin/python /usr/sbin/wallaced -l warning --fork --user kolab
10320 ?        Sl     0:00 /usr/bin/python /usr/sbin/wallaced -l warning --fork --user kolab
10321 ?        S      0:00 /usr/bin/python /usr/sbin/wallaced -l warning --fork --user kolab
10322 ?        S      0:00 /usr/bin/python /usr/sbin/wallaced -l warning --fork --user kolab
10323 ?        S      0:00 /usr/bin/python /usr/sbin/wallaced -l warning --fork --user kolab
10324 ?        S      0:00 /usr/bin/python /usr/sbin/wallaced -l warning --fork --user kolab

Fixed on kolabnow.com.

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 didn't check that on Debian 8, but a few notes:

1. It's not an issue on Debian 9 indeed.
2. Roundcube will not fallback to any other method if it is configured to use pspell.

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.

I confirm. This is for the Kolab skin based on Larry. Looks like it is caused by some style in Larry. The responsive skin has no such issue.

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?

I'm unable to reproduce on current beta.kolabnow.com with Chromim 73.0.3683.86.

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.

They are not maintained and they were never supported by Kolab.

It is a "fork" that we do not manage.

But you say it's a fix. So, what exactly are you trying to fix? I don't see a problem when I use chwala with Kolab storage connected using webdav driver.

The whole point is to never use infinity. Now the procedure is recursive and we never fetch more than one level of the folder tree. Or are you saying that your webdav server does not support "1,noroot"?

Fix problem with "numeric" folders (Bifrost#T209392)