Raw Markup Field Type Displaying in Incoming Form #1587
-
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
In the main, people use the raw markup fields for adding clauses and extra information/text to the forms - so they want those things in the final form. Why would you create input fields in your raw markup like this, rather than just making them text fields in the form? Doing it this way, you lose all of our form functionality, like being able to use "showif" to control visibility based on the value of other fields, or being able to make fields mandatory, etc. You could inject extra elements into the DOM with code in the header if you need to add things that shouldn't appear in the form output at the end. |
Beta Was this translation helpful? Give feedback.
Ok, I see. Yes, I'm afraid that is one limitation that can't be worked around easily - the fields have to be laid out vertically due to them being in table structures. We are considering how this might be changed in future.
For now though, if you want to change the layout completely, the only option is to make the form in our system, then make your own version of the form - and use the same names as the input/select fields as ours, and with the hidden inputs from the top of our form. You can then have your form POST to our handler.