Master Symfony2 fundamentals

Be trained by SensioLabs experts (2 to 6 day sessions -- French or English).
trainings.sensiolabs.com

Discover the SensioLabs Support

Access to the SensioLabs Competency Center for an exclusive and tailor-made support on Symfony
sensiolabs.com

Documentation Build Errors

Errors for the 2.4 branch in English


            

Errors for the 2.1 branch in English


            

Errors for the 2.5 branch in English

en/2.5/best_practices/business-logic.rst:92: ERROR: Unknown directive type "best-practice".
.. best-practice::
    The name of your application's services should be as short as possible,
    ideally just one simple word.
en/2.5/best_practices/business-logic.rst:119: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Use the YAML format to define your own services.
en/2.5/best_practices/business-logic.rst:151: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Don't define parameters for the classes of your services.
en/2.5/best_practices/business-logic.rst:200: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Use annotations to define the mapping information of the Doctrine entities.
en/2.5/best_practices/configuration.rst:12: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Define the infrastructure-related configuration options in the
    ``app/config/parameters.yml`` file.
en/2.5/best_practices/configuration.rst:46: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Define all your application's parameters in the
    ``app/config/parameters.yml.dist`` file.
en/2.5/best_practices/configuration.rst:65: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Define the application behavior related configuration options in the
    ``app/config/config.yml`` file.
en/2.5/best_practices/configuration.rst:88: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Use constants to define configuration options that rarely change.
en/2.5/best_practices/configuration.rst:157: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Don't define a semantic dependency injection configuration for your bundles.
en/2.5/best_practices/controllers.rst:14: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Make your controller extend the ``FrameworkBundle`` base Controller and
    use annotations to configure routing, caching and security whenever possible.
en/2.5/best_practices/controllers.rst:74: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Don't use the ``@Template()`` annotation to configure the template used by
    the controller.
en/2.5/best_practices/controllers.rst:130: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Use the ParamConverter trick to automatically query for Doctrine entities
    when it's simple and convenient.
en/2.5/best_practices/creating-the-project.rst:9: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Always use `Composer`_ to install Symfony.
en/2.5/best_practices/creating-the-project.rst:176: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Create only one bundle called ``AppBundle`` for your application logic
en/2.5/best_practices/forms.rst:11: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Define your forms as PHP classes.
en/2.5/best_practices/forms.rst:86: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Add buttons in the templates, not in the form classes or the controllers.
en/2.5/best_practices/forms.rst:169: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Don't use the ``form()`` or ``form_start()`` functions to render the
    starting and ending form tags.
en/2.5/best_practices/i18n.rst:27: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Use the XLIFF format for your translation files.
en/2.5/best_practices/i18n.rst:48: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Store the translation files in the ``app/Resources/translations/`` directory.
en/2.5/best_practices/i18n.rst:63: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Always use keys for translations instead of content strings.
en/2.5/best_practices/security.rst:14: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Unless you have two legitimately different authentication systems and
    users (e.g. form login for the main site and a token system for your
    API only), we recommend having only *one* firewall entry with the ``anonymous``
    key enabled.
en/2.5/best_practices/security.rst:30: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Use the ``bcrypt`` encoder for encoding your users' passwords.
en/2.5/best_practices/security.rst:79: ERROR: Unknown directive type "best-practice".
.. best-practice::
    * For protecting broad URL patterns, use ``access_control``;
    * Whenever possible, use the ``@Security`` annotation;
    * Check security directly on the ``security.context`` service whenever
      you have a more complex situation.
en/2.5/best_practices/security.rst:89: ERROR: Unknown directive type "best-practice".
.. best-practice::
    * For fine-grained restrictions, define a custom security voter;
    * For restricting access to *any* object by *any* user via an admin
      interface, use the Symfony ACL.
en/2.5/best_practices/templates.rst:8: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Use Twig templating format for your templates.
en/2.5/best_practices/templates.rst:28: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Store all your application's templates in ``app/Resources/views/`` directory.
en/2.5/best_practices/templates.rst:57: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Define your Twig extensions in the ``AppBundle/Twig/`` directory and
    configure them using the ``app/config/services.yml`` file.
en/2.5/best_practices/tests.rst:24: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Define a functional test that at least checks if your application pages
    are successfully loading.
