| Summary | Setting of 'name' via syncML in turba. |
| Queue | Turba |
| Queue Version | 2.2-RC1 |
| Type | Bug |
| State | Resolved |
| Priority | 3. High |
| Owners | mrubinsk (at) horde (dot) org |
| Requester | xk3 (at) mompl (dot) org |
| Created | 12/09/2007 (6415 days ago) |
| Due | |
| Updated | 12/09/2007 (6415 days ago) |
| Assigned | 12/09/2007 (6415 days ago) |
| Resolved | 12/09/2007 (6415 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
thanks
Martin
State ⇒ Feedback
Assigned to Michael Rubinsky
Diff available at:
http://cvs.horde.org/diff.php?f=turba%2Flib%2FDriver.php&r1=1.173&r2=1.174&t=unified
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ Setting of 'name' via syncML in turba.
Queue ⇒ Turba
New Attachment: ldapCN.patch
State ⇒ Unconfirmed
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.