PHP >= 7.1 compat. issue. Fixed.
Jul 7 2022
May 10 2022
May 19 2020
Jan 8 2020
Dec 25 2019
Aug 30 2019
This scenario is not possible at the moment and because SeaFile has it's own WebDAV service I'm not sure there's a need to use iRony for that. You can configure iRony to provide CalDAV and CardDAV only if needed.
Mar 22 2019
Correcting the priority from 60/40 to Normal
This ticket is no longer relevant.
This ticket is no longer relevant.
Jan 30 2019
Jan 25 2019
Fixed in 57e061251ee.
Mar 6 2018
Fixed in 876c956c24a4d.
So maybe we can just change in:
$size = $response['headers']['content-length'];
Looks like the fix in https://git.kolab.org/rC3b776f3a10e2443c0e47d331333265f9c75d7392 wasn't correct. We need to just support both cases.
I didn't logged the $response, good point. The server is returning the header but I think the format is different.
So, your webdav server does not return Content-Length or the http client code is buggy? Did you try to log response headers ($response['headers'])?
Mar 5 2018
Nov 9 2017
Jun 7 2017
Jun 6 2017
I've replaced the https_check() function with
As far as I can trace the calls back... our old friend api_url() is used to create the base URL and the scheme depends only on rcube_utils::https_check() and nothing else.
If the scheme "http" is used this can only mean, that rcube_utils::https_check() returned false - please correct me, if I'm wrong. Perhaps we should have a look at it next.
I've changed the file_api_url setting to some nonsense for testing purposes... Of course, it does not work, but the changed URL is passed along.
I've created a new text file and tried to open it. Same issue :-(
In this case it is Roundcube connecting to Chwala directly. It looks like the config has been ignored. I have no idea how's that possible. Maybe there's something in between that caches the request and returns old response? Check with a different file.
Is there anything I can do to help you to diagnose it?
I've set in kolab_files.inc.php
But it should work if you set file_api_url to a full url with https:// prefix? Do you set options in /etc/roundcubemail/config.inc.php? I'm unable to reproduce.
Yes, I've set use_https to true and applied the mentioned fixes. I'm sorry, but the issue persists :-/
And that is with use_https=true? BTW, there's another fix: rC0349c2d84661.
Now the error is away. Thank you!
Ok, try this change: rCd0539d6f029d.
I don't see how $_SERVER['SERVER_PORT'] == 80 would make it appended to the url. The if statement requires it to be different than $port and than 80. Maybe we should use intval($_SERVER['SERVER_PORT']).
I've written out $_SERVER['SERVER_PORT'] ... it's port 80. I assume that rcube_utils::https_check() returns true, so $schema is "https", this leads to $port = 443 and to a true, when evaluating the new if-block. So the port is appended to the hostname.
I've done just copy & paste. The code of the resulting function is ...
Maybe you just applied the patch incorrectly. Note the dot character in this line:
$url .= ':' . $_SERVER['SERVER_PORT'];
Forget my last comment. There's no such thing like $_SERVER['HTTP_PORT'].
Hmm... I'm just thinking. Maybe in your env you don't have $_SERVER['SERVER_PORT'] set either. Then try replacing this with $_SERVER['HTTP_PORT'].
What if you replace $_SERVER['SERVER_NAME'] with $_SERVER['HTTP_HOST']?
Thank you for the fix, but it doesn't seem to work :-/
Hope rCd886aeac2aec fixes that.
Jun 5 2017
Setting use_https to true does has not the desired effect. The created URL now contains the scheme "https", but it still uses port 80. Other parts of the application now complain about errors like this one:
May 31 2017
Fixed. You now would need to set use_https to true or file_api_uri to full chwala api path.
May 30 2017
The fix is in roundcubemail-plugins-kolab repo.
Fixed in rRPKce9ac27d783d.
Looks like rC21f6abd52a929 broke compatibility with Roundcube 1.2. Looks like we have now 3 options:
- Revert the change and wait with Roundcube 1.3 support until it's in Kolab, then apply it again
- Copy blank.tiff to blank.tif in roundcubemail package
- Use chwala URL to access these files.
May 29 2017
May 24 2017
No, K16 is enough
Apr 13 2017
The doc shows a few parameters:
- $config['fileapi_seafile_host'] = "files.example.com";
--> but the dialog box "add external storage" requires a server hostname...
Apr 12 2017
ok. I followed the doc:
Ok. This is what the original sample config says:
// Main files source, backend driver which handles // authentication and configuration of Chwala // Note: Currently only 'kolab' is supported $config['fileapi_backend'] = 'kolab';
So, this is not supported. Even if we implement this, it might be hard to use the Roundcube cache, because it requires ID of the user from users table.
root@xxx:/etc/roundcubemail# cat config.inc.php | grep fileapi
$config['fileapi_manticore'] = 'http://' . $_SERVER['HTTP_HOST'] . ':8080'; $config['fileapi_backend'] = 'seafile'; $config['fileapi_seafile_host'] = "https://files.xxxx.com"; $config['fileapi_seafile_ssl_verify_peer'] = false; $config['fileapi_seafile_ssl_verify_host'] = false; $config['fileapi_seafile_cache'] = 'db'; $config['fileapi_seafile_cache_ttl'] = '14d'; $config['fileapi_seafile_debug'] = false;
What is your config (only fileapi_* options)? When user logs into Chwala kolab driver is used to authenticate the user, so the user_id should be set in session.
Mar 19 2017
That's far easier than I thought. We already use save_file_content for special condition.
Let's just do that instead of sending the "Location:"-header too. This patch replaces
to one above. Would that work?
Feb 21 2017
Yes, that'll load the file into memory - no problem for my users, because our files are small.
To reproduce the issue just try to rename a file over WebDAV.
So, this would load the whole file into memory. Not something we'd like to do. So, first of all this probably should be an optional feature. Second, we should use seafile_request_observer to proxy the file content directly to the client. See seafile_file_storage::save_file_content(). Would you like to create a differential?
Jan 21 2017
Jan 20 2017
Dec 28 2016
I'm afraid Chwala does not log successful logins either. Failed logins log comes from kolab_auth plugin.
Dec 7 2016
This works for me. So, it may be some timing issue. Note that these notifications are not "instant", they are "pulled" in one minute intervals (timer starts when the page is loaded).
If you're in the File section of the web client, invitations about being invited to a collaborative session show up.
What File dialog? Could you be more precise? The notifications should be displayed in all Roundcube windows. That's how it worked.
Nov 28 2016
Nov 23 2016
Nov 14 2016
Yes, for now lets just settle on CloudSuite.
Nov 8 2016
Nov 7 2016
Current implementation gives prio to Collabora.
Nov 4 2016
Oct 20 2016
This is not required by CODE. No need to keep an open ticket.
Currently fixed, but the ticket will be open until we unify document_editor_api.