Nested entities are a charm of drupal...
field collection, paragraphs and others...
all face the same issue providing, integrating, improving token support... providing token support for fields and values on those entities is surely a matter of those projects.
But... all those projects still face the issue of providing means to get to fields and values on the host entity...
With paragraphs inside field collections or the other way around and the multiple levels or even a multilevel mix... add entity reference and it becomes almost unmanageable (said a non-programmer^^).
Expanding current-page token tree to be another entry-point to the node token tree would solve the host entity token issue for all nested entities... drupal core would become far more usable and compatible with the general idea of nested entities...
Current situation all projects providing nest-able entities struggle to integrate with drupal core token system... several issue cues trying to fix the same problem bottom up... in addition there are multiple other issues for file, image, and all sorts of other fields dependent on the maintainers willingness to provide, improve etc token support just to have an easy way to get to "natural"values like nid, author uid, and not to mention field values.
Expanding current-page token tree to become a mother of the other trees would "explode" the amount of tokens since every incorporate tree would add it's total amount of tokens... memory and loading times of token browser??? well every nest able entity adds their own tokens... do that for several projects and it is even worse^^
How about making it optional? small ui with check boxes "enable node tokens from current-page" "enable user tokens from current-page"and so on...
Current-page obviously got the node nid, and path aliased and raw... so it seems to be a simple mapping thing... few lines of code to get rid of several issues in several projects...
I am not a programmer... means I need to make due with I am provided with (exept the unavoidable small hacks...) but there is a virtue in this position... trying as hard as possible to reuse existing stuff rather then reinventing it...
Just a well meant idea to make core support the usability of a great number of projects rather then having several projects struggling to live up to drupals demands ;)
well again, not a programmer can't help with implementation (and honestly, got all i need.. for the moment^^) but it seems the sensible thing to do.
Closed: outdated
7.0 ⚰️
token system
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Given that Drupal 7 has now reached End Of Life → , this issue should be closed.
Please upgrade to a supported version and feel free to reopen the issue on the new version if applicable.
There's actually been some work done on this on the D8+ front. Take a look at issue 919760 ✨ Add a [current-page:object:?] dynamic token Needs work and the contrib module Current Page Entity Tokens → .