ACSD-50887: The product attribute property Use in Search Results Layered Navigation can be set to Yes…

Categories

Catalog Search

Components

magento/module-catalog, magento/module-catalog-search, magento/module-layered-navigation

Origin

adobe-commerce-support

Since QPT

1.1.36

Issue

The product attribute property Use in Search Results Layered Navigation can be set to Yes without the Use in Search option also being set to Yes. These settings were designed to be used together. With the patch applied, when the Use in Search option is set to No, the Use in Search Results Layered Navigation option is hidden to work as if it were also set to No.

Steps to reproduce

1. In the Admin, navigate to Stores > Attribute > Product and create an attribute with the multiselect type and set the following: * Use in Search = No * Use in Layered Navigation = (Any option) * Use in Search Results Layered Navigation = Yes * Name = Test_attribute * Options: * Sticker * Picker 1. Add the new attribute to the default attribute set. 1. Create two products: 1. First product: * Name = Sticker * Set Price, QTY, Weight to 1 * Test_attribute = select option Sticker 1. Second product: * Name = Picker * Set Price, QTY, Weight to 1 * Test_attribute = select both options 1. Run catalogsearch_fulltext reindex: bin/magento indexer:reindex catalogsearch_fulltext 1. Search by the word sticker on the storefront.

Adobe's page lists 2.4.0 - 2.4.6-p2 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-50887. On Cloud, add ACSD-50887 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-50887/ 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

Sources

• Adobe documentation for ACSD-50887
• JSON API: /api/v1/patches/ACSD-50887