I haven't toyed with the debugging tool yet. Thanks for the suggestion
-- I'll let you know how it woks out.
On Jun 8, 4:48 pm, Jashugan wrote:
> On Jun 4, 2:45 pm, Matt wrote:
>
> > It looks like you're right and the login page isn't actually logging
> > users in.
>
> > Any idea why that might
On Jun 4, 2:45 pm, Matt wrote:
> It looks like you're right and the login page isn't actually logging
> users in.
>
> Any idea why that might be? I'm using the auth.login view and a
> template that looks like this:
Your template code looks fine.
> Any thoughts on what might be going on here?
Thanks for replying so quickly.
It looks like you're right and the login page isn't actually logging
users in.
Any idea why that might be? I'm using the auth.login view and a
template that looks like this:
##login.html
{% extends "base.html" %}
{% block content %}
{% if form.errors %}
Your us
On Jun 2, 5:00 pm, Matt wrote:
> //views.py
> from django.template import RequestContext
> def detail(request):
> ...
> context = { 'employees': employees, 'entityinfo': entityinfo}
> return render_to_response('results/resultstable.html',
> context_instance=RequestContext(request, conte
This is a weird one. It's so weird, I'm positive I'm making a very
dumb mistake somewhere. This is my MO.
Anyway, I am trying to use django-registration to do some very basic
login, logout stuff. I'm using RequestContext to make usernames
available to all of my templates, like so:
//views.py
fro
5 matches
Mail list logo
