[horde] Should Turba ActiveSync contact import call the encode_attribute() hook?

[Michael J Rubinsky]

Quoting Patrice Levesque <horde.wayne at ptaff.ca>:

> Hi,
>
> 	Using Horde 4, latest stable versions.
>
> 	I got ActiveSync working for Kronolith full-duplex and I can fetch
> 	my Turba LDAP Contacts from my mobile phone; when trying to push a
> 	contact from my phone to Horde, I get a LDAP error.  I know what's
> 	wrong; part of my DN is mapped to an empty attribute and creation
> 	fails (my LDAP-Turba attribute mapping is kinda baroque).
>
> 	Using Turba's hooks.php I can fill that empty attribute using the
> 	value from another attribute, with encode_attribute().  That being
> 	said, that function is not called AFAIK when adding entries from
> 	ActiveSync.
>
> 	I'm not sure where the encode_attribute() call should be added in
> 	the ActiveSync codepath, or even if this hook should be shared
> 	between regular data entry and ActiveSync.

We were calling it when importing *changes*, but not when adding a new  
entry. I've made changes in git to address this. If you can run a git  
checkout, you can verify this fix now. Otherwise, it will be included  
in the next Turba release.

-- 
mike

The Horde Project (www.horde.org)
mrubinsk at horde.org