id summary reporter owner description type status component version severity resolution keywords cc stage has_patch needs_docs needs_tests needs_better_patch easy ui_ux
611 fields with editable=False do not render davidschein@… adrian "At least 3 issues (#455,#342,#262), I think, are related to this problem:
When a field has editable=False, it is not added to the FormWrapper's field list in the change manipulator {{{__init__()}}}.
We have,
{{{
def manipulator_init(opts, add, change, self, obj_key=None):
if change:
...
self.fields = []
for f in opts.fields + opts.many_to_many:
if f.editable and not (f.primary_key and change) and (not f.rel or not f.rel.edit_inline):
self.fields.extend(f.get_manipulator_fields(opts, self, change))
}}}
I do not know the design, but it is evident that django *intends* for editable=False to do something akin to render with the html disable attribute ON. Other comments imply that editable=False means ""do not display"", but of course there are other mechanisms for this, e.g via the fields attribute admin UI.
My workaround is to not use editable and instead add javascript to add the disable attribute to the fields I want displayed readonly.
" defect closed contrib.admin minor wontfix editable readonly disable Unreviewed 0 0 0 0