#15759: list_editable should respect per-object permissions
-------------------------------------+-------------------------------------
Reporter: Jeremy Dunck | Owner: Artyom
| Kotovskiy
Type: Bug | Status: new
Component: contrib.admin | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jacob Walls <jacobtylerwalls@…>):
In [changeset:"5b3cfce51770f46c6dc100e9be7f199a37176762" 5b3cfce]:
{{{#!CommitTicketReference repository=""
revision="5b3cfce51770f46c6dc100e9be7f199a37176762"
Refs #15759 -- Fixed ModelAdmin.list_editable form submission for non-
editable instances.
Added formset that excludes objects for which
user has no permission for POST formset as well.
Fixed regression test: the test was not simulating
real behaviour properly. By providing full form
data for the post request we skipped the part
where the user was actually limited in permissions
and only modified some of the rows.
Improved tests by getting rid of obj.id % 2
approach for granting permissions per object
for users, since it is not the safest.
Instead granting permissions simply by 'alive'
parameter, which is simpler and more stable.
Bug in 84db026228413dda4cd195464554d51c0b208e32.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/15759#comment:17>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019dd530f493-d3fb307b-d4b0-4124-bfda-96e9a545afbe-000000%40eu-central-1.amazonses.com.
