WARNING: You are browsing the documentation for Symfony 4.0 which is not maintained anymore. Consider upgrading your projects to Symfony 5.1.

How to Change the Action and Method of a Form

4.0 version

Maintained

3.4

Unmaintained

2.7 2.8 3.0 3.1 3.2 3.3 4.1 4.2

How to Change the Action and Method of a Form¶

By default, a form will be submitted via an HTTP POST request to the same URL under which the form was rendered. Sometimes you want to change these parameters. You can do so in a few different ways.

If you use the Symfony\Component\Form\FormBuilder to build your form, you can use setAction() and setMethod():

Framework Use

// src/Controller/DefaultController.php
namespace App\Controller;

use Symfony\Bundle\FrameworkBundle\Controller\Controller;
use Symfony\Component\Form\Extension\Core\Type\DateType;
use Symfony\Component\Form\Extension\Core\Type\SubmitType;
use Symfony\Component\Form\Extension\Core\Type\TextType;

class DefaultController extends Controller
{
    public function new()
    {
        $form = $this->createFormBuilder($task)
            ->setAction($this->generateUrl('target_route'))
            ->setMethod('GET')
            ->add('task', TextType::class)
            ->add('dueDate', DateType::class)
            ->add('save', SubmitType::class)
            ->getForm();

        // ...
    }
}

Standalone Use

use Symfony\Component\Form\Forms;
use Symfony\Component\Form\Extension\Core\Type\DateType;
use Symfony\Component\Form\Extension\Core\Type\FormType;
use Symfony\Component\Form\Extension\Core\Type\SubmitType;
use Symfony\Component\Form\Extension\Core\Type\TextType;

// ...

$formFactoryBuilder = Forms::createFormFactoryBuilder();

// Form factory builder configuration ...

$formFactory = $formFactoryBuilder->getFormFactory();

$form = $formFactory->createBuilder(FormType::class, $task)
    ->setAction('...')
    ->setMethod('GET')
    ->add('task', TextType::class)
    ->add('dueDate', DateType::class)
    ->add('save', SubmitType::class)
    ->getForm();

Note

This example assumes that you’ve created a route called target_route that points to the controller that processes the form.

When using a form type class, you can pass the action and method as form options:

Framework Use

// src/Controller/DefaultController.php
namespace App\Controller;

use App\Form\TaskType;
use Symfony\Bundle\FrameworkBundle\Controller\Controller;

class DefaultController extends Controller
{
    public function new()
    {
        // ...

        $form = $this->createForm(TaskType::class, $task, array(
            'action' => $this->generateUrl('target_route'),
            'method' => 'GET',
        ));

        // ...
    }
}

Standalone Use

use App\Form\TaskType;
use Symfony\Component\Form\Forms;

$formFactoryBuilder = Forms::createFormFactoryBuilder();

// Form factory builder configuration ...

$formFactory = $formFactoryBuilder->getFormFactory();

$form = $formFactory->create(TaskType::class, $task, array(
    'action' => '...',
    'method' => 'GET',
));

Finally, you can override the action and method in the template by passing them to the form() or the form_start() helper functions:

{# templates/default/new.html.twig #}
{{ form_start(form, {'action': path('target_route'), 'method': 'GET'}) }}

Note

If the form’s method is not GET or POST, but PUT, PATCH or DELETE, Symfony will insert a hidden field with the name _method that stores this method. The form will be submitted in a normal POST request, but Symfony’s router is capable of detecting the _method parameter and will interpret it as a PUT, PATCH or DELETE request. See the http_method_override option.

This work, including the code samples, is licensed under a Creative Commons BY-SA 3.0 license.