en/2.5/best_practices/tests.rst:69: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Hardcode the URLs used in the functional tests instead of using the URL
    generator.
en/2.5/best_practices/web-assets.rst:8: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Store your assets in the ``web/`` directory.
en/2.5/best_practices/web-assets.rst:47: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Use Assetic to compile, combine and minimize web assets, unless you're
    comfortable with frontend tools like GruntJS.

Errors for the 2.2 branch in English


            

Errors for the master branch in English

en/master/best_practices/business-logic.rst:92: ERROR: Unknown directive type "best-practice".
.. best-practice::
    The name of your application's services should be as short as possible,
    ideally just one simple word.
en/master/best_practices/business-logic.rst:119: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Use the YAML format to define your own services.
en/master/best_practices/business-logic.rst:151: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Don't define parameters for the classes of your services.
en/master/best_practices/business-logic.rst:200: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Use annotations to define the mapping information of the Doctrine entities.
en/master/best_practices/configuration.rst:12: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Define the infrastructure-related configuration options in the
    ``app/config/parameters.yml`` file.
en/master/best_practices/configuration.rst:46: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Define all your application's parameters in the
    ``app/config/parameters.yml.dist`` file.
en/master/best_practices/configuration.rst:65: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Define the application behavior related configuration options in the
    ``app/config/config.yml`` file.
en/master/best_practices/configuration.rst:88: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Use constants to define configuration options that rarely change.
en/master/best_practices/configuration.rst:157: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Don't define a semantic dependency injection configuration for your bundles.
en/master/best_practices/controllers.rst:14: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Make your controller extend the ``FrameworkBundle`` base Controller and
    use annotations to configure routing, caching and security whenever possible.
en/master/best_practices/controllers.rst:74: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Don't use the ``@Template()`` annotation to configure the template used by
    the controller.
en/master/best_practices/controllers.rst:130: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Use the ParamConverter trick to automatically query for Doctrine entities
    when it's simple and convenient.
en/master/best_practices/creating-the-project.rst:9: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Always use `Composer`_ to install Symfony.
en/master/best_practices/creating-the-project.rst:176: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Create only one bundle called ``AppBundle`` for your application logic
en/master/best_practices/forms.rst:11: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Define your forms as PHP classes.
en/master/best_practices/forms.rst:86: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Add buttons in the templates, not in the form classes or the controllers.
en/master/best_practices/forms.rst:169: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Don't use the ``form()`` or ``form_start()`` functions to render the
    starting and ending form tags.
en/master/best_practices/i18n.rst:27: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Use the XLIFF format for your translation files.
en/master/best_practices/i18n.rst:48: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Store the translation files in the ``app/Resources/translations/`` directory.
en/master/best_practices/i18n.rst:63: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Always use keys for translations instead of content strings.
en/master/best_practices/security.rst:14: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Unless you have two legitimately different authentication systems and
    users (e.g. form login for the main site and a token system for your
    API only), we recommend having only *one* firewall entry with the ``anonymous``
    key enabled.
en/master/best_practices/security.rst:30: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Use the ``bcrypt`` encoder for encoding your users' passwords.
en/master/best_practices/security.rst:79: ERROR: Unknown directive type "best-practice".
.. best-practice::
    * For protecting broad URL patterns, use ``access_control``;
    * Whenever possible, use the ``@Security`` annotation;
    * Check security directly on the ``security.context`` service whenever
      you have a more complex situation.
en/master/best_practices/security.rst:89: ERROR: Unknown directive type "best-practice".
.. best-practice::
    * For fine-grained restrictions, define a custom security voter;
    * For restricting access to *any* object by *any* user via an admin
      interface, use the Symfony ACL.
en/master/best_practices/templates.rst:8: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Use Twig templating format for your templates.
en/master/best_practices/templates.rst:28: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Store all your application's templates in ``app/Resources/views/`` directory.
en/master/best_practices/templates.rst:57: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Define your Twig extensions in the ``AppBundle/Twig/`` directory and
    configure them using the ``app/config/services.yml`` file.
en/master/best_practices/tests.rst:24: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Define a functional test that at least checks if your application pages
    are successfully loading.
