Ok, I have the two log files console.log and httpraw.log.
Where can I send them? They contain sensitive data?
When I send them they will be send from my business address and not from this account.
Nov 11 2019
Ok, I have the two log files console.log and httpraw.log.
iRony has two debug options that should give some logs.
// enable debug console showing the internal function calls triggered // by http requests. This will write log to /var/log/iRony/console $config['kolabdav_console'] = true;
Nov 7 2019
I'm unable to reproduce. current-user-privilege-set is correct for other user's calendar with lrs permissions. Could you enable debug and provide full request and response for the PROPFIND on a readonly calendar?
Sep 24 2019
The ACLs for shared readonly adressbooks are exposed correctly but not for readonly calendars.
Sep 23 2019
Any chance this will get fixed/implemented soon?
Thunderbird + TbSync + DAV-4-TbSync suffers from this, too.
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 1 2019
Ping? Any feedback on the wrong write privilege returned for (shared) readonly folders?
Aug 8 2018
We might need to store the original URL-ID of the contact object to be able to handle DELETE requests.
Apr 28 2018
I cannot confirm that ACLs are already exposed. Looking at the DAV response I get on the client side, for a readonly folder, shows:
Jul 20 2017
@bruederli Do you remember what's the reason for https://git.kolab.org/source/iRony/browse/master/lib/Kolab/CalDAV/CalendarBackend.php;ead6159e01eb2b44b9f90665d17168cd14f5ce3b$91 to be not active?
Jul 12 2017
Jul 4 2017
Fixed by 0c02d0d45c6 in roundcubemail-plugins-kolab [master].
Jul 3 2017
I verified with the code that if the original event would specify SCHEDULE-AGENT=CLIENT for the attendee it would be properly recognized by SabreDAV classes and the CANCEL would not be sent. So, what we need is to store this initial SCHEDULE-AGENT value in custom properties of Kolab format (or extend the format of https://wiki.kolab.org/User:Mollekopf/Drafts/KEP:17#Attendee).
Could be. I've tried to create new meeting and looking at the Caldav I see that ATTEDEE is:
So looks like SCHEDULE-AGENT is gone.
Jul 1 2017
However, https://tools.ietf.org/html/rfc6638#section-220.127.116.11 says that CANCEL is sent when an event was modified and previous scheduling was done by the server (default if SCHEDULE-AGENT is not specified). So, probably the issue is in recognizing the previous state.
Jun 30 2017
Jun 21 2017
Jun 7 2017
May 11 2017
May 10 2017
Mar 13 2017
Hard to say it's deployment or code issue and it's old. Closing.
Feb 28 2017
Feb 21 2017
To reproduce the issue just try to rename a file over WebDAV.
I came across this issue yesterday and the above patch appears to fix the problem for me. Please merge it into the iRony repository.
Jan 4 2017
I'm unable to reproduce this with Roundcube Calendar. So, it might be already fixed or the bug is in iRony.
Jan 2 2017
Dec 29 2016
Roundcube core and kolab_addressbook plugin does not support photo URLs. It is not clear to me if it is at all possible to store URL and mediatype in Kolab XML format (probably only URL without type is supported).
Dec 28 2016
The same as in syncroton (T1751) it is caused by authentication cache.
Dec 15 2016
Dec 7 2016
Nov 23 2016
DAVBackend::folder_create() returns false on error, but it should throw an exception.
Diff created. I didn't find a nice way to avoid imap_debug issue described in my comment above. There are two sides of this issue though:
- user id/name is not set before user is authenticated. That's why some part of logs go to logs/ directory instead of logs/<username>/. I found a workaround, but a little bit hacky. In DAVLogger::_construct() add:
$_SESSION['username'] = $_SERVER['PHP_AUTH_USER']; $_SESSION['user_id'] = -1;
this however requires to login with canonified username, if you use alias for login and canonified username for logs dir it will not catch up.
Anyway this is not a big issue, as most relevant logs are written on after auth.
- should logs/imap file (and others) be created at all if per_user_logging=true? I mean that's current behaviour, but changing this would allow as to have all debug options enabled with per_user_logging and get logs only for set up users.
Nov 22 2016
And related to this, enabling e.g. imap_debug together with any of above options does not really work as expected, i.e. the whole imap conversation from after login goes where expected, but everything before the user has been authenticated goes to logs/imap. Maybe it would be possible to fix this by setting $_SESSION['username'] before loging into imap.
Jul 13 2016
Is this related to why setting a picture for a contact in Android fails when syncing with DAVdroid? Should another bug be filed for that?
Jun 29 2016
Mar 23 2016
Mar 21 2016
Fixed the initial issue. I could not find a reproduceable test case, but the fix is really simple and the same check is used few lines before.
Mar 17 2016
All the tests which are in the iRony repository used to run through without errors. So if that changed on Winterfell, it should be looked at.
Mar 15 2016
I recently run iRony's tests on Kolab Winterfell, and it gave me 14 failed tests. It looks like we don't really use these for CI, are we?
Mar 14 2016
Also, adding the TYPE attribute in v3 seems a reasonable change to me.
Yes, Apple clients also use "b" when exporting and synching contact photos although they can handle upper-cased values as well. But the way to go definitely is lower-cased.
Mar 11 2016
Mar 8 2016
Mar 7 2016
"B" and "b" both work with iOS7 Contacts app.
This broke in my recent performance improvements in libkolab plugin code. https://git.kolab.org/rRPK52053f355af6c09db547f1b8d02bb9ae88abcb1c So, it's Winterfell only.
Mar 2 2016
Perhaps it has come from section 2.4.1?
Please create a ticket for this differential, and set the summary of this differential to "Resolves T$x", where $x is the ticket number you get.
Mar 1 2016
I don't recall where that change came from and I can't find an according test/sample case. We should comply with RCF here.
As this contradicts with rId20afc78222279, would be nice to have feedback from Thomas.
Dec 11 2015
Oct 9 2015
That's a different issue. Probably fixed by this https://git.kolab.org/rIbb534210020c5fedd9c4b780c995e8b7c20d81a6
The error remains.
Patched the internal webservers, @vincent is testing.
Sep 30 2015
The Sabre/VObject is in version 2.1.7, so it should be fine.
Sep 21 2015
BTW: Still seeing these after the recent Kolab Now service window. Should it have resolved them or is this something new/residual?
Sep 8 2015
Aug 4 2015
Also not reproducable with current KE14 - iRony DAV Server 0.2.8SabreSabre VObject 2.1.3.