#15602: Using get_readonly_fields and StackedInline/TabularInline admin objects
doesn't allow creating new objects, immutible existing objects
---------------------------------+------------------------------------
Reporter: bradwhittington | Owner: nobody
Type: Bug | Status: new
Component: contrib.admin | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Changes (by Scott Stevens):
* cc: Scott Stevens (added)
Comment:
This also affects `has_<value>_permission` calls, and actually causes the
wrong object to be checked for permissions.
I feel as though this increases the severity, since it no longer just
affects what fields are read-only, but is now a failure to enforce
permissions correctly (and could allow object permissions where it's
expected to be prohibited).
I'm unsure if we need a new bug for this, or to expand the scope of this
existing ticket (rename/etc.).
--
Ticket URL: <https://code.djangoproject.com/ticket/15602#comment:20>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/073.d8758b6215db365678eb2de7ce31488e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
