"content" Colum stores escaped JSON-Value if file-upload field is present

[xuneXTW]

Describe the bug

Hi there

It looks like the newest update will do something to my forms if file-upload fields are present.
The stored submissions in the CP are always empty and the "content" field in the submissions table seems to store some escaped JSON value that could not be parsed in the CP-Form.

Steps to reproduce

1. Add a file-upload field to a form
2. Submit the form

Form settings

• Multi-page form: No
• Submission Method: Ajax
• Client-side Validation: Yes and No
• Custom Form Templates: No

Craft CMS version

Craft Pro 5.5.10

Plugin version

3.0.18

Multi-site?

Yes

Additional context

I think this has something to do with the changes made to the MariaDB issues with file-uploads as it seems only to happen on MariaDB 10.x installs.

With 3.0.16 the forms were working properly.

[engram-design]

We're having incredibly mixed results with MariaDB it seems. For some people encoding is working, others seems like it's not working correctly. We certainly thought things were sorted!

Anyway, I've revamped how File Upload fields update their content to hopefully alleviate this. If you can let me know how you go with this! To get this early, run composer require verbb/formie:"dev-craft-5 as 3.0.18".

[xuneXTW]

@engram-design thank you! This seems to work at least on my side now. I've tested it local on MySQL8 and on the staging environment on MariaDB 10.6.x. Now the results are stored properly even with or without file-fields in the form

[engram-design]

Awesome, thanks for confirming!