Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport 'Fix account update without password change' to v0.27 #9735

Conversation

ahukkanen
Copy link
Contributor

馃帺 What? Why?

Backport #9582 to v0.27

鈾ワ笍 Thank you!

* Handle password change properly at the account form

When the user tried to update their account without changing their
password, they could not submit the form due to the front-end
validations.

Fix this issue by marking those fields required only when they
are visible on the form.

* Make sure the spec checks the encrypted password is not changed

When account is updated without providing a password, the
encrypted password shouldn't change.

* Do not autofill the password on the account form

In tests, the user record responds to  which causes
the account form updates to work differently in tests than they do
for actual users.

* Apply feedback from the code review

* Add also password and password confirmation errors on the form

In case the password update failed, the user doesn't get any
feedback. This fixes that issue.
@ahukkanen ahukkanen added backport Pull Requests that are a backport for a fixed bug module: core type: fix PRs that implement a fix for a bug labels Aug 15, 2022
@andreslucena andreslucena merged commit 85533ef into release/0.27-stable Sep 12, 2022
@andreslucena andreslucena deleted the backport/0.27/fix-account-update-without-pas-9582 branch September 12, 2022 08:51
@alecslupu alecslupu added this to the 0.27.0 milestone Jul 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport Pull Requests that are a backport for a fixed bug module: core type: fix PRs that implement a fix for a bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants