#24908: Overridden field in modelform used in modeladmin which name is returned 
by
get_readonly_fields
-------------------------------------+-------------------------------------
     Reporter:  jpic                 |                    Owner:  Tim
                                     |  Graham <timograham@…>
         Type:  Bug                  |                   Status:  closed
    Component:  contrib.admin        |                  Version:  1.8
     Severity:  Normal               |               Resolution:  fixed
     Keywords:                       |             Triage Stage:  Ready for
                                     |  checkin
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):

 * status:  new => closed
 * owner:   => Tim Graham <timograham@…>
 * resolution:   => fixed


Comment:

 In [changeset:"fedef7b2c6e80e1e58b028cf9c03267a8950bf6f" fedef7b2]:
 {{{
 #!CommitTicketReference repository=""
 revision="fedef7b2c6e80e1e58b028cf9c03267a8950bf6f"
 Fixed #24908 -- Fixed duplicate readonly field rendering.

 ModelAdmin added readonly_fields to exclude, but would not undeclare
 them if they were overridden.
 }}}

--
Ticket URL: <https://code.djangoproject.com/ticket/24908#comment:9>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.6a476d91b8195a75392ecb52dead2325%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to