Can I confirm that since v5.1.0 enforces the requirement of all fields to have a “name” field even if logically they don’t require them, fields such as spacer.
I think it’s in the new prepare_form_fields()
If I don’t include a name field they don’t render, took a while to figure out what was going on.
thanks for looking at thing @pamtbaau . I will raise it, I just wanted to be sure I hadn’t fallen into a different trap or was doing something wrong in the first place.
The fix was released in v5.1.1 of the Form plugin, I’ve download and tested the release with the form that was problematic and everything worked as it should.