#754 closed defect (fixed)
editable=False causes fields to lose current value upon save in admin interface
| Reported by: | Owned by: | Adrian Holovaty | |
|---|---|---|---|
| Component: | contrib.admin | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
If editable=False is set on a model field, that field's value will be set to its default upon saving from the admin interface, losing its current value. This behavior does not occur when manipulating model objects directly.
Example: a BooleanField has default=False and editable=False. If an object of its corresponding model has this field set to True, and the object is subsequently edited and saved in the admin interface, the object will have its value for that field set to False.
Change History (2)
comment:1 by , 18 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:2 by , 17 years ago
| Reporter: | changed from to |
|---|
Note:
See TracTickets
for help on using tickets.
It looks like this one got fixed somewhere along the way.