Closed (won't fix)
Project:
File (Field) Paths
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
21 Jul 2011 at 16:31 UTC
Updated:
29 Sep 2016 at 22:34 UTC
Jump to comment: Most recent
Comments
Comment #1
joelstein commentedOh, I also switched to using field_info_fields(), to resolve the outstanding todo. Now, file_filefield_paths_get_fields looks a lot more like image_filefield_paths_get_fields.
Comment #2
dave reidWe officially removed this token from core as it doesn't actually work, so you shouldn't work to support it. The proper way to support the description data is with Field token support - not supporting it for the file token type.
Comment #3
h0tw1r3 commentedThanks for commenting on this Dave. Putting on hold until #691078: Field tokens is worked out.
Comment #4
joelstein commentedAs of Drupal 7.6, [file:description] has been removed from core. See #978028: File token fixes: [file:description] does not exist and [file:owner] not using format_username.
In case anyone needs a temporary solution (like me), you can add this token in a custom module.
Comment #5
decipheredClosing this due to the fact that the token in question no longer exists.
If the custom implementation of the token doesn't work, then happy enough to re-open.
Comment #6
dead_armI came across this issue while trying to render the description field of a file with a token, and was disappointed to find that it wasn't possible.
We found a solution though. I should mention we are using Display Suite, and by enabling the description field on the file field, and then using the "Generic file" format for the field display, we achieved what we wanted, which was to have the text that is input into the description field display as the title of the uploaded file, without the filename extension.
Comment #7
steveoriolI like the temporary solution on #4, thank you joelstein
Comment #8
fallenturtle commentedWhat version of token_custom do I need to make the code in #4 work? I've tried both 7.x-1.1 and 7.x-2.0-beta3 with no success.Nevermind.