Merge branch '3.4'

* 3.4:
  parameter name typo
  [#8603] Rewording
  [BrowserKit] Updated Project URI of Goutte
  [#8495] Minor tweaks
  Update index.rst
  Update redirection_map
  Delete progresshelper.rst
  Minor reword in autowiring introduction
  Changed the title of a Doctrine article to avoid confusion
  Reworded the introduction of event listeners article
  Little typo error
  Update flex.rst
  Asset Component and absolute paths
  Grouped assets example
  Minor reword
  Mentioned the new case-sensitivity of container parameters
  Document disabling the usage of globally defined form themes

Author: weaverryan

_build/redirection_map

@@ -290,6 +290,7 @@
 /components/config/introduction /components/config
 /components/config/index /components/config
 /components/console/helpers/tablehelper /components/console/helpers/table
+/components/console/helpers/progresshelper /components/console/helpers/progressbar
 /components/console/introduction /components/console
 /components/console/index /components/console
 /components/debug/class_loader /components/debug

components/asset.rst

@@ -63,8 +63,13 @@ any versioning::
 
     $package = new Package(new EmptyVersionStrategy());
 
+    // Absolute path
     echo $package->getUrl('/image.png');
     // result: /image.png
+    
+    // Relative path
+    echo $package->getUrl('image.png');
+    // result: image.png
 
 Packages implement :class:`Symfony\\Component\\Asset\\PackageInterface`,
 which defines the following two methods:
@@ -105,8 +110,13 @@ suffix to any asset path::
 
     $package = new Package(new StaticVersionStrategy('v1'));
 
+    // Absolute path
     echo $package->getUrl('/image.png');
     // result: /image.png?v1
+    
+    // Relative path
+    echo $package->getUrl('image.png');
+    // result: image.png?v1
 
 In case you want to modify the version format, pass a sprintf-compatible format
 string as the second argument of the ``StaticVersionStrategy`` constructor::
@@ -122,6 +132,9 @@ string as the second argument of the ``StaticVersionStrategy`` constructor::
 
     echo $package->getUrl('/image.png');
     // result: /v1/image.png
+    
+    echo $package->getUrl('image.png');
+    // result: v1/image.png
 
 Custom Version Strategies
 .........................
@@ -168,8 +181,12 @@ that path over and over again::
 
     $package = new PathPackage('/static/images', new StaticVersionStrategy('v1'));
 
-    echo $package->getUrl('/logo.png');
+    echo $package->getUrl('logo.png');
     // result: /static/images/logo.png?v1
+    
+    // Base path is ignored when using absolute paths
+    echo $package->getUrl('/logo.png');
+    // result: /logo.png?v1
 
 Request Context Aware Assets
 ............................

components/browser_kit.rst

@@ -233,4 +233,4 @@ Learn more
 * :doc:`/components/dom_crawler`
 
 .. _`Packagist`: https://packagist.org/packages/symfony/browser-kit
-.. _`Goutte`: https://github.com/fabpot/Goutte
+.. _`Goutte`: https://github.com/FriendsOfPHP/Goutte

components/console/helpers/index.rst

@@ -11,7 +11,6 @@ The Console Helpers
     formatterhelper
     processhelper
     progressbar
-    progresshelper
     questionhelper
     table
     debug_formatter

components/console/helpers/progresshelper.rst

@@ -2,9 +2,10 @@
    single: Doctrine; Event listeners and subscribers
 
 .. _doctrine-event-config:
+.. _how-to-register-event-listeners-and-subscribers:
 
-How to Register Event Listeners and Subscribers
-===============================================
+Doctrine Event Listeners and Subscribers
+========================================
 
 Doctrine packages have a rich event system that fires events when almost anything
 happens inside the system. For you, this means that you can create arbitrary
@@ -188,15 +189,15 @@ For a full reference, see chapter `The Event System`_ in the Doctrine documentat
 Lazy loading for Event Listeners
 --------------------------------
 
-One subtle difference between listeners and subscribers is that Symfony can load 
+One subtle difference between listeners and subscribers is that Symfony can load
 entity listeners lazily. This means that your listener class will only be fetched
 from the service container (and thus be instantiated) once the event it is linked
 to actually fires.
 
-Lazy loading might give you a slight performance improvement when your listener 
-runs for events that rarely fire. Also, it can help you when you run into 
+Lazy loading might give you a slight performance improvement when your listener
+runs for events that rarely fire. Also, it can help you when you run into
 *circular dependency issues* that may occur when your listener service in turn
-depends on the DBAL connection. 
+depends on the DBAL connection.
 
 To mark a listener service as lazily loaded, just add the ``lazy`` attribute
 to the tag like so:

doctrine/event_listeners_subscribers.rst

@@ -9,10 +9,10 @@ During the execution of a Symfony application, lots of event notifications are
 triggered. Your application can listen to these notifications and respond to
 them by executing any piece of code.
 
-Internal events provided by Symfony itself are defined in the
-:class:`Symfony\\Component\\HttpKernel\\KernelEvents` class. Third-party bundles
-and libraries also trigger lots of events and your own application can trigger
-:doc:`custom events </components/event_dispatcher>`.
+Symfony triggers several :doc:`events related to the kernel </reference/events>`
+while processing the HTTP Request. Third-party bundles may also dispatch events, and
+you can even dispatch :doc:`custom events </components/event_dispatcher>` from your
+own code.
 
 All the examples shown in this article use the same ``KernelEvents::EXCEPTION``
 event for consistency purposes. In your own application, you can use any event

event_dispatcher.rst

@@ -343,6 +343,37 @@ name of all the templates as an array using the ``with`` keyword:
 The templates can also be located in different bundles, use the Twig namespaced
 path to reference these templates, e.g. ``@AcmeFormExtra/form/fields.html.twig``.
 
+Disabling usage of globally defined themes
+..........................................
+
+Sometimes you may want to disable the use of the globally defined form themes in order
+to have more control over rendering of a form. You might want this, for example,
+when creating an admin interface for a bundle which can be installed on a wide range
+of Symfony apps (and so you can't control what themes are defined globally).
+
+You can do this by including the ``only`` keyword after the list form themes:
+
+.. code-block:: html+twig
+
+    {% form_theme form with ['common.html.twig', 'form/fields.html.twig'] only %}
+
+    {# ... #}
+
+.. caution::
+
+    When using the ``only`` keyword, none of Symfony's built-in form themes
+    (``form_div_layout.html.twig``, etc.) will be applied. In order to render
+    your forms correctly, you need to either provide a fully-featured form theme
+    yourself, or extend one of the built-in form themes with Twig's ``use``
+    keyword instead of ``extends`` to re-use the original theme contents.
+
+    .. code-block:: html+twig
+
+        {# app/Resources/views/common.html.twig #}
+        {% use "form_div_layout.html.twig" %}
+
+        {# ... #}
+
 Child Forms
 ...........
 

form/form_customization.rst

@@ -34,7 +34,7 @@ several ways.
 Changing the default Page
 ~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Define the ``default_security_target`` option to change the page where the user
+Define the ``default_target_path`` option to change the page where the user
 is redirected to if no previous page was stored in the session. The value can be
 a relative/absolute URL or a Symfony route name:
 

security/form_login.rst

@@ -508,7 +508,7 @@ and add the following logic::
 
     use Symfony\Component\Security\Csrf\CsrfTokenManagerInterface;
     use Symfony\Component\Security\Csrf\CsrfToken;
-    use Symfony\Component\Security\Core\Exception\InvalidCsrfTokenExceptionl
+    use Symfony\Component\Security\Core\Exception\InvalidCsrfTokenException;
 
     class ExampleFormAuthenticator extends AbstractFormLoginAuthenticator
     {

security/guard_authentication.rst

@@ -4,11 +4,11 @@
 Defining Services Dependencies Automatically (Autowiring)
 =========================================================
 
-Autowiring allows you to manage services in the container with minimal configuration.
-It reads the type-hints on your constructor (or other methods) and automatically
-passes you the correct services. Symfony's autowiring is designed to be predictable:
-if it is not absolutely clear which dependency should be passed, you'll see an
-actionable exception.
+Autowiring allows you to manage services in the container with minimal
+configuration. It reads the type-hints on your constructor (or other methods)
+and automatically passes the correct services to each method. Symfony's
+autowiring is designed to be predictable: if it is not absolutely clear which
+dependency should be passed, you'll see an actionable exception.
 
 .. tip::
 

service_container/autowiring.rst

@@ -170,6 +170,11 @@ accessor methods for parameters::
     To learn more about compiling the container see
     :doc:`/components/dependency_injection/compilation`.
 
+.. versionadded:: 3.4
+    Container parameters are case sensitive starting from Symfony 3.4. In
+    previous Symfony versions, parameters were case insensitive, meaning that
+    ``mailer.transport`` and ``Mailer.Transport`` were considered the same parameter.
+
 .. _component-di-parameters-array:
 
 Array Parameters

service_container/parameters.rst

@@ -151,7 +151,7 @@ following directory structure, which is the same used by default in Symfony 4:
     └── vendor/
 
 This means that installing the ``symfony/flex`` dependency in your application
-is not enough. You must also upgrade the directory structure to the one showed
+is not enough. You must also upgrade the directory structure to the one shown
 above. There's no automatic tool to make this upgrade, so you must follow these
 manual steps: