Form Field

{{ form_field }}

{{ hidden_field }}

Should be used to output a hidden field inside a form, which by definition is not displayed to or directly editable by users.

Hidden form fields are generally only useful for template developers, since the user is not able to directly edit their value. When including a hidden field in a form, developers should ensure that there is some way for the value to be set - typically either using liquid markup to specify the value explicitly in the template or using javascript after the form is displayed to calculate and set a dynamic value

{{ checkboxlist_field }}

Should be used to display a list of checkboxes inside a form.

{{ textarea_field }}

Should be used to display a textarea field inside a form.

{{ checkbox_field }}

Should be used to display a checkbox field inside a form.

{{ file_field }}

Should be used to display a file upload field inside a form.

There may be additional restrictions on file uploads that are not specified in the validators, such as max upload filesize. Furthermore, after being uploaded, all files are automatically scanned for malware, although that does not prevent users from uploading malicious files; it only reports the expected security status of the file to administrators

{{ group_field }}

Should be used to display a group of fields inside a form.

Groups may be deeply nested, which templates should be able to handle. Template developers may optionally handle collapsing and expanding groups, although if possible it is recommended to allow it for optimal feature parity with the editor options when editing form fields

{{ submit_field }}

Should be used to display a submit button inside a form.

Almost every form should have one and only one submit button.

{{ button_field }}

Should be used to display a custom button inside a form.

The button field should only be used by power users who know what they are doing, and should always be tested to ensure that it works as anticipated. Most of the time the submit field should be used instead.

{{ select_field }}

Should be used to display a select list inside a form.

{{ radio_field }}

Should be used to display a radio field inside a form.

{{ label_field }}

Should be used to display a text label inside a form.

How the label is displayed in the form is entirely up to the template developer as there is currently no way for editors to specify the styling to use when displaying labels

{{ captcha_field }}

Should be used to display a captcha inside a form.

Captcha fields are recommended in order to prevent bots from spamming forms, although each form may only have a single catpcha field. Additionally, it is not recommended for the captcha field to be conditional, as that would defeat its purpose.

{{ text_field }}

Should be used to display a text field inside a form.

The text field may also be used to display number inputs, although there are not number-specific properties (eg: increment) so it is currently up to the template developer's discretion how they want to display number inputs

{{ date_field }}

Should be used to display a date field inside a form.