en/master/best_practices/tests.rst:69: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Hardcode the URLs used in the functional tests instead of using the URL
    generator.
en/master/best_practices/web-assets.rst:8: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Store your assets in the ``web/`` directory.
en/master/best_practices/web-assets.rst:47: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Use Assetic to compile, combine and minimize web assets, unless you're
    comfortable with frontend tools like GruntJS.

Errors for the 2.0 branch in English

en/2.0/cookbook/bundles/override.rst:130: WARNING: undefined label: translation-domains (if the link has no caption the label must precede a section header)

Errors for the 2.3 branch in English

en/2.3/best_practices/business-logic.rst:92: ERROR: Unknown directive type "best-practice".
.. best-practice::
    The name of your application's services should be as short as possible,
    ideally just one simple word.
en/2.3/best_practices/business-logic.rst:119: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Use the YAML format to define your own services.
en/2.3/best_practices/business-logic.rst:151: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Don't define parameters for the classes of your services.
en/2.3/best_practices/business-logic.rst:200: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Use annotations to define the mapping information of the Doctrine entities.
en/2.3/best_practices/configuration.rst:12: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Define the infrastructure-related configuration options in the
    ``app/config/parameters.yml`` file.
en/2.3/best_practices/configuration.rst:46: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Define all your application's parameters in the
    ``app/config/parameters.yml.dist`` file.
en/2.3/best_practices/configuration.rst:65: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Define the application behavior related configuration options in the
    ``app/config/config.yml`` file.
en/2.3/best_practices/configuration.rst:88: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Use constants to define configuration options that rarely change.
en/2.3/best_practices/configuration.rst:157: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Don't define a semantic dependency injection configuration for your bundles.
en/2.3/best_practices/controllers.rst:14: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Make your controller extend the ``FrameworkBundle`` base Controller and
    use annotations to configure routing, caching and security whenever possible.
en/2.3/best_practices/controllers.rst:74: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Don't use the ``@Template()`` annotation to configure the template used by
    the controller.
en/2.3/best_practices/controllers.rst:130: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Use the ParamConverter trick to automatically query for Doctrine entities
    when it's simple and convenient.
en/2.3/best_practices/creating-the-project.rst:9: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Always use `Composer`_ to install Symfony.
en/2.3/best_practices/creating-the-project.rst:176: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Create only one bundle called ``AppBundle`` for your application logic
en/2.3/best_practices/forms.rst:11: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Define your forms as PHP classes.
en/2.3/best_practices/forms.rst:86: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Add buttons in the templates, not in the form classes or the controllers.
en/2.3/best_practices/forms.rst:169: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Don't use the ``form()`` or ``form_start()`` functions to render the
    starting and ending form tags.
en/2.3/best_practices/i18n.rst:27: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Use the XLIFF format for your translation files.
en/2.3/best_practices/i18n.rst:48: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Store the translation files in the ``app/Resources/translations/`` directory.
en/2.3/best_practices/i18n.rst:63: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Always use keys for translations instead of content strings.
en/2.3/best_practices/security.rst:14: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Unless you have two legitimately different authentication systems and
    users (e.g. form login for the main site and a token system for your
    API only), we recommend having only *one* firewall entry with the ``anonymous``
    key enabled.
en/2.3/best_practices/security.rst:30: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Use the ``bcrypt`` encoder for encoding your users' passwords.
en/2.3/best_practices/security.rst:79: ERROR: Unknown directive type "best-practice".
.. best-practice::
    * For protecting broad URL patterns, use ``access_control``;
    * Whenever possible, use the ``@Security`` annotation;
    * Check security directly on the ``security.context`` service whenever
      you have a more complex situation.
en/2.3/best_practices/security.rst:89: ERROR: Unknown directive type "best-practice".
.. best-practice::
    * For fine-grained restrictions, define a custom security voter;
    * For restricting access to *any* object by *any* user via an admin
      interface, use the Symfony ACL.
en/2.3/best_practices/templates.rst:8: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Use Twig templating format for your templates.
en/2.3/best_practices/templates.rst:28: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Store all your application's templates in ``app/Resources/views/`` directory.
en/2.3/best_practices/templates.rst:57: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Define your Twig extensions in the ``AppBundle/Twig/`` directory and
    configure them using the ``app/config/services.yml`` file.
