After updating to 8.4.4 heading fields return status report warning.
TOKENS OR TOKEN TYPES MISSING NAME PROPERTY
$info['tokens']['paragraph-field_heading']['size']
$info['tokens']['paragraph-field_heading']['text']
In my case the heading fields are used on a paragraph type.
| Comment | File | Size | Author |
|---|---|---|---|
| #14 | Screen Shot 2018-08-15 at 3.14.03 PM.png | 65.18 KB | jnycz |
| #10 | token-or-token-name-missing-2934662-10.patch | 1.33 KB | zero2one |
| #8 | heading.module.patch | 1.31 KB | sdmeyers |
Comments
Comment #2
jnycz commentedComment #3
zero2one commentedI added the missing heading field token information.
See commit on 8.x-1.x branch
Comment #4
zero2one commentedComment #6
seirerman commentedThe patch only works if I use the same name for my heading field.
Can you reopen this issue?
Comment #7
zero2one commentedComment #8
sdmeyers commentedHere's a patch that seems to solve the issue no matter what machine name you have for your field. At least it works for me... enjoy.
Comment #9
jnycz commentedPatch from #8 fixed the issue. Not seeing any problems now, thanks @sdmeyers!
Comment #10
zero2one commentedThank you for the fix.
I refactored the patch of so it has less nesting.
Comment #12
zero2one commentedFix is merged.
Comment #13
zero2one commentedComment #14
jnycz commentedAfter updating the module to 8.x-1.1 and removing sdmeyers patch the warning appears again.
Comment #15
zero2one commentedThank you for the catch (paragraphs !== paragraph).
Code is fixed in the new 8.x-1.2 release.
I added also token support when the heading field is used in other entity types then paragraphs.
See release notes.
Comment #16
zero2one commentedComment #18
mpark commentedHello, I have to reopen it, cause still the warning can see it. Everything updated (12/02/2018).