Tickets :: [#14938] Contact with only company not possible, workaround not working

6.0.0-alpha10

5/14/25

Search Results: 14 of 57 [ <<First <Prev Next> Last>> ] [ Return to Search Results ]

Summary	Contact with only company not possible, workaround not working
Queue	Turba
Queue Version	Git master
Type	Bug
State	Feedback
Priority	1. Low
Owners
Requester	tim (at) tim-sch (dot) de
Created	07/15/2019 (2130 days ago)
Due
Updated	11/18/2019 (2004 days ago)
Assigned	08/07/2019 (2107 days ago)
Resolved
Milestone
Patch	No

11/18/2019 08:27:48 PM	tim (at) tim-sch (dot) de	Comment #3	Reply to this comment
Here is a paste of the map: https://pastebin.com/AQTbnv2s

08/07/2019 01:59:50 AM	Michael Rubinsky	Comment #2 State ⇒ Feedback Priority ⇒ 1. Low	Reply to this comment
[Show Quoted Text - 23 lines][Hide Quoted Text] First of all: This is related to bug 14753, but I think this one goes a bit further. I recently imported an addressbook, formerly hosted at another provider. The addressbook contained many entries without a name (only the company field was filled). This was no problem with the old provider and the used client (MS Outlook). While the import went successful, things have gone south after the first change of such a contact. If the company name contains whitespaces, the parts of the name are copied into the available name fields. For example: "company name" will be: first name: "company" last name: "name" company: "company name" When I tried to work around this, by saving the company name as last name, the things described in 14753 happen. While the issue with contacts only containing a company name seems to be a dav issue, my workaround worked with Baikal. How is this address book configured in backends.php? Specifically the map?

07/15/2019 04:33:18 PM	tim (at) tim-sch (dot) de	Comment #1 Priority ⇒ 2. Medium Patch ⇒ No Milestone ⇒ Queue ⇒ Turba Summary ⇒ Contact with only company not possible, workaround not working Type ⇒ Bug State ⇒ Unconfirmed	Reply to this comment
First of all: This is related to bug 14753, but I think this one goes a bit further. I recently imported an addressbook, formerly hosted at another provider. The addressbook contained many entries without a name (only the company field was filled). This was no problem with the old provider and the used client (MS Outlook). While the import went successful, things have gone south after the first change of such a contact. If the company name contains whitespaces, the parts of the name are copied into the available name fields. For example: "company name" will be: first name: "company" last name: "name" company: "company name" When I tried to work around this, by saving the company name as last name, the things described in 14753 happen. While the issue with contacts only containing a company name seems to be a dav issue, my workaround worked with Baikal.