Unfortunate /login behavior in 1.8 (and 1.7)?

70 views
Skip to first unread message

Christophe Pettus

unread,
Apr 6, 2015, 11:37:04 PM4/6/15
to django-d...@googlegroups.com
I have a site with a /login URL. This URL is for customer logins to an ecommerce site, and is distinct from the /admin/login to the Django admin.

However, having upgraded from 1.6 to 1.8, it appears that /admin/login is getting confused, and running the view associated with the /login URL. This effectively prevents me from logging into the admin. I assume this has something to do with the redirection change in 1.7 for the admin login.

If I change the name of /login to /customer_login, that confusion goes away.

--
-- Christophe Pettus
x...@thebuild.com

Christophe Pettus

unread,
Apr 6, 2015, 11:38:55 PM4/6/15
to django-d...@googlegroups.com
Ignore my silliness... operator error, that the 1.7 change flushed out!
> --
> You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
> To post to this group, send email to django-d...@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers.
> To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/F262F7CB-69ED-4BE3-B1FD-F1FDECA8591F%40thebuild.com.
> For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages