I'd prefer a real sentence likeUnable to find template "..." in any of these locations: ...

@Tobion I prefer a real sentence too. I did this to use the same error message as the original FilesystemLoader of Twig library (seehttps://github.com/twigphp/Twig/blob/1.x/lib/Twig/Loader/Filesystem.php#L209). Anyway, if others agree with you, I'll do the change. Thanks!

@javiereguiluz is it possible to use the Alias of bundles instead of the full path? I'm mentioning this because of my directory structure. If I were to look into a bundle it would become pretty deep:

• /home/ivanderberg/projects/my_project/www/app/Resources/views/
• /home/ivanderberg/projects/my_project/www/src/Hostnet/Bundle/AppBundle/Resources/views/
• /home/ivanderberg/projects/my_project/www/vendor/hostnet/some-bundle/src/Resources/views/

And this is with PSR-4 with only 1 vendor bundle. My suggestion would be to make an exception to /app and alias the rest with the bundle name:

• /app/Resources/views/
• @AppBundle/Resources/views/
• @SomeBundle/Resources/views/

It's quite clear in which application/project you are working with the given error so that information is redundant. Given you hardly ever use vendor templates, the last case would hardly ever be useful but cause a lot of clutter. The AppBundle shouldn't contain templates according to the best-practices but I think enough people still use multiple bundles in their application and know how to find it with the alias.

In88b913b I'm trying to solve the problem just by reusing the error message that Twig provides us. The result is the same:

@iltar I prefer to not show the namespaces. Although is more verbose, is easier to understand which real paths Symfony is looking into.

Now I'll try to add some test.

Now that the patch is much simpler, I don't get why we would need to change this. Basically, you are hiding one exception that might occur and the exception you put front and center is anyway available in the linked exceptions. So, I don't get it. Are you saying that people don't look at linked exceptions?

Let me explain why I think we should change this:

If your application uses the modern template syntax and put this in your controller:

return$this->render('wrong_template.html.twig');

Symfony will show you this message:

If we apply this patch, this other message is displayed:

If your application uses the old template syntax and put this in your controller:

return$this->render('AppBundle:Default:wrong_template.html.twig');

Symfony will show you this message:

(the four chained exceptions don't provide any information)

If we apply this patch, this other message is displayed:

And if your application uses the namespace template syntax and put this in your controller:

return$this->render('@App/Default/wrong_template.html.twig');

Symfony will show you this message:

(everything is very misleading! The second exception says that AppBundle doesn't exist!!!)

If we apply this patch, this other message is displayed:

So, it seems that the new error messages are more useful and always consistent, regardless of the template syntax used. But let's ping@nicolas-grekas to check if he sees something wrong in this proposed exception change.

Thank you@javiereguiluz.

Thanks@javiereguiluz for the very detailed analysis. It looks like it is indeed always better to use the new code.