Ryan Weaver, Symfony core team member and SymfonyCasts founder, needs our help

New in Symfony 2.6: Error page previews

October 23, 2014 · Published by Avatar of Javier Eguiluz Javier Eguiluz

Warning: This post is about an unsupported Symfony version. Some of this information may be out of date. Read the most recent Symfony Docs.

webfactory GmbH

Contributed by
webfactory GmbH
in #12096.

User Experience (UX) has become an essential part of web application development. One of the most important elements of UX is to provide comprehensible and helpful error pages in case things don't work as expected.

Developing and designing these error pages in previous Symfony versions was a bit involved because it required to trigger an exception with the exact HTTP code needed and you had to make the exception controller use the right template.

That's why Symfony 2.6 will include a new option to preview error pages. Specifically, TwigBundle now contains a routing file that you can import from your routing_dev.yml file:

1
2
3
4
# app/config/routing_dev.yml
_errors:
    resource: "@TwigBundle/Resources/config/routing/errors.xml"
    prefix:   /_error

Once these new routes are loaded, you can preview any error page using these special URLs:

http://localhost/app_dev.php/_error/{statusCode} http://localhost/app_dev.php/_error/{statusCode}.{format}

The statusCode corresponds to the HTTP Status Code of the error and the format option defaults to html and accepts any valid request format, such as json.

To learn more about customizing your error pages, read the revamped cookbook article about How to Customize Error Pages. Now it's time to test this feature and don't forget to leave a link to your beautiful error page in the comments of this article!

Note: this post was mostly written by Matthias Pigulla.

Published in #Living on the edge

Help the Symfony project!

As with any Open-Source project, contributing code or documentation is the most common way to help, but we also have a wide range of sponsoring opportunities.

Comments

Avatar of webfactory GmbH
webfactory GmbH said on Oct 23, 2014
In case you'd like to give this a try: There is still an open PR with a small fix for the case that you're using a custom exception controller: https://github.com/symfony/symfony/pull/12147
Avatar of Piotr Gołębiewski
Piotr Gołębiewski said on Oct 23, 2014
Very helpful when designing beautiful excpetion pages. Thanks.

"Sorry, it's broken.. but so pretty!" ;)
Avatar of Evan Owens
Evan Owens said on Oct 23, 2014
Great idea
Avatar of Chris Sedlmayr
Chris Sedlmayr said on Oct 23, 2014
This is great! We had a very hacky solution, glad to get rid of it!
Avatar of Loïc Vernet
Loïc Vernet Certified said on Oct 23, 2014
Useful indead, instead of throwing exceptions by hand, switch the debug flag... It was boring. Ty.
Avatar of Maks Rafalko
Maks Rafalko said on Oct 24, 2014
Nice
Avatar of Massimiliano Arione
Massimiliano Arione said on Dec 5, 2014
I just tried this with my brand new project, I get this:

Catchable Fatal Error: Argument 2 passed to Symfony\Bundle\TwigBundle\Controller\ExceptionController::showAction() must be an instance of Symfony\Component\HttpKernel\Exception\FlattenException, instance of Symfony\Component\Debug\Exception\FlattenException given
Avatar of Jules Pietri
Jules Pietri Certified said on Dec 9, 2014
@Massimiliano Arione, same here.

Seems to be a namespace problem.

You can change it in @TwigBundle/Controller/PreviewErrorController.php line 14, replace "Debug" by "HttpKernel".

Comments are closed.

To ensure that comments stay relevant, they are closed for old posts.