Jump to main content Jump to doc navigation


Call below the FormIt (or any other request-processing snippet) to generate a single HTML form field.

For example:

&label=`Enter your name:`]]

Managing Defaults

  • You can call the fieldSetDefaults snippet with any of the field snippet parameters to set the default values for subsequently-processed field snippets.
  • There is a complete property set in the dummy fieldPropSetExample snippet. You can copy this to the field snippet if desired. However, any property sets on the field snippet prevent the fieldSetDefaults snippet from working for those properties.

Simple Example Form

[[!FormIt? &prefix=`myprefix.` &submitVar=`submitForm`]]
<form action="[[~[[*id]]]]" method="post">
    [[!fieldSetDefaults? &prefix=`myprefix.` &outer_tpl=`myWrapTpl` &resetDefaults=`1`]]
    [[!field? &name=`full_name` &type=`text` &class=`required`]]
    [[!field? &name=`favorite_color` &type=`checkbox` &options=`Blue||Red||Yellow`]]
    [[!field? &name=`location` &type=`select` &label=`Where are you from?` &options=`United States==US||New Zealand==NZ||Never Never Land==NNL`]]
    [[!field? &name=`message` &type=`textarea`]]
    [[!field? &name=`submitForm` &type=`submit` &label=` ` &message=`Submit Form`]]

Snippet Parameters

The most common parameter names are in bold.

