@@ -177,10 +177,9 @@ environment by using this code and changing the environment string.
177177 not the application should run in "debug mode". Regardless of the environment,
178178 a Symfony2 application can be run with debug mode set to ``true `` or
179179 ``false ``. This affects many things in the application, such as whether
180- or not errors should be displayed or if cache files are dynamically rebuilt
181- on each request. Though not a requirement, debug mode is generally set
182- to ``true `` for the ``dev `` and ``test `` environments and ``false `` for
183- the ``prod `` environment.
180+ or not the cache files are dynamically rebuilt on each request. Though not
181+ a requirement, debug mode is generally set to ``true `` for the ``dev `` and
182+ ``test `` environments and ``false `` for the ``prod `` environment.
184183
185184 Internally, the value of the debug mode becomes the ``kernel.debug ``
186185 parameter used inside the :doc: `service container </book/service_container >`.
@@ -206,12 +205,15 @@ environment by using this code and changing the environment string.
206205 $container->loadFromExtension('doctrine', array(
207206 'dbal' => array(
208207 'logging' => '%kernel.debug%',
209-
210208 // ...
211209 ),
212210 // ...
213211 ));
214212
213+ As of Symfony 2.3, showing errors or not no longer depends on the debug
214+ mode. You'll need to enable that in your front controller by calling
215+ :method: `Symfony\\ Component\\ Debug\\ Debug::enable `.
216+
215217.. index ::
216218 single: Environments; Creating a new environment
217219
0 commit comments