Afternoon wrote:
One idiom which is common is to intepret an empty password field to
mean "no change to password".
On a similar note...
It's also common thing to extract password change in a separate view. I
beleive it complies more with user interaction model because changing
some generic data and changing a password are separate concepts for many
users.
I made this myself in my project and in a view with all the data except
password I used automatic ChangeManipulator and I had to prefill data
passed to the manipulator with current password or otherwise it would
actually set password to null.
- Re: Backwards-incompatible change in development version: Passwo... Maniac
-
