Replacement tokens from contextual filters are showing, but the fields used in the view aren't. You can still use them, but I think it should be clear to an user that this is the case. See screenshot for details.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | 2780583-7.patch | 2.38 KB | lendude |
| #7 | 2780583-7-TEST_ONLY.patch | 1.68 KB | lendude |
| #5 | 2780583-5.drupal.views-area-tokens-list.patch | 717 bytes | joachim |
| Schermafbeelding 2016-08-08 om 13.36.22.png | 119.98 KB | nitebreed |
Comments
Comment #2
neutromancer commentedI have the same issue, except I can't use the tokens that aren't shown.
This also happens when editing the view Title.
If I use the token before adding the Contextual Filter, it works even after I add it.
If I edit the Title, or Header and save, they stop working (displaying {{ title }} instead, for example), and I have to temporarily remove the contextual filter if I want to add these tokens again.
Comment #3
neutromancer commentedComment #4
joachim commentedThis is because the code to make the list of tokens is arranging them into groups, but then clobbering each group:
$form['tokens']['tokens'] is getting set each time, so earlier $type lists (where $type is fields, then arguments) get clobbered.
Patch coming.
Comment #5
joachim commentedHere's a patch.
This affects all area handlers that use TokenizeAreaPluginBase, so the unfiltered one too.
Comment #6
lendudeFix looks great, but this still needs tests.
Comment #7
lendudeTest and fix.
Bug fix, so this can go against 8.2.x
Comment #9
dawehnerThe fix looks perfect for me!
I like that we don't use node but rather the test entity type.
Its kinda funny how bad this API is :)
Comment #12
catchCommitted/pushed to 8.3.x and cherry-picked to 8.2.x. Thanks!