[Tickets #8358] turba with kolab-backend loses e-mail address when adding contact from imp/dimp

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/8358
------------------------------------------------------------------------------
  Ticket             | 8358
  Created By         | m.rolke at linux-ag.com
  Summary            | turba with kolab-backend loses e-mail address when
                     | adding contact from imp/dimp
  Queue              | Turba
  Version            | 2.3.1
  Type               | Bug
  State              | Unconfirmed
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


m.rolke at linux-ag.com (2009-06-18 12:44) wrote:

Hi there,

i have turba configured with kolab2 as the storage backend.

Creating a contact in turba itself works flawless.
But when i try to import the sender of an e-mail to my default  
addressbook (kolab backend) it fails.
Although the contact will be created, turba throws away the e-mail attribute.

The problem, i think, is that imp tries to add a contact with a single  
e-mail address ($attribute['email']).
Turba in contrast expects $attribute['emails'] (plural) and throws  
away the former.

Because i think this is a specialty for kolab, this should be fixed in  
the kolab driver itself:

So, i suggest adding something like the followin to the _add function  
in turba/lib/Driver/kolab.php

if (isset($attributes['email'])) {
                 $attributes['emails'] = $attributes['email'];
                 unset($attributes['email']);
         }

Thoughts?