QUALITY PATCH

ACP2E-5079: A customer segment assigned to multiple websites returns matching customers only…

A customer segment assigned to multiple websites returns matching customers only from the first website when customer accounts are shared globally. Quality patch ACP2E-5079 for magento/module-customer-segment applies to Magento Open Source and Adobe Commerce 2.4.4 to 2.4.9. Adobe lists the fix as scheduled for 2.4.10.

Source: Adobe Experience League

Categories
Customer
Components
magento/module-customer-segment
Origin
adobe-commerce-support
Since QPT
1.1.84

Issue

A customer segment assigned to multiple websites returns matching customers only from the first website when customer accounts are shared globally.

Steps to reproduce

1. From the Admin sidebar, go to Stores > Settings > Configuration > Customers > Customer Configuration > Account Sharing Options, and set Share Customer Accounts to Global. 1. Create two websites, then create registered customer accounts on each website and place orders for those customers. 1. Go to Customers > Segments > Add Segment, create an active segment for registered customers, assign it to both websites, and add an order-history condition that matches the test customers. 1. Save the segment, click Refresh Segment Data, and review the Matched Customers grid.

Adobe's page lists 2.4.4 - 2.4.9 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.10.

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 ACP2E-5079. On Cloud, add ACP2E-5079 under stage.build.QUALITY_PATCHES in .magento.env.yaml.

For cweagans/composer-patches, choose a compatible version below and download the bundle. Copy its ACP2E-5079/ 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.

Patch files and compatible versions

Packages across compatible versions (1): magento/module-customer-segment

Sources

Łukasz Bajsarowicz
Built by

Łukasz Bajsarowicz, e-commerce architect

Magento and Adobe Commerce architecture, upgrades, performance and audits for merchants and agencies since 2015; magento.watch is the tooling I use on those projects.

Open source, maintained on weekends.