Hi, and fast thanks for the super fast reply! Just to make sure that I understood it correctly ---> those standard permissions are unevitable if I use django.contrib.auth? That would really be inconvinient! And moreover, the documentation would be misleading as it states:
"Three basic permissions -- add, change and delete -- are automatically created for each Django model that has a class Admin set." :( Best regards, Carl On 30 Mrz., 14:23, "Russell Keith-Magee" <[EMAIL PROTECTED]> wrote: > On Sun, Mar 30, 2008 at 8:18 PM, Carl <[EMAIL PROTECTED]> wrote: > > > Hi Djangonauts, > > > just observed that the standard edit/update/delete-permissions get > > created for all my models without me having given them the inner class > > Admin. Anyone an idea why this happens? > > Because model permissions are part of the contrib.auth application, > not contrib.admin. If you don't want the Django built-in permissions, > you need to remove django.contrib.auth from your INSTALLED_APPS list > (although this will prevent you from using contrib.admin, and many > other applications). > > Yours, > Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
