[term], [event-dd] & [event-mm] do not translate to their respective values, and presumably nearly all the other tokens.

Even if the token module is installed then the resolve to blank
e.g. "[term]; [event-dd]-[event-mm]" becomes -> "; -"

Other threads suggest that it can only use data from the "Token" module that already exists i.e. it can't use values that are being created at the same time. Unfortunately that includes most of the available tokens and would defeat the point of the module, surely that can't be true?

If it is true then is the wrong hook is being used? Could changing when most of this modules logic is run fix this i.e. after the node is created, like with the notify/action facilities in Drupal 6.

P.S. Thanks for creating the module, the feedback is meant as constructive, honest 8¬)

Comments

John Bryan’s picture

John Bryan commented

Correction:

[term], [eventdd] & [eventmm] do not translate to their respective values, and presumably nearly all the other tokens.

Even if the token module is installed then the resolve to blank or "01" values
e.g. "[term]; [event-dd]-[event-mm]" becomes -> "; 01-01"

PHP failed:

I tried using PHP as suggested elsewhere bu that failed. I know there is a report of PHP not working on the 6.x versions of this module.

Partial work around:

Using [term-raw] does work.
Unfortunately there is no raw version of the event date fields

John Bryan’s picture

John Bryan commented
Title: Tokens do not work » Automatic Nodetitles: Tokens do not work
aren cambre’s picture

aren cambre commented

My limited understanding of how things works suggests that Token could be at fault. Are you on the latest version of Token?

fago’s picture

fago
Primary language German
Location Vienna
commented
Status: Active » Closed (works as designed)

you can only use tokens of available data - furthermore during node creation there might be problems with some tokens that don't work the the node format during creation - this depends on the specific token that is used.