This is going to need to be pushed back until a refactoring is underway, as the current application model does not allow for such distinction.

Cloning https://github.com/owncloud/format-filter-server.git in to rOFFS

The functions get_uid() and set_uid() functions [[https://git.kolab.org/diffusion/RPK/browse/master/plugins/libkolab/lib/kolab_storage_folder.php;a52bf1abe3d7f54fc6424237c282e0d40c507506$147|[1]]] are likely causes of the aforementioned discrepancy of folder metadata values in different namespaces.

would we require including the ability to invite people to edit documents they do not have the appropriate (IMAP-level) write access to?

• Use $result as already available

The actual fix for this problem is, as commented on the relevant line, probably a better search for LDAP objects, since it is not guaranteed that cn=kolab-admin is the only role configured in the relevant hierarchy or tree.

As mentioned on IRC, the indentation is a little off in places.

Being tracked as https://noc.kolabsys.net/T79

In T221#2797, @bruederli wrote:

Basically all options one can pass to the HTTP_Request2 constructor should be configurable, including

save_tags() (or more generically, write operations) should probably invalidate the cache(s) related to it, and as a matter of efficiency, one might seed the cache again with the internal structs rather than obtain them all all over again from source.