- Issue created by @johanvdr
- 🇺🇸United States DamienMcKenna NH, USA
Thank you for reporting the bug. I wonder if 🐛 Generate tokens values method does not take into account the entity language Needs work might solve the problem for you?
There is an issue with token inheritance in multilingual content when using the Metatag module. Specifically:
Default tokens (e.g. [node:title], [node:summary]) are set for ie. title and description fields during module installation for the default node (Content) metatag type.
These default tokens are not properly inherited by content type metatags in certain scenarios:
The issue manifests as the metatag fields reverting to the default tokens instead of using the expected, content-specific values.
Currently, the only workaround is to explicitly set the token or value (not defaults) for title and description in the Content type metatag settings.
By default, Drupal installs with [node:title] and [node:summary] tokens set for the default node (Content) metatag type.
When you replace these with a custom token (e.g., [node:custom:description] for the description), the custom token may not always be inherited by your node type (Content) metatag type. Instead, it may default back to [node:summary].
This issue is particularly noticeable on translated nodes.
If you manually set [node:custom:description] on the node type (Content) metatag type, it does work. However, this is not the desired behavior, as it bypasses proper inheritance.
The core problem is that token inheritance is not functioning correctly in this scenario, especially for translated content.
Active
2.0
Code
Thank you for reporting the bug. I wonder if 🐛 Generate tokens values method does not take into account the entity language Needs work might solve the problem for you?