Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#2696 closed defect (wontfix)

[per-object-permissions] altering per-object permissions always raises Permission Denied

Reported by: Joeboy Owned by: clong
Component: contrib.admin Version: master
Severity: normal Keywords: row level per object permissions permission denied
Cc: django25@… Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:


It might be that I'm misunderstanding, but as far as I can see changing per-object-permissions from always seems to lead to Permission Denied, even when editing as superuser.

Attachments (0)

Change History (3)

comment:1 Changed 8 years ago by clong

Can you give some more information (example models, database, steps taken) about this, I haven't been able to reproduce it on my system.

comment:2 Changed 8 years ago by clong

  • Status changed from new to assigned

comment:3 Changed 8 years ago by clong

  • Resolution set to wontfix
  • Status changed from assigned to closed

More info required.

Add Comment

Modify Ticket

Change Properties
<Author field>
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.