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
Thank you for providing the links to the Ckeditor 5 problem when using the gin theme that may occur after updating Backdrop to the 1.32.0 release, and the link to the new release of gin that...
Backdrop CMS 1.32.0 Upgrade Issues or Feedback
Here is a possibly related issue in the core issue queue: After upgrade from 1.31.1 to 1.32.0 update.php shows fatal errors and leaves site in maintenance mode https://github.com/...
Backdrop CMS 1.32.0 Upgrade Issues or Feedback
It sounds like a CSS/JS bug in the Layouts UI: when the "Add block" row is hidden with display:none, its help/description element isn’t being hidden together. 🔧 Things to try...
Add blocks filtering problem