Wed, May 22
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.
Tue, May 21
Hi, thanks for the update.
Bugs logged there are not considered here, they need to be logged here.
Mon, May 20
Apr 13 2019
I think we'd need a change around https://git.kolab.org/diffusion/C/browse/master/lib/api/common.php$237, but I didn't think about it yet.
I did some debugging in the seafile_file_storage class.
Apr 12 2019
$config['fileapi_sources'] = array( 'Seafile' => array( 'driver' => 'seafile', 'host' => 'seacloud.cc', // when username is set to '%u' current user name and password // will be used to authenticate to this storage source 'username' => '%u', ) ); // You can also add $config['fileapi_backend_storage_disabled'] = true;
Okay I’ll take a look on it later. I guess it’s this part:
That scenario is not supported because you can't store config and you can't use cache without kolab backend. You could probably live without these in some setups, so yes in theory it should work. There must be a bug somewhere.
Hmmm But in theory it could work. I get the list of repositories. Chwala works correctly and lists all folders. Just kolab_files doesn’t get over it and doesn’t request the subfolders of each repo which is presented. BTW the files on the roots of each repo are shown as well.
... and we should throw an error when fileapi_backend != 'kolab'.
I think we should finally remove that section from documentation. It is not supported scenario, I think it is not even supposed to work. There's a comment in sample config:
// Main files source, backend driver which handles // authentication and configuration of Chwala // Note: Currently only 'kolab' is supported $config['fileapi_backend'] = 'kolab';
Basically exactly like described in the howto: https://docs.kolab.org/howtos/use-seafile-with-chwala.html?highlight=seafile#using-seafile-as-an-exclusive-storage-mechanism
Yes, kolab_files uses now different (semi-recurrent) logic to fetch folders hierarchy. How exactly did you configure chwala with seafile?
Apr 11 2019
Mar 27 2019
Please do consider taking this to whatever the appropriate priority actually is, or however else you keep it off my radar until such time there's some meaningful involvement on my part ;-)
Mar 25 2019
Mar 22 2019
Correcting the priority from 60/40 to Normal
This ticket is no longer relevant.
This seems like low-priority aesthetics to me more so than an actual problem.
We do not actively support the database backend driver, so please bear in mind this has a very low priority for us.
Mar 21 2019
Jan 30 2019
Fixed in cbd1c1ae47b9.
Jan 28 2019
The issue is fixed in dev/fullcalendar-upgrade branch. It will be merged soon.
Jan 2 2019
Dec 17 2018
Confirmed. This is a known bug in fullcalendar library. Unfortunately an update is not trivial.
Nov 28 2018
Fixed in e85ff388293.
Sep 27 2018
Aug 23 2018
Probably it could, but in reality it doesn't make a big difference if you consider return value of both on kolab_storage_folder_user.
@vanmeeuwen Spaces and unicode are perfectly allowed in attachment names thanks to the RFCs about encoding the names in headers. The ticket is about iTip attachments specifically. I confirm that the code removes all non-ascii characters making the attachment name completely dummy in some cases. I don't really know why @bruederli make it this way. Maybe there was a reason.
Maybe I wasn't clear about what I would like to see: Roundcube's config/defaults.inc.php has by default this:
Aug 22 2018
There is "'d.M'," vs. "'d.M.'" (note the second dot).