picture worth 1000 words:

http://www.screencast.com/t/9znVJQF3

Comments

drewish’s picture

drewish commented
Category: bug » support

A picture may be worth a thousand words but the thousand words are much easier to find in a search query than the audio from a video. Please provide a text description.

That said watching your video it looks like you want to use the title tag rather than the job field. I'm guessing if you viewed the node you'd see there's no value in the job field. When there's no value the token isn't replaced.

drewish’s picture

drewish commented
Status: Active » Fixed

Sorry that should have read [title] token.

mtsanford’s picture

mtsanford commented

Ah... you are correct! That field is used for another content type, so it's not filled in for the content type I was trying to add a custom link for.

Thanks.

Here is a better description for the search engines:

I have a CCK Content type called "Job". I attempted to add a custom link to these Job nodes called "Apply For This Job" using the Custom Links module. In the query string section I entered:

job=[field_job-title]

[field_job-title] is a token provided by the CCK module that appeared in the Placeholder Tokens section of the custom links setup page. When I actually went to view a node, the custom link appeared, but the query string was not being filled in correctly and the query string at then end of the link just ended up being:

?job=[field_job-title]

Bottom line is the "Job" content type did not include a field_job-title field, so it did not get replaced. That was a field used by another content type. So watch out. Just because the token shows up in Placeholder Tokens section does not necessarily mean the token is available in the context you are using the custom link for.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.