On Thu, May 7, 2009 at 11:31 AM, Steve R <sraw...@gmail.com> wrote: > > I’m looking to create an Admin so that when a user from one Site logs > into the admin they will not be able to see or modify entries for > other sites. ... > Do I need to subclass AdminSite in contrib.admin.sites.py? Or modify > the Admin views? > > I’ve read all the documentation on django.contrib.admin and > django.contrib.sites, but I haven’t found a solution. It seems like > this should be possible, but I’m just not sure how to go about it. > Any suggestions you can offer would be greatly appreciated.
I haven't worked through all the details, but what you are doing certainly sounds possible, and shouldn't require too much heavy lifting. The first part is to build an admin site that limits access to objects. James Bennett described how to do this in lots of detail in his blog late last year: http://www.b-list.org/weblog/2008/dec/24/admin/ The second part is to allow different admin 'instances' for each of your site. This is the bit I haven't really played with, but I can think of two ways you might be able to do this: Firstly, you could actually create lots of admin.site instances, and deploy them using a wrapper to dispatch urls. To do this completely dynamically, you will need to do a little bit of programming to build a class that can wrap the admin instances, and dispatch requests to the right admin site per request. The good news is that this becomes a lot easier if you use Django trunk, rather than v1.0.X. In trunk, urlresolvers have been updated so that any object with a get_urls() method can be included into an urlresolver. The recommended syntax for including admin sites has been updated to reflect this change (the old syntax still works, but will eventually be deprecated). If you do a bit of code digging into the admin Site, you should hopefully be able to see how this could work. The second approach is to subclass admin.site so that the get_urls() method on site takes the sites.Site model as an argument in the URL. This essentially means you would have a single site, but individual requests on the admin site would be aware of the site for which they are operating (the use of the term site is getting a bit ambiguous here, but hopefully you grok my point) Neither of these two approaches are particularly well documented; I'm relying on your adventurous spirit here to dig into how the get_urls() approach works in Django trunk, and to see how this could be used to your advantage. 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
