6.0.0-beta1
7/20/25

[#7895] sync data corruption in firstname with spaces
Summary sync data corruption in firstname with spaces
Queue Turba
Queue Version 2.3.1
Type Bug
State Resolved
Priority 1. Low
Owners jan (at) horde (dot) org
Requester willem.verbruggen (at) anagky (dot) be
Created 01/26/2009 (6019 days ago)
Due
Updated 09/16/2009 (5786 days ago)
Assigned 09/04/2009 (5798 days ago)
Resolved 09/16/2009 (5786 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
09/16/2009 09:18:41 AM Jan Schneider Assigned to Jan Schneider
Taken from Gunnar Wrobel
Taken from Ben Klang
State ⇒ Resolved
 
09/04/2009 10:43:12 AM Jan Schneider Comment #10
State ⇒ Feedback
Reply to this comment
That sounds like a bug that had been fixed in CVS already. Can you try 
a snapshot?
09/01/2009 03:11:43 PM lst_hoe02 (at) kwsoft (dot) de Comment #9 Reply to this comment
This is not LDAP related. Turba always cut the "N" field in vCard at 
the blanks so if you have any name with blanks it get split to VName 
MiddlName LastName. According to the RFC 2426 Turba import should only 
split at ";" as far as i can see.

Export works fine BTW, but import fails with SyncML and import by file.

If you have any device which have no concept of "MiddlName" then part 
of the name get lost.
02/04/2009 09:28:25 PM internationils (at) gmx (dot) net Comment #8 Reply to this comment
I just had the same problem today. I'm running the Kolab Bundle 
2.2.1-beta1 under ubuntu 8.10. I synced my Nokia E71 via SyncML, and 
the same thing happened with last names with spaces. I have almost 200 
last names with spaces as I have first and last names stored in there, 
because an older phone didn't support them separately.  Please let me 
know what I can do to help track down the problem.



Thanks, Nils


01/29/2009 06:23:43 PM Jan Schneider Comment #7
Assigned to Ben Klang
Assigned to Gunnar Wrobel
State ⇒ Assigned
Reply to this comment
Maybe some of our LDAP folks can take a look at it.
01/29/2009 06:22:16 PM Jan Schneider Version ⇒ 2.3.1
Queue ⇒ Turba
 
01/29/2009 05:57:14 PM willem (dot) verbruggen (at) anagky (dot) be Comment #6 Reply to this comment
Yes it does.

Same error when importing manually.


01/29/2009 03:54:09 PM Jan Schneider Comment #5 Reply to this comment
That all looks fine. Does it also happen when importing that vCard 
manually into the address book?
01/29/2009 02:08:32 PM willem (dot) verbruggen (at) anagky (dot) be Comment #4
New Attachment: sources.php Download
Reply to this comment
And here is the sources.php
01/29/2009 02:02:31 PM willem (dot) verbruggen (at) anagky (dot) be Comment #3
New Attachment: data_ldap.jpg Download
Reply to this comment
Hi,



data.txt contains (display from vi editor):



Input received from client (text/x-vcard):

BEGIN:VCARD^M

VERSION:2.1^M

REV:20090129T135120Z^M

N:Verschueren;Test geert;;;^M

X-CLASS:private^M

TEL;CELL;HOME:0032477256138^M

END:VCARD



Result in LDAP attached in screenshot too.

Just let me know if you want more info from this session.

(It seems I can only attach one file at the time?)



gr,



Willem
01/29/2009 10:56:59 AM Jan Schneider Comment #2
State ⇒ Feedback
Reply to this comment
This almost sounds like the automatic last-name-detection in Turba is 
triggered somewhere, even though that shouldn't happen if both Turba 
and the phone use separate fields for first name and last name. Can 
your post your sources.php and a data.txt from such a sync session?
01/26/2009 05:42:35 PM willem (dot) verbruggen (at) anagky (dot) be Comment #1
Priority ⇒ 1. Low
State ⇒ Unconfirmed
Patch ⇒ No
Milestone ⇒
Summary ⇒ sync data corruption in firstname with spaces
Type ⇒ Bug
Queue ⇒ Synchronization
Reply to this comment
Hi,



I setup my Nokia N85 to sync to my horde Addressbook.

For the addressbook, I use an LDAP backend with a schema of 
nokiaperson I created myself.



When I loaded my N85 users to the empty LDAP addressbook, I had one 
major problem. In case of spaces in the first name like in this data 
example:



Firstname = Core Mattias

Lastname = Verbruggen



in LDAP this became



cn = Core

sn = Mattias



and the data for lastname was gone.

This only happens when syncing because the LDAP address book from 
within Turba handles spaces in the firstnames just fine.



When I resynced afterwards (but changing the protocol from 1.2 to 1.1 
on the phone), this doubled the number of addressbook entries in my 
phone.  Syncing again started tripling the data.

In horde on the other hand, only 10 entries were added unwanted 
compared to 500 in my phone.



Spaces in address entries did not cause troubles.



Now that I cleaned up my data without having any more spaces in 
firstnames, everything works fine.

I would love to help you testing this problem out by adding spaces 
again to my firstname fields.



gr,



Willem

Saved Queries