@@ -30,21 +30,21 @@ control you need:
30
30
information, see :ref: `kernel-kernel.exception `.
31
31
32
32
The default ``ExceptionController `` will either display an
33
- *exception * or *error * page, depending on the setting of the ``kernel
34
- .debug `` flag. While *exception * pages give you a lot of helpful
33
+ *exception * or *error * page, depending on the setting of the ``kernel.debug ``
34
+ flag. While *exception * pages give you a lot of helpful
35
35
information during development, *error * pages are meant to be
36
36
shown to the end-user.
37
37
38
- .. sidebar :: Testing error pages during development
38
+ .. sidebar :: Testing Error Pages during Development
39
39
40
- Setting ``kernel.debug `` to ``false `` in order to see your
41
- error pages during development is impractical as it also stops
40
+ You should not set ``kernel.debug `` to ``false `` in order to see your
41
+ error pages during development. This will also stop
42
42
Symfony2 from recompiling your twig templates, among other things.
43
43
44
44
The third-party `webfactory/exceptions-bundle `_ provides a special
45
45
test controller that allows you to display your custom error
46
- pages for arbitrary HTTP status codes even with `` kernel
47
- .debug `` set to ``true ``.
46
+ pages for arbitrary HTTP status codes even with
47
+ `` kernel .debug `` set to ``true ``.
48
48
49
49
All of the error templates live inside the TwigBundle. To override the
50
50
templates, simply rely on the standard method for overriding templates that
0 commit comments