(whitespace-)trimming of mapped attributes

Mapping attributes from multiple hash values can generate hi

Sun, 09 Dec 2007 09:11:17 -0500

Mapping attributes from multiple hash values can generate hideous results if some of the attributes are not set. Example: 'name' => array('fields' => array('firstname', 'lastname'), 'format' => '%s %s', 'attribute' => 'cn'), If firstname is not set, cn becomes " Lastname" with a leading space. Would be nice if mapped attributes get trimmed afterwards, maybe even on multiple whitespaces within the string. Yes, there cannot be a general trim rule, but maybe another map parameter just for the (common?) whitespace separation?

This happens already. Where exactly do you see this not ha

Mon, 10 Dec 2007 06:07:38 -0500

This happens already. Where exactly do you see this *not* happening? And in case this has been implemented after RC1, did you try a recent snaphot?

horde-FRAMEWORK_3-2007-12-11 horde-HEAD-2007-12-11 turba-H

Tue, 11 Dec 2007 12:59:28 -0500

horde-FRAMEWORK_3-2007-12-11 horde-HEAD-2007-12-11 turba-HEAD-2007-12-11 $attributes just before adding to LDAP at horde/turba/lib/Driver/ldap.php:266 error_log and print_r for new contact with only lastname (and email) Array ( [DUFFtype] => Object [cn] => Lastname <-- " Lastname" with leading space [sn] => Lastname [mail] => xxx@a.com [SNIP] ldapsearch results in: cn:: IExhc3RuYW1l <-- " Lastname" with leading space (base64) sn: Lastname

Can you try if the following commit fixed it: http://cvs.ho

Thu, 13 Dec 2007 20:13:49 -0500

Can you try if the following commit fixed it: http://cvs.horde.org/diff.php/turba/lib/Driver.php?r1=1.175&r2=1.176&ty=u

yes, works Thanks!

Fri, 14 Dec 2007 15:13:21 -0500

yes, works Thanks!