On Tue, Jul 3, 2012 at 12:31 PM, Larry Martell <larry.mart...@gmail.com> wrote: > On Tue, Jul 3, 2012 at 11:55 AM, Robert Steckroth > <robertsteckr...@gmail.com> wrote: >> Django is a very open-ended framework. The admin system is built around >> developer/user customization. > > > Yes, I realize that. But I was asking if there was something that just > worked (i.e. like foreign key references do). I don't think so, but my > client seems to.
Apparently there is. Stepping through their app I found that it calls has_perm in contrib/auth/models.py, which calls has_perm in contrib/auth/backends.py, and this controls what specific functionality each user has access to. >> On Tue, Jul 3, 2012 at 1:51 PM, Larry Martell <larry.mart...@gmail.com> >> wrote: >>> >>> On Tue, Jul 3, 2012 at 11:49 AM, Robert Steckroth >>> <robertsteckr...@gmail.com> wrote: >>> > Yes, I have seen some very impressive admin media controls for websites >>> > with >>> > larger projects >>> > having wordpress like functionality. However, there are not easy >>> > or cheap to >>> > make. >>> > I recommend checking open-souce projects for a good start. >>> >>> But there's nothing inherently built into Django admin that supports >>> this, correct? >>> >>> > >>> > >>> > On Tue, Jul 3, 2012 at 1:39 PM, Larry Martell <larry.mart...@gmail.com> >>> > wrote: >>> >> >>> >> I have a client that asked me to add some new functionality to their >>> >> app, and then they said 'This new functionality should be controlled >>> >> in Django admin so that only the admin user can see it.' Is there a >>> >> way to control this in Django admin? I know in the python code i can >>> >> check to see if they're the admin user or not and allow or disallow >>> >> access, but what they're saying makes it seem I can just do it admin. >>> >> >>> >> -- >>> >> 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. >>> >> >>> > >>> > >>> > >>> > -- >>> > Bust0ut, Surgemcgee: Systems Engineer --- >>> > PBDefence.com >>> > BudTVNetwork.com >>> > RadioWeedShow.com >>> > "Bringing entertainment to Unix" >>> > >>> > -- >>> > 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. >>> >>> -- >>> 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. >>> >> >> >> >> -- >> Bust0ut, Surgemcgee: Systems Engineer --- >> PBDefence.com >> BudTVNetwork.com >> RadioWeedShow.com >> "Bringing entertainment to Unix" >> >> -- >> 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. -- 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.
