[Tickets #5978] Setting of 'name' via syncML in turba.

[bugs at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/?id=5978
-----------------------------------------------------------------------
 Ticket             | 5978
 Created By         | xk3 at mompl.org
 Summary            | Setting of 'name' via syncML in turba.
 Queue              | Turba
 Version            | 2.2-RC1
 Type               | Bug
 State              | Unconfirmed
 Priority           | 3. High
 Owners             | 
+New Attachment     | ldapCN.patch
-----------------------------------------------------------------------


xk3 at mompl.org (2007-12-09 06:02) wrote:

I use an LDAP backend with an obligatory "cn" assembled by "firstname
lastname" on the fly. 

'name' => array('fields' => array('firstname', 'lastname'),
                          'format' => '%s %s',
                          'attribute' => 'cn')

Adding a contact via turba works well, but adding via syncML fails with an
object class violation. There is no $hash["name"] set, so cn is not
created.

Why name is not set via syncML, I do not know. Some of the synced contacts
contain FN, some not, but I thought mapped attributes are always created
and added to source?

The attached patch only fixes the symptom.