Thanks, That makes sense. I guess could either patch the login view, AuthenticationForm or call set_test_cookie() on unauthenticated users on their first page view, probably through middleware.
One odd thing though: I'm using the sample code from the docs in my login.html template that tests for form.has_errors and then displays an error message. I tried listing form.errors to see if I could get a better error message, but form.errors is empty. Looking at the code for AuthenticationForm and views.login, forms.errors should contain a validation error complaining about cookies. -Justin On Aug 31, 3:47 pm, "James Bennett" <[EMAIL PROTECTED]> wrote: > On 8/31/07, jfagnani <[EMAIL PROTECTED]> wrote: > > > I can't figure out what's going on, the form obviously works in some > > circumstances, and the log-in data is also correct. > > You're running into the issue in ticket #3393[1]. I keep meaning to > put together a better patch, but other things keep coming up with > higher importance. > > [1]http://code.djangoproject.com/ticket/3393 > > -- > "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
