Although Data Browser is interesting. I was hoping for something much closer to the admin interface, but for viewing and searching. It would seem like DRY would suggest that using the admin interface for read- only access would actually be the right way to do this, simply making someone staff, and adding read-only permissions, or maybe even better yet creating a reviewer role or something in addition to staff and admin, that only allows read-only access and can not be given write/ alter access.
Is there some reason that this is not the right approach and things like databrowse are trying to recreate the interface in some ways? Thanks, Sean On Oct 29, 10:07 am, Sean <[EMAIL PROTECTED]> wrote: > I just found this: > > http://www.djangoproject.com/documentation/databrowse/ > > but other input is welcome. > > Thanks, > Sean > > On Oct 29, 9:43 am, Sean <[EMAIL PROTECTED]> wrote: > > > I add a staff user with no additional permission to my admin > > interface, hoping that they would be able to use the interface for > > searching, but unfortunately since they do not have permissions to > > edit anything they seem unable to search either. At the moment, I > > would actually prefer to use this interface instead of writing a new > > one, since eventually some of these users may also have edit rights > > (however others may still be restricted to searching). Is there an > > easy way to accomplish this in admin.py or elsewhere? > > > Thanks, > > Sean --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
