On 09-Jan-08, at 12:14 AM, James Bennett wrote:

>> Another dirty solution would be to simply create a user account, and
>> give it permissions to only view things. I haven't played with
>> permissions at all, but I imagine it would be possible.
>> The correct way is still to write your own code to do it.
>
> No, that won't work. The Django admin operates on three permissions:
> "add", "change" and "delete". There is no "view but make no
> modifications" permission, hence there is no way to apply such a
> restriction without doing significant custom coding.

the correct way is to only give admin rights to those you can trust  
to read and not edit. Any one else should be handled outside admin -  
after all 2 lines of extra code needs to be written.

-- 

regards
kg
http://lawgon.livejournal.com
http://nrcfosshelpline.in/web/
Foss Conference for the common man: http://registration.fossconf.in/web/



--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to