On Sun, Mar 30, 2008 at 8:41 PM, Carl <[EMAIL PROTECTED]> wrote: > > 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?
Yes. > That would really be inconvinient! Why? They don't take up much space; if you don't like the built-in permissions, but you still want users, etc, you can ignore them. Alternatively, you can set up your own permissions and ignore the built-in permissions. What are the automatically added permissions preventing you from doing? > 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." Hrm... that's interesting, and definitely wrong. This might be a hangover from an early incarnation. Permissions are definitely created as part of contrib.auth synchronization. Could you please open a ticket reporting this fact so that this can be corrected. 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 -~----------~----~----~----~------~----~------~--~---
