diff --git a/book/controller.rst b/book/controller.rst index aa4ffb873e6..cfceabfc6fd 100644 --- a/book/controller.rst +++ b/book/controller.rst @@ -520,9 +520,6 @@ console command: $ php app/console debug:container -.. versionadded:: 2.6 - Prior to Symfony 2.6, this command was called ``container:debug``. - For more information, see the :doc:`/book/service_container` chapter. .. index:: diff --git a/book/forms.rst b/book/forms.rst index 0ed28c3e9c6..969404824b4 100644 --- a/book/forms.rst +++ b/book/forms.rst @@ -122,10 +122,6 @@ other things, determines which HTML form tag(s) is rendered for that field. Finally, you added a submit button with a custom label for submitting the form to the server. -.. versionadded:: 2.3 - Support for submit buttons was introduced in Symfony 2.3. Before that, you had - to add buttons to the form's HTML manually. - Symfony comes with many built-in types that will be discussed shortly (see :ref:`book-forms-type-reference`). @@ -240,12 +236,6 @@ controller:: // ... } -.. versionadded:: 2.3 - The :method:`Symfony\\Component\\Form\\FormInterface::handleRequest` method - was introduced in Symfony 2.3. Previously, the ``$request`` was passed - to the ``submit`` method - a strategy which is deprecated and will be - removed in Symfony 3.0. For details on that method, see :ref:`cookbook-form-submit-request`. - This controller follows a common pattern for handling forms, and has three possible paths: @@ -294,9 +284,6 @@ possible paths: Submitting Forms with Multiple Buttons ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -.. versionadded:: 2.3 - Support for buttons in forms was introduced in Symfony 2.3. - When your form contains more than one submit button, you will want to check which of the buttons was clicked to adapt the program flow in your controller. To do this, add a second button with the caption "Save and add" to your form:: @@ -492,9 +479,6 @@ be used to validate the underlying object. Disabling Validation ~~~~~~~~~~~~~~~~~~~~ -.. versionadded:: 2.3 - The ability to set ``validation_groups`` to false was introduced in Symfony 2.3. - Sometimes it is useful to suppress the validation of a form altogether. For these cases you can set the ``validation_groups`` option to ``false``:: @@ -593,9 +577,6 @@ work in the book section about :ref:`validation groups setPassword($encoded); -.. versionadded:: 2.6 - The ``security.password_encoder`` service was introduced in Symfony 2.6. - In order for this to work, just make sure that you have the encoder for your user class (e.g. ``AppBundle\Entity\User``) configured under the ``encoders`` key in ``app/config/security.yml``. diff --git a/book/service_container.rst b/book/service_container.rst index 6e97d4831c1..e0a8da9c802 100644 --- a/book/service_container.rst +++ b/book/service_container.rst @@ -1132,9 +1132,6 @@ console. To show all services and the class for each service, run: $ php app/console debug:container -.. versionadded:: 2.6 - Prior to Symfony 2.6, this command was called ``container:debug``. - By default, only public services are shown, but you can also view private services: .. code-block:: bash diff --git a/book/templating.rst b/book/templating.rst index 35d477c0ed3..072bd38196d 100644 --- a/book/templating.rst +++ b/book/templating.rst @@ -1178,12 +1178,6 @@ automatically:

Application Environment: getEnvironment() ?>