en/2.3/best_practices/tests.rst:24: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Define a functional test that at least checks if your application pages
    are successfully loading.
en/2.3/best_practices/tests.rst:69: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Hardcode the URLs used in the functional tests instead of using the URL
    generator.
en/2.3/best_practices/web-assets.rst:8: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Store your assets in the ``web/`` directory.
en/2.3/best_practices/web-assets.rst:47: ERROR: Unknown directive type "best-practice".
.. best-practice::
    Use Assetic to compile, combine and minimize web assets, unless you're
    comfortable with frontend tools like GruntJS.

Errors for the 2.5 branch in Italian

it/2.5/bundles/SensioFrameworkExtraBundle/annotations/cache.rst:57: WARNING: undefined label: release-cycle-note (if the link has no caption the label must precede a section header)
it/2.5/bundles/SensioFrameworkExtraBundle/annotations/security.rst:6: WARNING: undefined label: release-cycle-note (if the link has no caption the label must precede a section header)

Errors for the 2.4 branch in Italian

it/2.4/bundles/SensioFrameworkExtraBundle/annotations/cache.rst:57: WARNING: undefined label: release-cycle-note (if the link has no caption the label must precede a section header)
it/2.4/bundles/SensioFrameworkExtraBundle/annotations/security.rst:6: WARNING: undefined label: release-cycle-note (if the link has no caption the label must precede a section header)

Errors for the 2.1 branch in Italian


            

Errors for the master branch in Italian

it/master/bundles/SensioFrameworkExtraBundle/annotations/cache.rst:57: WARNING: undefined label: release-cycle-note (if the link has no caption the label must precede a section header)
it/master/bundles/SensioFrameworkExtraBundle/annotations/security.rst:6: WARNING: undefined label: release-cycle-note (if the link has no caption the label must precede a section header)

Errors for the 2.0 branch in Italian

it/2.0/components/serializer.rst:15: WARNING: image file not readable: images/components/serializer/serializer_workflow.png
it/2.0/contributing/community/releases.rst:None: WARNING: image file not readable: images/release-process.jpg
it/2.0/components/dependency_injection/workflow.rst:: WARNING: document isn't included in any toctree
it/2.0/contributing/community/releases.rst:: WARNING: document isn't included in any toctree
it/2.0/cookbook/configuration/override_dir_structure.rst:: WARNING: document isn't included in any toctree
it/2.0/cookbook/console/sending_emails.rst:: WARNING: document isn't included in any toctree
it/2.0/cookbook/console/usage.rst:: WARNING: document isn't included in any toctree
it/2.0/book/http_fundamentals.rst:490: WARNING: unknown document: /components/routing
it/2.0/components/dependency_injection/workflow.rst:32: WARNING: undefined label: components-dependency-injection-dumping (if the link has no caption the label must precede a section header)
it/2.0/components/dependency_injection/workflow.rst:42: WARNING: undefined label: components-dependency-injection-loading-config (if the link has no caption the label must precede a section header)
it/2.0/components/dependency_injection/workflow.rst:42: WARNING: undefined label: components-dependency-injection-extension (if the link has no caption the label must precede a section header)
it/2.0/components/dependency_injection/workflow.rst:64: WARNING: undefined label: components-dependency-injection-compiler-passes (if the link has no caption the label must precede a section header)
it/2.0/cookbook/console/console_command.rst:7: WARNING: unknown document: /components/console
it/2.0/cookbook/map.rst.inc:78: WARNING: unknown document: /cookbook/form/create_form_type_extension
it/2.0/cookbook/map.rst.inc:138: WARNING: unknown document: /cookbook/testing/bootstrap
it/2.0/reference/twig_reference.rst:53: WARNING: undefined label: book-security-template (if the link has no caption the label must precede a section header)
it/2.0/reference/twig_reference.rst:68: WARNING: undefined label: book-translation-twig (if the link has no caption the label must precede a section header)
it/2.0/reference/twig_reference.rst:71: WARNING: undefined label: book-translation-twig (if the link has no caption the label must precede a section header)
it/2.0/reference/twig_reference.rst:111: WARNING: undefined label: book-translation-twig (if the link has no caption the label must precede a section header)
it/2.0/reference/twig_reference.rst:114: WARNING: undefined label: book-translation-twig (if the link has no caption the label must precede a section header)

