Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#2403 closed defect (fixed)

[patch] forms documentation should use flatten_data rather than __dict__

Reported by: cmgreen@… Owned by: Jacob
Component: Documentation Version: master
Severity: normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

http://www.djangoproject.com/documentation/forms/

  else:
        errors = {}
        # This makes sure the form accurate represents the fields of the place.
        new_data = place.__dict__

When the object has a associated references, the dict approach does not populate those other items. I tracked down to understand why a custom view was not working but a generic view was.

that new_data should be replaced by place.flatten_data()

Attachments (1)

doc_update.diff (538 bytes) - added by heckj@… 10 years ago.
attaching patch to resolve exactly this

Download all attachments as: .zip

Change History (3)

Changed 10 years ago by heckj@…

Attachment: doc_update.diff added

attaching patch to resolve exactly this

comment:1 Changed 10 years ago by heckj@…

Summary: forms documentation should use flatten_data rather than __dict__[patch] forms documentation should use flatten_data rather than __dict__

attached patch to update the forms/manipulator documentation to utilize manipulator.flatten_data() instead of accessing the objects dict for the raw goods...

comment:2 Changed 10 years ago by anonymous

Resolution: fixed
Status: newclosed

This was fixed in r3758.

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