Hello,

I am using metatags context and have a situation in which when a user selects a destination from the Travel menu such as Travel/Philippines, it takes the destination, in this case, philippines and passes it in the url as an arguement which then that gets passed a custom panels landing page for travel and then to the views for the travel page so that data on page is reflective of the destination selected from the menu. In the context that I created for metatags, I would like to place one of the following tokens ( [menu-link:title] or [url:args:first] or [url:arg1] )in the metatag description field so that based on the travel destination selected from the menu, certain parts of the description will update with the token/arguement selected from the menu so that we will have unique descriptions. Can someone tell me if this is possible and whether or not metatags context supports tokens in the description field?

I've tried added each of the tokens listed above to the description field and I get an error stating that they are invalid tokens for that field.

Please advise.

Thanks

Comments

damienmckenna’s picture

I believe general tokens should work, just entity tokens do not (yet).

oystercrackher’s picture

Damien,

From my limited knowledge, I believe all tokens listed above are general tokens and not entity tokens. Can you confirm this? And if so, do you have an idea on why they are coming up as invalid in the description field?

Please advise.

Thanks so much!
Melissa

oystercrackher’s picture

Any idea?

damienmckenna’s picture

Component: Code » Context
bago’s picture

So [node:*] tokens are not currently supported even if the token browser list them?

Is there a specific issue for "entity tokens not yet supported in context metatag reaction" that we can "follow" to know when this will be implemented?

I've just "followed" this one and these two:
#1838554: Either enable entity tokens in Context, or disable those tokens in Context
#1980938: Node tokens invalid in context "node type"

damienmckenna’s picture

Status: Active » Closed (duplicate)

This is the same issue as #1838554: Either enable entity tokens in Context, or disable those tokens in Context, so lets focus all efforts there.

damienmckenna’s picture

Issue summary: View changes

Added my actions for tokens for desc field