Fix issue with unexpected changing of subscription status after customer saving #18488
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
If in some cases (for example: after migration data from M1) customer will have store_id = 0 and there are subscriber that related to this customer, after re-saving customer data, it might cause unexpected "unsubscribe" letter which would confuse customer experience.
My changes solves this problem because of adding additional checking storeId and if it's 0, getting it directly from the website.
Manual testing scenarios
Expected result:
Nothing, except saving customer data, will happen
Actual result:
Customer will receive unsubscription letter.
Contribution checklist