I did think of another way to do this, though it still doesn't seem like the most elegant solution to me. I can give users permission to change/delete model A, but then "hide" the links on the admin index page. Obviously this doesn't prevent an astute user from simply entering the url, so it's by far an ideal solution. Any other thoughts?
On Mar 12, 4:09 pm, Michael Repucci <mich...@repucci.org> wrote: > Hi Django'ers, > > I've got three models, call them A, B, and C. A contains a > ManyToManyField to model B. Users in my admin can add/change/delete B > and C but not A. When users delete C, there is no problem. However, > when users attempt to delete B, permission is denied due to the > relation to A, which the user does not have permission to delete. The > admin form displays: > > Are you sure? > Deleting the [instance of model B] would result in deleting related > objects, but your account doesn't have permission to delete the > following types of objects: > * [instance(s) of model A] > > The odd part, to me, is that instances of model A shouldn't be DELETED > when deleting an instance of model B, it should simply be removing > that relation from one or more instances of model A, as is apparent if > the same thing is attempted by a superuser: > > Are you sure? > Are you sure you want to delete the [instance of model B]? All of the > following related items will be deleted: > * [instance of model B] > o One or more [instance(s) of model B] in [instance of model > A] > > I tried overriding the has_delete_permission method in my model B > admin, but that doesn't appear to be where permissions are denied, as > that method returns true for my users. I looked at django/contrib/ > admin/options.py and am guessing that the permissions are denied at > line 697 (Django 1.0.2-final) of the delete_view, with > get_deleted_objects(deleted_objects, perms_needed, request.user, obj, > opts, 1, self.admin_site). But overriding that view would be much more > involved than I'd hoped it would be. > > Am I just being silly? Is there an easier way to do this? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
