> >Are you aware that every user can already change his password on his
own? I really had forgoten that it was possible to do so through the Tryton interface. Now that you had said that, I tried it and it solves at least the immediate problem. > >What are you trying to achieve with your module exactly? > I am trying to make a special class of Users (Psychologists). I considered inheritance, a container for a User, and my actual solution (that creates an independent user but uses the fact that it has a unique login field). The solution of "Psychologist" containing a User (With a One2One field e.g.) wasn't good because it would be a bit confusing given the actual GUI, and considering the target people that will use the software. I was afraid of the way of handling permissions in the inheritance solution, but maybe that was because of my poor knowledge of Python. I think inheritance would be the natural solution if I can solve the details. In any case my actual solution (maybe temporary but something at least) involves creating a User when an instance of the class Psychologist is created, and I would like to be able to modify the "User" class fields as well. But by now may adopt an ad hoc solution (after all it was this way since the begining) and use the Tryton interface for that. It could help if anyone knows what am I doing wrong when writing to a User, though. Thank you for your answer. Regards, Miguel Tasende -- -- [email protected] mailing list
