Newsletter product widget wrong store view per send batch

[vandijkstef]

Preconditions and environment

• Mage 2.4.7
• comes with module-newsletter@100.4.7

Steps to reproduce

1. Create a newsletter template containing a product widget ("Catalog Products List" used, made product selection based on specific SKU's) ánd other {{trans ""}} elements (albeit those are just to prove the point)
2. Send (async + batched) out newsletter to multiple customers on different store views (languages)

Expected result

A nicely translated email with the products for the correct store-view/language

Actual result

While the header/footer, subject and {{trans ""}} element work fine the "catalog products list" widget is not always in the correct store-view/language

Additional information

I couldn't find a specific reason yet, however it isn't completely random.

It seems that the "catalog products list" widget is only being generated ONCE per batch. Batches contain multiple subscribers on different store view, but all will receive the catalog-product-list widget in the same language. I haven't been able if this is down to the first or last entry in the batch as async sending can trip up the order here, but the entire batch has that store-view/language while all other elements internationalize just fine. So while some batches are send out fine (100% same store-view subscribers in batch), others are 95% wrong. This needs to be tested where batches are containing mixed subscribers.

Technically you can work around this by queuing newsletters per store-view.

Release note

No response

Triage and priority

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [X] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• [ ] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant[bot]]

Hi @vandijkstef. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this

• To learn more about issue processing workflow, refer to the Code Contributions.

  Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant[bot]]

Hi @engcom-Bravo. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• [ ] 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• [ ] 5. Add label Issue: Confirmed once verification is complete.
• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.