As title says, we had to hack the user_import module to include user's realname (Content Profile field value) in the activation email. As a result of this we came out with a patch that supports tokens like "!field_profile_firstname". Patch follows.

CommentFileSizeAuthor
#1 user_import_content_profile_fields_token.patch909 bytesSivaji_Ganesh_Jojodae
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Sivaji_Ganesh_Jojodae’s picture

Sivaji_Ganesh_Jojodae CreditAttribution: Sivaji_Ganesh_Jojodae commented
Issue tags: +token, +content profile
FileSize
user_import_content_profile_fields_token.patch909 bytes

Attached in the patch working fine in one of our production sites.

srees’s picture

srees CreditAttribution: srees commented

Thank you, was looking for just this thing. Not difficult to write, but was trying to find if it already existed with user_import.

gisle’s picture

gisle
he/him
Primary language Norwegian Bokmål
Location Norway
CreditAttribution: gisle at Hannemyr Nye Medier AS commented
Issue summary: View changes
Status: Active » Closed (outdated)

The Drupal 6 version is no longer supported.

There is no version of Content Profile for Drupal 7. Closing as outdated.