- Issue created by @Anybody
- 🇬🇧United Kingdom scott_euser
So you are using the Flattened loader (essentially the one mimicking 1x branch to make upgrade easier)?
Probably easiest way to support the tokens related to that from 1x are to move token info and alter into methods within that loader. Both 1x and 2x have the full entity tokens but only 1x has the flattened tokens. So active loader can be checked in the token info and alter functions and if the methods exist, the extra tokens can be added. This would then discourage use of the flattened tokens for new installs at least (since the full entity ones are really much more in line with Drupal way of doing things).
- Status changed to Postponed: needs info
4 months ago 4:04am 5 June 2024 - 🇩🇪Germany Anybody Porta Westfalica
@scott_euser thank you. We decided to switch away from the module finally, so I can't provide further information as it doesn't affect us any more. Please decide to leave this open for other reports or simply close it. Thank you.
- Status changed to Closed: cannot reproduce
2 months ago 11:46am 24 July 2024 - 🇬🇧United Kingdom scott_euser
Probably this is fixed in #3067325: Provide the whole (rendered) entity as token → in any case.