Hi, I am using Seblod user registration and since password field should be required in registration but not on editing profile (user may change other profile fields without changing the password), I duplicated user password and user password2 using workflow restriction (original fields are set to optional with workflow edit and new fields are set to Required with workflow Add).
The storage of the new fields is the same of the original ones (standard - user - password / password2) with second field having the validation on user_password, but the validation in the new fields is not working: typing the same value in password and confirmation fields, I always get "fields do not match". Why? By the way, password2 is not a real field (I can't see it in the DB), so maybe there is an internal Seblod trick that is not working with custom fields...?
Thanks a lot
Giuse
is it support by Seblod to clone user email and confirmation email fields for registration to differentiate between and and edit, with same storage (password and password) of the standard fields? Anyone has succeeded?
Thanks!
Giuse
validation "confirm" should work on any field.You just need to enter your first password field name in the configuration of validation
Ok, understood the problem: since I cloned pwd/confirm pwd, the validation confirm must reference the cloned field, not the original field, even if the two fields have the same storage!
Thanks Klas. I marked this thread as solved!
cheers
Giuse
The problem is when the user wants to upgrade from the public side only their first or last name, but not your password. Seblod forces us to enter the password again.
yes, I have this problem too ... Seblod is forcing the password to be entered (it's blank) by the admin when editing the user profile in the front-end, why?