My pleasure :D
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL
Oops, I see it now. Thanks!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send ema
It's determined by the settings under the admin options. By default
both are set to false, so no permissions will be creation. To do what
you want:
...
class Admin:
grant_change_row_level_perm = True
...
That should just set the change row levle permission and not set any
delete row level per
I noticed in the patch(3609,
http://code.djangoproject.com/changeset/3609) that you seem to grant
permissions automatically to the creator of an object. Is there any
way we can set this behavior? In my circumstance, I don't want the
writer of an article to be able to delete it.
Chris Long wrote:
I'm considering doing what you describe, it shouldn't be too hard to
implement and will probably be updating the branch with the code
tomorrow depending on any unforeseen problems.
Chris
Joe wrote:
> I'm not sure if this is more relevant to the Generic Authorization
> branch, but has anyone loo
I'm about to switch zyons over to using it, just got a lot of other
stuff to do beforehand.
maybe next week.
regards
Ian
On 18/08/2006, at 3:51 AM, Chris Long wrote:
>
> Hi,
>
> I'm the GSoCer working on row level permissions.
>
> Row level permissions are now implemented and, in my test cas
On 8/17/06, Joe <[EMAIL PROTECTED]> wrote:
>
> I'm not sure if this is more relevant to the Generic Authorization
> branch, but has anyone looked at implementing the owner permissions
> (the user who creates the object automatically has delete/modify
> permissions)?
This is something that should
I'm not sure if this is more relevant to the Generic Authorization
branch, but has anyone looked at implementing the owner permissions
(the user who creates the object automatically has delete/modify
permissions)? For example, a META field sort of like the following:
class Meta:
row_l
Hi,
I'm the GSoCer working on row level permissions.
Row level permissions are now implemented and, in my test cases, are
working.
I wanted to find out if anyone has had an opportunity to try the row
level permissions (per-object-permission) branch or read my wiki pages
on it. Are there any com
