Symfony3中如何更改Twig文件渲染控制器的模板？

Absolutely! I’ve tackled this exact scenario before—while the default FOSUserBundle:Security:login controller doesn’t natively accept a custom template parameter, you can make it work with a quick controller override, or use a template-focused workaround if you prefer. Here’s how:

Option 1: Override the Security Controller (Most Flexible) #

This lets you pass a template parameter directly when rendering the controller, which is perfect if you need dynamic template switching across different parts of your app.

1. Create a custom SecurityController that extends the FOSUserBundle version:

// src/App/Controller/SecurityController.php (Symfony 4+)
// or src/AppBundle/Controller/SecurityController.php (Symfony 3-)
namespace App\Controller;

use FOS\UserBundle\Controller\SecurityController as BaseSecurityController;
use Symfony\Component\HttpFoundation\Request;

class SecurityController extends BaseSecurityController
{
    public function loginAction(Request $request)
    {
        // Grab the template parameter from the request, fall back to the default if not provided
        $template = $request->get('template', 'FOSUserBundle:Security:login.html.twig');
        
        // Keep all the original login logic from the parent controller (error handling, username retention)
        $authenticationUtils = $this->get('security.authentication_utils');
        $error = $authenticationUtils->getLastAuthenticationError();
        $lastUsername = $authenticationUtils->getLastUsername();
        $baseTemplate = $request->get('baseTemplate', false);

        // Render using the custom template (or default if none is passed)
        return $this->render($template, [
            'last_username' => $lastUsername,
            'error' => $error,
            'baseTemplate' => $baseTemplate,
        ]);
    }
}

2. Update your Twig render call to include the template parameter:

{{ render(controller('App\\Controller\\SecurityController::loginAction', {
    "baseTemplate": true,
    "template": "security/custom_login.html.twig"
})) }}

(Adjust the controller path and template path to match your Symfony version and project structure)

Option 2: Template Inheritance (No Controller Changes) #

If you don’t need dynamic template switching and just want a global override of the login template, you can leverage FOSUserBundle’s built-in template inheritance:

1. Create a custom login template in your project:

{# templates/bundles/FOSUserBundle/Security/login.html.twig #}
{% extends '@FOSUser/Security/login.html.twig' %}

{# Override specific blocks to customize the form, styling, or layout #}
{% block form %}
    <div class="custom-login-form">
        {# Your custom login form markup here #}
        {{ parent() }} {# Keep the original form fields if needed, or remove this line to replace entirely #}
    </div>
{% endblock %}

Symfony will automatically pick up this template instead of the default FOSUserBundle one across your entire app.

Quick Side Note #

If you only need to render the login form in a single spot without reusing the controller’s authentication logic, you could build the form manually in your Twig template. But using the controller render method is better for reusing the error handling and username retention logic that FOSUserBundle provides out of the box.

内容的提问来源于stack exchange，提问作者vuquanghoang