On 8/3/06, Chris Long <[EMAIL PROTECTED]> wrote: > 1) Will there be any support for the previous method of checking > permissions? (e.g. will users.has_permission work?)
I was planning on keeping the User.has_perm method around for now, but I think it ought to go away before 1.0. It won't be called anymore in any of Django's code by the time I'm finished. > 2) How are the two of us going to integrate our two systems? I mostly > have final testing and making the admin interface for editing row level > permissions left and then it's integrating them into the > permission/auth system. I have a few ideas, but we should really have a > long conversation about this and decide who si doing what and how so we > can maximize both our features. Sooner rather then later. :D Agreed. I'll hang out on #django for awhile tonight if you're available. I'll plan on being there from 7-11pm MDT off and on. If I'm not there I won't be gone for long. my nick is jkocherhans > 3) More a little mistake, in your patch you have in the main admin > views file: > > if not has_perm(request.user, app_label + '.' + > opts.get_delete_permission(), obj): > > probably meant has_permission. Yep. On top of that, all of those permissions strings that get passed in will need to change to actual permission objects. I wrote a bunch of the admin code last night, but didn't get around to testing it. Probably tonight. Thanks for pointing it out. Joseph --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
