Notorious form data issue about aldryn-forms HOT 9 CLOSED

Sounds like you're proposing the right way forward to me.

from aldryn-forms.

I agree on the general idea.
We should use plain TextField with externally encoded json, though, to be compatible with every database instead of relying on specific field type (if I understand correctly the jsonfield / array field mentions)

from aldryn-forms.

@yakky yes is why I think we should use https://github.com/bradjasper/django-jsonfield which uses a textfield for representation and takes care of serialization and such

from aldryn-forms.

@czpython "django-jsonfield is looking for maintainers" :(

from aldryn-forms.

So I've tried to find a way to cleanup the old form submissions to match proper fields in the form,
unfortunately because form submissions have no direct relationships to the form except for a name
and because of the big : problem, it's just impossible to accurately determine which entries are fields and which are not.

To properly fix this going forward, I've decided to create another model for form data that will have the new form structure as json (without using json field). The structure will include the field type, field label and field value.

The old structure will remain in the admin/db to be slowly deprecated and allow time to export this data.

Migrating the old data format to the new is not possible because things like field type are impossible to know from the old format.

from aldryn-forms.

@czpython looks perfectly reasonable

from aldryn-forms.

+1

from aldryn-forms.

Close this ticket?

from aldryn-forms.

Yes, thanks!.
Fixed by b50e039

from aldryn-forms.