# Field Types

# Text

Text fields are meant to be used for simple text value collection. You may wish to use this field type for multi-option fields that can only collect a single value, such as Select and Radio fields. You can optionally use the Options fieldtype instead.

• Can be set to be required inside the Form Builder.
• Check on the type text in a conditional when automating rendering of forms.
• Stored in database as varchar(255) type.

# Textarea

Textarea fields are simple multi-line input fields.

• Can be set to be required inside the Form Builder.
• Check on the type textarea in a conditional when automating rendering of forms.
• Stored in database as text type.

# Email

Email fields are basically Text fields but have email address validation and added ability for handling email notifications. These fields can be set to be required inside the Form Builder.

• Can be set to be required inside the Form Builder.
• Required field type if you wish for your users to receive an email notification.
• Required field type if you're using with a Mailing List API integration.
• To allow sending of email notifications to more than 1 email address (e.g. in the case of a "tell-a-friend" type form), you will need to add multiple input fields, each with the input name like email[].
• Check on the type email in a conditional when automating rendering of forms.
• Stored in database as varchar(255) type.

# Hidden

Hidden fields are simple input fields meant for "quietly" collecting data from the user or about the page they're on.

• Check on the type hidden in a conditional when automating rendering of forms.
• Stored in database as varchar(255) type.

# Options

Since Express Forms takes a more simplistic approach to building forms and handling field data, there's no real need for multi-option field types to be defined. However, to aid with data handling (arrays) and template conditionals when automating form rendering, the special Options field type is available in place of field types like:

• Select
• Multiple Select
• Checkbox Group
• Radio Group

You may wish to use a Text field type for Select and Radio fields however, since they would just be storing a single value.

• Can be set to be required inside the Form Builder.
• Check on the type options in a conditional when automating rendering of forms.
• Stored in database as varchar(255) type.

# Checkbox

Single checkbox fields are available for collecting a simple boolean true value for a field. There is no option to change the value of this field type.

• Can be set to be required inside the Form Builder.
• Check on the type checkbox in a conditional when automating rendering of forms.
• Stored in database as tinyint(1) type.

# File

File fields allow you to collect file uploads/attachments for your forms using Craft Assets. They are complete with validation as well. The following controls are available:

• Upload Location - select an Asset volume.
  • Does NOT work with Image Transforms.
• Restrict allowed file types?
  • When enabled, shows a list of available file types to be allowed/disallowed.
• Max File Size - specify the default maximum file size, in KB. Defaults to 2048 KB, respecting Craft system settings. Is subject to:
  • Craft's maxUploadFileSize setting
  • PHP memory_limit
  • PHP post_max_size
  • PHP upload_max_filesize
• Limit - total number of files allowed to be uploaded, defaults to 1.
  • Specify a number larger than 1 to allow multiple files to be uploaded at the same time.
  • Be sure that your template code contains multiple attribute to a single file upload input if accepting more than 1 file.
• Stored in database as varchar(255) type.

Additional info:

• Can be set to be required inside the Form Builder.
• Check on the type file in a conditional when automating rendering of forms.

# Other Types

There are other field type options available beyond the ones listed above:

# Dynamic Recipients

Sometimes you might need a field that allows a user to specify which recipient/location/department should receive an email notification about their inquiry. For this, you can use the Dynamic Recipients field approach. In Express Forms, you'll need to manually approach this as follows:

{% set form = craft.expressforms.form("formHandle") %}

{{ form.openTag({
  dynamicRecipients: {
    myFieldHandle: {
      map: {
        sales: "sales@example.com",
        service: "service@example.com",
        support: ["support@example.com", "another@example.com"]
      },
      template: "template-filename.twig",
    },
  }
}) }}

<select name="myFieldHandle">
  <option value="sales">Sales</option>
  <option value="service">Service</option>
  <option value="support">Support</option>
</select>

To break it down:

# reCAPTCHA

Express Forms includes built-in support for reCAPTCHA v2 Checkbox. To enable, visit the Spam section of the Settings area (Express Forms -> Settings -> Spam).

<div class="form-group{% if form.recaptcha.hasErrors %} has-error{% endif %}">
  <label class="required">
    Please confirm you're not a robot...
  </label>
  {{ form.recaptcha.render }}
  {{ forms.renderErrors(form.recaptcha) }}
</div>

• If you're loading an entire form via AJAX, you'll need to load the reCAPTCHA JS yourself, since it's considered insecure otherwise and the browser blocks it. You should add this script tag anywhere on your page, preferably the footer:

<script
  type="text/javascript"
  src="https://www.google.com/recaptcha/api.js?render=explicit"
></script>