#15611: Readonly fields not hidden during create
-------------------------------------+-------------------------------------
               Reporter:             |          Owner:  jezdez
  coderanger                         |         Status:  new
                   Type:  Bug        |      Component:  contrib.admin
              Milestone:  1.3        |       Severity:  Normal
                Version:  1.2        |       Keywords:
             Resolution:             |      Has patch:  0
           Triage Stage:  Design     |    Needs tests:  0
  decision needed                    |  Easy pickings:  0
    Needs documentation:  0          |
Patch needs improvement:  0          |
                  UI/UX:  1          |
-------------------------------------+-------------------------------------
Changes (by julien):

 * easy:   => 0
 * stage:  Accepted => Design decision needed


Comment:

 I'm not convinced that read-only fields should systematically and
 implicitly be hidden (or omitted) from the add form as, for example, one
 may want to display read-only default values. Instead I would prefer to
 let the admin offer more flexibility so that one could explicitly control
 what fields are displayed in the add/change forms on a per-request basis.
 For this reason I'm marking this ticket as DDN.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/15611#comment:8>
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