By the looks of it, since this TemplateNameParser just converts @SyliusShop/template.html.twig notation to bundle notation, which Symfony does by default, this parser can just be removed, right?

@pamil Can you shed some more light on this?

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions.

@pamil Any news on this? Can this be fixed for 1.1?

@emodric sorry to keep you waiting! At the time I've written ThemeBundle I think the paths were not handled like this, so it looks like a bug caused by Twig changes in the meantime. I'd love to spend some time on it, but I'm quite limited on this matter, so I'd really appreciate if you or someone else could help with this issue. I would be happy to answer all the questions, you can also catch me on Slack :)

As for releases, we can fix it for both 1.0.x and 1.1.x branch.

From my very limited investigation, I think that just removing Sylius\Bundle\ThemeBundle\Templating\TemplateNameParser altogether might be a way to go, since its functionality is already included in Symfony, by default. However, I don't know enough about Sylius as a whole to say with certainty that removing it would be a valid fix.

If community has anything to add, I'll gladly listen :)

For a possible workaround (basically just disabling SyliusThemeBundle if you're not using it), see #7491 (comment) see #7491 (comment)

#9804 should fix this one.