With the current paradigm, a single form database record is used to both store the current state of the form and create the submissions coming in from published forms.
This flow is buggy in the case that:
1) a form is created an published
2) a form is edited and saved, but not published
3) a user submits responses to the originally published form
This is because the originally published form may have fields that have been removed from the new database form record. These fields will be thrown away.
Fix: make sure that form submissions are saved regarless of any edits that may have happened to the form itself in the meantime.
kgardnr
commented
8 years ago
With the current paradigm, a single form database record is used to both store the current state of the form and create the submissions coming in from published forms.
This flow is buggy in the case that: 1) a form is created an published 2) a form is edited and saved, but not published 3) a user submits responses to the originally published form
This is because the originally published form may have fields that have been removed from the new database form record. These fields will be thrown away.
Fix: make sure that form submissions are saved regarless of any edits that may have happened to the form itself in the meantime.
FYI: @riley @impronunciable @pablocubico