#8906: django.contrib.auth settings.py URL's aren't portable
-------------------------------------+--------------------------------------
Reporter: levity | Owner:
Status: new | Milestone:
Component: Authentication | Version: 1.0
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 1
Needs_better_patch: 0 |
-------------------------------------+--------------------------------------
Comment (by AmanKow):
I don't know who says this isn't worth pursuing, but I have been bitten by
this. It severly hampers the usability of the auth system. I've got a
custom login_required decorator going with 'pull this out when the bug is
fixed in django' comments.
Since reverse lookups are portable, perhaps the ability to use LOGIN_NAME,
etc. in auth would be a good way to quash this? It could be backwards
compatible by using a AUTH_USE_NAMED_URLS settings defaulting to 'False',
and falling back to the _URL variants.
I would be happy to work on this if this seems to be an acceptable
solution, or would appreciate input on alternate paths of attack.
--
Ticket URL: <http://code.djangoproject.com/ticket/8906#comment:4>
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 [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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
