.. versionadded:: 2.3

The ``http_method_override`` option was introduced in Symfony 2.3.

This determines whether the ``_method`` request parameter is used as the intended

HTTP method on POST requests. If enabled, the

test

If this configuration parameter is present (and not ``false``), then the

services related to testing your application (e.g. ``test.client``) are loaded.

cookie_secure

This determines whether cookies should only be sent over secure connections.

cookie_httponly

This determines whether cookies should only be accessible through the HTTP protocol.

This means that the cookie won't be accessible by scripting languages, such

enable_annotations

If this option is enabled, validation constraints can be defined using annotations.

use_forward

If you'd like the user to be forwarded to the login form instead of being

redirected, set this option to ``true``.

post_only

By default, you must submit your login form to the ``check_path`` URL as

a POST request. By setting this option to ``false``, you can send a GET request

Redirecting after Login

* ``default_target_path`` (type: ``string``, default: ``/``)

* ``target_path_parameter`` (type: ``string``, default: ``_target_path``)

.. _reference-security-pbkdf2:

disable_delivery

If true, the ``transport`` will automatically be set to ``null``, and no

emails will actually be delivered.

logging

If true, Symfony's data collector will be activated for Swift Mailer and the

information will be available in the profiler.

multiple

If this option is true, the input value is expected to be an array instead

of a single, scalar value. The constraint will check that each value of

strict

If true, the validator will also check the type of the input value. Specifically,

this value is passed to as the third argument to the PHP :phpfunction:`in_array` method

allowExtraFields

If this option is set to ``false`` and the underlying collection contains

one or more elements that are not included in the `fields`_ option, a validation

extraFieldsMessage

The message shown if `allowExtraFields`_ is false and an extra field is detected.

allowMissingFields

If this option is set to ``false`` and one or more fields from the `fields`_

option are not present in the underlying collection, a validation error will

missingFieldsMessage

The message shown if `allowMissingFields`_ is false and one or more fields

are missing from the underlying collection.

checkMX

If true, then the :phpfunction:`checkdnsrr` PHP function will be used to

check the validity of the MX record of the host of the given email.

checkHost

If true, then the :phpfunction:`checkdnsrr` PHP function will be used to

check the validity of the MX *or* the A *or* the AAAA record of the host

caseSensitive

The validator will allow ISSN values to end with a lower case 'x' by default.

When switching this to ``true``, the validator requires an upper case 'X'.

requireHyphen

The validator will allow non hyphenated ISSN values by default. When switching

this to ``true``, the validator requires a hyphenated ISSN value.

match

If ``true`` (or not set), this validator will pass if the given string matches

the given `pattern`_ regular expression. However, when this option is set

ignoreNull

.. versionadded:: 2.1

The ``ignoreNull`` option was introduced in Symfony 2.1.

| Variable | Type | Usage |

| preferred_choices | ``array`` | A nested array containing the ``ChoiceView`` objects of |

| | | choices which should be presented to the user with priority. |

| is_selected | ``callable`` | A callable which takes a ``ChoiceView`` and the selected value(s) |

| | | and returns whether the choice is in the selected value(s). |

.. tip::

allow_add

If set to ``true``, then if unrecognized items are submitted to the collection,

they will be added as new items. The ending array will contain the existing

allow_delete

If set to ``true``, then if an existing item is not contained in the submitted

data, it will be correctly absent from the final array of items. This means

prototype

This option is useful when using the `allow_add`_ option. If ``true`` (and

if `allow_add`_ is also ``true``), a special "prototype" attribute will be

prototype_name

If you have several collections in your form, or worse, nested collections

you may want to change the placeholder so that unrelated placeholders are not

error_bubbling

.. include:: /reference/forms/types/options/_error_bubbling_body.rst.inc

Variable Type Usage

choices

Instead of allowing the `class`_ and `query_builder`_ options to fetch the

entities to include for you, you can pass the ``choices`` option directly.

attr

~~~~

If you want to add extra attributes to an HTML field representation

you can use the ``attr`` option. It's an associative array with HTML attributes

attr

~~~~

If you want to add extra attributes to the HTML representation of the button,

you can use ``attr`` option. It's an associative array with HTML attribute

by_reference

~~~~~~~~~~~~

In most cases, if you have a ``name`` field, then you expect ``setName()``

to be called on the underlying object. In some cases, however, ``setName()``

cascade_validation

~~~~~~~~~~~~~~~~~~

Set this option to ``true`` to force validation on embedded form types.

For example, if you have a ``ProductType`` with an embedded ``CategoryType``,

constraints

~~~~~~~~~~~

Allows you to attach one or more validation constraints to a specific field.

For more information, see :ref:`Adding Validation<form-option-constraints>`.

data

~~~~

When you create a form, each field initially displays the value of the

corresponding property of the form's domain object (if an object is bound

Since Symfony 2.3, empty values are also supported if the ``expanded``

option is set to true.

This option determines whether or not a special "empty" option (e.g. "Choose an option")

will appear at the top of a select widget. This option only applies if the

~~~~~~~~~~~~~~

.. include:: /reference/forms/types/options/_error_bubbling_body.rst.inc

.. versionadded:: 2.1

The ``error_mapping`` option was introduced in Symfony 2.1.

This option allows you to modify the target of a validation error.

expanded

~~~~~~~~

If set to true, radio buttons or checkboxes will be rendered (depending

on the ``multiple`` value). If false, a select element will be rendered.

multiple

~~~~~~~~

If true, the user will be able to select multiple options (as opposed

to choosing just one option). Depending on the value of the ``expanded``

read_only

If this option is true, the field will be rendered with the ``readonly``

attribute so that the field is not editable.

required

If true, an `HTML5 required attribute`_ will be rendered. The corresponding

``label`` will also render with a ``required`` class.