Re: Bug in login_required?

Il giorno venerdì 10 luglio 2009 02:34:59 UTC+2, Manoj Govindan ha scritto:

This problem was logged as a bug and closed without fixing because the
development team thought it was not worthwhile. 

 

Time for necroposting. As of 2013, the 1.5 version of Django has nice news for us:

This setting now also accepts view function names and named URL patterns which can be used to reduce configuration duplication since you no longer have to define the URL in two places (settings and URLconf). For backward compatibility reasons the default remains unchanged.

So you can now use: 

LOGIN_URL  = 'django.contrib.auth.views.login'

LOGOUT_URL = 'django.contrib.auth.views.logout'

Instead of paths and this is not an issue anymore.

More on: 

https://docs.djangoproject.com/en/dev/ref/settings/#login-url

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.