QUALITY PATCH

ACSD-49013: Email confirmation is not translated to the website locale…

Email confirmation is not translated to the website locale when creating customers using bulk API. Quality patch ACSD-49013 for magento/module-store applies to Magento Open Source and Adobe Commerce 2.4.3 to 2.4.6-p15.

Categories: Emails
Components: magento/module-store
Origin: adobe-commerce-support
Since QPT: 1.1.27

Issue

Email confirmation is not translated to the website locale when creating customers using bulk API.

Steps to reproduce

1. Install a different locale like de_DE. 1. Configure RabbitMQ. 1. Execute bin/magento setup:upgrade to install the queues in RabbitMQ and set up the language pack. 1. Create an additional website in Admin > Stores > All Stores. 1. Set the locale of this new website to de_DE in Admin > Stores > Configuration > General > Locale Options. 1. Execute an API call to create a customer account using bulk API. Use the corresponding website_id. Endpoint: /rest/async/bulk/V1/customers [{ "customer": { "email": "test@example.com", "firstname": "test", "lastname": "test", "website_id": 2 }, "password": "Passw0rd!" }] 1. Execute bin/magento queue:consumers:start async.operations.all --single-thread --max-messages=10. 1. You can see that the customer account is created correctly on the specified website. 1. Check the email received for customer registration.

Adobe's page lists 2.4.3 - 2.4.6 as compatible; the versions below are resolved from the current QPT constraints and are the ones the tool will offer.

Adobe scheduled the permanent fix for 2.4.7.

Install

Install the Quality Patches Tool with composer require magento/quality-patches, apply the prerequisites listed for all files applicable to your distribution and version first, then run vendor/bin/magento-patches apply ACSD-49013. On Cloud, add ACSD-49013 under stage.build.QUALITY_PATCHES in .magento.env.yaml.

For cweagans/composer-patches, choose a compatible version below and download the bundle. Copy its ACSD-49013/ folder into patches/composer/, merge composer.patches.json into composer.json, then run composer install. Bundle prerequisites the same way and list them first. Paths are relative to each package root, using the default -p1 level. Prefer local files when configuring composer-patches; a remote URL can change.