Symfony Forms Cookbook
Basic form building[edit]
Build a form object and render it in a template from within a controller:[1]
// src/AppBundle/Controller/DefaultController.php
namespace AppBundle\Controller;
use Symfony\Bundle\FrameworkBundle\Controller\Controller;
use AppBundle\Entity\Task;
use Symfony\Component\HttpFoundation\Request;
class DefaultController extends Controller
{
public function newAction(Request $request)
{
// create a task and give it some dummy data for this example
$task = new Task();
$task->setTask('Write a blog post');
$task->setDueDate(new \DateTime('tomorrow'));
$form = $this->createFormBuilder($task)
->add('task', 'text')
->add('dueDate', 'date')
->add('save', 'submit', array('label' => 'Create Task'))
->getForm();
return $this->render('Default/new.html.twig', array(
'form' => $form->createView(),
));
}
}
Form classes[edit]
The convention is to put form classes in src/AppBundle/Form/Type/.
// src/AppBundle/Form/Type/TaskType.php
namespace AppBundle\Form\Type;
use Symfony\Component\Form\AbstractType;
use Symfony\Component\Form\FormBuilderInterface;
use Symfony\Component\OptionsResolver\OptionsResolverInterface;
class TaskType extends AbstractType
{
public function buildForm(FormBuilderInterface $builder, array $options)
{
$builder
->add('task')
->add('dueDate', null, array('widget' => 'single_text'))
->add('save', 'submit');
}
public function setDefaultOptions(OptionsResolverInterface $resolver)
{
$resolver->setDefaults(array(
'data_class' => 'AppBundle\Entity\Task',
));
}
public function getName()
{
return 'task';
}
}
getName() should return a unique identifier to be used by the controller.
To use the form class in the controller:
// src/AppBundle/Controller/DefaultController.php
// add this new use statement at the top of the class
use AppBundle\Form\Type\TaskType;
public function newAction()
{
$task = ...;
$form = $this->createForm(new TaskType(), $task);
// ...
}
Services for forms[edit]
Once the form class is built, it can be set up as a service.
# src/AppBundle/Resources/config/services.yml
services:
acme_demo.form.type.task:
class: AppBundle\Form\Type\TaskType
tags:
- { name: form.type, alias: task }
To use the form service in a controller (note that the use statement isn't necessary now):
// src/AppBundle/Controller/DefaultController.php
// ...
public function newAction()
{
$task = ...;
$form = $this->createForm('task', $task);
// ...
}
Or to use the form service in another form class:
// src/AppBundle/Form/Type/ListType.php
// ...
class ListType extends AbstractType
{
public function buildForm(FormBuilderInterface $builder, array $options)
{
// ...
$builder->add('someTask', 'task');
}
}
Render a form[edit]
After passing a form "view" object to a Twig template, the form can be rendered with form helper functions:[2]
{# app/Resources/views/Default/new.html.twig #}
{{ form_start(form) }}
{{ form_errors(form) }}
{{ form_widget(form) }}
{{ form_end(form) }}
form_end(form) renders the form's end tag along with hidden fields, including CSRF protection. It also renders any fields that have not already been rendered.
Rendering form fields[edit]
form_row(form.property)renders a form input along with a label and error messages specific to the form field.formis the name of the form variable, andpropertyis the name of the property being rendered, e.g.form.id,form.name, etc.- The components wrapped up in
form_row()can be rendered separately:form_label(form.property)renders just the label for the field.- Override the label text with
form_label(form.property, 'Custom Label Text')
- Override the label text with
form_errors(form.property)renders errors for the field.form_widget(form.property)renders the form input.- Set properties for the input with
form_widget(form.property, {attr: {'class': 'my-custom-class'}})
- Set properties for the input with
- Individual properties of the fields can be accessed with
form.entity.property.idform.entity.property.nameform.entity.property.label- ^^ Actually I'm not 100% sure that's how it works. Try it out to confirm.
See also[edit]
Handling form submissions[edit]
In the controller, the form object translates user data submitted with the form.[3]
public function newAction(Request $request)
{
// just setup a fresh $task object (remove the dummy data)
$task = new Task();
$form = $this->createFormBuilder($task)
->add('task', 'text')
->add('dueDate', 'date')
->add('save', 'submit', array('label' => 'Create Task'))
->getForm();
$form->handleRequest($request);
if ($form->isValid()) {
// perform some action, such as saving the task to the database
return $this->redirect($this->generateUrl('task_success'));
}
// ...
}
- When the page is first loaded, the form is created and rendered.
handleRequest()recognizes that the form was not submitted and does nothing.isValid()returnsfalseif the form was not submitted.
- When the form is submitted,
handleRequest()translates the datahandleRequest()updates the corresponding properties of the entity object ($taskin this case) with the form data.isValid()returnsfalseif the form data isn't valid.- Execution skips that block where the data would be processed, and instead goes to the original view, which is rendered with the submitted form data and error messages.
Multiple submit buttons[edit]
Add the buttons to the form builder in the controller:[4]
$form = $this->createFormBuilder($task)
->add('task', 'text')
->add('dueDate', 'date')
->add('save', 'submit', array('label' => 'Create Task'))
->add('saveAndAdd', 'submit', array('label' => 'Save and Add'))
->getForm();
Test which button was clicked in the controller using the button's isClicked() method:
if ($form->isValid()) {
// ... perform some action, such as saving the task to the database
$nextAction = $form->get('saveAndAdd')->isClicked()
? 'task_new'
: 'task_success';
return $this->redirect($this->generateUrl($nextAction));
}
Form validation[edit]
With Symfony, it isn't the form that is validated, rather it is the entity object that is tested to confirm that it contains valid data. This is does by defining a set of rules, or constraints, for the entity class.[5]
# AppBundle/Resources/config/validation.yml
AppBundle\Entity\Task:
properties:
task:
- NotBlank: ~
dueDate:
- NotBlank: ~
- Type: \DateTime
The above configuration specifies that the task field cannot be empty and the dueDate field cannot be empty and must be a valid DateTime object.
Validation groups[edit]
Different groups can be defined to validate the underlying object, either in the controller:
$form = $this->createFormBuilder($users, array(
'validation_groups' => array('registration'),
))->add(...);
Or in a form class:
use Symfony\Component\OptionsResolver\OptionsResolverInterface;
public function setDefaultOptions(OptionsResolverInterface $resolver)
{
$resolver->setDefaults(array(
'validation_groups' => array('registration'),
));
}
Disabling validation[edit]
Set the validation_groups option to false:
public function setDefaultOptions(OptionsResolverInterface $resolver)
{
$resolver->setDefaults(array(
'validation_groups' => false,
));
}
Forms without classes[edit]
Example of how to set this up in a controller:[6]
// make sure you've imported the Request namespace above the class
use Symfony\Component\HttpFoundation\Request;
// ...
public function contactAction(Request $request)
{
$defaultData = array('message' => 'Type your message here');
$form = $this->createFormBuilder($defaultData)
->add('name', 'text')
->add('email', 'email')
->add('message', 'textarea')
->add('send', 'submit')
->getForm();
$form->handleRequest($request);
if ($form->isValid()) {
// data is an array with "name", "email", and "message" keys
$data = $form->getData();
}
// ... render the form
}
See also[edit]
See also[edit]
Notes[edit]
- ↑ Building The Form, Symfony forms documentation
- ↑ Rendering The Form, Symfony forms documentation
- ↑ Handling Form Submissions, Symfony forms documentation
- ↑ Submitting Forms With Multiple Buttons, Symfony forms documentation
- ↑ Form Validation, Symfony forms documentation
- ↑ Using a Form Without a Class, Symfony forms documentation