-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Magento 2.7 and 2.1.1 - While changing the password form the my account page User group changed to default customer group #6787
Comments
@thirumoorthyp thank you for your feedback. |
While changing the password from the my account page user group changed to default customer group. Preconditions
Steps to reproduce
Expected result: The user remains in "XXXX Group" Actual result: The user changes to default user group |
This should be fixed in 2.09, please update your codebase |
@sevos1984: Thanks for the reply. |
This issue also still exists in Magento 2.1.2 |
I can't reproduce this on clear magento install, need more detailed steps. |
Hi @sevos1984 Below are the steps to reproduce. Preconditions
Steps to reproduce
Expected result: Actual result: |
Thanks, I found ticket for this problem MAGETWO-58335 it will be soon delivered. |
But I have checked in 2.1.0 version also, this issue exist |
Hi @sevos1984: Any ETA when this problem will be resolved? |
@thirumoorthyp, thank you for your report. |
[Arrows] Fixes for 2.4 (pr142) (2.4-develop)
While changing the password from the my account page user group changed to default customer group. For example : 1) I have created Customer group named "XXXX Group" 2) I have created a user with "XXXX Group" from admin panel. 3) When i change the password from the my account change password section, the current user group has been assigned to default User group.
Note:
I have checked both the versions 2.0.7 and 2.1.1, which facing the same issue.
kindly provide the solution
Expectation: When i change the password, user must be assigned to expected "XXXX Group"
The text was updated successfully, but these errors were encountered: