How to Render a Template without a custom Controller
Warning: You are browsing the documentation for Symfony 2.x, which is no longer maintained.
Read the updated version of this page for Symfony 7.1 (the current stable version).
Usually, when you need to create a page, you need to create a controller
and render a template from within that controller. But if you're rendering
a simple template that doesn't need any data passed into it, you can avoid
creating the controller entirely, by using the built-in FrameworkBundle:Template:template
controller.
For example, suppose you want to render a static/privacy.html.twig
template, which doesn't require that any variables are passed to it. You
can do this without creating a controller:
1 2 3 4 5
acme_privacy:
path: /privacy
defaults:
_controller: FrameworkBundle:Template:template
template: static/privacy.html.twig
The FrameworkBundle:Template:template
controller will simply render whatever
template you've passed as the template
default value.
You can of course also use this trick when rendering embedded controllers from within a template. But since the purpose of rendering a controller from within a template is typically to prepare some data in a custom controller, this is probably only useful if you'd like to cache this page partial (see How to Render a Template without a custom Controller).
1
{{ render(url('acme_privacy')) }}
Caching the static Template
Since templates that are rendered in this way are typically static, it might make sense to cache them. Fortunately, this is easy! By configuring a few other variables in your route, you can control exactly how your page is cached:
1 2 3 4 5 6 7
acme_privacy:
path: /privacy
defaults:
_controller: FrameworkBundle:Template:template
template: 'static/privacy.html.twig'
maxAge: 86400
sharedAge: 86400
The maxAge
and sharedAge
values are used to modify the Response
object created in the controller. For more information on caching, see
HTTP Cache.
There is also a private
variable (not shown here). By default, the Response
will be made public, as long as maxAge
or sharedAge
are passed.
If set to true
, the Response will be marked as private.