-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
Symfony 3.2-RC1 errors in the Symfony Profiler #20556
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I've just upgraded an internal Symfony app to 3.2-rc1 and I'm getting the same errors. |
Status: Reviewed I reproduced the bug on symfony demo upgrading |
I have created PR twigphp/Twig#2269 that fixes this issue. But maybe we should revert the commit I've mentioned above until the issue is fixed in Twig. |
I don't think we need reverting this, as Symfony 2.7 does not have an impacted release yet. We just need to release Twig 1.28.1 before the next Symfony 2.7 patch release (which is under our control as @fabpot is doing releases on both sides) |
…s the local blocks array (derrabus, fabpot) This PR was merged into the 1.x branch. Discussion ---------- Bugfix: When rendering blocks of other templates, don't pass the local blocks array This PR fixes symfony/symfony#20556. When referring to a block of another template from within a template that also has a block with the same name, Twig renders the wrong block. Commits ------- 8c090a7 added tests for block() when using a template argument a5526f3 fixed block() is defined call when using a template argument c04d077 Bugfix: When rendering blocks of other templates, don't pass the local blocks array.
In symfony/demo#403 I've just updated the Symfony Demo app to Symfony 3.2-RC1 and Twig 1.28. I have a lot of issues in the Symfony profiler:
The text was updated successfully, but these errors were encountered: