The Entity Token submodule for Drupal 7 provides support for chained tokens, so they can be used with entities referenced by fields. However, Backdrop's implementation of entity_token is very simple and doesn't include that, only chained url
and original
tokens are included.
This whole feature has been already requested in https://github.com/backdrop/backdrop-issues/issues/1440. However, that doesn't seem a straight-foward implementation. It's relying a lot on Drupal 7 Entity functions, such as entity wrappers and other utilities Backdrop doesn't have, or use the same way.
My approach here would be to start providing something simpler and more widely used, a taxonomy term reference field chained token.
For example, we can use the parents path in an alias pattern [node:_field_taxonomy_term_:parents:join-path]
. We can provide this from the Field module.
Recent comments
I understand that this is not in the subject, but using a separate field (for <iframe> or file upload, doesn't matter) you get an advantage in displaying content. You can create blocks and...
Best way to embed media with CKEditor
I got confused by this too so I wanted to clarify the last comment here: You need to enable the input filter called: "Convert image captions to figure and figcaption elements" at the...
Image Captions
Hi I added the 2 additional settings in settings.php, did a restart - and the error disappeared! Thanks for the support! (but the issues with the conversion still remain .....
Problem with utf8mb4 Format when importing database