Skip to content

Commit c66649d

Browse files
mpdudeweaverryan
authored andcommitted
Update error_pages.rst
1 parent 2be0de9 commit c66649d

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

cookbook/controller/error_pages.rst

+7-7
Original file line numberDiff line numberDiff line change
@@ -30,21 +30,21 @@ control you need:
3030
information, see :ref:`kernel-kernel.exception`.
3131

3232
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
3535
information during development, *error* pages are meant to be
3636
shown to the end-user.
3737

38-
.. sidebar:: Testing error pages during development
38+
.. sidebar:: Testing Error Pages during Development
3939

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
4242
Symfony2 from recompiling your twig templates, among other things.
4343

4444
The third-party `webfactory/exceptions-bundle`_ provides a special
4545
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``.
4848

4949
All of the error templates live inside the TwigBundle. To override the
5050
templates, simply rely on the standard method for overriding templates that

0 commit comments

Comments
 (0)