- What is Symfony?
- Get started
- Documentation
- Community
- Services
-
News
Latest News
What happened last week in Symfony?
This week, after the successful launch of Symfony 2.3, the development activity focused on the upcoming Symfony 2.4 version. The most important change was the introduction of simpler customization options for the Security component. In addition, Symfony 2.3.1 was released to address some minor bugs.
Upcoming EventsThe Symfony Community organizes events all over the world on a regular basis. Here are the next ones.
Switzerland, Colab Zurich Zentralstrasse 37, Zürich — #5 Symfony UserGroup ZH
on June 19, 2013, from 19:00 to 22:15
Switzerland, Zurich — Symfony CMF workshop day
on June 21, 2013, from 09:00 to 18:00
Spain, Madrid — deSymfony 2013
from June 21, 2013 to June 23, 2013
Germany, Cologne — SymfonySummit
from July 04, 2013 to July 05, 2013 - About
Table of Contents
Questions & Feedback
Found a typo or an error?
Want to improve this document? Edit it.
Need support or have a technical question?
Post to the user mailing-list.
Master Symfony2 fundamentals
Symfony hosting done right
Discover the SensioLabs Support
email Field Type
email Field Type¶
The email field is a text field that is rendered using the HTML5
<input type="email" /> tag.
| Rendered as | input email field (a text box) |
| Inherited options | |
| Parent type | field |
| Class | EmailType |
Inherited Options¶
These options inherit from the field type:
max_length¶
type: integer
This option is used to add a maxlength attribute, which is used by
some browsers to limit the amount of text in a field.
required¶
type: Boolean default: true
If true, an HTML5 required attribute will be rendered. The corresponding
label will also render with a required class.
This is superficial and independent from validation. At best, if you let Symfony guess your field type, then the value of this option will be guessed from your validation information.
label¶
type: string default: The label is "guessed" from the field name
Sets the label that will be used when rendering the field. The label can also be directly set inside the template:
1 | {{ form_label(form.name, 'Your name') }}
|
trim¶
type: Boolean default: true
If true, the whitespace of the submitted string value will be stripped
via the trim() function when the data is bound. This guarantees that
if a value is submitted with extra whitespace, it will be removed before
the value is merged back onto the underlying object.
read_only¶
type: Boolean default: false
If this option is true, the field will be rendered with the readonly
attribute so that the field is not editable.
disabled¶
type: boolean default: false
If you don't want a user to modify the value of a field, you can set the disabled option to true. Any submitted value will be ignored.
error_bubbling¶
type: Boolean default: false unless the form is compound
If true, any errors for this field will be passed to the parent field or form. For example, if set to true on a normal field, any errors for that field will be attached to the main form, not to the specific field.
mapped¶
type: boolean
If you wish the field to be ignored when reading or writing to the object, you
can set the mapped option to false.
NEWS FROM THE BLOG
IN THE NEWS
is a trademark of Fabien Potencier. All rights reserved.