Merge branch '3.0'

* 3.0: (27 commits)
  Removed all 2.x versionadded directives
  removed duplicate lines
  Updated "Learn more from the Cookbook" section
  [#6072] some tweaks
  [Cookbook][Console] change API doc class name
  Improvement to the apache/mod_php configuration example
  Fixed a syntax issue
  Implemented changes suggested by Wouter
  Fixed a reference
  Minor fixes
  Fixed a syntax issue
  Finished the first version of the BrowserKit doc
  fix title underline
  spelling and formating
  Adding documentation for cookies
  added docs on histroy
  added form submissions and moved creating a client to top
  more outlines, fixed link, added more about creating a client
  added a link snippit
  fixed spelling
  ...

Author: xabbuh

best_practices/configuration.rst

@@ -52,8 +52,8 @@ Canonical Parameters
     Define all your application's parameters in the
     ``app/config/parameters.yml.dist`` file.
 
-Since version 2.3, Symfony includes a configuration file called ``parameters.yml.dist``,
-which stores the canonical list of configuration parameters for the application.
+Symfony includes a configuration file called ``parameters.yml.dist``, which
+stores the canonical list of configuration parameters for the application.
 
 Whenever a new configuration parameter is defined for the application, you
 should also add it to this file and submit the changes to your version control

best_practices/creating-the-project.rst

@@ -114,8 +114,7 @@ ProductBundle, then there's no advantage to having two separate bundles.
     Create only one bundle called AppBundle for your application logic
 
 Implementing a single AppBundle bundle in your projects will make your code
-more concise and easier to understand. Starting in Symfony 2.6, the official
-Symfony documentation uses the AppBundle name.
+more concise and easier to understand.
 
 .. note::
 

best_practices/forms.rst

@@ -85,9 +85,10 @@ makes them easier to re-use later.
 
     Add buttons in the templates, not in the form classes or the controllers.
 
-Since Symfony 2.3, you can add buttons as fields on your form. This is a nice
-way to simplify the template that renders your form. But if you add the buttons
-directly in your form class, this would effectively limit the scope of that form:
+The Symfony Form component allows you to add buttons as fields on your form.
+This is a nice way to simplify the template that renders your form. But if you
+add the buttons directly in your form class, this would effectively limit the
+scope of that form:
 
 .. code-block:: php
 

best_practices/i18n.rst

@@ -32,9 +32,9 @@ Of all the available translation formats, only XLIFF and gettext have broad
 support in the tools used by professional translators. And since it's based
 on XML, you can validate XLIFF file contents as you write them.
 
-Symfony 2.6 added support for notes inside XLIFF files, making them more
-user-friendly for translators. At the end, good translations are all about
-context, and these XLIFF notes allow you to define that context.
+Symfony supports notes in XLIFF files, making them more user-friendly for
+translators. At the end, good translations are all about context, and these
+XLIFF notes allow you to define that context.
 
 .. tip::
 

best_practices/security.rst

@@ -270,7 +270,6 @@ the same ``getAuthorEmail`` logic you used above:
     use Symfony\Component\Security\Core\User\UserInterface;
     use AppBundle\Entity\Post;
 
-    // Voter class requires Symfony 2.8 or higher version
     class PostVoter extends Voter
     {
         const CREATE = 'create';

book/forms.rst

@@ -123,20 +123,9 @@ You've also assigned each a "type" (e.g. ``TextType`` and ``DateType``),
 represented by its fully qualified class name. Among other things, it determines
 which HTML form tag(s) is rendered for that field.
 
-.. versionadded:: 2.8
-    To denote the form type, you have to use the fully qualified class name - like
-    ``TextType::class`` in PHP 5.5+ or ``Symfony\Component\Form\Extension\Core\Type\TextType``.
-    Before Symfony 2.8, you could use an alias for each type like ``text`` or
-    ``date``. The old alias syntax will still work until Symfony 3.0. For more details,
-    see the `2.8 UPGRADE Log`_.
-
 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`).
 
@@ -259,12 +248,6 @@ your controller::
     is called. Otherwise, changes done in the ``*_SUBMIT`` events aren't applied to the
     view (like validation errors).
 
-.. 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:
 
@@ -313,9 +296,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::
@@ -491,10 +471,6 @@ you'll need to specify which validation group(s) your form should use::
         'validation_groups' => array('registration'),
     ))->add(...);
 
-.. versionadded:: 2.7
-    The ``configureOptions()`` method was introduced in Symfony 2.7. Previously,
-    the method was called ``setDefaultOptions()``.
-
 If you're creating :ref:`form classes <book-form-creating-form-classes>` (a
 good practice), then you'll need to add the following to the ``configureOptions()``
 method::
@@ -517,9 +493,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``::
 
@@ -620,9 +593,6 @@ work in the book section about :ref:`validation groups <book-validation-validati
 Groups based on the Clicked Button
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 2.3
-    Support for buttons in forms was introduced in Symfony 2.3.
-
 When your form contains multiple submit buttons, you can change the validation
 group depending on which button is used to submit the form. For example,
 consider a form in a wizard that lets you advance to the next step or go back
@@ -1044,8 +1014,6 @@ to the ``form()`` or the ``form_start()`` helper:
 
         <!-- app/Resources/views/default/newAction.html.php -->
         <?php echo $view['form']->start($form, array(
-            // The path() method was introduced in Symfony 2.8. Prior to 2.8,
-            // you had to use generate().
             'action' => $view['router']->path('target_route'),
             'method' => 'GET',
         )) ?>
@@ -1981,4 +1949,3 @@ Learn more from the Cookbook
 .. _`form_div_layout.html.twig`: https://github.com/symfony/symfony/blob/master/src/Symfony/Bridge/Twig/Resources/views/Form/form_div_layout.html.twig
 .. _`Cross-site request forgery`: http://en.wikipedia.org/wiki/Cross-site_request_forgery
 .. _`view on GitHub`: https://github.com/symfony/symfony/tree/master/src/Symfony/Bundle/FrameworkBundle/Resources/views/Form
-.. _`2.8 UPGRADE Log`: https://github.com/symfony/symfony/blob/2.8/UPGRADE-2.8.md#form

book/from_flat_php_to_symfony2.rst

@@ -417,7 +417,7 @@ content:
 
     {
         "require": {
-            "symfony/symfony": "2.6.*"
+            "symfony/symfony": "3.0.*"
         },
         "autoload": {
             "files": ["model.php","controllers.php"]

book/http_cache.rst

@@ -1095,12 +1095,7 @@ matter), Symfony uses the standard ``render`` helper to configure ESI tags:
 
         <!-- ... or a URL -->
         <?php echo $view['actions']->render(
-            // The url() method was introduced in Symfony 2.8. Prior to 2.8,
-            // you had to use generate($name, $parameters, UrlGeneratorInterface::ABSOLUTE_URL)
-            $view['router']->url(
-                'latest_news',
-                array('maxPerPage' => 5),
-            ),
+            $view['router']->url('latest_news', array('maxPerPage' => 5)),
             array('strategy' => 'esi'),
         ) ?>
 

book/page_creation.rst

@@ -582,6 +582,6 @@ There's also a :doc:`Cookbook </cookbook/index>` *packed* with more advanced
 Have fun!
 
 .. _`Joyful Development with Symfony`: http://knpuniversity.com/screencast/symfony/first-page
-.. _`app/Resources/views/base.html.twig`: https://github.com/symfony/symfony-standard/blob/2.7/app/Resources/views/base.html.twig
+.. _`app/Resources/views/base.html.twig`: https://github.com/symfony/symfony-standard/blob/3.0/app/Resources/views/base.html.twig
 .. _`Composer`: https://getcomposer.org
 .. _`find open source bundles`: http://knpbundles.com

book/routing.rst

@@ -1543,10 +1543,6 @@ a template helper function:
             Read this blog post.
         </a>
 
-.. versionadded:: 2.8
-    The ``path()`` PHP templating helper was introduced in Symfony 2.8. Prior
-    to 2.8, you had to use the ``generate()`` helper method.
-
 .. index::
    single: Routing; Absolute URLs
 
@@ -1581,12 +1577,6 @@ URL) rather than the ``path()`` function (which generates a relative URL):
             Read this blog post.
         </a>
 
-.. versionadded:: 2.8
-    The ``url()`` PHP templating helper was introduced in Symfony 2.8. Prior
-    to 2.8, you had to use the ``generate()`` helper method with
-    ``Symfony\Component\Routing\Generator\UrlGeneratorInterface::ABSOLUTE_URL``
-    passed as the third argument.
-
 .. note::
 
     The host that's used when generating an absolute URL is automatically
@@ -1608,5 +1598,12 @@ Learn more from the Cookbook
 ----------------------------
 
 * :doc:`/cookbook/routing/scheme`
+* :doc:`/cookbook/routing/slash_in_parameter`
+* :doc:`/cookbook/routing/redirect_in_config`
+* :doc:`/cookbook/routing/method_parameters`
+* :doc:`/cookbook/routing/service_container_parameters`
+* :doc:`/cookbook/routing/custom_route_loader`
+* :doc:`/cookbook/routing/redirect_trailing_slash`
+* :doc:`/cookbook/routing/extra_information`
 
 .. _`FOSJsRoutingBundle`: https://github.com/FriendsOfSymfony/FOSJsRoutingBundle