1

why is it that ordinary tokens appear in fields where use is made of the "token field" and "field default token" modules?

I created a rule which creates a node with the username in the user creation form. I need to have fields in this new node to be populated by custom fields in the user creation form using tokens.

ordinary tokens work fine, tokens from custom fields either turn out as blank for the "field default token" module or as the token name in "token field" module.

Am I missing something?

More Information as requested in the comments:

I have custom fields on the standard user profile. When a user account is created, a content node is created, using the "rules" module. That node's name is pulled off the user profile using the "token" module, the token being for one of the custom fields. This works 100%. Now I want to do the same for two fields in the new content node, i.e. pulling content from the user profile's custom node's and placing them into the content node. This can be done with "field default token" or "token field". For some reason only standard drupal tokens work, tokens for custom fields don't, as described.

  • Oh, the terms of reference of the project are to only use stock modules. No code snippets or custom code should be used in this case. – NamSandStorm Nov 11 '13 at 19:40
  • Can you be more specific? Which tokens return blank in which situations? – Scott Joudry Nov 11 '13 at 21:37
  • I have custom fields on the standard user profile. When a user account is created, a content node is created, using the "rules" module. That node's name is pulled off the user profile using the "token" module, the token being for one of the custom fields. This works 100%. Now I want to do the same for two fields in the new content node, i.e. pulling content from the user profile's custom node's and placing them into the content node. This can be done with "field default token" or "token field". For some reason only standard drupal tokens work, tokens for custom fields don't, as described. – NamSandStorm Nov 12 '13 at 5:48
  • Please update your answer with these new details so all of the information is in one place. – Scott Joudry Nov 12 '13 at 12:49
  • You mean my question? – NamSandStorm Nov 12 '13 at 13:05
0

This seems to have to do with porting data from a content node field to a user node field. I solved this by creating the User and then creating the node with data pulled from the user node fields.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.