user_pass_reset_url token
I am trying to use the CCK+Rules+Token module to accomplish creation of a user when a content with its email address is being created.
This user should get an email notification with his password and/or a user_pass_reset_url link.
The token_user.inc does not provide password, nor the creation of the user using the rules action.
In addition, the !password of the user_mail_tokens does not apply here.
Any suggestion what should be the right way to solve this ?
Regards,
Shushu
hi
I'am using the add user rules action to add a user when a node of a special contentype is created. In this rule I just added another action where I send an e-mail with the generated password (available as token and php variable, I use php variable).
See token replacement patterns and php evaluation in your rule....
cheers,
chris
Cannot add the generated password
Hi,
It seems we do the same, but while you say it is "available as token and php variable", I don't see it.
What do I miss ? In the token replacement patterns I don't see it.
For PHP evaluation, should I use an additional module ?
What exactly you write and where ?
Please advise,
Shushu
no, this should work out of
no, this should work out of the box. see for example image in http://drupal.org/node/409014#comment-1396258.
Did anyone ever solve this?
Did anyone ever solve this? I'd like to mimic the registration or admin created user account notification email and include the username and password for a user created when a certain content type is created. Sadly, it looks like the new user password is not available as a token. Ideas?
that makes perfectly sense. i
that makes perfectly sense. i am searching for a very similar solution.
the scenario:
an anonymous user is creating content. after submission the content is set unpublished.
rules creates an user out of the name and email field of the content
the user is set to 'blocked' and an user activation/password reset link is sent to the given email adress
when the user activates his account, his content is published.
i tried to achieve this with the rules module, but it seems not to be possible. or did i muss something?
another way of doing this would be the use of drupal.org/project/inline_registration, but this is not as beautiful as the rules way would be. so any advise is very welcome