It sure seems like #2 that I mentioned before is the issue. Your context
processor is overriding the 'user' template context variable that the admin
uses. I just looked at some admin templates and they definitely use the
'user' variable. Name it something else or add logic to the context
On Tue, Dec 20, 2011 at 11:09 PM, Divick Kishore
wrote:
> On Wed, Dec 21, 2011 at 6:04 AM, Branton Davis
> wrote:
> > It sounds like your custom user template context variable might be
> causing a
> > conflict with the default if you're also using
Hi Branton,
On Wed, Dec 21, 2011 at 11:09 AM, Branton Davis wrote:
>
> That stack trace is unrelated to the other problem. Somewhere (guessing
> gifts/urls.py) you've referenced a view
> at gifts.views.ajax_handle_wishinvite, which doesn't exist. Check
> gifts/views.py for
On Dec 21, 7:05 am, Karen Tracey wrote:
> People would be able to help you more effectively if you included the stack
> trace that goes with the exception.
>
> Karen
> --http://tracey.org/kmt/
The stack trace for the error is:
ERROR Caught AttributeError while rendering:
On Wed, Dec 21, 2011 at 6:04 AM, Branton Davis wrote:
> It sounds like your custom user template context variable might be causing a
> conflict with the default if you're also using django.contrib.auth (which is
> what the admin uses by default). I'm guessing that the admin
People would be able to help you more effectively if you included the stack
trace that goes with the exception.
Karen
--
http://tracey.org/kmt/
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to
I get the following error when I try to access admin site. I am not
sure what is causing this. I am not sure if it could be caused because
one of the two reasons:
1. I have a User model in one of my apps which does not have a id as
primary key. I have some other key as the primary key.
2. I have
7 matches
Mail list logo