1042801 - "ldap_2.servers.*.autoComplete.nameFormat|addressFormat|commentFormat" settings no longer work

Status: NEW

(Thunderbird :: Message Compose Window, defect)

Description

[Michał Sacharewicz]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:30.0) Gecko/20100101 Firefox/30.0 (Beta/Release)
Build ID: 20140605174243

Steps to reproduce:

Configure LDAP address book (source: Microsoft ActiveDirectory) with following setting:
ldap_2.servers.MyLDAP.autoComplete.nameFormat = "[givenName] [sn]"


Actual results:

User displayed as "[cn] <[mail]>"


Expected results:

User displayed as "[givenName] [sn] <[mail]>"

This actually worked before 31.0.

Temporary workaround is to set ldap_2.servers.MyCompany.attrmap.DisplayName into some other attribute (eg. [displayName]), but it does not allow Administrator to use more than one attribute (eg. to omit middle names).

Comment 1

[Andreas Wagner [:TheOne] [use NI]]

Dupe of bug 1050672?

Comment 2

[Michał Sacharewicz]

This ticket is about autoComplete.nameFormat attribute, while bug 1050672 relates to autoComplete.commentFormat.

When talking about drop-down autocomplete list only, first attribute refers to the first column and latter refers to the second (in certain scenarios). The first attribute (of which this bug is about) has a wider scope of influence though, the outcome of this setting affects eg. mail headers (formatting of recipient name).

So it's not exactly a duplicate, though the whole set of features might be affected by single source issue.

Comment 3

[Kent James (:rkent)]

Let's keep looking at this, but we won't block release on it.

Comment 4

[Karl]

This issue still exists in 38.3.0 on Ubuntu [Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0, Build ID: 20150930122345]

Comment 5

[:aceman]

It seems reading those preferences was removed in bug 452232, but which claims the support was just switched over to another framework.  I can't say, whether the switch was successful.