It would be nice to be able to follow the issues that affect the token code in core.

We have issues - #609090: Invalid call to node_get_types() in node.tokens.inc and #609118: node.tokens.inc: $node->body issues - but no easy way to track them.

We could use tags, but there are currently lots of tags about token that seem unrelated.

Comments

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

As the token code is now in Drupal core, it could be useful to have a component for it. It could be token system.

te-brian’s picture

te-brian commented

I just created a new issue with a patch for taxonomy.tokens.inc. There were some references to {taxonomy_node_term}.

http://drupal.org/node/610022#comment-2173548

+1 for a "token system" component

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

Why are we debating this in the webmasters' issue queue? Would not it better to move it in the project issue queue?

It could be that all the maintainers of Drupal are webmasters, but it is not true the opposite. Moving the report to the project queue would allow who is interested to see it.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

The project module supports arbitrary components. We need to decide on the term to use ("tokens" or "token system"?) and then get agreement from a fair number of people and then make the change at http://drupal.org/node/3060/edit/issues

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Active » Fixed

I added the component token system.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.