Hello.
There is an annoying problem.
So, I can use common tokens such as [node:title] without any problen, but I create some custom field (i.e. named field_city), then attach it to the node and select it from available tokens list for node during the meta tags composing. Well my configuration saved propertly on database.
For example, I have description field such as "[node:title], City: [node:field_city]"
But as a result I get on html source for node than have title "Some My Node Title" and field_city "Moscow":
<meta name="description" content="Some My Node Title, City: " />
So, you can see, it is blank.
I use modules Display Suite (Metatag patched for compat), and Domain Access, if it may be important or helpful.
Comments
Comment #1
mattukplym commentedI too have this issue but they used to work!
It appears that the tokens for many (if not all) of my custom fields have changed from having dashes to underscores, and using the underscore values renders no output.
Comment #2
mattukplym commentedFigured this out...
The data that you want to use needs to be displayed on the page (via the CONTENT TYPE display).
It used to work without having to do this but it seems to be linked to a recent core update I made.
Comment #3
Shaltay commentedWhat do you mean?
This data is displayed on the page itself.
But I cant see it on meta description.
Comment #4
damienmckennaThis should work correctly using the latest codebase & latest version of the Token module, if it's still not working please re-open the issue. Thanks.
Comment #5
damienmckennaLast night saw the release of 7.x-1.0-beta1, so I'm closing all these "fixed" issues in the interest of tidying up the issue queue. Thank you all for your help getting us to this point!
Comment #5.0
damienmckennaadded
tags