Skip to content

Commit

Permalink
Remove duplicate and confusing info about testing error pages
Browse files Browse the repository at this point in the history
We added new information about using the ExceptionController to test the error pages but the old info was not deleted. In this way, the section was duplicated and offered information which seemed to be contradictory. I have removed the old info.
  • Loading branch information
Carlos Granados authored and xabbuh committed Oct 21, 2015
1 parent d83a2d8 commit 4007ba1
Showing 1 changed file with 3 additions and 11 deletions.
14 changes: 3 additions & 11 deletions cookbook/controller/error_pages.rst
Original file line number Diff line number Diff line change
Expand Up @@ -142,24 +142,16 @@ is undefined. The solution is to add the following check before using this funct
{# ... #}
{% endif %}
.. _testing-error-pages:

Testing Error Pages during Development
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

While you're in the development environment, Symfony shows the big *exception*
page instead of your shiny new customized error page. So, how can you see
what it looks like and debug it?

The recommended solution is to use a third-party bundle called `WebfactoryExceptionsBundle`_.
This bundle provides a special test controller that allows you to easily display
custom error pages for arbitrary HTTP status codes even when ``kernel.debug`` is
set to ``true``.

.. _testing-error-pages:

Testing Error Pages during Development
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The default ``ExceptionController`` also allows you to preview your
Fortunately, the default ``ExceptionController`` allows you to preview your
*error* pages during development.

.. versionadded:: 2.6
Expand Down

0 comments on commit 4007ba1

Please sign in to comment.