Opened 13 years ago

Closed 2 months ago

#15611 closed New feature (fixed)

Readonly fields not hidden during create

Reported by: Noah Kantrowitz Owned by:
Component: contrib.admin Version: 1.2
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: yes

Description

A field marked as readonly should be hidden when creating a new object from the admin.

Attachments (1)

django-ticket-15611.diff (8.8 KB ) - added by Noah Kantrowitz 13 years ago.

Download all attachments as: .zip

Change History (16)

comment:1 by Noah Kantrowitz, 13 years ago

Keywords: blocker added

comment:2 by Russell Keith-Magee, 13 years ago

Keywords: blocker removed
Triage Stage: UnreviewedAccepted

FYI: blocker doesn't mean "this is annoying and I want someone to fix it". It means "this is a problem so serious that we need to hold back the release".

This *certainly* isn't a blocker. It doesn't cause data loss. It doesn't cause crashes. It isn't a regression in behavior since the last release, and it isn't a bug in a new feature. It is, at best, an mild annoyance.

comment:3 by Noah Kantrowitz, 13 years ago

The flag was set on the request of Jannis ;-) The fix is done, going to make some tests tomorrow when I get down to the sprints.

by Noah Kantrowitz, 13 years ago

Attachment: django-ticket-15611.diff added

comment:4 by Noah Kantrowitz, 13 years ago

Owner: changed from Noah Kantrowitz to Jannis Leidel

comment:5 by Luke Plant, 13 years ago

Type: Bug

comment:6 by Luke Plant, 13 years ago

Severity: Normal

comment:7 by Julien Phalip, 13 years ago

UI/UX: set

comment:8 by Julien Phalip, 13 years ago

Easy pickings: unset
Triage Stage: AcceptedDesign decision needed

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.

comment:9 by Jacob, 12 years ago

milestone: 1.3

Milestone 1.3 deleted

comment:10 by Jannis Leidel, 12 years ago

Cc: Jannis Leidel removed
Owner: Jannis Leidel removed

comment:11 by Aymeric Augustin, 11 years ago

Triage Stage: Design decision neededAccepted

The option to offer "more flexibility" didn't apper, and it doesn't look like it will be implemented any time soon. Can we proceed with the bugfix?

comment:12 by Tim Graham, 11 years ago

Has patch: set

comment:13 by Tim Graham, 10 years ago

Patch needs improvement: set

Patch doesn't apply cleanly.

comment:14 by Tim McCurrach, 3 years ago

I think this can be closed now. We have get_readonly_fields, and get_fields both of which accept an obj argument which will be None in the case of an add_view. This allows you to completely customise what fields you want to be readonly (or even present) for both add_view and change_view.

comment:15 by Mariusz Felisiak, 2 months ago

Has patch: unset
Patch needs improvement: unset
Resolution: fixed
Status: newclosed
Type: BugNew feature

Customization options are now available, and they are better than hiding readonly fields all the time. Closing as "fixed".

Note: See TracTickets for help on using tickets.
Back to Top