[Tickets #6621] Re: Category handling

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/6621
-----------------------------------------------------------------------
 Ticket             | 6621
 Updated By         | thomas.jarosch at intra2net.com
 Summary            | Category handling
 Queue              | Horde Base
 Version            | HEAD
 Type               | Bug
 State              | Feedback
 Priority           | 1. Low
 Milestone          |
 Patch              |
 Owners             |
-----------------------------------------------------------------------


thomas.jarosch at intra2net.com (2008-04-21 06:05) wrote:

>> As far as I understood the internal data format of
>> Prefs/CategoryManager.php,
>> all clients save the (array) id of a category in their data
>> structures, regardless if you use a Kolab or SQL backend. Is that
>> correct?
>
> Right now the string category name is stored, not an array index.

Ok, looks like a bug in the Kolab implementation. I'll look into it.

Would it make sense if the Kolab driver sees an unknown (=new)
category to automatically add it?

>> Also Horde allows only one category f.e. for a contact. Kolab allows
>> n categories. Still have to think about a way to properly fix that,
>> if possible.
>
> Yeah, would be great to upgrade all Horde groupware apps to allow
> multiple categories - also known as tags? ;) - but I don't think it's
> productive to try and do that for the 3.2 releases.

Yeah, let's stabilize the release and then add more features :-)
I'll have to check if I can -reliable- preserve the multiple fields
somehow.

Thomas