Opened 19 years ago
Closed 18 years ago
#2159 closed defect (invalid)
dropdowns defaulting to a lone value cause edit_inline objects with core=True to try to be saved
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | contrib.admin | Version: | dev | 
| Severity: | normal | Keywords: | |
| Cc: | gary.wilson@… | Triage Stage: | Design decision needed | 
| Has patch: | no | Needs documentation: | no | 
| Needs tests: | no | Patch needs improvement: | no | 
| Easy pickings: | no | UI/UX: | no | 
Description
Normally, defaulting to a value when it is the only selection option is fine; however, it is annoying when the object is being edited inline of the related object (even more annoying with the default of three related objects displayed).  This is because, on save, the form thinks you are trying to enter an entry for the inline object when, in fact, you are not.  This behavior will be seen for ForeignKey fields and CharFields using the choices parameter.  They must also have core=True.
In order to have the edit_inline objects not try to get saved, user must change the selection to "---------" for each object before saving.  Either "---------" should always be the default (even when there is only one selection option), or "---------" should be the default when the object is edited inline
Change History (3)
comment:1 by , 19 years ago
| Cc: | added | 
|---|
comment:2 by , 19 years ago
| Triage Stage: | Unreviewed → Design decision needed | 
|---|
comment:3 by , 18 years ago
| Resolution: | → invalid | 
|---|---|
| Status: | new → closed | 
Luckily, thankfully, there's no such thing as the horrific "core" in newforms admin, so we don't have to figure out what the hell's going on here :)