Using forms on Plone 6.2 with Volto: Best practices and blocking errors

Plone Support Add-on Development
1

I'm currently working on a Plone 6.2 project and I am facing some blocking issues regarding forms rendering and submission.

I've performed several tests using Plone 6.2 and Volto 19, but I can't get it to work reliably.

  • In some configurations, the form component doesn't even load on the frontend or backend layout editor.

  • In one specific setup using @plone/volto-form-block, I managed to render the form on the frontend, but submitting it triggers a block error.

I opened a GitHub issue back in April describing this behavior: [Bug] OPTIONS request fails with 404 when using ++api++ traverser (Plone 6.2rc1 / Volto 19a31) · Issue #4315 · plone/Products.CMFPlone · GitHub .
I tested it again after the Plone 6.2 release with volto 19.1.3, but the behavior remains unchanged.

My questions to the community are:

  1. What is currently the recommended/standard way to handle user-facing forms in Plone 6.2 (Volto)? Should I try again collective.easyform with block extensions, or is there a new native approach?

  2. Am I missing any crucial setup or serialization configuration between the backend and the Volto frontend?

Thanks in advance for any insights!

2

Visit GitHub - RenteriaMX/MF-Blocks-Manager · GitHub create blocks forms.