- ๐ฎ๐ณIndia sarguna raj M
++
I'm also facing the same issue. Is there any update?
Thanks.
- Status changed to Needs review
about 1 year ago 5:05am 6 June 2023 - ๐ฎ๐ณIndia narendra.rajwar27 India
narendra.rajwar27 โ made their first commit to this issueโs fork.
- ๐จ๐ณChina zterry95
#10 patch not works in my case.
Here is new patch, it's a temporary solution. but it works. - ๐ถ๐ฆQatar harivenuv Qatar
First of all i'm not using this module, but i faced the same issue. This issue due to the user object not loaded correctly on the form, possibly due to a missing of user ID from the route used in your form. This problem often arises in Ajax callbacks button, where the route name and user parameter should be passed through the Ajax's URL property.
'#ajax' => [ 'callback' => 'custom_user__back_to_step_2', 'url' => Url::fromRoute('custom_user.user_edit', ['user' => $user->id()]), 'options' => [ 'query' => [ FormBuilderInterface::AJAX_FORM_REQUEST => TRUE, ], ], ],
- ๐บ๐ธUnited States fskreuz
#15 solves a related issue regarding Password Policy's
password_username
constraint.Because
change_pwd_page
separates the password form from the user edit form, thename
field is not present. Password Policy treats the missingname
field as a blank string, causing it to fail thepassword_username
constraint. Adding thename
field as a hidden field works.