On Thu, May 7, 2009 at 4:49 PM, Russell Keith-Magee <freakboy3...@gmail.com> wrote: > 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? >> > 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: ...
Thinking about this a little more, you may not even need this bit, depending on how you deploy your application. If all you are looking for is for each site to have it's own admin, then you may not need to do any modifications to the admin; as long as each site has its own settings file and site ID, you may be able to use a standard admin deployment, with content filtered as James described. 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 -~----------~----~----~----~------~----~------~--~---
