#17967: "change password" link in the admin header should be easier to disable
-------------------------------+--------------------
     Reporter:  d00gs          |      Owner:  nobody
         Type:  Bug            |     Status:  new
    Component:  contrib.admin  |    Version:  1.4
     Severity:  Normal         |   Keywords:
 Triage Stage:  Unreviewed     |  Has patch:  0
Easy pickings:  0              |      UI/UX:  0
-------------------------------+--------------------
 The "change password" link in the admin header doesn't make sense for all
 installations. For example, sites that use `django-auth-ldap` as the
 primary authentication scheme don't necessarily allow users to change
 their password, because it [[https://bitbucket.org/psagers/django-auth-
 ldap/issue/8/add-the-ablility-to-change-password#comment-402102|might not
 make sense to do so]]. In that case, having the "change password" link in
 the header of the admin is confusing for users, because it doesn't work /
 do what they expect it to.

 I've overriden the `base.html` template and made this change:

 {{{
 35c35,37
 <                 <a href="{% url 'admin:password_change' %}">{% trans
 'Change password' %}</a> /
 ---
 >                 {% if user.has_usable_password %}
 >                     <a href="{% url 'admin:password_change' %}">{% trans
 'Change password' %}</a> /
 >                 {% endif %}
 }}}
 which is appropriate for my sites, though I'm not sure if it is in
 general.

 But this is annoying, because then when you update Django (as I did today)
 any changes to `base.html` just won't happen and there will probably be
 problems.

 If `has_usable_password` isn't a good way to distinguish in general, then
 there should either be a setting for whether this should be displayed, or
 the `<div id="user-tools">` should be in its own template for easy
 overriding.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/17967>
Django <https://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