I'm not sure if that was ever supported as the default structure would've been loading templates from your view directory.

It have been using this long before 2.8 :)

That doesn't mean it's a supported notation though, I wasn't aware that this was possible in the first place. Supported notations are here: http://symfony.com/doc/current/book/templating.html#template-naming-and-locations

If this is intended to work, it should be fixed of course.

Namespaced path support was introduced in 2.2.

Unless support for this has been removed and I missed that along the way.

You could add your own twig namespace: http://symfony.com/doc/current/cookbook/templating/namespaced_paths.html

And why would I want to do that when it worked perfectly fine before?

This sounds more like a workaround for a bug then anything else...

I'm not saying you'd want to do that. I'm saying you could do that to get it to work in the newer version. If it's a bug, it can be fixed. If it was something that was possible but not intended to be, your solution will keep your system working. However, I recommend to stick to the documentation or best-practices regarding template locations.

I think this is the same as #17777

In that case, @brechtdewinne can you try if this fix works for you? #17894

Indeed, this should be fixed by #17894. @Jean85 if you could confirm your case is fixed it would be great, thanks!

The problem in my view is that people were relying on few unsupported cases, which obviously were not covered by tests.

@iltar Yes that fixes the issue!
CC: @Jean85 @jakzal