Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
This change record in Token module implies that we need to update the way that we create the token browser in Metatag module: [#2648394].
Comments
Comment #2
juampynr CreditAttribution: juampynr at Lullabot commentedHere is a patch that fixes it. You need the latest development release of token for this to work.
Comment #3
juampynr CreditAttribution: juampynr at Lullabot commentedPlease, slap me with a trout. Here is the patch.
Comment #4
juampynr CreditAttribution: juampynr at Lullabot commentedComment #5
BerdirNot directly related to this issue, but:
It's a problem that you use this in such a generic context with no way to customize it and then have to resort to token_types all. This is problematic for two reasons:
a) It will possibly display a huge amount of tokens, which will take longer to load and is more likely to crash on the server (memory) or even in the browser, until we re-design that UI.
b) It's also confusing to the user, because he might use tokens that are then not available.. e.g. node tokens on a term or the other way round.
Comment #7
DamienMcKenna@juampynr: Thanks. Committed.
@berdir: I've added a new issue for your observation: #2650848: Only show appropriate tokens in the token browser