No user account tokens are replaced for the user account created trigger [#870868]

The gap between the expectation of this working and the failure to work is large enough that i'm filing this as a bug report, at least for now.

User-related replacement tokens are not working for the send e-mail action (configured in advanced actions) when used on account creation related triggers.

That is, nothing is replaced for:
[user:mail]
[user:name]
[account:mail]
[account:name]

When using at least the following triggers:
"Trigger: When either creating a new user account or updating an existing"
"Trigger: After creating a new user account"
"Trigger: After updating a user account"

Comment	File	Size	Author
#3	user-870868-account-tokens-when-saving-user.patch	707 bytes	mlncn
#3
#2	user-870868-user-account-when-saving.patch	0 bytes	mlncn
#2

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

mlncn CreditAttribution: mlncn commented 1 August 2010 at 16:52

Similar problem reported in Drupal 6: #479218: Advanced Actions - Send email - Only global variables work - System Module

Comment #2

mlncn CreditAttribution: mlncn commented 1 August 2010 at 22:45

Status:	Active	» Needs review
Issue tags:		+dgd7

File	Size
user-870868-user-account-when-saving.patch	0 bytes

Here is a patch that fulfills the expectation that user tokens will be available to actions when a user is being saved. User module's token integration was only checking for user account data in a sub-array called 'user', when more often (when not referring to the current user) the user account data is in a sub-array called 'account' (using account instead of user when the user being acted upon need not be the currently logged in user is best coding practice followed by in user.tokens.inc itself).

So long as both are checked (and this patch checks account first) token replacement works as expected. We can send an e-mail to an administrator whenever a user registers that includes that user's username and e-mail address. Joy!

[The magical disappearing patch... the one in the next comment will work better.]

Comment #3

mlncn CreditAttribution: mlncn commented 1 August 2010 at 22:46

File	Size
user-870868-account-tokens-when-saving-user.patch	707 bytes

Comment #4

pfrenssen

Sofia

CreditAttribution: pfrenssen commented 3 August 2010 at 21:11

I tested your patch against the latest drupal-7.x-dev.

Without applying your patch the [user:mail] and [user:name] tokens were correctly replaced in the email for me. The [account:mail] and [account:name] were not replaced, but applying the patch did not fix this. I had the exact same result with or without patch.

Exact steps I did to replicate the problem:

* installed drupal-7.x-dev with a clean db
* admin/modules > enabled the trigger module
* admin/config/system/actions > create advanced action > send email

I used these settings for the advanced action:
- Label: Send e-mail
- Recipient: (my email address, not using any tokens)
- Subject: test
- Message:

user:mail [user:mail]
user:name [user:name]
account:mail [account:mail]
account:name [account:name]

* admin/structure/trigger/user > assign "send e-mail" action to:
- Trigger: After creating a new user account
- Trigger: After updating a user account

(note: I did not assign this action to the "When either creating a new user account or updating an existing" trigger, because this option was not in the list)

* admin/people/create > added a new user with a random name, email and password

I received an email with the following body text:

user:mail test.test@test.com
user:name testuser
account:mail [account:mail]
account:name [account:name]

* applied the patch in comment #3
* created a new user with a random name, email and password

Resulting email:

user:mail nanad@nana.com
user:name chickenpox
account:mail [account:mail]
account:name [account:name]

The patch did not have any effect. I tried to look up which tokens are available but couldn't find anything but the few examples in the actions config pages.