-
Notifications
You must be signed in to change notification settings - Fork 9.4k
Description
Steps to reproduce
- Create a new customer in 2.07
- Upgrade to 2.1
- Create a new customer group
3b. Update the existing customer to the new group - Create new customer in 2.1
- Change that customer to another customer group.
Expected result
- Any existing customer in 2.07 should be able to update to new customer group in 2.1
Actual result
- Customer who were setup in 2.07 could not updated to a new customer group in 2.1
- Customers who were created in 2.1 could be updated to a new customer group.
- Note: I never tried updating an existing customer in 2.07 to a new group.
Notes from my host provider:
I've reviewed the two customers on the database, and there are some differences between the two, however, when changing both of them to a different group, I am able to replicate the issue with only the user that I did not create. These changes made the test user have a group ID change from 1 to 2 when switching from General to Wholesale, while the other customer remained at 1.
Manually changing this database value to 2 had no effect on the customer in the backend. Additionally, there are a number of differences by default between the two users. The user that existed before the update has a variety of columns populated with content that the new user does not, such as a password hash and gender. You can see this yourself in the customer_entity table.
This definitely appears to be an issue only with the user that existed before the update.