Parameter Description Default
array Used with field types that can provide multiple responses (checkbox, select & file input types by default) to signify that the field should be treated as an array. This will append [] to the field name to signify to the form that multiple result values may be selected.
If you're passing an array of options (which will look like this `One Two
cache By default, caching is "auto". Auto caching works as follows: Simple fields without options, elements, or overrides are not cached, nor do they usually benefit from it. To enable caching to see if it helps performance specify &cache=1. Fields that have options use selective caching. To disable caching, specify &cache=0.
Note that caching does not cache checked/ selected status or the following dynamically-generated placeholders: error, error_class, and current_value auto
custom_ph (OPTIONAL) Speed improvement. Listing your custom placeholders here or in a fieldSetDefaults call speeds up chunk processing by setting a blank default value. You do not need to list placeholders here that already have a value set somewhere else. class,multiple,array,header, default,class,outer_class,label,note,note_class,size,
debug Turn on debugging. 0
delimiter_template The template for the chunk type separator. <!-- [[+type]] -->
default_delimiter If no outer_type or type is specified, this will be used as the type for the purposes of processing the template chunk. default
default_value The default value to use if no value is found.
error_class The name of the class to use for the [[+error_class]] placeholder. This placeholder is generated along with [[+error]] if a FormIt error is found for this field. error
error_prefix Usually automatically determined, you can override the prefix that is prepended to the field name for the purpose of getting the field errors from the MODX placeholders.
inner_element_class The element class (modSnippet or modChunk). modChunk
inner_element Similar to inner_html, but accepts the name of an element (a chunk or snippet for example). All of the placeholders and parameters are passed to the chunk. You can also specify an optional chunks_path parameter that allows file-based chunks in the form name.chunk.tpl
inner_element_properties A JSON array of additional parameters to pass. Example: {"tpl" : "myChunk"} []
inner_html Specify your own HTML instead of using the field template. Useful if you want to use the outer_tpl and smart caching but specify your own HTML for the field.
key_prefix To use the same field names for different forms on the same page, specify a key prefix.
mark_selected If left blank or set to zero, disables option marking. By default if "options" or an options override is specified, the field snippet will add a marker such as \' checked="checked"\' or (if the field type is "select") \' selected="selected"\' in the right place, assuming you are using HTML syntax for value (value="X"). You can specify the marker to use with the selected_text option. This is a lot faster than using FormItIsSelected or FormItIsChecked. 1
name The name of the field.
options_delimiter_inner The delimiter used to separate the label from the value in the options parameter. ==
options_delimiter_outer The delimiter used to separate each option in the options parameter.
options If your field is a nested or group type, such as checkbox, radio, or select, specify the options in tv-style format like so: Label One==value1
options_element_class The element class (modSnippet or modChunk). modChunk
options_element Similar to options_html, but accepts the name of an element (a chunk or snippet for example). All of the placeholders and parameters are passed to the chunk. You can also specify an optional chunks_path parameter that allows file-based chunks in the form name.chunk.tpl
options_element_properties A JSON array of additional parameters to pass. Example: {"tpl" : "myChunk"} []
options_html You can specify your own HTML instead of using the &options parameter to generate options. For example, you might decide to pass in option value="something" data="something" if the type is set to "select". It otherwise acts exactly as if you had specified the options parameter for marking and caching purposes.
option_type Specify the field type used for each option. For &type=select, this defaults to "option". For &type=checkbox or &type=radio, this defaults to "bool".
outer_tpl The outer template chunk, which can be used for any HTML that stays consistent between fields. This is a good place to put your label tags and any wrapping li or div elements that wrap each field in your form. This template can be segmented by field type (or outer type) just like the inner template (&tpl). fieldWrapTpl
outer_type The outer type. The outer template chunk can divided just like the fieldTypesTpl, but with names unrelated to field types. If left empty, outer_type will default to type.
prefix The prefix used by the FormIt call this field is for - may also work with EditProfile, Register, etc... snippet calls. The prefix is also used for other purposes, such as getting and setting the value in the session. fi.
selected_text The text to use for marking options as selected, checked, or whatnot. Usually automatically determined based on the type, but this can be useful if you have a custom type or want something else.
set_type_ph Sets these placeholders to either true or false depending on whether they match this field type. So, if the field type is text and text is listed here, the placeholder "text" will be set to 1, and the other types listed will be set to an empty string. text,textarea,checkbox,radio,select
to_placeholders If set, will set all of the placeholders as global MODx placeholders as well. 0
tpl The template chunk to use for templating all of the various fields. Each field is separated from the others by wrapping it - both above and below - with the following HTML comment: <!-- fieldtype --> , where fieldtype is the field type. fieldTypesTpl
type The field type. Used to decide which subset of the tpl chunk to use. text
use_cookies If no value is found, get the value from the $_COOKIES global array. The array key is use_cookies_prefix+prefix+name. 0
use_cookies_prefix The prefix to use for cookie storage. field.
use_formit Get the value from MODX placeholders such as those set by formit. The placeholder key is PREFIX+NAME (so you can make this compatible with Login and similar snippets by changing the prefix). 1
use_get If no value is found, get the value from the $_GET global array. The array key is the name of the field. 0
use_request If no value is found, get the value from the $_REQUEST global array. The array key is the name of the field. 0
use_session If no value is found, get the value from the $_SESSION global array. The array key is use_session_prefix+prefix+name. 0
use_session_prefix The prefix to use for session storage. field.


Field snippets use the following two chunks by default to template inner and outer HTML, respectively: FieldTypesTpl and FieldWrapTpl. The &tpl and &outer_tpl parameters can be used to change the names of these chunks.

The default templates are installed in the core/components/formitfastpack/elements/chunks/. Future versions will include an option to install these chunks automatically, but for now you can copy and paste the content into chunks called "FieldTypesTpl" and "FieldWrapTpl".

Special separators are used to separate the HTML for each type, allowing all of the field types to be managed with only two chunks.

