Attempting to use tokens for the upload path results in a directory of the token name. eg: I put [user] into the path box, and it gets me a subdirectory of /files/[user]/ and all images are still uploaded to that one file. Token.module is installed and enabled, I get the little helper table, but the tokens still aren't processed.

Comments

Bencoon’s picture

Bencoon commented
Status: Active » Closed (fixed)

Nevermind.. I figured it out.

mike.hobo’s picture

mike.hobo commented
Version: 5.x-2.x-dev » 5.x-2.0-rc2

How did you go about fixing this??

Bencoon’s picture

Bencoon commented

Well, the production site still made the files/[token] directory, but also behaved afterwards as it should, so I just let it be. The test site required starting over from scratch, though. Never could figure out what was causing the problem.

asak’s picture

asak commented

I can't get this working...

Tried 'photos/[nid]' but i get them all in '/[nid]' ...

Any idea?
Does this actually work?

Updated to rc-4 and got "the little helper table".

Now the question is - why isn't [nid] an available token?

SlipAngel’s picture

SlipAngel commented
Version: 5.x-2.0-rc2 » 6.x-3.0-alpha1
Status: Closed (fixed) » Postponed (maintainer needs more info)

I am having similar issues. I am experiencing form issues where [user] is being evaluated in ImageField's image path, but not for the image's alt tags or title, it just displays as [user]. Any ideas as to why the token is being evaluated in the image upload path and not in the image attributes?

quicksketch’s picture

quicksketch
he/him
commented
Status: Postponed (maintainer needs more info) » Closed (fixed)

SlipAngel, the tokens were not being evaluated properly in ALT and Title attributes until beta1. This request is really old and contains a couple different issues. Please open a new request for any problems with the latest versions.