In the comment is suggested that:

1. terminology clarification
2. crossreferences between D6 and D7 (equivalence table maybe) to support migration projects
3. illustrative examples

Posted by GrahamShepherd on August 25, 2011 at 7:35am new

The descriptions in this list (and the lists provided in D7 admin pages) should be distinct and comprehensive to represent the distinctiveness of each token. Just one example of many: the following tokens all have the same name and the same description and appear in the same lists in pathauto and other modules.
[node:menu-link:parent:parent:title]
[node:menu-link:parent:title]
[node:menu-link:parent:root:title]
[node:menu-link:root:parent:title]
[node:menu-link:root:title]
[node:menu-link:title]

They obviously give different results. What are they? Some examples would help.

Tokens and token names have changed dramatically from D6 to D7. The terminology needs definition. For example, what is the difference between Title and Name, and Parent and Root?

Does every admin trying to upgrade from D6 to D7 have to spend hours of trial and error finding the right token for a particular requirement? This actually a crucial issue in upgrading. It is essential for any site that its paths don't change with an upgrade. If you have thousands of nodes and aliases the consequences of a mistake can very very great.

Apologies to those who have put the hard work into this but it might be useful if you sense the frustration.

Comments

batigolix’s picture

Assigned: Unassigned » batigolix

gonna take a stab at this

batigolix’s picture

i dont know enough of token to fix this issue.

should we move this issue to the token project?

batigolix’s picture

Assigned: batigolix » Unassigned

unassign