[Tickets #4957] Re: Problems with handling of default shares

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=4957
-----------------------------------------------------------------------
 Ticket             | 4957
 Updated By         | wrobel at pardus.de
 Summary            | Problems with handling of default shares
 Queue              | Horde Framework Packages
 Version            | HEAD
 Type               | Bug
 State              | Feedback
 Priority           | 1. Low
 Owners             | 
-----------------------------------------------------------------------


wrobel at pardus.de (2007-01-31 10:42) wrote:

> This change completely breaks backwards compatibility. Why can't the 
> Kolab driver support the current handling?

Ah, sorry I have to admit that I did not consider backward compatibility
at all.

It will be possible to handle the issue without tampering with the nag,
mnemo and kronolith side of things though this will require a less elegant
solution on the side of the kolab driver.

The reason why it does not work at the moment is that kolab uses a
"default" attribute on the shares while the datatree driver uses the
unique id of the object to indicate if it is a default share or not
(ID==username if it is a default share, random number otherwise).

I need to reconsider if I can reorganize the way the kolab driver uses the
id so that it can convert the way horde uses the id into the necessary
kolab attributes.