hi jacob,
thanks for the report.
i've committed a fix to cvs - please test it (although it may take a while to reach public cvs).
if you want to test before then, here are the changes:
in program/steps/addressbook/ldapsearchform.inc, change lines 106-109 to:
// store the search fields in a js array for each server $js = ''; foreach ($server['search_fields'] as $search_name => $search_value) $js .= "['$search_name', '$search_value'], ";
in skins/default/includes/ldapscripts.html, change lines 37-38 to:
new_option.text = server_fields[i][0]; new_option.value = server_fields[i][1];
cheers justin
Jacob Brunson wrote:
On Sunday 08 January 2006 16:45, justin randell wrote:
- The searchfields could use aliasses...
could you give me more detail on this point?
I've come across a similar thing. I am using two LDAP servers. This means that when the LDAP server is changed "function updateLdapSearchFields(element) " in skins/default/includes/ldapscripts.html is executed, which changes the searchfields options. On lines 37 and 38 of ldapscripts.html: new_option.text = server_fields[i]; new_option.value = server_fields[i];
This means that the text of the options turns to the same as the value, which in my case is "cn" and "mail" However, to most users, "cn" isn't going to mean much. It needs to be instead "Name"