Errors for the 2.3 branch in Italian

it/2.3/contributing/documentation/format.rst:105: ERROR: Malformed table.
Text in column margin in table line 12.
=================   ==========================
Formato markup      Mostrato
=================   ==========================
``html``            HTML
``xml``             XML
``php``             PHP
``yaml``            YAML
``jinja             Twig puro
``html+jinja        Twig mescolato con HTML
``html+php          PHP mescolato con HTML
``ini               INI
``php-annotations`` Annotazioni PHP
=================   ==========================
it/2.3/cookbook/bundles/override.rst:108: ERROR: Unknown target name: "servizi & configurazione".
it/2.3/bundles/SensioFrameworkExtraBundle/annotations/cache.rst:57: WARNING: undefined label: release-cycle-note (if the link has no caption the label must precede a section header)

Errors for the 2.2 branch in Italian

it/2.2/bundles/SensioFrameworkExtraBundle/annotations/cache.rst:57: WARNING: undefined label: release-cycle-note (if the link has no caption the label must precede a section header)
it/2.2/bundles/SensioFrameworkExtraBundle/annotations/security.rst:6: WARNING: undefined label: release-cycle-note (if the link has no caption the label must precede a section header)

Errors for the 2.4 branch in French


            

Errors for the master branch in French


            

Errors for the 2.3 branch in French


            

Errors for the 2.2 branch in French


            

Errors for the 2.1 branch in French

fr/2.1/reference/forms/twig_reference.rst:158: WARNING: Inline literal start-string without end-string.
fr/2.1/reference/forms/types/entity.rst:148: SEVERE: Problems with "include" directive path:
InputError: [Errno 2] No such file or directory: 'fr/2.1/reference/forms/types/options/error_mapping.rst.inc'.
fr/2.1/reference/forms/types/entity.rst:150: SEVERE: Problems with "include" directive path:
InputError: [Errno 2] No such file or directory: 'fr/2.1/reference/forms/types/options/mapped.rst.inc'.
fr/2.1/reference/twig_reference.rst:: WARNING: document isn't included in any toctree
fr/2.1/reference/twig_reference.rst:29: WARNING: undefined label: book-templating-assets (if the link has no caption the label must precede a section header)
fr/2.1/reference/twig_reference.rst:32: WARNING: undefined label: book-templating-assets (if the link has no caption the label must precede a section header)
fr/2.1/reference/twig_reference.rst:35: WARNING: undefined label: reference-forms-twig-enctype (if the link has no caption the label must precede a section header)
fr/2.1/reference/twig_reference.rst:39: WARNING: undefined label: reference-forms-twig-widget (if the link has no caption the label must precede a section header)
fr/2.1/reference/twig_reference.rst:42: WARNING: undefined label: reference-forms-twig-errors (if the link has no caption the label must precede a section header)
fr/2.1/reference/twig_reference.rst:45: WARNING: undefined label: reference-forms-twig-label (if the link has no caption the label must precede a section header)
fr/2.1/reference/twig_reference.rst:48: WARNING: undefined label: reference-forms-twig-row (if the link has no caption the label must precede a section header)
fr/2.1/reference/twig_reference.rst:51: WARNING: undefined label: reference-forms-twig-rest (if the link has no caption the label must precede a section header)
fr/2.1/reference/twig_reference.rst:57: WARNING: undefined label: book-security-template (if the link has no caption the label must precede a section header)
fr/2.1/reference/twig_reference.rst:64: WARNING: undefined label: book-templating-pages (if the link has no caption the label must precede a section header)
fr/2.1/reference/twig_reference.rst:82: WARNING: undefined label: book-translation-twig (if the link has no caption the label must precede a section header)
fr/2.1/reference/twig_reference.rst:85: WARNING: undefined label: book-translation-twig (if the link has no caption the label must precede a section header)
fr/2.1/reference/twig_reference.rst:126: WARNING: undefined label: book-translation-twig (if the link has no caption the label must precede a section header)
fr/2.1/reference/twig_reference.rst:129: WARNING: undefined label: book-translation-twig (if the link has no caption the label must precede a section header)

Errors for the 2.5 branch in French