I'm using the token list shown in EVA (with this patch #1233158: Provide list of available tokens) and only some of the taxonomy term ref fields are showing expanded tokens.

In other words, for some fields I can't get the term tid.

Comments

fago’s picture

fago
Primary language German
Location Vienna
commented
Status: Active » Postponed (maintainer needs more info)

Are you using the latest entity api? Are the expanded tokens working although they are not listed?
What kind of fields work and what kinds not? And lastly, is the problem EVA specific or does it generally apply to tokens, e.g. does it work with pathauto?

reujwils’s picture

reujwils commented

I too am experiencing a similar problem. For me, I'm on the latest version of entity api and it shows up when I'm looking at available substitutions either in pathauto or in the help screen for token. In my situation, I expand Node through the UI, and I see all the tokens available for all of my fields. In my case, I have multiple term reference fields, however it is only showing the chained tokens for all fields added to my taxonomies on the first term reference field only.

I'm not sure what the root cause in, but I will try and dig in the code when I have some time, unfortunately, I have a release coming so time is short. For the OP, I added my own token definition in my module to get the value I need in the meantime if that helps you.

Golem07’s picture

Golem07 commented

I am experiencing the very same problem (after a recent upgrade from D6.22 to D7.10). Some fields do show expanded tokens, some are not (without any noticable difference in settings).

fietserwin’s picture

fietserwin
Location Le Mont-Dore
commented

Could this comment be the explanation: #1339708-4: 'Undefined index: taxonomy_term' with taxonomy reference field token?

Or, for this situation: is the noticeable difference in settingsthe fact that 1 token is for a field that is not displayed otherwise, while the other token is displayed otherwise?