Hi Eric,

I also ran into this issue.  There is an issue in membrane when it  
tries to deal with certain types of fields.  For instance,  
ComputedField and BooleanField are not handled correctly.  I needed to  
put in a quick fix so I just overrode the property factories.  You can  
see the code here.

http://pastebin.com/f4e289407

I entered this bug into the membrane issue tracker:

http://plone.org/products/membrane/issues/15

claytron
-- 
S i x  F e e t  U p ,  I n c .  |  "Nowhere to go but open source"
Silicon Valley: +1 (650) 401-8579 x603
Midwest: +1 (317) 861-5948 x603
Toll-Free: 1-866-SIX-FEET
mailto:clayton@...
http://www.sixfeetup.com  |  Zope/Plone Custom Development



On Mar 24, 2008, at 2:33 PM, Wohnlich, Eric (IMS) wrote:
> Ok, this turned out to be my own stupid mistake - I had been  
> tinkering with PlonePAS and it wasn't checking all of the managers.  
> I nuked that instance of Zope and reinstalled to make sure I had a  
> fresh copy, and setting the passwords is fine.
>
> However, I have been unable to change the email address from  
> prefs_users_overview (see error message below). If I change the  
> email in the archetypes schema I don't have a problem, but that also  
> does not change the email on the property sheet. Does anyone know if  
> this is being worked on for Plone 3, or would perhaps have some  
> advice? I really would like to have these products available for us  
> in 3.
>
>   Module Products.CMFPlone.PloneTool, line 105, in setMemberProperties
>   Module Products.PlonePAS.plugins.ufactory, line 228, in  
> setProperties
>   Module Products.PlonePAS.sheet, line 113, in setProperties
>   Module Products.membrane.plugins.propertymanager, line 115, in  
> setPropertiesForUser
>   Module Products.membrane.factories.properties, line 87, in  
> setPropertiesForUser
> ValueError:
>                     Exception raised when writing title property:
>                     exceptions.TypeError: 'NoneType' object is not  
> callable
>
> Thanks,
> Eric
>
> From: Wohnlich, Eric (IMS) [mailto:WohnlichE@...]
> Sent: Thursday, March 20, 2008 1:33 PM
> To: remember@...
> Subject: [Remember Mailing List] password reset in plone 3
>
> Hi all,
> I've been playing around with membrane/remember in Plone3. Mostly I  
> just want to have referenceable objects for members, as I created  
> several Products that took advantage of this implementation back in  
> the days of CMFMember, although being able to customize the schema  
> is certainly nice.
>
> My problem right now is that when resetting a user's password, or  
> creating a new user without explicitly setting a password, I get a  
> traceback like this
> 	• Module None, line 6, in pwreset_action
> <FSControllerPythonScript at /Plone7/pwreset_action>
> Line 6
> 	• Module Products.PasswordResetTool.PasswordResetTool, line 142, in  
> resetPassword
> 	• Module Products.PlonePAS.pas, line 339, in userSetPassword
> 	• Module Products.PlonePAS.plugins.user, line 93, in doChangeUser
> RuntimeError: User does not exist: user1
>
> The user of course does exist; I can log in as that user, mess  
> around with permissions, etc. I thought perhaps PlonePAS might be  
> looking for the member UID instead, so I changed pwreset_action to  
> get the UID instead, but this fails the reset since the request to  
> reset was for user1 not its UID (not sure if it would have worked  
> anyway). I don't really understand PlonePAS that well to be honest  
> (which is why I'm using remember); can anyone point me in the right  
> direction? Has anyone else experienced this problem?
>
> Any help appreciated
> Eric
>
>
> Information in this e-mail may be confidential. It is intended only  
> for the addressee(s) identified above. If you are not the  
> addressee(s), or an employee or agent of the addressee(s), please  
> note that any dissemination, distribution, or copying of this  
> communication is strictly prohibited. If you have received this e- 
> mail in error, please notify the sender of the error.
>
>
> Information in this e-mail may be confidential. It is intended only  
> for the addressee(s) identified above. If you are not the  
> addressee(s), or an employee or agent of the addressee(s), please  
> note that any dissemination, distribution, or copying of this  
> communication is strictly prohibited. If you have received this e- 
> mail in error, please notify the sender of the error.