From f345092ba62fd5dc3b848872f6f2a3571e2a84f1 Mon Sep 17 00:00:00 2001 From: Carlos Granados Date: Tue, 20 Oct 2015 11:51:50 +0200 Subject: [PATCH] Remove duplicate and confusing info about testing error pages 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. --- cookbook/controller/error_pages.rst | 14 +++----------- 1 file changed, 3 insertions(+), 11 deletions(-) diff --git a/cookbook/controller/error_pages.rst b/cookbook/controller/error_pages.rst index 1b4bc784dff..217cd20bda4 100644 --- a/cookbook/controller/error_pages.rst +++ b/cookbook/controller/error_pages.rst @@ -142,6 +142,8 @@ is undefined. The solution is to add the following check before using this funct {# ... #} {% endif %} +.. _testing-error-pages: + Testing Error Pages during Development ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -149,17 +151,7 @@ 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