Hi Russ, On Wednesday, November 13, 2013 2:16:13 AM UTC+1, Russell Keith-Magee wrote: > > The use case was simple -- deploy two instances of admin in a single > project. For example, you might have a truly 'access-all-areas' admin, and > a cut down/modified admin for trusted editors that has specially customised > workflows, etc. Admin has been specifically designed to allow this, and > it's a documented feature [1]. >
This is something which can be done currently by supplying the name argument to the AdminSite [1] (this changes the instance namespace name for the urlconf). But we also have a lesser known (and not working) feature where you can also modify the app_name itself [2] -- which is causing problems here (application namespace vs instance namespace). I am not sure what app_name provides aside from more complexity :) Cheers, Florian [1] https://docs.djangoproject.com/en/dev/ref/contrib/admin/#django.contrib.admin.AdminSite [2] https://github.com/django/django/blob/master/django/contrib/admin/sites.py#L55 -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/f8529924-493e-4e3c-9be9-50462747d2d3%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
