Re: Login crazyness...

2006-09-25 Thread Karen Tracey
John M wrote: > I'm not passing anything into my > templatles except ... whatever the Render_to_Response > does. ... You need to pass a RequestContext as the 2nd argument to render_to_response. See: http://www.djangoproject.com/documentation/templates_python/ (Search for RequestContext, it's

Re: Login crazyness...

2006-09-25 Thread John M
Thanks for the feedback... Karen Tracey wrote: > Shots in the dark -- you are passing a RequestContext, not a regular > old Context, into your main template? Karen how would I know that? I'm not passing anything into my templatles except the call by except whatever the Render_to_Response does.

Re: Login crazyness...

2006-09-25 Thread Laundro
Be sure to always pass the request information from one view to another. The request object holds session information and the user object (amongst others). --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django use

Re: Login crazyness...

2006-09-24 Thread Karen Tracey
Shots in the dark -- you are passing a RequestContext, not a regular old Context, into your main template? And you've got django.core.context_processors.auth in your TEMPLATE_CONTEXT_PROCESSORS setting? Karen John M wrote: > I'm trying out the login / logout methods from a simple webpage, and a

Login crazyness...

2006-09-24 Thread John M
I'm trying out the login / logout methods from a simple webpage, and am having some real trouble here. My main page has a link to /accounts/login, setup according to the docs, allows the user to fill in a name and password, hit OK, and viola they are logged in. On the main page, i check to see i