Hi,
On 26.05.2009, at 12:17, Sam Kuper wrote:
> 2009/5/26 Alex Gaynor <alex.gay...@gmail.com>
>> It's not even an authorisation issue, it's that I'd be overiding
>> nearly every method to make sure the behavior was what I wanted,
>> and then I'd replace all the templates since I want everything the
>> user sees to be similarly themed, and at this point I've already
>> rewritten a ton of code.
>
> OK, so is the trust issue you mentioned in your first email more to
> do with being able to trust your admin users not to mind the default
> admin presentation?
>
> Sorry if I'm asking basic questions, but I do want to gain a really
> thorough understanding of when it is appropriate to give users
> access to (parts of) the admin, and when it isn't.
In my humble opinion. As soon as you mention users, the admin is the
wrong tool.
contrib.admin is for admin's and not for users.
Another take on it is:
- Anyone that creates an account on your site, doesn't get to ses the
admin
- Anyone that you create an account for, might be a user to get to see
the admin.
Regards
adi
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
