Re: [Zope-dev] LoginManager ownership bug!

2000-10-06 Thread Jonas Juselius
Cheers! I actually tried to implement support for local roles in almost exactly the same way as you did, but for some reason I didn't get it to work. Perhaps I should look into the matter again... I just threw in the user_names(), and getUserNames() into the LoginManager, added some dtml to

Re: [Zope-dev] LoginManager ownership bug!

2000-10-06 Thread Phillip J. Eby
At 04:01 PM 10/6/00 +, Ty Sarna wrote: I think this is due to Shane's fix for allowing LM's as non-top-level acl_users. I had it originally so that _owner was a class attribute, which works fine. With the change, it was added as an instance attribute. Now, UnownableOwner is just an empty

Re: [Zope-dev] LoginManager ownership bug!

2000-10-06 Thread Jonas Juselius
Thanks! I actually tried to make _owner a class attrib, but then I tried to add a LM to a sub-folder ;-) It didn't work out... Would it be an ugly solution to check whether the LM _is_ top-level, and if it is, make _owner a class attrib? Would it work? Or is this solution only curing the

[Zope-dev] LoginManager ownership bug!

2000-10-05 Thread Jonas Juselius
Hola, There seems to be a problem with the ownership model in Zope (or ZPatterns). The problem is the following: I have implemented a nice login system based on the LoginManager and SQL methods. I would like to make this acl_users the top level user folder, but... then hell brakes lose...

Re: [Zope-dev] LoginManager ownership bug!

2000-10-05 Thread Michael Bernstein
Jonas Juselius wrote: Another thing which I have tried to do, is to add support for local roles to the LoginManager. At first it looked rather simple, but then I realized that it wasn't really _that_ simple, and dropped it because I don't have time... It would however be nice to have local