Re: Permissions get automatically created without class Admin in models
On Sun, Mar 30, 2008 at 10:47 AM, Karen Tracey <[EMAIL PROTECTED]> wrote: > Note ticket #5926 has been hanging around for a few months on this issue, > with at least 3 people (one who provided a patch) hoping the fix would be to > change the code to match the docs versus changing the docs to match the > code. I went ahead and wontfixed that; it's easy enough to just remove the permissions if you don't want them, and it's just silly to have them tied to the inner Admin class when that class will soon be part of history. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Permissions get automatically created without class Admin in models
On Sun, Mar 30, 2008 at 9:36 AM, James Bennett <[EMAIL PROTECTED]> wrote: > > On Sun, Mar 30, 2008 at 8:06 AM, Carl <[EMAIL PROTECTED]> wrote: > > I will open a ticket right away... > > Fixed in changeset 7388. > Note ticket #5926 has been hanging around for a few months on this issue, with at least 3 people (one who provided a patch) hoping the fix would be to change the code to match the docs versus changing the docs to match the code. Karen --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Permissions get automatically created without class Admin in models
On Sun, Mar 30, 2008 at 8:06 AM, Carl <[EMAIL PROTECTED]> wrote: > The only problem is, that those automatically created permissions have > english descriptions and I'm building something for a german-only > speaking user base. But i think i'll just change the descriptions > manually in the database. That's just a few lines of SQL at the end... When you do that, the value you want to change is the "name" column, which can be any value you'd like; the automatic bits, and the admin interface and other built-in things which check for the default permissions, won't look at that; they care about the unique combination of the "codename" column (which must, for these purposes, be of the form "(add|change|delete)_modelname") and the foreign key to ContentType. So long as those are left alone, you can change "name" to anything you want. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Permissions get automatically created without class Admin in models
On Sun, Mar 30, 2008 at 8:06 AM, Carl <[EMAIL PROTECTED]> wrote: > I will open a ticket right away... Fixed in changeset 7388. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Permissions get automatically created without class Admin in models
Thanks again! The only problem is, that those automatically created permissions have english descriptions and I'm building something for a german-only speaking user base. But i think i'll just change the descriptions manually in the database. That's just a few lines of SQL at the end... I will open a ticket right away... On 30 Mrz., 15:02, "Russell Keith-Magee" <[EMAIL PROTECTED]> wrote: > 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 -~--~~~~--~~--~--~---
Re: Permissions get automatically created without class Admin in models
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 -~--~~~~--~~--~--~---
Re: Permissions get automatically created without class Admin in models
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 -~--~~~~--~~--~--~---
Re: Permissions get automatically created without class Admin in models
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 -~--~~~~--~~--~--~---
