-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
"Customer can login to the store" checkbox bug in the customer admin #10951
Comments
Bug spotted! In the
The
Should be:
or simply
|
Indeed there is a bug. Are you willing to open a PR with the fix? Regarding a test, we should probably add some scenario in this file, with some new step like |
if applied, this commit will -make sync behaviour works on both customer and shop user, resulting in username will never by setting username value whenever shopuser or customer are inserted or updated.
if applied, this commit will -make sync behaviour works on both customer and shop user, resulting in username will never by setting username value whenever shopuser or customer are inserted or updated.
if applied, this commit will -make sync behaviour works on both customer and shop user, resulting in username will never by setting username value whenever shopuser or customer are inserted or updated.
if applied, this commit will -make sync behaviour works on both customer and shop user, resulting in username will never by setting username value whenever shopuser or customer are inserted or updated.
if applied, this commit will -make sync behaviour works on both customer and shop user, resulting in username will never by setting username value whenever shopuser or customer are inserted or updated.
if applied, this commit will -make sync behaviour works on both customer and shop user, resulting in username will never by setting username value whenever shopuser or customer are inserted or updated.
if applied, this commit will -make sync behaviour works on both customer and shop user, resulting in username will never by setting username value whenever shopuser or customer are inserted or updated.
if applied, this commit will -make sync behaviour works on both customer and shop user, resulting in username will never by setting username value whenever shopuser or customer are inserted or updated.
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions. |
if applied, this commit will -make sync behaviour works on both customer and shop user, resulting in username will never by setting username value whenever shopuser or customer are inserted or updated.
if applied, this commit will -make sync behaviour works on both customer and shop user, resulting in username will never by setting username value whenever shopuser or customer are inserted or updated.
if applied, this commit will -make sync behaviour works on both customer and shop user, resulting in username will never by setting username value whenever shopuser or customer are inserted or updated.
if applied, this commit will -make sync behaviour works on both customer and shop user, resulting in username will never by setting username value whenever shopuser or customer are inserted or updated.
… (hatem20) This PR was merged into the 1.7 branch. Discussion ---------- If applied, this commit will -make sync behavior works on both customer and shop user, resulting in username will never by setting username value whenever shop user or customer is inserted or updated. | Q | A | --------------- | ----- | Branch? | 1.6 or master <!-- see the comment below --> | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Related tickets | fixes #10951 | License | MIT I could have used the solution proposed here #10951 (comment) but it might be better if the username is always in sync with customer email Commits ------- 924c819 Bug #10951 [Account] fix sync username with customer email
… (hatem20) This PR was merged into the 1.7 branch. Discussion ---------- If applied, this commit will -make sync behavior works on both customer and shop user, resulting in username will never by setting username value whenever shop user or customer is inserted or updated. | Q | A | --------------- | ----- | Branch? | 1.6 or master <!-- see the comment below --> | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Related tickets | fixes #10951 | License | MIT I could have used the solution proposed here Sylius/Sylius#10951 (comment) but it might be better if the username is always in sync with customer email Commits ------- 924c819e08d475618327ff4ce449f0a7a179512a Bug #10951 [Account] fix sync username with customer email
* 1.7: Fix docs for custom resource controllers [Documentation] fix typo in fixture docs Bug #10951 [Account] fix sync username with customer email
…atem20) This PR was merged into the 1.7 branch. Discussion ---------- | Q | A | --------------- | ----- | Branch? | 1.7 | Bug fix? | no | New feature? | no | BC breaks? | no | Deprecations? | no | Related tickets | #10951 | License | MIT I added spec as request in #11048 <!-- - Bug fixes must be submitted against the 1.7 branch (the lowest possible) - Features and deprecations must be submitted against the master branch - Make sure that the correct base branch is set To be sure you are not breaking any Backward Compatibilities, check the documentation: https://docs.sylius.com/en/latest/book/organization/backward-compatibility-promise.html --> Commits ------- c5e245f [Account] Add spec to sync username with customer email
if applied, this commit will -make sync behaviour works on both customer and shop user, resulting in username will never by setting username value whenever shopuser or customer are inserted or updated.
Sylius version affected: 1.6.2
Description
Even though customer has an account, the "user can login" checkbox is not checked.
Steps to reproduce
first name
,last name
and theemail
, DON'T check the "user can login" checkboxuser can login
checkbox, type a password and press saveWhen you check it, the form disappears LOL ! This bug makes my clients go crazy.
The text was updated successfully, but these errors were encountered: