ACP2E-4300: Changing a customer group in the Admin does not update catalog permissions…

Categories

Customer, Order/Checkout

Components

magento/module-checkout, magento/module-catalog-permissions

Origin

adobe-commerce-support

Since QPT

1.1.81

Issue

Changing a customer group in the Admin does not update catalog permissions on the storefront, causing the catalog and cart to reflect outdated permissions.

Steps to reproduce

1. In Admin, go to Stores > Settings > Configuration. 1. In the left panel, expand Catalog and choose Catalog. Expand Category Permissions. Set Enable to Yes. Set Allow Browsing Category to Yes, for Specified Customer Groups. Select General in Customer Groups. 1. Create a simple product and assign it to a category. 1. Go to Catalog > Categories, select the category, expand Category Permissions, click New Permission, choose the applicable Website and Customer Group as the retailer, and set Browsing Category, Display Product Prices, and Add to Cart to Deny. 1. Create a customer account on the storefront with the default General customer group. 1. Add the product to the cart. 1. Go to Customers > All Customers. Select the customer, set the Actions control to Assign a Customer Group, choose Retailer, and click OK when prompted to confirm. 1. Refresh the cart or proceed to the checkout on the storefront.

Adobe's page lists 2.4.5 - 2.4.8-p5 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-4300. On Cloud, add ACP2E-4300 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-4300/ 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 ACP2E-4300
• JSON API: /api/v1/patches/ACP2E-4300