Home/ Questions/Q 6548973
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T12:02:10+00:00

I have a problem with the error page 500 of symfony (apps/%app-name%/config/error/error.html.php). I had

  • 0

I have a problem with the error page 500 of symfony (apps/%app-name%/config/error/error.html.php).
I had to learn that symfony skip the standard way of page creation completely. I had to organize all the helpers myselve.

require_once dirname(__FILE__) . '/../../../../lib/vendor/symfony/lib/helper/HelperHelper.php';
use_helper('Tag', 'Asset', 'Url', 'I18N', 'Date', 'Partial');

But now I am missing the contents of the configuration. How can I manually trigger the autoloader mechanism, so that I get the information from view.yml and so on?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I don’t know if it’s smart to depend on the whole Symfony stack when you’re displaying an error.

    IMHO the error pages need to be designed as light-weight as possible, 99% static HTML, with only some php code to display a friendly error message.
    Because, what if something is wrong with your Symfony stack, then you can’t even present a decent error page to the user.

    The 500 error page is also a “hard fail” page, it is the most generic error handler which is only shown if no action tried to catch the exception.
    In the cases where you want to use the view and everything, I think it’s better to catch the exceptions right there in the action, and present better error pages (return sfView::ERROR) with information the user can act on.

    • 0