On demo.plone.org form block is broken.

[jensens]

It emits an error. See https://demo.plone.org/block/form/edit

[davisagli]

The error traces shown by a production build of volto are pretty much useless, since they are positions in the minified bundles.

There's a more useful trace in the browser console, which uses the sourcemap to show source filenames:

In this case, it might be a problem with the error that is passed into the FormFieldWrapper:

[fredvd]

Updates/improvements have been made to volto-form-block and the supported backend recently, that caused some issues with enabling volto-form-block in another project, like requiring a spam protection. We briefly discussed this at the beethoven sprint this week. collective.honeypot is a good simple protection.

I could look into it, I see the backend add'on collective.volto.formsupport is in the backend setup.py, but not pinned in constraints.txt.

I would like to check if it is 'wise' to add form support to a demo site where we give people admin accounts so they can start using any hacked/open smtp server/account they find. Ok, we should reset the instances every day, but still. I'd like to check possible security implications.