Hello,

I was wondering if token support would be possible with this module.

For example in the settings:
Email address change request email subject: *
Email address change request for !username at !site

I would like to replace !username with [user-realname] (token from the Realname module) or a profile field or a cck field.
Token support would be helpful to allow replacing with the user's real first name etc instead of the username.

I appreciate your hard work in creating this module and hope there may be a chance of implementing token support.

Thank you!

Comments

jaydub’s picture

With token in core for Drupal 7 it will certainly happen for the d7 version. I doubt I will be able to find the time to add this in for d6. If you can provide a patch I can try to work it in.

robby.smith’s picture

Sorry I do not have any programming skills =(
Maybe someone in the community may be able to help?
This would be a great new feature to this module

Thanks!

YK85’s picture

+1 subscribing

jaydub’s picture

I'm thinking that the way to accomplish this will be to add a hook that will allow the replacement variables in the email to be altered. That way Token module will not be explicitly required but can be used in any custom hook implementation that any one site requires.

Bilmar’s picture

subscribing

jaydub’s picture

Version: 6.x-1.x-dev » 7.x-1.x-dev
Assigned: Unassigned » jaydub
jaydub’s picture

Status: Active » Needs review

I've pushed code to support extra Tokens in the Drupal 7 version of the module. I am hoping I can get some extra testing before I say the feature is ready to roll out as part of a stable release.

Please check out the latest developer snapshot to try out tokens.

jaydub’s picture

Version: 7.x-1.x-dev » 6.x-1.x-dev
Status: Needs review » Patch (to be ported)

Token support was added in now released drupal 7 version of the module. Setting version to 6.x for possible later port.

greggles’s picture

Issue summary: View changes
Status: Patch (to be ported) » Closed (outdated)

The 6.x branch is no longer supported, so moving the status to Closed (outdated).

Please reopen it if you feel this issue still needs to be be addressed in some way.