Opened 12 years ago

Closed 12 years ago

Last modified 11 years ago

#754 closed defect (fixed)

editable=False causes fields to lose current value upon save in admin interface

Reported by: Tom Tobin <korpios@…> 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: UI/UX:


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 Changed 12 years ago by Tom Tobin <korpios@…>

Resolution: fixed
Status: newclosed

It looks like this one got fixed somewhere along the way.

comment:2 Changed 11 years ago by korpios

Reporter: changed from Tom Tobin <korpios@…> to Tom Tobin <korpios@…>
Note: See TracTickets for help on using tickets.
Back to Top