Thanks for a great module.

For my use case, I actually needed the password to be visible to the editor, in case he forgets what he entered. As a feature suggestion, perhaps that can be an option, so when a password is added the editor can choose whether it should be hidden or not (I do realize that would require quite a few changes to the module and how the password is stored and not sure if others would need this)

As a work around, I just added a cck text field to the content type called "Password reminder" which allows the editor to enter the password -- and then excluded then hid and excluded that field under "display)

Comments

roderik’s picture

roderik
Primary language Dutch
Location Amsterdam,NL / Budapest,HU
commented

This is a general issue.
A lot of password implementations do not store the literal password, only the encrypted version. The original password cannot be recreated from the encrypted version (only compared with the encrypted version of 'whatever the user entered').

protected_node is the same.

...and should remain the same, so your solution should probably remain a workaround, unless there is huge demand for this option. It seems better not to store unencrypted passwords in the database, by default.

mtolmacs’s picture

mtolmacs commented
Status: Active » Closed (won't fix)

I concur roderik on this.