I regards to http://groups.google.com/group/django-developers/browse_thread/thread/2bad3ad84e9beb81
One aid in this area would be to remove the dependancy of context_processor.auth in the Admin world (which most certainly needs the user, messages and perms in the context) Admin can detect if it is present, and use it, otherwise it would simply "add" the three vars (user, messages, perms) to the context itself. I think all it requires is to move the calls to "template.RequestContext" to "self.RequestContext" inside of contrib.admin.site.py .. making it backward compatible bo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---