Token expansion: [nid] and other node information

I was told that node data cannot be used as this stuff also happens when the node is not known or does not yet exist. Or something like that... heard that at a time when I didn't know much about Token, it would be neat if someone could verify or deny if this is doable (from a coding point of view) with CCK file uploads. Perhaps I'll find out by myself. I think it might work, but then again dopry should have known why he did it that way... right?

I try to only use fixed data for tokens... using transient data is a recipe for problems, but static paths are stores in the db... I'm not going to do this for now though until I can spend time making sure it works.

subscribe

bumping version..

Here is a very simple 2 lines patch to provide node tokens. I use it to have a node-specific folder where files are uploaded. Hope it helps.

@steingard: This is possibly a workaround indeed, as the home made module i'm coding and that uses this patch without problems has its weight greater than 0. I don't know though how we could better the patch so that it wouldn't be necessary to do this.

Anyway, if you want to try to change the weight of the module that uses token, be cautious because it might have side effects (as other things will probably change their order of execution).

I would love this: it would make it possible to set up file paths like 'CCYY/MM/DD' (those tokens being replaced with the node's create info) instead of just dumping everything straight into '/files'.

no I'm afraid I'll be foregoing node tokens. If you want more generic date tokens... poke eaton the token module maintainer. or write up the tokens yourself... There is even a patch in the token queue you can totally use.

Ok. I'll try using [site-date] first. That might work as well.

Hmm, the [site-date] token seems to be not so handy for my purpose after all. These ones are though.

Have a working option for this at: #280704: node tokens revisted