#30231: "verbose_name" is ignored in FilteredSelectMultiple widget for new 
               Reporter:  FlorianSchuler  |          Owner:  nobody
                   Type:  Bug             |         Status:  new
              Component:  contrib.admin   |        Version:  2.1
               Severity:  Normal          |       Keywords:
           Triage Stage:  Unreviewed      |      Has patch:  0
    Needs documentation:  0               |    Needs tests:  0
Patch needs improvement:  0               |  Easy pickings:  1
                  UI/UX:  1               |
 When using the FilteredSelectMultiple widget (filter_horizontal) in a
 TabularInline view on a ModelAdmin page the "verbose_name" of a
 ManyToManyField is ignored for newly added objects via the "add another"
 button. It simply displays the field name for those elements. The
 FilteredSelectMultiple widgets of initially loaded / already existing
 objects is displayed correctly with the use of the "verbose_name" of the
 regarding field.

 It seems like a small JS Bug, because when checking out the generated HTML
 source code, the "select"-element has always the correct "data-field-name"
 attribute which fits to the "verbose_name" (for the newly added objects
 too). But when the FilteredSelectMultiple widget of newly added objects is
 initialized the generation of the heading and the help texts seems to
 ignore this "data-field-name" attribute / the "verbose_name" and instead
 uses simply the field name.

 See attached screenshot for explanation.

Ticket URL: <https://code.djangoproject.com/ticket/30231>
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
For more options, visit https://groups.google.com/d/optout.

Reply via email to