-
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
customer objects are equal to eachother after observing event customer_save_after_data_object #7915
Comments
The problem here is a bug in the file vendor/magento/module-customer/Model/ResourceModel/CustomerRepository.php line 227. See below:
It should be:
Until Magento Team fixes it, you should overwrite the method to fix the issue. I've written a how to here https://blog.mdnsolutions.com/magento-2-customer_save_after_data_object-equal-objects/ Cheers, |
@Koekoet, thank you for your report. |
…bserving event customer_save_after_data_object #11649
#11546 Add AuthenticationInterface to the public API by @navarr #11659 [TASK] Removed Typo in Paypal TestCase didgit => digit by @lewisvoncken #11649 #7915: customer objects are equal to eachother after observing event customer_save_after_data_object by @RomaKis #11587 #11586 Fix duplicated crontab 2>&1 expression by @adrian-martinez-interactiv4 #11609 Fix a typo by @ajpevers #11582 M2 11581 by @tzyganu #11452 #11328 : app:config:dump adds extra space every time in multiline array value by @adrian-martinez-interactiv4 #11457 Added carrier code to ID to distinguish shipping methods [port 2.3] by @peterjaap #10769 Fix: Keep packages sorted by @localheinz
Internal ticket to track issue progress: MAGETWO-82529 |
…bserving event customer_save_after_data_object #11676
The issue has been fixed in 2.2-develop branch |
Internal ticket to track issue progress: MAGETWO-82652 |
Preconditions
Steps to reproduce
Expected result
Actual result
Screenshot here: http://imgur.com/a/IDV1t
This also happens with last name and email. There may be more, but I haven't checked.
The text was updated successfully, but these errors were encountered: