How to Use and Register Namespaced Twig Paths
Edit this pageWarning: You are browsing the documentation for Symfony 2.3, which is no longer maintained.
Read the updated version of this page for Symfony 6.3 (the current stable version).
How to Use and Register Namespaced Twig Paths
2.2
Namespaced path support was introduced in 2.2.
Usually, when you refer to a template, you'll use the MyBundle:Subdir:filename.html.twig
format (see Creating and Using Templates).
Twig also natively offers a feature called "namespaced paths", and support is built-in automatically for all of your bundles.
Take the following paths as an example:
1 2
{% extends "AppBundle::layout.html.twig" %}
{{ include('AppBundle:Foo:bar.html.twig') }}With namespaced paths, the following works as well:
1 2
{% extends "@App/layout.html.twig" %}
{{ include('@App/Foo/bar.html.twig') }}Both paths are valid and functional by default in Symfony.
Tip
As an added bonus, the namespaced syntax is faster.
Registering your own Namespaces
You can also register your own custom namespaces. Suppose that you're using
some third-party library that includes Twig templates that live in
vendor/acme/foo-bar/templates. First, register a namespace for this
directory:
1 2 3 4 5
# app/config/config.yml
twig:
# ...
paths:
"%kernel.root_dir%/../vendor/acme/foo-bar/templates": foo_barCaution
Prior to 2.8, templates in custom namespaces are not pre-compiled by Symfony's cache warmup process. They are compiled on demand. This may cause problems if two simultaneous requests are trying to use the template for the first time.
The registered namespace is called foo_bar, which refers to the
vendor/acme/foo-bar/templates directory. Assuming there's a file
called sidebar.twig in that directory, you can use it easily:
1
{{ include('@foo_bar/sidebar.twig') }}Multiple Paths per Namespace
You can also assign several paths to the same template namespace. The order in which paths are configured is very important, because Twig will always load the first template that exists, starting from the first configured path. This feature can be used as a fallback mechanism to load generic templates when the specific template doesn't exist.
1 2 3 4 5 6 7
# app/config/config.yml
twig:
# ...
paths:
"%kernel.root_dir%/../vendor/acme/themes/theme1": theme
"%kernel.root_dir%/../vendor/acme/themes/theme2": theme
"%kernel.root_dir%/../vendor/acme/themes/common": themeNow, you can use the same @theme namespace to refer to any template located
in the previous three directories:
1
{{ include('@theme/header.twig') }}
