Closed (fixed)
Project:
Token
Version:
8.x-1.x-dev
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
28 Jul 2015 at 09:46 UTC
Updated:
10 Oct 2015 at 14:44 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
tstoecklerI had the same problem when testing the module browser at
/admin/config/people/accountsto put some tokens in the user emails.This fixed the problem.
Comment #2
berdirThere's a second problem now, the csrf access token fails. The reason is that it is now a placeholder and that doesn't bubble up because we call \Drupal::l() in a theme function (not sure if that part is related).
@dawehner told me to do this.
Comment #3
wim leersHrm… do we need a core issue to figure out a solution to this? Or is this sufficiently rare, that the solution in #2 is acceptable?
Comment #4
dave reidI know that calling l() will be a pattern we see quite often in contrib (or in site implementations). So it would be better to have something that everyone could use.
Comment #6
dave reidCommitted #2 to 8.x-1.x in the meantime. But leaving as needs review in the mean time, maybe pending a core DX issue being open?
Comment #7
berdirThanks!
Opened #2575519: Twig template variables containing result of Drupal::url() and Drupal:l:() don't bubble up their cacheability and attachment metadata (e.g. token placeholder), closing this for now.