Have commented out the 'SESSION_COOKIE_SECURE' and 'SESSION_EXPIRE_AT_BROWSER_CLOSE' from the settings.py file.
This has fixed the problem and I can now log in to admin. On Jun 6, 1:33 pm, Aidan <[email protected]> wrote: > Thanks for the input. > > I've tried deleting all .pyc files and still get the same issue. > > Also checked the cookies - I've got one sessionid and one csrftoken, > so that doesn't look like the issue. > > I've tried using the chrome javascript debugger to look for 404's and > haven't found any. > > I haven't deleted the database yet as there's data used (by South), to > do migrations on the tables underneath my models. I don't want to have > to recreate it all. > > On Jun 6, 12:19 pm, Karen Tracey <[email protected]> wrote: > > > > > > > > > On Mon, Jun 6, 2011 at 6:57 AM, Aidan <[email protected]> wrote: > > > I'm having trouble with the Django Admin. My login page appears ok at > > >http://127.0.0.1:8000/adminbutwhen I try to login with a valid > > > username or password the page seems to refresh - it reappears with > > > text boxes empty. It doesn't display any errors on the page (logging > > > in with invalid username / password brings up all the red errors you'd > > > expect). > > > I have seen this (though not with admin -- with a custom site login form) > > when somehow two sessionid cookies have been set. Using the browser tools to > > delete the sessionid cookies and try again allows login. I don't believe > > we've tracked down yet how the multiple sessionid cookies are getting set. > > > 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 [email protected]. 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.