-.. versionadded:: 2.6 - The global ``app.security`` variable (or the ``$app->getSecurity()`` - method in PHP templates) is deprecated as of Symfony 2.6. Use `app.user` - (`$app->getUser()`) and `is_granted()` (`$view['security']->isGranted()`) - instead. - .. tip:: You can add your own global template variables. See the cookbook example diff --git a/book/testing.rst b/book/testing.rst index bf69da90f0a..1226557b54c 100644 --- a/book/testing.rst +++ b/book/testing.rst @@ -414,11 +414,6 @@ The Client supports many operations that can be done in a real browser:: Accessing internal Objects ~~~~~~~~~~~~~~~~~~~~~~~~~~ -.. versionadded:: 2.3 - The :method:`Symfony\\Component\\BrowserKit\\Client::getInternalRequest` - and :method:`Symfony\\Component\\BrowserKit\\Client::getInternalResponse` - methods were introduced in Symfony 2.3. - If you use the client to test your application, you might want to access the client's internal objects:: @@ -461,9 +456,6 @@ Be warned that this does not work if you insulate the client or if you use an HTTP layer. For a list of services available in your application, use the ``debug:container`` console task. -.. versionadded:: 2.6 - Prior to Symfony 2.6, this command was called ``container:debug``. - .. tip:: If the information you need to check is available from the profiler, use diff --git a/book/translation.rst b/book/translation.rst index a847344b90d..340bee8adb7 100644 --- a/book/translation.rst +++ b/book/translation.rst @@ -400,9 +400,6 @@ checks translation resources for several locales: #. If the translation still isn't found, Symfony uses the ``fallback`` configuration parameter, which defaults to ``en`` (see `Configuration`_). -.. versionadded:: 2.6 - The ability to log missing translations was introduced in Symfony 2.6. - .. note:: When Symfony doesn't find a translation in the given locale, it will @@ -673,9 +670,6 @@ Debugging Translations .. versionadded:: 2.5 The ``debug:translation`` command was introduced in Symfony 2.5. -.. versionadded:: 2.6 - Prior to Symfony 2.6, this command was called ``translation:debug``. - When maintaining a bundle, you may use or remove the usage of a translation message without updating all message catalogues. The ``debug:translation`` command helps you to find these missing or unused translation messages for a diff --git a/components/config/definition.rst b/components/config/definition.rst index f0f45f4e585..3b703559f1d 100644 --- a/components/config/definition.rst +++ b/components/config/definition.rst @@ -290,10 +290,6 @@ method. The info will be printed as a comment when dumping the configuration tree. -.. versionadded:: 2.6 - Since Symfony 2.6, the info will also be added to the exception message - when an invalid type is given. - Optional Sections ----------------- diff --git a/components/console/events.rst b/components/console/events.rst index 8dac89520a0..66c5bd17d75 100644 --- a/components/console/events.rst +++ b/components/console/events.rst @@ -4,9 +4,6 @@ Using Events ============ -.. versionadded:: 2.3 - Console events were introduced in Symfony 2.3. - The Application class of the Console component allows you to optionally hook into the lifecycle of a console application via events. Instead of reinventing the wheel, it uses the Symfony EventDispatcher component to do the work:: @@ -54,9 +51,6 @@ dispatched. Listeners receive a Disable Commands inside Listeners ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -.. versionadded:: 2.6 - Disabling commands inside listeners was introduced in Symfony 2.6. - Using the :method:`Symfony\\Component\\Console\\Event\\ConsoleCommandEvent::disableCommand` method, you can disable a command inside a listener. The application diff --git a/components/console/helpers/debug_formatter.rst b/components/console/helpers/debug_formatter.rst index 6368686b78d..405ca90f01f 100644 --- a/components/console/helpers/debug_formatter.rst +++ b/components/console/helpers/debug_formatter.rst @@ -4,9 +4,6 @@ Debug Formatter Helper ====================== -.. versionadded:: 2.6 - The Debug Formatter helper was introduced in Symfony 2.6. - The :class:`Symfony\\Component\\Console\\Helper\\DebugFormatterHelper` provides functions to output debug information when running an external program, for instance a process or HTTP request. It is included in the default helper set diff --git a/components/console/helpers/dialoghelper.rst b/components/console/helpers/dialoghelper.rst index 94ff99d942b..fd9dda73ab4 100644 --- a/components/console/helpers/dialoghelper.rst +++ b/components/console/helpers/dialoghelper.rst @@ -208,9 +208,6 @@ or the maximum attempts is reached (which you can define in the fifth argument). The default value for the attempts is ``false``, which means infinite attempts. You can define your own error message in the sixth argument. -.. versionadded:: 2.3 - Multiselect support was introduced in Symfony 2.3. - Multiple Choices ................ diff --git a/components/console/helpers/processhelper.rst b/components/console/helpers/processhelper.rst index 5494ca0137f..6a4f7c6f6b5 100644 --- a/components/console/helpers/processhelper.rst +++ b/components/console/helpers/processhelper.rst @@ -4,9 +4,6 @@ Process Helper ============== -.. versionadded:: 2.6 - The Process Helper was introduced in Symfony 2.6. - The Process Helper shows processes as they're running and reports useful information about process status. diff --git a/components/console/helpers/progressbar.rst b/components/console/helpers/progressbar.rst index 1b8edf309cc..c99c8b6d104 100644 --- a/components/console/helpers/progressbar.rst +++ b/components/console/helpers/progressbar.rst @@ -44,22 +44,11 @@ Instead of advancing the bar by a number of steps (with the you can also set the current progress by calling the :method:`Symfony\\Component\\Console\\Helper\\ProgressBar::setProgress` method. -.. versionadded:: 2.6 - The ``setProgress()`` method was called ``setCurrent()`` prior to Symfony 2.6. - .. caution:: Prior to version 2.6, the progress bar only works if your platform supports ANSI codes; on other platforms, no output is generated. -.. versionadded:: 2.6 - If your platform doesn't support ANSI codes, updates to the progress - bar are added as new lines. To prevent the output from being flooded, - adjust the - :method:`Symfony\\Component\\Console\\Helper\\ProgressBar::setRedrawFrequency` - accordingly. By default, when using a ``max``, the redraw frequency - is set to *10%* of your ``max``. - If you don't know the number of steps in advance, just omit the steps argument when creating the :class:`Symfony\\Component\\Console\\Helper\\ProgressBar` instance:: @@ -307,9 +296,6 @@ that displays the number of remaining steps:: } ); -.. versionadded:: 2.6 - The ``getProgress()`` method was called ``getStep()`` prior to Symfony 2.6. - Custom Messages ~~~~~~~~~~~~~~~ diff --git a/components/console/helpers/progresshelper.rst b/components/console/helpers/progresshelper.rst index 78e09e0eb25..a8b717d6c5c 100644 --- a/components/console/helpers/progresshelper.rst +++ b/components/console/helpers/progresshelper.rst @@ -4,9 +4,6 @@ Progress Helper =============== -.. versionadded:: 2.3 - The ``setCurrent`` method was introduced in Symfony 2.3. - .. versionadded:: 2.4 The ``clear`` method was introduced in Symfony 2.4. diff --git a/components/console/helpers/tablehelper.rst b/components/console/helpers/tablehelper.rst index d1c094938cf..63720ea50cd 100644 --- a/components/console/helpers/tablehelper.rst +++ b/components/console/helpers/tablehelper.rst @@ -4,9 +4,6 @@ Table Helper ============ -.. versionadded:: 2.3 - The ``table`` helper was introduced in Symfony 2.3. - .. caution:: The Table Helper was deprecated in Symfony 2.5 and will be removed in diff --git a/components/console/introduction.rst b/components/console/introduction.rst index 46c728b07da..294ad5095c5 100644 --- a/components/console/introduction.rst +++ b/components/console/introduction.rst @@ -170,10 +170,6 @@ You can also set these colors and options inside the tagname:: Verbosity Levels ~~~~~~~~~~~~~~~~ -.. versionadded:: 2.3 - The ``VERBOSITY_VERY_VERBOSE`` and ``VERBOSITY_DEBUG`` constants were introduced - in version 2.3 - The console has 5 levels of verbosity. These are defined in the :class:`Symfony\\Component\\Console\\Output\\OutputInterface`: diff --git a/components/debug/introduction.rst b/components/debug/introduction.rst index 8f3fc17102e..25f13006e64 100644 --- a/components/debug/introduction.rst +++ b/components/debug/introduction.rst @@ -7,10 +7,6 @@ The Debug Component The Debug component provides tools to ease debugging PHP code. -.. versionadded:: 2.3 - The Debug component was introduced in Symfony 2.3. Previously, the classes - were located in the HttpKernel component. - Installation ------------ diff --git a/components/dependency_injection/factories.rst b/components/dependency_injection/factories.rst index 56acbe9a7f1..5573017af7a 100644 --- a/components/dependency_injection/factories.rst +++ b/components/dependency_injection/factories.rst @@ -4,11 +4,6 @@ Using a Factory to Create Services ================================== -.. versionadded:: 2.6 - The new :method:`Symfony\\Component\\DependencyInjection\\Definition::setFactory` - method was introduced in Symfony 2.6. Refer to older versions for the - syntax for factories prior to 2.6. - Symfony's Service Container provides a powerful way of controlling the creation of objects, allowing you to specify arguments passed to the constructor as well as calling methods and setting parameters. Sometimes, however, this diff --git a/components/dependency_injection/lazy_services.rst b/components/dependency_injection/lazy_services.rst index 2af8471b054..35ff2304667 100644 --- a/components/dependency_injection/lazy_services.rst +++ b/components/dependency_injection/lazy_services.rst @@ -4,9 +4,6 @@ Lazy Services ============= -.. versionadded:: 2.3 - Lazy services were introduced in Symfony 2.3. - Why lazy Services? ------------------ diff --git a/components/dom_crawler.rst b/components/dom_crawler.rst index 37ef6e24827..2e7f56dfa86 100644 --- a/components/dom_crawler.rst +++ b/components/dom_crawler.rst @@ -193,10 +193,6 @@ Get all the child or parent nodes:: Accessing Node Values ~~~~~~~~~~~~~~~~~~~~~ -.. versionadded:: 2.6 - The :method:`Symfony\\Component\\DomCrawler\\Crawler::nodeName` - method was introduced in Symfony 2.6. - Access the node name (HTML tag name) of the first node of the current selection (eg. "p" or "div"):: // will return the node name (HTML tag name) of the first child element under @@ -230,11 +226,6 @@ Call an anonymous function on each node of the list:: return $node->text(); }); -.. versionadded:: 2.3 - As seen here, in Symfony 2.3, the ``each`` and ``reduce`` Closure functions - are passed a ``Crawler`` as the first argument. Previously, that argument - was a :phpclass:`DOMNode`. - The anonymous function receives the node (as a Crawler) and the position as arguments. The result is an array of values returned by the anonymous function calls. diff --git a/components/expression_language/extending.rst b/components/expression_language/extending.rst index 4aded7c5aeb..b65783f6012 100644 --- a/components/expression_language/extending.rst +++ b/components/expression_language/extending.rst @@ -56,9 +56,6 @@ evaluating or the "names" if compiling). Using Expression Providers -------------------------- -.. versionadded:: 2.6 - Expression providers were introduced in Symfony 2.6. - When you use the ``ExpressionLanguage`` class in your library, you often want to add custom functions. To do so, you can create a new expression provider by creating a class that implements diff --git a/components/filesystem/introduction.rst b/components/filesystem/introduction.rst index 9f58e450300..aad7772a32d 100644 --- a/components/filesystem/introduction.rst +++ b/components/filesystem/introduction.rst @@ -241,9 +241,6 @@ isAbsolutePath dumpFile ~~~~~~~~ -.. versionadded:: 2.3 - The ``dumpFile()`` was introduced in Symfony 2.3. - :method:`Symfony\\Component\\Filesystem\\Filesystem::dumpFile` allows you to dump contents to a file. It does this in an atomic manner: it writes a temporary file first and then moves it to the new file location when it's finished. diff --git a/components/filesystem/lock_handler.rst b/components/filesystem/lock_handler.rst index d57889190ef..76169fcf8d4 100644 --- a/components/filesystem/lock_handler.rst +++ b/components/filesystem/lock_handler.rst @@ -1,9 +1,6 @@ LockHandler =========== -.. versionadded:: 2.6 - The lock handler feature was introduced in Symfony 2.6 - What is a Lock? --------------- diff --git a/components/finder.rst b/components/finder.rst index 48a6c55a9b9..5f2fa2fafed 100644 --- a/components/finder.rst +++ b/components/finder.rst @@ -93,10 +93,6 @@ Exclude directories from matching with the $finder->in(__DIR__)->exclude('ruby'); -.. versionadded:: 2.3 - The :method:`Symfony\\Component\\Finder\\Finder::ignoreUnreadableDirs` - method was introduced in Symfony 2.3. - It's also possible to ignore directories that you don't have permission to read:: $finder->ignoreUnreadableDirs()->in(__DIR__); diff --git a/components/form/form_events.rst b/components/form/form_events.rst index 91e14522c3d..ab92ddae53f 100644 --- a/components/form/form_events.rst +++ b/components/form/form_events.rst @@ -248,11 +248,6 @@ Name ``FormEvents`` Constant Event's Data ``form.post_bind`` ``FormEvents::POST_SUBMIT`` View data ====================== ============================= =============== -.. versionadded:: 2.3 - Before Symfony 2.3, ``FormEvents::PRE_SUBMIT``, ``FormEvents::SUBMIT`` - and ``FormEvents::POST_SUBMIT`` were called ``FormEvents::PRE_BIND``, - ``FormEvents::BIND`` and ``FormEvents::POST_BIND``. - .. caution:: The ``FormEvents::PRE_BIND``, ``FormEvents::BIND`` and diff --git a/components/form/introduction.rst b/components/form/introduction.rst index 09c947429b5..0e326906468 100644 --- a/components/form/introduction.rst +++ b/components/form/introduction.rst @@ -66,9 +66,6 @@ factory. Request Handling ~~~~~~~~~~~~~~~~ -.. versionadded:: 2.3 - The ``handleRequest()`` method was introduced in Symfony 2.3. - To process form data, you'll need to call the :method:`Symfony\\Component\\Form\\Form::handleRequest` method:: @@ -498,10 +495,6 @@ to do that in the ":ref:`form-rendering-template`" section. Changing a Form's Method and Action ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -.. versionadded:: 2.3 - The ability to configure the form method and action was introduced in - Symfony 2.3. - By default, a form is submitted to the same URI that rendered the form with an HTTP POST request. This behavior can be changed using the :ref:`form-option-action` and :ref:`form-option-method` options (the ``method`` option is also used diff --git a/components/http_foundation/introduction.rst b/components/http_foundation/introduction.rst index 9a5edd7d495..9ea3a3d632e 100644 --- a/components/http_foundation/introduction.rst +++ b/components/http_foundation/introduction.rst @@ -517,9 +517,6 @@ You can still set the ``Content-Type`` of the sent file, or change its ``Content 'filename.txt' ); -.. versionadded:: 2.6 - The ``deleteFileAfterSend()`` method was introduced in Symfony 2.6. - It is possible to delete the file after the request is sent with the :method:`Symfony\\Component\\HttpFoundation\\BinaryFileResponse::deleteFileAfterSend` method. Please note that this will not work when the ``X-Sendfile`` header is set. diff --git a/components/http_foundation/trusting_proxies.rst b/components/http_foundation/trusting_proxies.rst index fbe9b30cdee..a8c0193668d 100644 --- a/components/http_foundation/trusting_proxies.rst +++ b/components/http_foundation/trusting_proxies.rst @@ -19,10 +19,6 @@ Since HTTP headers can be spoofed, Symfony does *not* trust these proxy headers by default. If you are behind a proxy, you should manually whitelist your proxy. -.. versionadded:: 2.3 - CIDR notation support was introduced in Symfony 2.3, so you can whitelist whole - subnets (e.g. ``10.0.0.0/8``, ``fc00::/7``). - .. code-block:: php use Symfony\Component\HttpFoundation\Request; diff --git a/components/intl.rst b/components/intl.rst index 1c1dcc65a59..23a447d2214 100644 --- a/components/intl.rst +++ b/components/intl.rst @@ -8,10 +8,6 @@ The Intl Component A PHP replacement layer for the C `intl extension`_ that also provides access to the localization data of the `ICU library`_. -.. versionadded:: 2.3 - The Intl component was introduced in Symfony 2.3. In earlier versions of Symfony, - you should use the Locale component instead. - .. caution:: The replacement layer is limited to the locale "en". If you want to use diff --git a/components/options_resolver.rst b/components/options_resolver.rst index ef9a0f18bd2..2264f675d6b 100644 --- a/components/options_resolver.rst +++ b/components/options_resolver.rst @@ -20,11 +20,6 @@ You can install the component in 2 different ways: Notes on Previous Versions -------------------------- -.. versionadded:: 2.6 - This documentation was written for Symfony 2.6 and later. If you use an older - version, please `read the Symfony 2.5 documentation`_. For a list of changes, - see the `CHANGELOG`_. - Usage ----- @@ -220,10 +215,6 @@ For example, to make the ``host`` option required, you can do:: } } -.. versionadded:: 2.6 - As of Symfony 2.6, ``setRequired()`` accepts both an array of options or a - single option. Prior to 2.6, you could only pass arrays. - If you omit a required option, a :class:`Symfony\\Component\\OptionsResolver\\Exception\\MissingOptionsException` will be thrown:: @@ -248,11 +239,6 @@ one required option:: } } -.. versionadded:: 2.6 - The methods :method:`Symfony\\Component\\OptionsResolver\\OptionsResolver::isRequired` - and :method:`Symfony\\Component\\OptionsResolver\\OptionsResolver::getRequiredOptions` - were introduced in Symfony 2.6. - Use :method:`Symfony\\Component\\OptionsResolver\\OptionsResolver::isRequired` to find out if an option is required. You can use :method:`Symfony\\Component\\OptionsResolver\\OptionsResolver::getRequiredOptions` to @@ -273,11 +259,6 @@ retrieve the names of all required options:: } } -.. versionadded:: 2.6 - The methods :method:`Symfony\\Component\\OptionsResolver\\OptionsResolver::isMissing` - and :method:`Symfony\\Component\\OptionsResolver\\OptionsResolver::getMissingOptions` - were introduced in Symfony 2.6. - If you want to check whether a required option is still missing from the default options, you can use :method:`Symfony\\Component\\OptionsResolver\\OptionsResolver::isMissing`. The difference between this and :method:`Symfony\\Component\\OptionsResolver\\OptionsResolver::isRequired` @@ -360,12 +341,6 @@ is thrown:: In sub-classes, you can use :method:`Symfony\\Component\\OptionsResolver\\OptionsResolver::addAllowedTypes` to add additional allowed types without erasing the ones already set. -.. versionadded:: 2.6 - Before Symfony 2.6, `setAllowedTypes()` and `addAllowedTypes()` expected - the values to be given as an array mapping option names to allowed types:: - - $resolver->setAllowedTypes(array('port' => array('null', 'int'))); - Value Validation ~~~~~~~~~~~~~~~~ @@ -412,14 +387,6 @@ returns ``true`` for acceptable values and ``false`` for invalid values:: In sub-classes, you can use :method:`Symfony\\Component\\OptionsResolver\\OptionsResolver::addAllowedValues` to add additional allowed values without erasing the ones already set. -.. versionadded:: 2.6 - Before Symfony 2.6, `setAllowedValues()` and `addAllowedValues()` expected - the values to be given as an array mapping option names to allowed values: - - .. code-block:: php - - $resolver->setAllowedValues(array('transport' => array('sendmail', 'mail', 'smtp'))); - Option Normalization ~~~~~~~~~~~~~~~~~~~~ @@ -448,11 +415,6 @@ option. You can configure a normalizer by calling } } -.. versionadded:: 2.6 - The method :method:`Symfony\\Component\\OptionsResolver\\OptionsResolver::setNormalizer` - was introduced in Symfony 2.6. Before, you had to use - :method:`Symfony\\Component\\OptionsResolver\\OptionsResolver::setNormalizers`. - The normalizer receives the actual ``$value`` and returns the normalized form. You see that the closure also takes an ``$options`` parameter. This is useful if you need to use other options during normalization:: @@ -587,11 +549,6 @@ comes from the default:: } } -.. versionadded:: 2.6 - The method :method:`Symfony\\Component\\OptionsResolver\\OptionsResolver::setDefined` - was introduced in Symfony 2.6. Before, you had to use - :method:`Symfony\\Component\\OptionsResolver\\OptionsResolver::setOptional`. - You can use :method:`Symfony\\Component\\OptionsResolver\\OptionsResolver::setDefined` to define an option without setting a default value. Then the option will only be included in the resolved options if it was actually passed to @@ -643,11 +600,6 @@ options in one go:: } } -.. versionadded:: 2.6 - The method :method:`Symfony\\Component\\OptionsResolver\\OptionsResolver::isDefined` - and :method:`Symfony\\Component\\OptionsResolver\\OptionsResolver::getDefinedOptions` - were introduced in Symfony 2.6. - The methods :method:`Symfony\\Component\\OptionsResolver\\OptionsResolver::isDefined` and :method:`Symfony\\Component\\OptionsResolver\\OptionsResolver::getDefinedOptions` let you find out which options are defined:: diff --git a/components/process.rst b/components/process.rst index ef77f6078da..c2fa57150ce 100644 --- a/components/process.rst +++ b/components/process.rst @@ -134,9 +134,6 @@ are done doing other stuff:: Stopping a Process ------------------ -.. versionadded:: 2.3 - The ``signal`` parameter of the ``stop`` method was introduced in Symfony 2.3. - Any asynchronous process can be stopped at any time with the :method:`Symfony\\Component\\Process\\Process::stop` method. This method takes two arguments : a timeout and a signal. Once the timeout is reached, the signal @@ -173,10 +170,6 @@ To make your code work better on all platforms, you might want to use the $builder = new ProcessBuilder(array('ls', '-lsa')); $builder->getProcess()->run(); -.. versionadded:: 2.3 - The :method:`ProcessBuilder::setPrefix` - method was introduced in Symfony 2.3. - In case you are building a binary driver, you can use the :method:`Symfony\\Component\\Process\\Process::setPrefix` method to prefix all the generated process commands. @@ -256,9 +249,6 @@ exceeds 3600 seconds, or the process does not produce any output for 60 seconds. Process Signals --------------- -.. versionadded:: 2.3 - The ``signal`` method was introduced in Symfony 2.3. - When running a program asynchronously, you can send it posix signals with the :method:`Symfony\\Component\\Process\\Process::signal` method:: @@ -282,9 +272,6 @@ When running a program asynchronously, you can send it posix signals with the Process Pid ----------- -.. versionadded:: 2.3 - The ``getPid`` method was introduced in Symfony 2.3. - You can access the `pid`_ of a running process with the :method:`Symfony\\Component\\Process\\Process::getPid` method. diff --git a/components/property_access/introduction.rst b/components/property_access/introduction.rst index d8d4c774610..2d9679f7ab7 100644 --- a/components/property_access/introduction.rst +++ b/components/property_access/introduction.rst @@ -29,10 +29,6 @@ default configuration:: $accessor = PropertyAccess::createPropertyAccessor(); -.. versionadded:: 2.3 - The :method:`Symfony\\Component\\PropertyAccess\\PropertyAccess::createPropertyAccessor` - method was introduced in Symfony 2.3. Previously, it was called ``getPropertyAccessor()``. - Reading from Arrays ------------------- @@ -213,9 +209,6 @@ enable this feature by using :class:`Symfony\\Component\\PropertyAccess\\Propert echo $accessor->getValue($person, 'wouter'); // array(...) -.. versionadded:: 2.3 - The use of magic ``__call()`` method was introduced in Symfony 2.3. - .. caution:: The ``__call`` feature is disabled by default, you can enable it by calling diff --git a/components/security/authentication.rst b/components/security/authentication.rst index 035065dc5b1..92d7aeb9165 100644 --- a/components/security/authentication.rst +++ b/components/security/authentication.rst @@ -4,11 +4,6 @@ Authentication ============== -.. versionadded:: 2.6 - The ``TokenStorageInterface`` was introduced in Symfony 2.6. Prior, you - had to use the ``getToken()`` method of the - :class:`Symfony\\Component\\Security\\Core\\SecurityContextInterface`. - When a request points to a secured area, and one of the listeners from the firewall map is able to extract the user's credentials from the current :class:`Symfony\\Component\\HttpFoundation\\Request` object, it should create diff --git a/components/security/authorization.rst b/components/security/authorization.rst index 17d51b6e998..cb24e73981e 100644 --- a/components/security/authorization.rst +++ b/components/security/authorization.rst @@ -29,11 +29,6 @@ An authorization decision will always be based on a few things: Any object for which access control needs to be checked, like an article or a comment object. -.. versionadded:: 2.6 - The ``TokenStorageInterface`` was introduced in Symfony 2.6. Prior, you - had to use the ``setToken()`` method of the - :class:`Symfony\\Component\\Security\\Core\\SecurityContextInterface`. - .. _components-security-access-decision-manager: Access Decision Manager diff --git a/components/security/firewall.rst b/components/security/firewall.rst index 64603efb319..c3fe82f4c49 100644 --- a/components/security/firewall.rst +++ b/components/security/firewall.rst @@ -34,11 +34,6 @@ certain action or resource of the application:: throw new AccessDeniedException(); } -.. versionadded:: 2.6 - As of Symfony 2.6, the :class:`Symfony\\Component\\Security\\Core\\SecurityContext` class was split - in the :class:`Symfony\\Component\\Security\\Core\\Authorization\\AuthorizationChecker` and - :class:`Symfony\\Component\\Security\\Core\\Authentication\\Token\\Storage\\TokenStorage` classes. - .. note:: Read the dedicated sections to learn more about :doc:`/components/security/authentication` diff --git a/components/serializer.rst b/components/serializer.rst index ac40aa46a19..0865244ba47 100644 --- a/components/serializer.rst +++ b/components/serializer.rst @@ -119,10 +119,6 @@ in this case :class:`Symfony\\Component\\Serializer\\Encoder\\JsonEncoder`. Ignoring Attributes when Serializing ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -.. versionadded:: 2.3 - The :method:`GetSetMethodNormalizer::setIgnoredAttributes` - method was introduced in Symfony 2.3. - As an option, there's a way to ignore attributes from the origin object when serializing. To remove those attributes use the :method:`Symfony\\Component\\Serializer\\Normalizer\\GetSetMethodNormalizer::setIgnoredAttributes` @@ -165,10 +161,6 @@ needs three parameters: Using Camelized Method Names for Underscored Attributes ------------------------------------------------------- -.. versionadded:: 2.3 - The :method:`GetSetMethodNormalizer::setCamelizedAttributes` - method was introduced in Symfony 2.3. - Sometimes property names from the serialized content are underscored (e.g. ``first_name``). Normally, these attributes will use get/set methods like ``getFirst_name``, when ``getFirstName`` method is what you really want. To @@ -241,10 +233,6 @@ When serializing, you can set a callback to format a specific object property:: Handling Circular References ---------------------------- -.. versionadded:: 2.6 - Handling of circular references was introduced in Symfony 2.6. In previous - versions of Symfony, circular references led to infinite loops. - Circular references are common when dealing with entity relations:: class Organization diff --git a/components/var_dumper/introduction.rst b/components/var_dumper/introduction.rst index 869c73fc6fe..8d3d5192f46 100644 --- a/components/var_dumper/introduction.rst +++ b/components/var_dumper/introduction.rst @@ -9,9 +9,6 @@ The VarDumper Component arbitrary PHP variable. Built on top, it provides a better ``dump()`` function that you can use instead of :phpfunction:`var_dump`. -.. versionadded:: 2.6 - The VarDumper component was introduced in Symfony 2.6. - Installation ------------ diff --git a/cookbook/configuration/pdo_session_storage.rst b/cookbook/configuration/pdo_session_storage.rst index 774ebe0478e..038834e2098 100644 --- a/cookbook/configuration/pdo_session_storage.rst +++ b/cookbook/configuration/pdo_session_storage.rst @@ -144,10 +144,6 @@ a second array argument to ``PdoSessionHandler``: ); $container->setDefinition('session.handler.pdo', $storageDefinition); -.. versionadded:: 2.6 - The ``db_lifetime_col`` was introduced in Symfony 2.6. Prior to 2.6, - this column did not exist. - The following things can be configured: * ``db_table``: (default ``session``) The name of the session table in your diff --git a/cookbook/console/logging.rst b/cookbook/console/logging.rst index ae69c4264da..e2946d17146 100644 --- a/cookbook/console/logging.rst +++ b/cookbook/console/logging.rst @@ -72,9 +72,6 @@ Enabling automatic Exceptions Logging To get your console application to automatically log uncaught exceptions for all of your commands, you can use :doc:`console events`. -.. versionadded:: 2.3 - Console events were introduced in Symfony 2.3. - First configure a listener for console exception events in the service container: .. configuration-block:: diff --git a/cookbook/console/sending_emails.rst b/cookbook/console/sending_emails.rst index dd2e021cf93..268976f2dfc 100644 --- a/cookbook/console/sending_emails.rst +++ b/cookbook/console/sending_emails.rst @@ -85,10 +85,6 @@ from the ``router`` service and override its settings:: Using Memory Spooling --------------------- -.. versionadded:: 2.3 - When using Symfony 2.3+ and SwiftmailerBundle 2.3.5+, the memory spool is now - handled automatically in the CLI and the code below is not necessary anymore. - Sending emails in a console command works the same way as described in the :doc:`/cookbook/email/email` cookbook except if memory spooling is used. diff --git a/cookbook/controller/error_pages.rst b/cookbook/controller/error_pages.rst index 35199483430..b52201802e5 100644 --- a/cookbook/controller/error_pages.rst +++ b/cookbook/controller/error_pages.rst @@ -153,10 +153,6 @@ Testing Error Pages during Development The default ``ExceptionController`` also allows you to preview your *error* pages during development. -.. versionadded:: 2.6 - This feature was introduced in Symfony 2.6. Before, the third-party - `WebfactoryExceptionsBundle`_ could be used for the same purpose. - To use this feature, you need to have a definition in your ``routing_dev.yml`` file like so: diff --git a/cookbook/controller/service.rst b/cookbook/controller/service.rst index 238d343b121..bf2cadb2887 100644 --- a/cookbook/controller/service.rst +++ b/cookbook/controller/service.rst @@ -120,10 +120,6 @@ the route ``_controller`` value: defined as a service. See the `FrameworkExtraBundle documentation`_ for details. -.. versionadded:: 2.6 - If your controller service implements the ``__invoke`` method, you can simply refer to the service id - (``acme.hello.controller``). - Alternatives to base Controller Methods --------------------------------------- diff --git a/cookbook/doctrine/mapping_model_classes.rst b/cookbook/doctrine/mapping_model_classes.rst index 9894777a339..da5943dc915 100644 --- a/cookbook/doctrine/mapping_model_classes.rst +++ b/cookbook/doctrine/mapping_model_classes.rst @@ -16,19 +16,6 @@ register the mappings for your model classes. for one of the ODMs. For reusable bundles, rather than duplicate model classes just to get the auto-mapping, use the compiler pass. -.. versionadded:: 2.3 - The base mapping compiler pass was introduced in Symfony 2.3. The Doctrine bundles - support it from DoctrineBundle >= 1.2.1, MongoDBBundle >= 3.0.0, - PHPCRBundle >= 1.0.0 and the (unversioned) CouchDBBundle supports the - compiler pass since the `CouchDB Mapping Compiler Pass pull request`_ - was merged. - -.. versionadded:: 2.6 - Support for defining namespace aliases was introduced in Symfony 2.6. - It is safe to define the aliases with older versions of Symfony as - the aliases are the last argument to ``createXmlMappingDriver`` and - are ignored by PHP if that argument doesn't exist. - In your bundle class, write the following code to register the compiler pass. This one is written for the CmfRoutingBundle, so parts of it will need to be adapted for your case:: diff --git a/cookbook/form/create_custom_field_type.rst b/cookbook/form/create_custom_field_type.rst index a472ad7e687..a3c77ac59cb 100644 --- a/cookbook/form/create_custom_field_type.rst +++ b/cookbook/form/create_custom_field_type.rst @@ -252,10 +252,6 @@ But this only works because the ``GenderType()`` is very simple. What if the gender codes were stored in configuration or in a database? The next section explains how more complex field types solve this problem. -.. versionadded:: 2.6 - The ``placeholder`` option was introduced in Symfony 2.6 in favor of - ``empty_value``, which is available prior to 2.6. - .. _form-cookbook-form-field-service: Creating your Field Type as a Service diff --git a/cookbook/form/direct_submit.rst b/cookbook/form/direct_submit.rst index 221f7f534d8..8e1fa8bd85f 100644 --- a/cookbook/form/direct_submit.rst +++ b/cookbook/form/direct_submit.rst @@ -4,10 +4,6 @@ How to Use the submit() Function to Handle Form Submissions =========================================================== -.. versionadded:: 2.3 - The :method:`Symfony\\Component\\Form\\FormInterface::handleRequest` - method was introduced in Symfony 2.3. - With the ``handleRequest()`` method, it is really easy to handle form submissions:: @@ -42,9 +38,6 @@ submissions:: Calling Form::submit() manually ------------------------------- -.. versionadded:: 2.3 - Before Symfony 2.3, the ``submit()`` method was known as ``bind()``. - In some cases, you want better control over when exactly your form is submitted and what data is passed to it. Instead of using the :method:`Symfony\\Component\\Form\\FormInterface::handleRequest` @@ -89,9 +82,6 @@ method, pass the submitted data directly to Passing a Request to Form::submit() (Deprecated) ------------------------------------------------ -.. versionadded:: 2.3 - Before Symfony 2.3, the ``submit`` method was known as ``bind``. - Before Symfony 2.3, the :method:`Symfony\\Component\\Form\\FormInterface::submit` method accepted a :class:`Symfony\\Component\\HttpFoundation\\Request` object as a convenient shortcut to the previous example:: diff --git a/cookbook/form/dynamic_form_modification.rst b/cookbook/form/dynamic_form_modification.rst index 0389ae88fb9..d83df603431 100644 --- a/cookbook/form/dynamic_form_modification.rst +++ b/cookbook/form/dynamic_form_modification.rst @@ -336,11 +336,6 @@ and fill in the listener logic:: // ... } -.. versionadded:: 2.6 - The :class:`Symfony\\Component\\Security\\Core\\Authentication\\Token\\Storage\\TokenStorageInterface` was - introduced in Symfony 2.6. Prior, you had to use the ``getToken()`` method of - :class:`Symfony\\Component\\Security\\Core\\SecurityContextInterface`. - .. note:: The ``multiple`` and ``expanded`` form options will default to false @@ -502,10 +497,6 @@ sport like this:: // ... } -.. versionadded:: 2.6 - The ``placeholder`` option was introduced in Symfony 2.6 in favor of - ``empty_value``, which is available prior to 2.6. - When you're building this form to display to the user for the first time, then this example works perfectly. @@ -521,10 +512,6 @@ On a form, we can usually listen to the following events: * ``SUBMIT`` * ``POST_SUBMIT`` -.. versionadded:: 2.3 - The events ``PRE_SUBMIT``, ``SUBMIT`` and ``POST_SUBMIT`` were introduced - in Symfony 2.3. Before, they were named ``PRE_BIND``, ``BIND`` and ``POST_BIND``. - The key is to add a ``POST_SUBMIT`` listener to the field that your new field depends on. If you add a ``POST_SUBMIT`` listener to a form child (e.g. ``sport``), and add new children to the parent form, the Form component will detect the diff --git a/cookbook/form/inherit_data_option.rst b/cookbook/form/inherit_data_option.rst index 75db174ea3e..5a124f7274f 100644 --- a/cookbook/form/inherit_data_option.rst +++ b/cookbook/form/inherit_data_option.rst @@ -4,10 +4,6 @@ How to Reduce Code Duplication with "inherit_data" ================================================== -.. versionadded:: 2.3 - This ``inherit_data`` option was introduced in Symfony 2.3. Before, it - was known as ``virtual``. - The ``inherit_data`` form field option can be very useful when you have some duplicated fields in different entities. For example, imagine you have two entities, a ``Company`` and a ``Customer``:: diff --git a/cookbook/form/unit_testing.rst b/cookbook/form/unit_testing.rst index a6d2cd458ce..945ceaf53c1 100644 --- a/cookbook/form/unit_testing.rst +++ b/cookbook/form/unit_testing.rst @@ -20,11 +20,6 @@ There is already a class that you can benefit from for simple FormTypes testing: :class:`Symfony\\Component\\Form\\Test\\TypeTestCase`. It is used to test the core types and you can use it to test your types too. -.. versionadded:: 2.3 - The ``TypeTestCase`` has moved to the ``Symfony\Component\Form\Test`` - namespace in 2.3. Previously, the class was located in - ``Symfony\Component\Form\Tests\Extension\Core\Type``. - .. note:: Depending on the way you installed your Symfony or Symfony Form component diff --git a/cookbook/profiler/matchers.rst b/cookbook/profiler/matchers.rst index b01ba820952..4a7955bc041 100644 --- a/cookbook/profiler/matchers.rst +++ b/cookbook/profiler/matchers.rst @@ -89,11 +89,6 @@ something like:: } } -.. 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, you need to configure the service: .. configuration-block:: @@ -123,10 +118,6 @@ Then, you need to configure the service: array(new Reference('security.authorization_checker')) ); -.. 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. - Now 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 6894a5043c2..026fe8d49cf 100644 --- a/cookbook/security/custom_password_authenticator.rst +++ b/cookbook/security/custom_password_authenticator.rst @@ -16,9 +16,6 @@ The Password Authenticator .. versionadded:: 2.4 The ``SimpleFormAuthenticatorInterface`` interface was introduced in Symfony 2.4. -.. versionadded:: 2.6 - The ``UserPasswordEncoderInterface`` interface was introduced in Symfony 2.6. - First, create a new class that implements :class:`Symfony\\Component\\Security\\Core\\Authentication\\SimpleFormAuthenticatorInterface`. Eventually, this will allow you to create custom logic for authenticating diff --git a/cookbook/security/pre_authenticated.rst b/cookbook/security/pre_authenticated.rst index 7a0775a8ab8..21b08586153 100644 --- a/cookbook/security/pre_authenticated.rst +++ b/cookbook/security/pre_authenticated.rst @@ -83,9 +83,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/security/remember_me.rst b/cookbook/security/remember_me.rst index 590d8d9eaac..a364e9cf5c8 100644 --- a/cookbook/security/remember_me.rst +++ b/cookbook/security/remember_me.rst @@ -171,10 +171,6 @@ In the following example, the action is only allowed if the user has the // ... } -.. 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. - You can also choose to install and use the optional JMSSecurityExtraBundle_, which can secure your controller using annotations: diff --git a/cookbook/security/securing_services.rst b/cookbook/security/securing_services.rst index b11900638eb..75179c1bf95 100644 --- a/cookbook/security/securing_services.rst +++ b/cookbook/security/securing_services.rst @@ -21,10 +21,6 @@ and checking the current user's role:: // ... } -.. 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. - You can also secure *any* service in a similar way by injecting the ``security.authorization_checker`` service into it. For a general introduction to injecting dependencies into services see the :doc:`/book/service_container` chapter of the book. For diff --git a/cookbook/security/voters_data_permission.rst b/cookbook/security/voters_data_permission.rst index 057d8e04919..c00673d2c22 100644 --- a/cookbook/security/voters_data_permission.rst +++ b/cookbook/security/voters_data_permission.rst @@ -221,8 +221,4 @@ from the authorization checker is called. } } -.. 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. - It's that easy! diff --git a/cookbook/serializer.rst b/cookbook/serializer.rst index 762a0f86d19..8214dc0c7fe 100644 --- a/cookbook/serializer.rst +++ b/cookbook/serializer.rst @@ -17,10 +17,6 @@ functionality offered by Symfony's core serializer. Activating the Serializer ------------------------- -.. versionadded:: 2.3 - The Serializer has always existed in Symfony, but prior to Symfony 2.3, - you needed to build the ``serializer`` service yourself. - The ``serializer`` service is not available by default. To turn it on, activate it in your configuration: diff --git a/cookbook/service_container/scopes.rst b/cookbook/service_container/scopes.rst index 80928dacb19..ccca34a0ecb 100644 --- a/cookbook/service_container/scopes.rst +++ b/cookbook/service_container/scopes.rst @@ -117,9 +117,6 @@ Each scenario is detailed in the following sections. A) Using a Synchronized Service ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -.. versionadded:: 2.3 - Synchronized services were introduced in Symfony 2.3. - Both injecting the container and setting your service to a narrower scope have drawbacks. Assume first that the ``client_configuration`` service has been marked as ``synchronized``: diff --git a/cookbook/session/php_bridge.rst b/cookbook/session/php_bridge.rst index fd18a7e3b75..2c2cec6dad8 100644 --- a/cookbook/session/php_bridge.rst +++ b/cookbook/session/php_bridge.rst @@ -4,9 +4,6 @@ Bridge a legacy Application with Symfony Sessions ================================================= -.. versionadded:: 2.3 - The ability to integrate with a legacy PHP session was introduced in Symfony 2.3. - If you're integrating the Symfony full-stack Framework into a legacy application that starts the session with ``session_start()``, you may still be able to use Symfony's session management by using the PHP Bridge session. diff --git a/cookbook/web_server/built_in.rst b/cookbook/web_server/built_in.rst index 33289907614..e4902ea2b36 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/framework.rst b/reference/configuration/framework.rst index 5c2d3bc2547..399b997a76c 100644 --- a/reference/configuration/framework.rst +++ b/reference/configuration/framework.rst @@ -78,9 +78,6 @@ parameter named ``kernel.secret``. http_method_override ~~~~~~~~~~~~~~~~~~~~ -.. versionadded:: 2.3 - The ``http_method_override`` option was introduced in Symfony 2.3. - **type**: ``Boolean`` **default**: ``true`` This determines whether the ``_method`` request parameter is used as the intended @@ -107,9 +104,6 @@ using the following keys: * ``emacs`` * ``sublime`` -.. versionadded:: 2.3.14 - The ``emacs`` and ``sublime`` editors were introduced in Symfony 2.3.14. - You can also specify a custom url string. If you do this, all percentage signs (``%``) must be doubled to escape that character. For example, if you have installed `PhpStormOpener`_ and use PHPstorm, you will do something like: @@ -180,10 +174,6 @@ trusted_proxies Configures the IP addresses that should be trusted as proxies. For more details, see :doc:`/cookbook/request/load_balancer_reverse_proxy`. -.. versionadded:: 2.3 - CIDR notation support was introduced in Symfony 2.3, so you can whitelist whole - subnets (e.g. ``10.0.0.0/8``, ``fc00::/7``). - .. configuration-block:: .. code-block:: yaml @@ -498,11 +488,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 key to ``true``. When you are @@ -512,12 +497,6 @@ and ``test`` environments. collect ....... -.. versionadded:: 2.3 - The ``collect`` option was introduced in Symfony 2.3. Previously, when - ``profiler.enabled`` was ``false``, the profiler *was* actually enabled, - but the collectors were disabled. Now, the profiler and the collectors - can be controlled independently. - **type**: ``boolean`` **default**: ``true`` This option configures the way the profiler behaves when it is enabled. If set @@ -553,9 +532,6 @@ For more details, see :doc:`/book/translation`. 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 diff --git a/reference/constraints/Collection.rst b/reference/constraints/Collection.rst index 2c93325da2f..539ec835d42 100644 --- a/reference/constraints/Collection.rst +++ b/reference/constraints/Collection.rst @@ -175,10 +175,6 @@ from the ``$personalData`` property, no validation error would occur. Required and optional Field Constraints ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -.. versionadded:: 2.3 - The ``Required`` and ``Optional`` constraints were moved to the namespace - ``Symfony\Component\Validator\Constraints\`` in Symfony 2.3. - Constraints for fields within a collection can be wrapped in the ``Required`` or ``Optional`` constraint to control whether they should always be applied (``Required``) or only applied when the field is present (``Optional``). diff --git a/reference/constraints/Currency.rst b/reference/constraints/Currency.rst index 553c2be4ec1..5a18d743415 100644 --- a/reference/constraints/Currency.rst +++ b/reference/constraints/Currency.rst @@ -1,9 +1,6 @@ Currency ======== -.. versionadded:: 2.3 - The ``Currency`` constraint was introduced in Symfony 2.3. - Validates that a value is a valid `3-letter ISO 4217`_ currency name. +----------------+---------------------------------------------------------------------------+ diff --git a/reference/constraints/EqualTo.rst b/reference/constraints/EqualTo.rst index c57fce55e11..0b53bc78587 100644 --- a/reference/constraints/EqualTo.rst +++ b/reference/constraints/EqualTo.rst @@ -1,9 +1,6 @@ EqualTo ======= -.. versionadded:: 2.3 - The ``EqualTo`` constraint was introduced in Symfony 2.3. - Validates that a value is equal to another value, defined in the options. To force that a value is *not* equal, see :doc:`/reference/constraints/NotEqualTo`. diff --git a/reference/constraints/File.rst b/reference/constraints/File.rst index eb45c931475..41c8e8b0f89 100644 --- a/reference/constraints/File.rst +++ b/reference/constraints/File.rst @@ -155,9 +155,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 order @@ -183,9 +180,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 @@ -225,10 +219,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 2d773953bcd..52d2e1a732b 100644 --- a/reference/constraints/GreaterThan.rst +++ b/reference/constraints/GreaterThan.rst @@ -1,9 +1,6 @@ GreaterThan =========== -.. versionadded:: 2.3 - The ``GreaterThan`` constraint was introduced in Symfony 2.3. - Validates that a value is greater than another value, defined in the options. To force that a value is greater than or equal to another value, see :doc:`/reference/constraints/GreaterThanOrEqual`. To force a value is less diff --git a/reference/constraints/GreaterThanOrEqual.rst b/reference/constraints/GreaterThanOrEqual.rst index 9d4cf37ecc5..5e2216b3d23 100644 --- a/reference/constraints/GreaterThanOrEqual.rst +++ b/reference/constraints/GreaterThanOrEqual.rst @@ -1,9 +1,6 @@ GreaterThanOrEqual ================== -.. versionadded:: 2.3 - The ``GreaterThanOrEqual`` constraint was introduced in Symfony 2.3. - Validates that a value is greater than or equal to another value, defined in the options. To force that a value is greater than another value, see :doc:`/reference/constraints/GreaterThan`. diff --git a/reference/constraints/Iban.rst b/reference/constraints/Iban.rst index 45a423e945c..33b4e822985 100644 --- a/reference/constraints/Iban.rst +++ b/reference/constraints/Iban.rst @@ -1,9 +1,6 @@ Iban ==== -.. versionadded:: 2.3 - The Iban constraint was introduced in Symfony 2.3. - This constraint is used to ensure that a bank account number has the proper format of an `International Bank Account Number (IBAN)`_. IBAN is an internationally agreed means of identifying bank accounts across national borders with a reduced risk of propagating diff --git a/reference/constraints/IdenticalTo.rst b/reference/constraints/IdenticalTo.rst index 068035f31a9..b5391cbc943 100644 --- a/reference/constraints/IdenticalTo.rst +++ b/reference/constraints/IdenticalTo.rst @@ -1,9 +1,6 @@ IdenticalTo =========== -.. versionadded:: 2.3 - The ``IdenticalTo`` constraint was introduced in Symfony 2.3. - Validates that a value is identical to another value, defined in the options. To force that a value is *not* identical, see :doc:`/reference/constraints/NotIdenticalTo`. diff --git a/reference/constraints/Isbn.rst b/reference/constraints/Isbn.rst index 6883f0e1aa4..8d7c4990abe 100644 --- a/reference/constraints/Isbn.rst +++ b/reference/constraints/Isbn.rst @@ -1,9 +1,6 @@ Isbn ==== -.. versionadded:: 2.3 - The Isbn constraint was introduced in Symfony 2.3. - .. caution:: The ``isbn10`` and ``isbn13`` options are deprecated since Symfony 2.5 diff --git a/reference/constraints/Issn.rst b/reference/constraints/Issn.rst index 0c200a73490..40e0931a6fc 100644 --- a/reference/constraints/Issn.rst +++ b/reference/constraints/Issn.rst @@ -1,9 +1,6 @@ Issn ==== -.. versionadded:: 2.3 - The Issn constraint was introduced in Symfony 2.3. - Validates that a value is a valid `International Standard Serial Number (ISSN)`_. +----------------+-----------------------------------------------------------------------+ diff --git a/reference/constraints/LessThan.rst b/reference/constraints/LessThan.rst index ea5be3c6675..a5704eeea51 100644 --- a/reference/constraints/LessThan.rst +++ b/reference/constraints/LessThan.rst @@ -1,9 +1,6 @@ LessThan ======== -.. versionadded:: 2.3 - The ``LessThan`` constraint was introduced in Symfony 2.3. - Validates that a value is less than another value, defined in the options. To force that a value is less than or equal to another value, see :doc:`/reference/constraints/LessThanOrEqual`. To force a value is greater diff --git a/reference/constraints/LessThanOrEqual.rst b/reference/constraints/LessThanOrEqual.rst index a936ee76ba8..cdbdc6235cb 100644 --- a/reference/constraints/LessThanOrEqual.rst +++ b/reference/constraints/LessThanOrEqual.rst @@ -1,9 +1,6 @@ LessThanOrEqual =============== -.. versionadded:: 2.3 - The ``LessThanOrEqual`` constraint was introduced in Symfony 2.3. - Validates that a value is less than or equal to another value, defined in the options. To force that a value is less than another value, see :doc:`/reference/constraints/LessThan`. diff --git a/reference/constraints/NotEqualTo.rst b/reference/constraints/NotEqualTo.rst index 1ea36a08994..051df1376f4 100644 --- a/reference/constraints/NotEqualTo.rst +++ b/reference/constraints/NotEqualTo.rst @@ -1,9 +1,6 @@ NotEqualTo ========== -.. versionadded:: 2.3 - The ``NotEqualTo`` constraint was introduced in Symfony 2.3. - Validates that a value is **not** equal to another value, defined in the options. To force that a value is equal, see :doc:`/reference/constraints/EqualTo`. diff --git a/reference/constraints/NotIdenticalTo.rst b/reference/constraints/NotIdenticalTo.rst index 63e6b0462dd..0e0c9a45486 100644 --- a/reference/constraints/NotIdenticalTo.rst +++ b/reference/constraints/NotIdenticalTo.rst @@ -1,9 +1,6 @@ NotIdenticalTo ============== -.. versionadded:: 2.3 - The ``NotIdenticalTo`` constraint was introduced in Symfony 2.3. - Validates that a value is **not** identical to another value, defined in the options. To force that a value is identical, see :doc:`/reference/constraints/IdenticalTo`. diff --git a/reference/dic_tags.rst b/reference/dic_tags.rst index 8a58ff4e8b1..2a1766a7fc1 100644 --- a/reference/dic_tags.rst +++ b/reference/dic_tags.rst @@ -887,10 +887,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 @@ -901,10 +897,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/twig_reference.rst b/reference/forms/twig_reference.rst index 3f45d66c0b8..aca79d273e9 100644 --- a/reference/forms/twig_reference.rst +++ b/reference/forms/twig_reference.rst @@ -313,9 +313,6 @@ object: get('name')->vars['label'] ?> -.. versionadded:: 2.3 - The ``method`` and ``action`` variables were introduced in Symfony 2.3. - .. versionadded:: 2.4 The ``submitted`` variable was introduced in Symfony 2.4. diff --git a/reference/forms/types/button.rst b/reference/forms/types/button.rst index 67d8bef4055..1a6197592d1 100644 --- a/reference/forms/types/button.rst +++ b/reference/forms/types/button.rst @@ -4,9 +4,6 @@ button Field Type ================= -.. versionadded:: 2.3 - The ``button`` type was introduced in Symfony 2.3 - A simple, non-responsive button. +----------------------+----------------------------------------------------------------------+ diff --git a/reference/forms/types/date.rst b/reference/forms/types/date.rst index 8197e7da328..448f07ec1cd 100644 --- a/reference/forms/types/date.rst +++ b/reference/forms/types/date.rst @@ -86,10 +86,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/options/action.rst.inc b/reference/forms/types/options/action.rst.inc index 7cfcadae101..73affbc59b6 100644 --- a/reference/forms/types/options/action.rst.inc +++ b/reference/forms/types/options/action.rst.inc @@ -1,9 +1,6 @@ action ~~~~~~ -.. versionadded:: 2.3 - The ``action`` option was introduced in Symfony 2.3. - **type**: ``string`` **default**: empty string This option specifies where to send the form's data on submission (usually a 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/inherit_data.rst.inc b/reference/forms/types/options/inherit_data.rst.inc index 9f5f1510ca8..5a90c180056 100644 --- a/reference/forms/types/options/inherit_data.rst.inc +++ b/reference/forms/types/options/inherit_data.rst.inc @@ -1,10 +1,6 @@ inherit_data ~~~~~~~~~~~~ -.. versionadded:: 2.3 - The ``inherit_data`` option was introduced in Symfony 2.3. Before, it - was known as ``virtual``. - **type**: ``boolean`` **default**: ``false`` This option determines if the form will inherit data from its parent form. diff --git a/reference/forms/types/options/method.rst.inc b/reference/forms/types/options/method.rst.inc index 6a327c21b26..3d8a85bdc3b 100644 --- a/reference/forms/types/options/method.rst.inc +++ b/reference/forms/types/options/method.rst.inc @@ -1,9 +1,6 @@ method ~~~~~~ -.. versionadded:: 2.3 - The ``method`` option was introduced in Symfony 2.3. - **type**: ``string`` **default**: ``POST`` This option specifies the HTTP method used to submit the form's data. Its diff --git a/reference/forms/types/options/placeholder.rst.inc b/reference/forms/types/options/placeholder.rst.inc index 143f8d60c12..ef9c5eb71c2 100644 --- a/reference/forms/types/options/placeholder.rst.inc +++ b/reference/forms/types/options/placeholder.rst.inc @@ -1,14 +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. - **type**: ``string`` or ``Boolean`` This option determines whether or not a special "empty" option (e.g. "Choose an option") diff --git a/reference/forms/types/reset.rst b/reference/forms/types/reset.rst index 20b2d9dad70..ded00804e40 100644 --- a/reference/forms/types/reset.rst +++ b/reference/forms/types/reset.rst @@ -4,9 +4,6 @@ reset Field Type ================ -.. versionadded:: 2.3 - The ``reset`` type was introduced in Symfony 2.3 - A button that resets all fields to their original values. +----------------------+---------------------------------------------------------------------+ diff --git a/reference/forms/types/submit.rst b/reference/forms/types/submit.rst index 63385eb328c..3c4c929d210 100644 --- a/reference/forms/types/submit.rst +++ b/reference/forms/types/submit.rst @@ -4,9 +4,6 @@ submit Field Type ================= -.. versionadded:: 2.3 - The ``submit`` type was introduced in Symfony 2.3 - A submit button. +----------------------+----------------------------------------------------------------------+ diff --git a/reference/twig_reference.rst b/reference/twig_reference.rst index 1e23c89c381..8e04a9d83db 100644 --- a/reference/twig_reference.rst +++ b/reference/twig_reference.rst @@ -685,10 +685,6 @@ The available attributes are: * ``app.debug`` * ``app.security`` -.. versionadded:: 2.6 - 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 -----------------------------------