#10306: login.html example FORM tag is wrong in
http://docs.djangoproject.com/en/dev/topics/auth/
---------------------------+------------------------------------------------
 Reporter:  jkafader       |       Owner:  nobody    
   Status:  new            |   Milestone:  post-1.0  
Component:  Documentation  |     Version:  1.0       
 Keywords:                 |       Stage:  Unreviewed
Has_patch:  0              |  
---------------------------+------------------------------------------------
 Hi I just thought I'd pass this along:

 the ACTION parameter on the FORM tag for your sample login.html template
 is almost certainly wrong. It should not be '.' -- I'm not an expert on
 FORM ACTION but I think it should instead be '' , which at least worked
 for me.

 This cost me, actually, about an hour of development time, thinking there
 was something drastically wrong with the way I was passing or handling the
 ?next= parameter in my login form. You see, an action of '.' cuts off the
 GET CGI string, making your form unable to redirect properly
 (django.contrib.auth.views.login gets the 'redirect_to' variable from the
 GET string, not from POST), but still, confusingly, logging in the user
 correctly.

 This really took up a lot of time to figure out, I guess I should have
 gone with my original instinct of action="" with my login.html rather than
 slavishly copying the one in the docs. But I just thought I'd let you know
 about an unnecessary gotcha.

 --james

-- 
Ticket URL: <http://code.djangoproject.com/ticket/10306>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to