PDF file name token fails for specific content type
drupal_jon - September 28, 2009 - 19:27
| Project: | Token |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
Hi,
I have the following PDF filename token configured, however for one content type, any node specific tokens (e.g. nid, title) fail to work.
Token setting: [site-name] - [title]
Other content types work fine. Does that seem like a token issue?
John
#1
How does it fail to work? Is the filename including the tokens, or is it the node path?
If it is the former, it is a token thing, if it is the latter then something weird is going on.
#2
For the tokens:
[site-name] - [title]
It will create the file as:
Example.com - .pdf
The title, or nid, or anything node related seems to disappear completely. However, it only happens for a single content type.
#3
It seems like a token issue to me.
I only call the token module like this:
$pdf_filename = token_replace($pdf_filename, 'node', $node) .'.pdf';So if it replaces one token, but fails to replace the other for a single content type, I would guess it has something to do with that content type.. Maybe there's no title defined in that content type?
Anyway, moving this to the token issue queue.
João
#4
Just noticed that this appears to be fixed after updating various things including Drupal core to 6.14.
#5
Automatically closed -- issue fixed for 2 weeks with no activity.