Re: user object in templates

[Ben Jones]

> it seems like I have no user object in my templates, which is weird,
> as it comes w/ my request object, and I can access it in my views. In
> other words, request.user.is_authenticated evaluates to True in my
> views, but to False in my templates.

See this thread:

http://groups.google.com/group/django-users/browse_thread/thread/84c15332671e02f8?hl=en

I suspect that your missing user object is because of the same reasons
that {{ perms }} was empty in thread above.

--
-Ben

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

user object in templates

[John]

it seems like I have no user object in my templates, which is weird,
as it comes w/ my request object, and I can access it in my views. In
other words, request.user.is_authenticated evaluates to True in my
views, but to False in my templates.

Before you ask, I do have 'django.core.context_processors.auth' in my
TEMPLATE_CONTENTS_PROCESSORS, and AuthenticationMiddleware and
SessionMiddleware in my MIDDLEWARE_CLASES.

I am running the trunk version of django as of today.

Has the sintax for accessing the user object ( {{ user.foo }} )
changed, or am I missing something really, really silly?

Thanks.


--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---