`` element.
@@ -693,7 +693,7 @@ customize the ``name`` field only:
- echo $view['form']->block('form_widget_simple') ?>
+ block('form_widget_simple') ?>
Here, the ``_product_name_widget`` fragment defines the template to use for the
diff --git a/cookbook/form/unit_testing.rst b/cookbook/form/unit_testing.rst
index c45a0e40e3a..8f0c6bff22b 100644
--- a/cookbook/form/unit_testing.rst
+++ b/cookbook/form/unit_testing.rst
@@ -168,10 +168,10 @@ It often happens that you use some options that are added by
:doc:`form extensions `. One of the
cases may be the ``ValidatorExtension`` with its ``invalid_message`` option.
The ``TypeTestCase`` only loads the core form extension, which means an
-"Invalid option" exception will be raised if you try to test a class that
-depends on other extensions. The
-:method:`Symfony\\Component\\Form\\Test\\TypeTestCase::getExtensions` allows you to
-return a list of extensions to register::
++:class:`Symfony\\Component\\OptionsResolver\\Exception\\InvalidOptionsException`
++will be raised if you try to test a class that depends on other extensions.
++The :method:`Symfony\\Component\\Form\\Test\\TypeTestCase::getExtensions` method
++allows you to return a list of extensions to register::
// tests/AppBundle/Form/Type/TestedTypeTests.php
namespace Tests\AppBundle\Form\Type;
diff --git a/cookbook/frontend/bower.rst b/cookbook/frontend/bower.rst
index 39ba43f9802..1051dd7db64 100644
--- a/cookbook/frontend/bower.rst
+++ b/cookbook/frontend/bower.rst
@@ -135,6 +135,12 @@ For more details, read the article `Checking in front-end dependencies`_.
But, it's very possible that Bower will add a lock feature in the future
(e.g. `bower/bower#1748`_).
+If you don't care too much about having *exact* the same versions, you can only
+commit the ``bower.json`` file. Running ``bower install`` will give you the
+latest versions within the specified version range of each package in
+``bower.json``. Using strict version constraints (e.g. ``1.10.*``) is often
+enough to ensure only bringing in compatible versions.
+
.. _Bower: http://bower.io
.. _`Node.js`: https://nodejs.org
.. _BowerPHP: http://bowerphp.org/
diff --git a/cookbook/map.rst.inc b/cookbook/map.rst.inc
index b175020f713..1c36955c9d5 100644
--- a/cookbook/map.rst.inc
+++ b/cookbook/map.rst.inc
@@ -45,6 +45,7 @@
* :doc:`/cookbook/console/console_command`
* :doc:`/cookbook/console/usage`
+ * :doc:`/cookbook/console/style`
* :doc:`/cookbook/console/command_in_controller`
* :doc:`/cookbook/console/sending_emails`
* :doc:`/cookbook/console/logging`
diff --git a/cookbook/profiler/matchers.rst b/cookbook/profiler/matchers.rst
index 0cfd3f953c0..600883cc41d 100644
--- a/cookbook/profiler/matchers.rst
+++ b/cookbook/profiler/matchers.rst
@@ -102,11 +102,6 @@ matcher::
}
}
-.. versionadded:: 2.6
- The :class:`Symfony\\Component\\Security\\Core\\Authorization\\AuthorizationCheckerInterface` was
- introduced in Symfony 2.6. Prior, you had to use the ``isGranted`` method of
- :class:`Symfony\\Component\\Security\\Core\\SecurityContextInterface`.
-
Then, configure a new service and set it as ``private`` because the application
won't use it directly:
@@ -144,10 +139,6 @@ won't use it directly:
$container->setDefinition('app.super_admin_matcher', $definition);
-.. versionadded:: 2.6
- The ``security.authorization_checker`` service was introduced in Symfony 2.6. Prior
- to Symfony 2.6, you had to use the ``isGranted()`` method of the ``security.context`` service.
-
Once the service is registered, the only thing left to do is configure the
profiler to use this service as the matcher:
diff --git a/cookbook/security/custom_password_authenticator.rst b/cookbook/security/custom_password_authenticator.rst
index d6efd122981..9a536c80ebd 100644
--- a/cookbook/security/custom_password_authenticator.rst
+++ b/cookbook/security/custom_password_authenticator.rst
@@ -10,17 +10,12 @@ How to Create a Custom Form Password Authenticator
flexible way to accomplish custom authentication tasks like this.
Imagine you want to allow access to your website only between 2pm and 4pm
-UTC. Before Symfony 2.4, you had to create a custom token, factory, listener
-and provider. In this entry, you'll learn how to do this for a login form
-(i.e. where your user submits their username and password).
-Before Symfony 2.6, you had to use the password encoder to authenticate the user password.
+UTC. In this entry, you'll learn how to do this for a login form (i.e. where
+your user submits their username and password).
The Password Authenticator
--------------------------
-.. versionadded:: 2.6
- The ``UserPasswordEncoderInterface`` interface was introduced in Symfony 2.6.
-
.. versionadded:: 2.8
The ``SimpleFormAuthenticatorInterface`` interface was moved to the
``Symfony\Component\Security\Http\Authentication`` namespace in Symfony
diff --git a/cookbook/security/form_login_setup.rst b/cookbook/security/form_login_setup.rst
index 77c0aa87936..527c971b197 100644
--- a/cookbook/security/form_login_setup.rst
+++ b/cookbook/security/form_login_setup.rst
@@ -186,11 +186,6 @@ form::
);
}
-.. versionadded:: 2.6
- The ``security.authentication_utils`` service and the
- :class:`Symfony\\Component\\Security\\Http\\Authentication\\AuthenticationUtils`
- class were introduced in Symfony 2.6.
-
Don't let this controller confuse you. As you'll see in a moment, when the
user submits the form, the security system automatically handles the form
submission for you. If the user had submitted an invalid username or password,
diff --git a/cookbook/security/pre_authenticated.rst b/cookbook/security/pre_authenticated.rst
index e3501c54884..82adbd3f8fd 100644
--- a/cookbook/security/pre_authenticated.rst
+++ b/cookbook/security/pre_authenticated.rst
@@ -92,9 +92,6 @@ in the x509 firewall configuration respectively.
REMOTE_USER Based Authentication
--------------------------------
-.. versionadded:: 2.6
- REMOTE_USER pre authenticated firewall was introduced in Symfony 2.6.
-
A lot of authentication modules, like ``auth_kerb`` for Apache provide the username
using the ``REMOTE_USER`` environment variable. This variable can be trusted by
the application since the authentication happened before the request reached it.
diff --git a/cookbook/validation/severity.rst b/cookbook/validation/severity.rst
index 22cb267d6c3..34b091bd5c6 100644
--- a/cookbook/validation/severity.rst
+++ b/cookbook/validation/severity.rst
@@ -21,9 +21,6 @@ The process to achieve this behavior consists of two steps:
1. Assigning the Error Level
----------------------------
-.. versionadded:: 2.6
- The ``payload`` option was introduced in Symfony 2.6.
-
Use the ``payload`` option to configure the error level for each constraint:
.. configuration-block::
@@ -131,10 +128,6 @@ Use the ``payload`` option to configure the error level for each constraint:
2. Customize the Error Message Template
---------------------------------------
-.. versionadded:: 2.6
- The ``getConstraint()`` method in the ``ConstraintViolation`` class was
- introduced in Symfony 2.6.
-
When validation of the ``User`` object fails, you can retrieve the constraint
that caused a particular failure using the
:method:`Symfony\\Component\\Validator\\ConstraintViolation::getConstraint`
diff --git a/cookbook/web_server/built_in.rst b/cookbook/web_server/built_in.rst
index 10dceab5b4e..fe7ee95c283 100644
--- a/cookbook/web_server/built_in.rst
+++ b/cookbook/web_server/built_in.rst
@@ -4,10 +4,6 @@
How to Use PHP's built-in Web Server
====================================
-.. versionadded:: 2.6
- The ability to run the server as a background process was introduced
- in Symfony 2.6.
-
Since PHP 5.4 the CLI SAPI comes with a `built-in web server`_. It can be used
to run your PHP applications locally during development, for testing or for
application demonstrations. This way, you don't have to bother configuring
diff --git a/reference/configuration/debug.rst b/reference/configuration/debug.rst
index 78a3ba6c85f..8a405e57e50 100644
--- a/reference/configuration/debug.rst
+++ b/reference/configuration/debug.rst
@@ -10,9 +10,6 @@ Symfony full-stack framework and can be configured under the ``debug`` key
in your application configuration. When using XML, you must use the
``http://symfony.com/schema/dic/debug`` namespace.
-.. versionadded::
- The DebugBundle was introduced in Symfony 2.6.
-
.. tip::
The XSD schema is available at
diff --git a/reference/configuration/framework.rst b/reference/configuration/framework.rst
index f7f56422799..0320543864e 100644
--- a/reference/configuration/framework.rst
+++ b/reference/configuration/framework.rst
@@ -526,11 +526,6 @@ profiler
enabled
.......
-.. versionadded:: 2.2
- The ``enabled`` option was introduced in Symfony 2.2. Prior to Symfony
- 2.2, the profiler could only be disabled by omitting the ``framework.profiler``
- configuration entirely.
-
**type**: ``boolean`` **default**: ``false``
The profiler can be enabled by setting this option to ``true``. When you
@@ -1321,9 +1316,6 @@ found.
logging
.......
-.. versionadded:: 2.6
- The ``logging`` option was introduced in Symfony 2.6.
-
**default**: ``true`` when the debug mode is enabled, ``false`` otherwise.
When ``true``, a log entry is made whenever the translator cannot find a translation
@@ -1404,9 +1396,6 @@ error messages.
strict_email
............
-.. versionadded:: 2.5
- The ``strict_email`` option was introduced in Symfony 2.5.
-
**type**: ``Boolean`` **default**: ``false``
If this option is enabled, the `egulias/email-validator`_ library will be
@@ -1416,9 +1405,6 @@ the validator uses a simple regular expression to validate email addresses.
api
...
-.. versionadded:: 2.5
- The ``api`` option was introduced in Symfony 2.5.
-
**type**: ``string``
Starting with Symfony 2.5, the Validator component introduced a new validation
diff --git a/reference/configuration/security.rst b/reference/configuration/security.rst
index fe340993adf..6fb2fd93f9b 100644
--- a/reference/configuration/security.rst
+++ b/reference/configuration/security.rst
@@ -13,10 +13,6 @@ Full Default Configuration
The following is the full default configuration for the security system.
Each part will be explained in the next section.
-.. versionadded:: 2.5
- Support for restricting security firewalls to specific http methods was introduced in
- Symfony 2.5.
-
.. configuration-block::
.. code-block:: yaml
diff --git a/reference/constraints/Expression.rst b/reference/constraints/Expression.rst
index 9f5ce639966..1f0278ca9e3 100644
--- a/reference/constraints/Expression.rst
+++ b/reference/constraints/Expression.rst
@@ -216,12 +216,6 @@ more about the expression language syntax, see
// ...
}
- .. versionadded:: 2.6
- In Symfony 2.6, the Expression constraint *is* executed if the value
- is ``null``. Before 2.6, if the value was ``null``, the expression
- was never executed and the value was considered valid (unless you
- also had a constraint like ``NotBlank`` on the property).
-
For more information about the expression and what variables are available
to you, see the :ref:`expression
`
option details below.
diff --git a/reference/constraints/File.rst b/reference/constraints/File.rst
index 2ff8a081ee7..842badb272a 100644
--- a/reference/constraints/File.rst
+++ b/reference/constraints/File.rst
@@ -156,9 +156,6 @@ Options
maxSize
~~~~~~~
-.. versionadded:: 2.6
- The suffixes ``Ki`` and ``Mi`` were introduced in Symfony 2.6.
-
**type**: ``mixed``
If set, the size of the underlying file must be below this file size in
@@ -185,9 +182,6 @@ see `Wikipedia: Binary prefix`_.
binaryFormat
~~~~~~~~~~~~
-.. versionadded:: 2.6
- The ``binaryFormat`` option was introduced in Symfony 2.6.
-
**type**: ``boolean`` **default**: ``null``
When ``true``, the sizes will be displayed in messages with binary-prefixed
@@ -227,10 +221,6 @@ per the `mimeTypes`_ option.
disallowEmptyMessage
~~~~~~~~~~~~~~~~~~~~
-.. versionadded:: 2.6
- The ``disallowEmptyMessage`` option was introduced in Symfony 2.6. Prior to 2.6,
- if the user uploaded an empty file, no validation error occurred.
-
**type**: ``string`` **default**: ``An empty file is not allowed.``
This constraint checks if the uploaded file is empty (i.e. 0 bytes). If it is,
diff --git a/reference/constraints/GreaterThan.rst b/reference/constraints/GreaterThan.rst
index cc1372f3bbd..95c8726f1fc 100644
--- a/reference/constraints/GreaterThan.rst
+++ b/reference/constraints/GreaterThan.rst
@@ -93,9 +93,6 @@ If you want to ensure that the ``age`` of a ``Person`` class is greater than
Comparing Dates
---------------
-.. versionadded:: 2.6
- The feature to compare dates was introduced in Symfony 2.6.
-
This constraint can be used to compare ``DateTime`` objects against any date
string `accepted by the DateTime constructor`_. For example, you could check
that a date must at least be the next day:
diff --git a/reference/constraints/GreaterThanOrEqual.rst b/reference/constraints/GreaterThanOrEqual.rst
index 822b8bc10bc..7c0f8e7f451 100644
--- a/reference/constraints/GreaterThanOrEqual.rst
+++ b/reference/constraints/GreaterThanOrEqual.rst
@@ -92,9 +92,6 @@ or equal to ``18``, you could do the following:
Comparing Dates
---------------
-.. versionadded:: 2.6
- The feature to compare dates was introduced in Symfony 2.6.
-
This constraint can be used to compare ``DateTime`` objects against any date
string `accepted by the DateTime constructor`_. For example, you could check
that a date must at least be the current day:
diff --git a/reference/constraints/LessThan.rst b/reference/constraints/LessThan.rst
index 65f171bf834..05decac79f9 100644
--- a/reference/constraints/LessThan.rst
+++ b/reference/constraints/LessThan.rst
@@ -93,9 +93,6 @@ If you want to ensure that the ``age`` of a ``Person`` class is less than
Comparing Dates
---------------
-.. versionadded:: 2.6
- The feature to compare dates was introduced in Symfony 2.6.
-
This constraint can be used to compare ``DateTime`` objects against any date
string `accepted by the DateTime constructor`_. For example, you could check
that a date must be in the past like this:
diff --git a/reference/constraints/LessThanOrEqual.rst b/reference/constraints/LessThanOrEqual.rst
index 48d3b1cef61..20633acd4c3 100644
--- a/reference/constraints/LessThanOrEqual.rst
+++ b/reference/constraints/LessThanOrEqual.rst
@@ -92,9 +92,6 @@ equal to ``80``, you could do the following:
Comparing Dates
---------------
-.. versionadded:: 2.6
- The feature to compare dates was introduced in Symfony 2.6.
-
This constraint can be used to compare ``DateTime`` objects against any date
string `accepted by the DateTime constructor`_. For example, you could check
that a date must be today or in the past like this:
diff --git a/reference/constraints/_payload-option.rst.inc b/reference/constraints/_payload-option.rst.inc
index 30c6d46bbc8..c32ad633989 100644
--- a/reference/constraints/_payload-option.rst.inc
+++ b/reference/constraints/_payload-option.rst.inc
@@ -3,9 +3,6 @@ payload
**type**: ``mixed`` **default**: ``null``
-.. versionadded:: 2.6
- The ``payload`` option was introduced in Symfony 2.6.
-
This option can be used to attach arbitrary domain-specific data to a constraint.
The configured payload is not used by the Validator component, but its processing
is completely up to you.
diff --git a/reference/dic_tags.rst b/reference/dic_tags.rst
index 73a1bbf3eeb..7b3efece11a 100644
--- a/reference/dic_tags.rst
+++ b/reference/dic_tags.rst
@@ -877,10 +877,6 @@ For more information, see :doc:`/cookbook/routing/custom_route_loader`.
routing.expression_language_provider
------------------------------------
-.. versionadded:: 2.6
- The ``routing.expression_language_provider`` tag was introduced in Symfony
- 2.6.
-
**Purpose**: Register a provider for expression language functions in routing
This tag is used to automatically register
@@ -891,10 +887,6 @@ functions to the routing expression language.
security.expression_language_provider
-------------------------------------
-.. versionadded:: 2.6
- The ``security.expression_language_provider`` tag was introduced in Symfony
- 2.6.
-
**Purpose**: Register a provider for expression language functions in security
This tag is used to automatically register :ref:`expression function providers
diff --git a/reference/forms/types/choice.rst b/reference/forms/types/choice.rst
index be0bf17265a..1f70161f6d6 100644
--- a/reference/forms/types/choice.rst
+++ b/reference/forms/types/choice.rst
@@ -244,6 +244,8 @@ would replace the ``choices`` option.
.. include:: /reference/forms/types/options/placeholder.rst.inc
+.. include:: /reference/forms/types/options/choice_translation_domain.rst.inc
+
.. include:: /reference/forms/types/options/expanded.rst.inc
.. include:: /reference/forms/types/options/multiple.rst.inc
@@ -359,29 +361,32 @@ These options inherit from the :doc:`FormType `:
Field Variables
---------------
-+------------------------+--------------+-------------------------------------------------------------------+
-| Variable | Type | Usage |
-+========================+==============+===================================================================+
-| multiple | ``boolean`` | The value of the `multiple`_ option. |
-+------------------------+--------------+-------------------------------------------------------------------+
-| expanded | ``boolean`` | The value of the `expanded`_ option. |
-+------------------------+--------------+-------------------------------------------------------------------+
-| preferred_choices | ``array`` | A nested array containing the ``ChoiceView`` objects of |
-| | | choices which should be presented to the user with priority. |
-+------------------------+--------------+-------------------------------------------------------------------+
-| choices | ``array`` | A nested array containing the ``ChoiceView`` objects of |
-| | | the remaining choices. |
-+------------------------+--------------+-------------------------------------------------------------------+
-| separator | ``string`` | The separator to use between choice groups. |
-+------------------------+--------------+-------------------------------------------------------------------+
-| placeholder | ``mixed`` | The empty value if not already in the list, otherwise |
-| | | ``null``. |
-+------------------------+--------------+-------------------------------------------------------------------+
-| is_selected | ``callable`` | A callable which takes a ``ChoiceView`` and the selected value(s) |
-| | | and returns whether the choice is in the selected value(s). |
-+------------------------+--------------+-------------------------------------------------------------------+
-| placeholder_in_choices | ``boolean`` | Whether the empty value is in the choice list. |
-+------------------------+--------------+-------------------------------------------------------------------+
++----------------------------+--------------+-------------------------------------------------------------------+
+| Variable | Type | Usage |
++============================+==============+===================================================================+
+| multiple | ``boolean`` | The value of the `multiple`_ option. |
++----------------------------+--------------+-------------------------------------------------------------------+
+| expanded | ``boolean`` | The value of the `expanded`_ option. |
++----------------------------+--------------+-------------------------------------------------------------------+
+| preferred_choices | ``array`` | A nested array containing the ``ChoiceView`` objects of |
+| | | choices which should be presented to the user with priority. |
++----------------------------+--------------+-------------------------------------------------------------------+
+| choices | ``array`` | A nested array containing the ``ChoiceView`` objects of |
+| | | the remaining choices. |
++----------------------------+--------------+-------------------------------------------------------------------+
+| separator | ``string`` | The separator to use between choice groups. |
++----------------------------+--------------+-------------------------------------------------------------------+
+| placeholder | ``mixed`` | The empty value if not already in the list, otherwise |
+| | | ``null``. |
++----------------------------+--------------+-------------------------------------------------------------------+
+| choice_translation_domain | ``mixed`` | ``boolean``, ``null`` or ``string`` to determine if the value |
+| | | should be translated. |
++----------------------------+--------------+-------------------------------------------------------------------+
+| is_selected | ``callable`` | A callable which takes a ``ChoiceView`` and the selected value(s) |
+| | | and returns whether the choice is in the selected value(s). |
++----------------------------+--------------+-------------------------------------------------------------------+
+| placeholder_in_choices | ``boolean`` | Whether the empty value is in the choice list. |
++----------------------------+--------------+-------------------------------------------------------------------+
.. tip::
diff --git a/reference/forms/types/date.rst b/reference/forms/types/date.rst
index 2d93e10a00f..f39872c3316 100644
--- a/reference/forms/types/date.rst
+++ b/reference/forms/types/date.rst
@@ -90,10 +90,6 @@ Field Options
placeholder
~~~~~~~~~~~
-.. versionadded:: 2.6
- The ``placeholder`` option was introduced in Symfony 2.6 in favor of
- ``empty_value``, which is available prior to 2.6.
-
**type**: ``string`` or ``array``
If your widget option is set to ``choice``, then this field will be represented
diff --git a/reference/forms/types/entity.rst b/reference/forms/types/entity.rst
index 4eacb7078f8..4b0d7c93ebf 100644
--- a/reference/forms/types/entity.rst
+++ b/reference/forms/types/entity.rst
@@ -23,6 +23,7 @@ objects from the database.
| Inherited | from the :doc:`ChoiceType `: |
| options | |
| | - `placeholder`_ |
+| | - `choice_translation_domain`_ |
| | - `expanded`_ |
| | - `multiple`_ |
| | - `preferred_choices`_ |
@@ -213,6 +214,8 @@ These options inherit from the :doc:`ChoiceType `
.. include:: /reference/forms/types/options/placeholder.rst.inc
+.. include:: /reference/forms/types/options/choice_translation_domain.rst.inc
+
.. include:: /reference/forms/types/options/expanded.rst.inc
.. include:: /reference/forms/types/options/multiple.rst.inc
diff --git a/reference/forms/types/form.rst b/reference/forms/types/form.rst
index ccd229795d4..1b66ac5c626 100644
--- a/reference/forms/types/form.rst
+++ b/reference/forms/types/form.rst
@@ -56,9 +56,6 @@ Field Options
allow_extra_fields
~~~~~~~~~~~~~~~~~~
-.. versionadded:: 2.6
- The ``allow_extra_fields`` option was introduced in Symfony 2.6.
-
**type**: ``boolean`` **default**: ``false``
Usually, if you submit extra fields that aren't configured in your form,
diff --git a/reference/forms/types/options/choice_translation_domain.rst.inc b/reference/forms/types/options/choice_translation_domain.rst.inc
new file mode 100644
index 00000000000..1d42f222e2e
--- /dev/null
+++ b/reference/forms/types/options/choice_translation_domain.rst.inc
@@ -0,0 +1,15 @@
+choice_translation_domain
+~~~~~~~~~~~~~~~~~~~~~~~~~
+
+.. versionadded:: 2.7
+ The ``choice_translation_domain`` option was introduced in Symfony 2.7.
+
+**type**: ``string``, ``boolean`` or ``null``
+
+This option determines if the choice values should be translated and in which
+translation domain.
+
+The values of the ``choice_translation_domain`` option can be ``true`` (reuse the current
+translation domain), ``false`` (disable translation), ``null`` (uses the parent translation
+domain or the default domain) or a string which represents the exact translation
+domain to use.
diff --git a/reference/forms/types/options/html5.rst.inc b/reference/forms/types/options/html5.rst.inc
index 1022412f3b3..30ba9762c4e 100644
--- a/reference/forms/types/options/html5.rst.inc
+++ b/reference/forms/types/options/html5.rst.inc
@@ -1,9 +1,6 @@
html5
~~~~~
-.. versionadded:: 2.6
- The ``html5`` option was introduced in Symfony 2.6.
-
**type**: ``boolean`` **default**: ``true``
If this is set to ``true`` (the default), it'll use the HTML5 type (date, time
diff --git a/reference/forms/types/options/placeholder.rst.inc b/reference/forms/types/options/placeholder.rst.inc
index 12d20b00f3a..ad947dd0e08 100644
--- a/reference/forms/types/options/placeholder.rst.inc
+++ b/reference/forms/types/options/placeholder.rst.inc
@@ -1,10 +1,6 @@
placeholder
~~~~~~~~~~~
-.. versionadded:: 2.6
- The ``placeholder`` option was introduced in Symfony 2.6 in favor of
- ``empty_value``, which is available prior to 2.6.
-
.. versionadded:: 2.3
Since Symfony 2.3, empty values are also supported if the ``expanded``
option is set to true.
diff --git a/reference/map.rst.inc b/reference/map.rst.inc
index 1d322527c61..8339192ab96 100644
--- a/reference/map.rst.inc
+++ b/reference/map.rst.inc
@@ -13,7 +13,7 @@
* :doc:`twig `
* :doc:`monolog `
* :doc:`web_profiler `
- * :doc:`debug ` (new in 2.6)
+ * :doc:`debug `
* :doc:`Configuring the Kernel (e.g. AppKernel) `
diff --git a/reference/twig_reference.rst b/reference/twig_reference.rst
index b8c0c3db278..08a77b0ac7d 100644
--- a/reference/twig_reference.rst
+++ b/reference/twig_reference.rst
@@ -361,9 +361,6 @@ information in :ref:`book-templating-pages`.
absolute_url
~~~~~~~~~~~~
-.. versionadded:: 2.6
- The ``absolute_url`` function was introduced in Symfony 2.7
-
.. code-block:: jinja
{{ absolute_url(path) }}
@@ -381,9 +378,6 @@ an existing path:
relative_path
~~~~~~~~~~~~~
-.. versionadded:: 2.6
- The ``relative_path`` function was introduced in Symfony 2.7
-
.. code-block:: jinja
{{ relative_path(path) }}
@@ -726,11 +720,6 @@ The available attributes are:
* ``app.debug``
* ``app.security`` (deprecated as of 2.6)
-.. caution::
-
- The ``app.security`` global is deprecated as of 2.6. The user is already
- available as ``app.user`` and ``is_granted()`` is registered as function.
-
Symfony Standard Edition Extensions
-----------------------------------