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
Hi Jochen You could test https://github.com/backdrop-contrib/commerce_invoice_receipt which doesn't yet have a release, but may meet your needs when combined with other modules to generate...
Commerce modules
Setting up a multisite with multilingual support can definitely get a bit tricky with all those configurations. If you're looking for a way to keep things clean, I've found that using a quick...
Multisite for multilingual website
Start with basics: install modules for meta tags and XML sitemaps, set proper alt text on images, and keep URLs clean. Backdrop SEO is mostly about structure and content quality, not tricks.
How to Improve SEO Performance in Backdrop CMS