The &type and &outer_type parameters can be used to change the inner and outer types. Field types that contain options also use a third type: **&**option_type. For example, a select field might use &type=`select` &option_type=`option.

Which segment of the chunk is used for a particular type?

  1. By default, the separators above and below the segment are <!-- TYPE -->, where TYPE is the type of the field. For example, if &type=text``, the separator (above and below the HTML field) is <!-- text -->.
  2. If the separators for the type are not found, the snippet looks for the default separators: <!-- default -->
  3. Finally, if the default separators are also not found, the entire chunk is used.

Here is a subset of the default &tpl chunk ( fieldTypesTpl):

<!-- default -->
<input type="[[+type]]" name="[[+name]]" id="[[+key]]" value="[[+current_value]]" class="[[+type]] [[+class]][[+error_class]]" />
<!-- default -->
<!-- hidden -->
<input type="[[+type]]" name="[[+name]]" value="[[+current_value]]" />
<!-- hidden -->
<!-- textarea -->
<textarea id="[[+key]]" class="[[+type]] [[+class]][[+error_class]]" name="[[+name]]">[[+current_value]]</textarea>
<!-- textarea -->

Here is the default &outer_tpl chunk ( fieldWrapTpl):

<!-- default -->
<div class="[[+outer_class]]" id="[[+name]]_wrap">
<label for="[[+name]]" title="[[+name:replace=`_== `:ucwords]]">[[+label:default=`[[+name:replace=`_== `:ucwords]]`]][[+req:notempty=` *`]]</label>
[[+note:notempty=`<span class="[[+note_class:default=`note`]]"><em>[[+note]]</em></span>`]]
[[+error:notempty=`<span class="[[+error_class]]">[[+error]]</span>`]]
<!-- default -->

The "note", "note_field", and "req" placeholders above are examples of custom placeholders.


All of the parameters you pass into the snippet are available as placeholders. This allows you to add custom placeholders such as "required", "class", etc.... simply by passing them into the snippet as parameters.

In addition, the following special placeholders are passed in:

Placeholder Description
inner_html Used in the outer_tpl to position the generated content, which will vary by field type. Simple example: <li>[[+inner_html]]</li>
options_html Used in the tpl to position the options html (only when using &options or an options override). Example: <select name="[[+name]]">[[+options_html]]</select>
current_value The value of the FormIt value for the field name. Exactly the same as writing [[!fi.fieldname]] for each fieldname (if the prefix is fi.). Never gets cached.
error The value of the FormIt error message for the field name, if one is found. Exactly the same as writing [[!fi.error.fieldname]] for each fieldname (if the prefix is fi.). Never gets cached.
error_class set to the value of the error_class parameter (default is " error") ONLY if a FormIt error for the field name is found. Exactly the same as using [[+error:notempty=error]].
key A unique but human-friendly identifier for each field or sub-field (useful for HTML id attributes). Generated from the key_prefix, prefix, field name, and (only if using an option field) value.

Using in PHP Scripts

You can write snippets to generate forms from a configuration by simply calling $modx->runSnippet('field', $field_properties_array); . For example:

$output = '';
$output .= $modx->runSnippet('field', array('name'=> 'name', 'type'=> 'text'));
$output .= $modx->runSnippet('field', array('name'=> 'email', 'type'=> 'email'));
return $output;

More Examples

Set the defaults for all field snippets lower down


Type defaults to text:

[[!field? &name=`name`]]

Options use the same format as template variables: Label1==Value1||Another Label==another_value. To use the same value for both label and value, just use Value1||Value2||Value3

    &label=`Your Favorite Color:`
    &label=` `
    &options=`Publish==publish||Save as draft==save||Preview==preview`

Here, a different style of form fields is used by switching out of the default chunks. Use property sets to easily maintain various form styles around the site.


You can disable the outer template:


Here, there were too many options to list, so a chunk name is specified instead that contains the option HTML:

    &header=`Please select...`

A snippet can be used instead of a chunk:

    &title=`Choose some categories`

&req=1 is an example of a custom placeholder. In this case, it can be used to add an asterisk or something similar to the label using the notempty output filter


There is no need to specify a label if you have a naming convention for your form fields. For example, use [[+label:default=``[[+name:replace= == :ucwords]]``]] to generate a label in your templates. This is already done in the default templates.


Here is a custom field with a custom type. If you use options with a custom type, you need to specify the type of the options fields with &option_type.

    &_note=`Make sure you add this custom field to the &tpl chunk!`
    &another_custom_placeholder=`And another custom value`

You can even use field snippets for the submit field:


Support the team building MODX with a monthly donation.

The budget raised through OpenCollective is transparent, including payouts, and any contributor can apply to be paid for their work on MODX.



$0 per month—let's make that $500!

Learn more