Re: [Django] #15139: Admin delete_view don't use per object permissions backends

[Django]

#15139: Admin delete_view don't use per object permissions backends
+---
   Reporter:  msaelices | Owner:  msaelices
 Status:  closed| Milestone:   
  Component:  django.contrib.admin  |   Version:  1.2  
 Resolution:  duplicate |  Keywords:   
   Triage Stage:  Accepted  | Has patch:  1
Needs documentation:  0 |   Needs tests:  1
Patch needs improvement:  1 |  
+---
Changes (by julien):

  * status:  new => closed
  * resolution:  => duplicate


Comment:

 Dupe of #13539.

-- 
Ticket URL: 
Django 
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-updates@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.

Re: [Django] #15139: Admin delete_view don't use per object permissions backends

[Django]

#15139: Admin delete_view don't use per object permissions backends
---+
  Reporter:  msaelices | Owner:  msaelices
Status:  new   | Milestone:   
 Component:  django.contrib.admin  |   Version:  1.2  
Resolution:|  Keywords:   
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  0 |   Needs_tests:  1
Needs_better_patch:  1 |  
---+
Changes (by russellm):

  * needs_better_patch:  0 => 1
  * has_patch:  0 => 1
  * needs_tests:  0 => 1
  * stage:  Unreviewed => Accepted

Comment:

 The admin needs to undergo a broad permission audit; I'm not convinced
 that per-object permissions are being honored everywhere that they should
 be. This is one example of the problem.

-- 
Ticket URL: 
Django 
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-updates@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.

Re: [Django] #15139: Admin delete_view don't use per object permissions backends

[Django]

#15139: Admin delete_view don't use per object permissions backends
---+
  Reporter:  msaelices | Owner:  msaelices
Status:  new   | Milestone:   
 Component:  django.contrib.admin  |   Version:  1.2  
Resolution:|  Keywords:   
 Stage:  Unreviewed| Has_patch:  0
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by msaelices):

  * needs_better_patch:  => 0
  * component:  Uncategorized => django.contrib.admin
  * needs_tests:  => 0
  * needs_docs:  => 0

-- 
Ticket URL: 
Django 
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-updates@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.

[Django] #15139: Admin delete_view don't use per object permissions backends

[Django]

#15139: Admin delete_view don't use per object permissions backends
---+
 Reporter:  msaelices  |   Owner:  msaelices 
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.2   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 The admin delete confirmation view should use permissions per objects.
 Only uses the object model to check if user has or not permissions to
 delete the object.

-- 
Ticket URL: 
Django 
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-updates@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.