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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

#31168 fix for customer which have more than two subscriptions #31261

Merged
merged 3 commits into from
Dec 21, 2020
Merged

#31168 fix for customer which have more than two subscriptions #31261

merged 3 commits into from
Dec 21, 2020

Conversation

korovitskyi
Copy link
Collaborator

Description (*)

Rolled back updating is_subscribed Extension attribute at Magento\Customer\Api\Data\CustomerInterface.
And test for this case was added.
Column reference_field must be unique to avoid exceptions on getList method.

Fixed Issues
Fixes #31168.

Manual testing scenarios (*)

  1. Create customer.
  2. Add several(more then one) newsletter subscriptions for this customer.
  3. Get this customer by \Magento\Customer\Api\CustomerRepositoryInterface::getList method.

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds are green)

@m2-assistant
Copy link

m2-assistant bot commented Dec 11, 2020

Hi @korovitskyi. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento give me test instance - deploy test instance based on PR changes
  • @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

  • @magento run all tests - run or re-run all required tests against the PR changes
  • @magento run <test-build(s)> - run or re-run specific test build(s)
    For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

  1. Database Compare
  2. Functional Tests CE
  3. Functional Tests EE,
  4. Functional Tests B2B
  5. Integration Tests
  6. Magento Health Index
  7. Sample Data Tests CE
  8. Sample Data Tests EE
  9. Sample Data Tests B2B
  10. Static Tests
  11. Unit Tests
  12. WebAPI Tests

You can find more information about the builds here

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

For more details, please, review the Magento Contributor Guide documentation.

⚠️ According to the Magento Contribution requirements, all Pull Requests must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of Pull Requests happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

@m2-community-project m2-community-project bot added Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Severity: S2 Major restrictions or short-term circumventions are required until a fix is available. labels Dec 11, 2020
@swnsma swnsma self-requested a review December 11, 2020 11:46
Copy link
Contributor

@swnsma swnsma left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @korovitskyi!
Thank you for your contribution.
I am afraid that such changes could be considered backward-incompatible for those who are using the 'is_subscribed' extension attribute.

With new behavior, we will receive a list of customers without these values.
My suggestion is to adjust logic inside 'app/code/Magento/Newsletter/Model/Plugin/CustomerPlugin' by using a subscribers collection to fill the required data.
What do you think about this?

@engcom-Charlie
Copy link
Contributor

Hi @korovitskyi could you please look at #31261 (review)?
Thank you.

@korovitskyi
Copy link
Collaborator Author

Hi, @swnsma, @engcom-Charlie.
Thanks for notice.
Changes was sent.
Please, let me know if you have some notes.

@swnsma
Copy link
Contributor

swnsma commented Dec 17, 2020

@magento run all tests

@swnsma swnsma self-requested a review December 17, 2020 20:43
@magento-engcom-team magento-engcom-team added Partner: Atwix Pull Request is created by partner Atwix partners-contribution Pull Request is created by Magento Partner labels Dec 17, 2020
@magento-engcom-team
Copy link
Contributor

Hi @swnsma, thank you for the review.
ENGCOM-8551 has been created to process this Pull Request

@engcom-Alfa
Copy link
Contributor

✔️ QA Passed

Preconditions:

  1. Admin -> Stores -> Configuration -> Customers -> Customer Configuration -> Account Sharing Options and set Share Customer Accounts to Global

Screenshot from 2020-12-07 12-59-48

  1. Multiple-store views setup in Magento

Screenshot from 2020-12-07 12-56-25

  1. Have one customer ( [email protected] for ex.);

Steps to reproduce (*)

  1. Go to Admin -> Customers -> All Customers and open customer for edit;
  2. On left side, select Newsletter, to have the Newsletter Informaiton panel where all stores views are displayed.
  3. Select more than 1 checkbox to subscriber customer to the store's newsletter and save customer
    (at this point, in Newsletter Subscribers view, customer is subscribed to newsletter for multiple-store views)

Screenshot from 2020-12-07 13-04-43

  1. Use REST to call GET /V1/customers/search to retrieve the customer

V1/customers/search?searchCriteria[filterGroups][0][filters][0][field]=email&searchCriteria[filterGroups][0][filters][0][value]=[email protected]&searchCriteria[filterGroups][0][filters][0][conditionType]=eq

Screenshot from 2020-12-07 13-06-15

Before: ✖️ Exception occurs.

Screenshot from 2020-12-18 10-47-27

And in the exception.log file:

Screenshot from 2020-12-18 10-48-07

After: ✔️ Customer details are returned correctly

Screenshot from 2020-12-18 10-55-29

@m2-assistant
Copy link

m2-assistant bot commented Dec 21, 2020

Hi @korovitskyi, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

@robbie-thompson
Copy link

@korovitskyi we just ran into this error, thanks for fixing this! 🙌

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests Award: bug fix Component: Newsletter Partner: Atwix Pull Request is created by partner Atwix partners-contribution Pull Request is created by Magento Partner Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: accept QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope Release Line: 2.4 Severity: S2 Major restrictions or short-term circumventions are required until a fix is available.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

REST endpoint /customers/search not working for multi-store newsletter subscriptions
6 participants