#11124: ModelAdmin's has_change_permission() and has_delete_permission() methods
don't examine their obj parameter
-------------------------------------------+--------------------------------
Reporter: ramiro | Owner: nobody
Status: new | Milestone:
Component: django.contrib.admin | Version: SVN
Resolution: | Keywords:
has_change_permission has_delete_permission ModelAdmin
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------------+--------------------------------
Comment (by apollo13):
Okay ignore my previous two posts, it was late yesterday :/ This is the
current situation:
The !ModelBackend kicks in even if an obj is passed in; which is kinda
suboptimal I guess as according to the docs Backends will return False if
not supporting rowlevel perms.
After that got fixed (#12462) the !Modelbackend will return False always
for obj!=None. This means that as soon as a user updates his !ModelAdmin
to supply obj to the backends he will have to use a rowlevel-backend
(Those who don't want to use row level perms could write a dummy backend
which passes the check to the !ModelBackend but without passing the obj to
the !ModelBackend).
--
Ticket URL: <http://code.djangoproject.com/ticket/11124#comment:7>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
