ACP2E-4706: The Target Rule indexer cron doesn't pick products that are enabled only at a store view…
The Target Rule indexer cron doesn't pick products that are enabled only at a store view scope, causing products not enabled in the Adobe Commerce Admin scope to be skipped by the indexer. Quality patch ACP2E-4706 for magento/module-target-rule applies to Magento Open Source and Adobe Commerce 2.4.5 to 2.4.8-p4.
- Categories
- Catalog/Product
- Components
- magento/module-target-rule
- Origin
- adobe-commerce-support
- Since QPT
- 1.1.79
Issue
The Target Rule indexer cron doesn't pick products that are enabled only at a store view scope, causing products not enabled in the Adobe Commerce Admin scope to be skipped by the indexer.
Steps to reproduce
1. Create a simple Related Product Rule. 1. Create a product that is disabled at the Admin (global) scope but matches the rule conditions. (the rule can be kept simple by not adding any conditions under Products to Match or Products to Display). 1. Run the cron to execute the indexer backlog. 1. Edit the product and switch to the Default Store View scope. 1. Enable the product only at the Default Store View scope. 1. Run the cron to execute the indexer backlog. 1. Check the Storefront on a different product for the Related Products section, or query the magento_targetrule_product table to verify that the newly created product ID exists.
Adobe's page lists 2.4.5 - 2.4.8-p4 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.9.
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-4706. On Cloud, add ACP2E-4706 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-4706/ 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
magento/magento2-ee-base >=2.4.5 <2.4.5-p17 || >=2.4.6 <2.4.6-p15 || >=2.4.7 <2.4.7-p10 || >=2.4.8 <2.4.8-p5
- Magento Open Source
- —
- Adobe Commerce
- 2.4.8-p4, 2.4.8-p3, 2.4.8-p2, 2.4.8-p1, 2.4.8, 2.4.7-p9, 2.4.7-p8, 2.4.7-p7, 2.4.7-p6, 2.4.7-p5, 2.4.7-p4, 2.4.7-p3, 2.4.7-p2, 2.4.7-p1, 2.4.7, 2.4.6-p14, 2.4.6-p13, 2.4.6-p12, 2.4.6-p11, 2.4.6-p10, 2.4.6-p9, 2.4.6-p8, 2.4.6-p7, 2.4.6-p6, 2.4.6-p5, 2.4.6-p4, 2.4.6-p3, 2.4.6-p2, 2.4.6-p1, 2.4.6, 2.4.5-p16, 2.4.5-p15, 2.4.5-p14, 2.4.5-p13, 2.4.5-p12, 2.4.5-p11, 2.4.5-p10, 2.4.5-p9, 2.4.5-p8, 2.4.5-p7, 2.4.5-p6, 2.4.5-p5, 2.4.5-p4, 2.4.5-p3, 2.4.5-p2, 2.4.5-p1, 2.4.5
- Requires
- ACP2E-4431
- vendor/magento/module-target-rule/Model/Indexer/TargetRule/AbstractAction.php
