Token chains like [node:reference_field_name:entity:entity_token] support only content entities as restricted by the code in token.tokens.inc:
if (isset($field_item->$property_name) && ($field_item->$property_name instanceof FieldableEntityInterface)) {
This doesn't allow to use (in chains) tokens defined for config entities such as domains. I suggest to ease this restriction, so that any entity reference can be used in chains.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | token-entity_reference-3194681-4.patch | 1.04 KB | b-prod |
| #2 | token-entity_reference-3194681-2.patch | 637 bytes | maximpodorov |
Comments
Comment #2
maximpodorov commentedComment #3
djdevinTested working.
Example, we have an enrollment entity that has an entity reference to credit awarded, which has an entity reference to a config entity of a credit type.
Patch allows this token to work
Course enrollment (Content) -> Credit awarded (Content) -> Credit type (Config)
[course_enrollment:course_credit_awarded:0:entity:type:0:entity]
Probably needs some tests.
Comment #4
b-prod commentedReroll for 1.17