Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[FrameworkBundle][TwigBridge] Fix BC break from strong dependency on CSRF token storage#27454
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Merged
Uh oh!
There was an error while loading.Please reload this page.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
nicolas-grekas approved these changesMay 31, 2018
fabpot approved these changesMay 31, 2018
Member
fabpot commentedMay 31, 2018
Thank you@tgalopin. |
fabpot added a commit that referenced this pull requestMay 31, 2018
…endency on CSRF token storage (tgalopin)This PR was merged into the 4.1 branch.Discussion----------[FrameworkBundle][TwigBridge] Fix BC break from strong dependency on CSRF token storage| Q | A| ------------- | ---| Branch? | 4.1| Bug fix? | yes| New feature? | no| BC breaks? | no| Deprecations? | no| Tests pass? | yes| Fixed tickets | -| License | MIT| Doc PR | -The PR#25197 introduced the `csrf_token` function in Twig. This extension relies on `CsrfTokenManagerInterface`, which itself relies on the session. In some contexts such as when sessions are stored in Redis and we try to warmup the cache in CLI without Redis available, this makes the process fails.This PR fixes this by using a Twig runtime instead of a direct extension to avoid a strong dependency on `CsrfTokenManagerInterface`.Commits-------68994a6 [FrameworkBundle][TwigBridge] Fix BC break from strong dependency on CSRF token storage
Merged
nicolas-grekas added a commit that referenced this pull requestJul 4, 2018
…idge version (xabbuh)This PR was merged into the 4.1 branch.Discussion----------[FrameworkBundle] add conflict for non-compatible TwigBridge version| Q | A| ------------- | ---| Branch? | 4.1| Bug fix? | yes| New feature? | no| BC breaks? | no| Deprecations? | no| Tests pass? | yes| Fixed tickets |#27713| License | MIT| Doc PR |The argument was dropped in#27454.Commits-------251e684 add conflict for non-compatible TwigBridge version
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The PR#25197 introduced the
csrf_tokenfunction in Twig. This extension relies onCsrfTokenManagerInterface, which itself relies on the session. In some contexts such as when sessions are stored in Redis and we try to warmup the cache in CLI without Redis available, this makes the process fails.This PR fixes this by using a Twig runtime instead of a direct extension to avoid a strong dependency on
CsrfTokenManagerInterface.