On Nov 3, 10:24 am, "Collin Grady" <[EMAIL PROTECTED]> wrote:
>
> I think you're confused - the context processor doesn't set a cookie,
> so it isn't causing any Vary behavior, and admin *does* currently
> depend on it - it needs the info the processor provides. Unless admin
> was rewritten to
On Sun, Nov 2, 2008 at 8:57 AM, bo <[EMAIL PROTECTED]> wrote:
> Yes, that may be true.
>
> But why does the 'default' behavior impose these dependencies when
> they are not required? As that context processor has this other 'side
> effect' of making an entire site "Vary" under a cookie, hit the
>
Yes, that may be true.
But why does the 'default' behavior impose these dependencies when
they are not required? As that context processor has this other 'side
effect' of making an entire site "Vary" under a cookie, hit the
session and hit the DB.
and one would need to override every other funct
On Sat, Nov 1, 2008 at 9:45 AM, bo <[EMAIL PROTECTED]> wrote:
> 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)
You can already do this - simply make your own subclass
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