Re: [collective-cmfmember] LDAP+schemas again

[Rob M. <ra...@bu...>]

IOhannes m zmoelnig wrote:
> IOhannes m zmoelnig wrote:
>> i created a new "Plone Site" (type "Default Plone"), set up my LUF in 
>> the acl_users.
>> then i changed the LDAP Schema mapping according to my needs (mapped 
>> mail(ldap) -> email(plone); cn(ldap) -> fullname(plone))
>> and lo and behold, when i logged into plone with my ldap account, 
>> everything behaved as expected (fullname and email showed up!)
>> so i installed CMFMember via SiteSetup->addProducts and updated it: and 
>> still my mapping works.
> 
> i cheered out to early :-(
> when i log in with my ldap account _before_ updating CMFMember, the 
> mapped values are fetched from the ldap-server and are stored in the 
> AttributeStorage.
> upgrading CMFMember keeps these values.
> however, when i now log in with another ldap user (whose fields have not 
> yet been retrieved and stored locally), it does not do the mapping any more.
> 
> so back to the start....

i wish i could offer you more help, but, as i said, the place to go from here 
would be to do interactive investigation of the live objects using 'zopectl 
debug', to see what's going on w.r.t. the field storage of the newly created 
objects.  have you made any progress using the steps that i outlined in my 
earlier post?

another thing you might consider is NOT using ATSENG, but instead using a 
custom member class with a custom schema using LDAPUFStorage.  this will 
remove one layer of complexity from the setup.

-r