Update: Dave Reid just added basic field token support to Token. Try the beta4 of Token (http://drupal.org/project/token) before Entity Tokens. I worked out what needed to happen a few weeks ago, and finally wrote it up. I didn’t realize there was an update the Token when I posted. Haha! Internet moves quick!

The lack of field tokens in Drupal 7 is a huge problem (See http://drupal.org/node/691078), but there is a good workaround: Entity Token in the Entity module (http://drupal.org/project/entity). Enable Entity and Entity Token, and the majority of your fields become available as tokens.

A problem youi’ll quickly run into, especially if the Node Reference module (http://drupal.org/project/references) is enabled, is that the Token Tree UI will become unwieldy. In my case, the Account Settings page (admin/config/people/accounts) becomes 42 megabytes. A temporary solution is my patch in: http://drupal.org/node/1058912#comment-4830326 which allows you to adjust the tree depth from 4 to 3 or 2, significantly reducing the amount of tokens.

Modules required:

Modules I am using Entity Token supplied Field Tokens with:

An example working Pathauto URL alias pattern: profile/[node:author:name]/measurements/series/[node:field-measurement-location]/[node:field-measurement-meter]/[node:field-measurement-device]/[node:title]


(Statically copied from previous site)

Dave Reid replied on August 18, 2011 - 11:59am

Of course this was written after we managed to commit the first part of field tokens to Token module itself. This could at least be amended to point people to the new 7.x-1.0-beta4 release.

Fair warning: the solutions used by Entity token will conflict with proper field tokens in Token module. The token names provided by Entity are never guaranteed to be the ‘final’ token names provided by Token module and could break.

brad replied on August 18, 2011 - 12:36pm

Good point. I’ve added an update about the beta4