Closed (won't fix)
Project:
Protected Node
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
6 Jul 2012 at 08:55 UTC
Updated:
21 Sep 2016 at 13:53 UTC
Jump to comment: Most recent
Comments
Comment #1
zoraxI need this fonctionnality, because I can't send at the creation of the node the password.
So I use a view for sending it when the administrator need to send it.
Comment #2
zoraxCan you explain how to do for adding this field in view,
Best Regards,
Comment #3
izus commentedHi
i am afraid this is a won't fix issue :
actually we do not store the password clearly at all, it is hashed in the database or in the variables when it is global.
this gives no way to bulk send mails with the password using views.
the only way that the module provides currently is :
1) active the email sending in the configuration page and make sure the message body has the node:password token.
2) edit existing node (works also during creation) and do set the password again + fil the emails adresses list and save.
this will send the password in clear way, and if changed from what is used to be, will also update the hash of it in the database.
so, the only way if we want to keep not saving the passwords in clear, is to reenter it again in the edit node form and use it while it is not hashed.
Thanks
Comment #4
marco.bI did a workaround that could fix your problem:
add a hidden text field in your nodetype and trigger a rule with the action 'set value' with the token [node:password] which delivers the password data. This rule works only with editing existing nodes.Triggered at node creation you must set the rules action 'save entity' before firing the above action, otherwise the field be left empty.
With the cleartext data you can do whatever you want in views etc.