using token
agharbeia - January 20, 2008 - 23:59
| Project: | Fullname field for CCK |
| Version: | 5.x-1.5 |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
I'm using CCK Fullname along with Auto Nodetitle, both of which support Token.
I use the token [field_fullname], which is the name I gave the field but I'm unable to get Auto Nodetitle to set the node's title field based on the sub-fields of CCK Fulname.
Maybe I should submit this to Autonode Field instead, but I would like to know exactly what token should I be using in place of the full name, isn't it the name of the field of type Fullname which I had created?
Also, is it possible to extract sub-fields individually?
Thank you and regards,
#1
It would seem that you failed to notice the fieldset within the "Automatic title generation" fieldset labeled "Replacement patterns" but instead typed that token by hand. Am I correct? Well, you are using the wrong token name. The answers you seek are in the "Replacement patterns" fieldset.
#2
Thank you, Ryan for your reply.
Sorry, I'm not sure I understand what you mean.
I had noticed the "Replacement pattern field". Here's exactly what I had done. (I just created that issue entry but I had tried what is described there before I submitted my first issue here).
What about using the wrong token? what do you mean?
#3
There is a giant list of available tokens in the "Replacement pattern" fieldset. You have to look there to get the correct names of the tokens you want. This is really, really simple, so I'm not sure why you are so confused. On my system, I see about 200+ tokens to choose from on one of my content types including 44 possible tokens for use with the fullname module.
So what it comes down to is you must not be reading the available documentation of the token module and the auto-nodetitle module. There is literally nothing more for me to tell you.
#4
If I don't hear more, I'll just have to close this. Marking fixed so it will timeout in two weeks.
#5
Automatically closed -- issue fixed for two weeks with no activity.