6.0.0-git
2019-10-14

[#14938] Contact with only company not possible, workaround not working
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 2019-07-15 (91 days ago)
Due
Updated 2019-08-07 (68 days ago)
Assigned 2019-08-07 (68 days ago)
Resolved
Milestone
Patch No

History
2019-08-07 01:59:50 Michael Rubinsky Comment #2
State ⇒ Feedback
Priority ⇒ 1. Low
Reply to this comment

[Show Quoted Text - 23 lines]
How is this address book configured in backends.php? Specifically the map?
2019-07-15 16:33:18 tim (at) tim-sch (dot) de Comment #1
Type ⇒ Bug
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Summary ⇒ Contact with only company not possible, workaround not working
Queue ⇒ Turba
Milestone ⇒
Patch ⇒ No
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.

Saved Queries