QUALITY PATCH

ACSD-69129: Deleting the default base website and using the secondary website as the default…

Deleting the default base website and using the secondary website as the default, results in an error when attempting to update the tier price for the secondary website via REST API. Quality patch ACSD-69129 for magento/module-catalog applies to Magento Open Source and Adobe Commerce 2.4.5 to 2.4.8-p5.

Categories: Catalog/Product
Components: magento/module-catalog
Origin: adobe-commerce-support
Since QPT: 1.1.76

Issue

Deleting the default base website and using the secondary website as the default, results in an error when attempting to update the tier price for the secondary website via REST API.

Steps to reproduce

1. Log in to Admin panel. 1. Set Catalog Price Scope = Website. 1. Create a new website/store/storeview. 1. Set Set as default for the newly created website. 1. Clear the cache. 1. Create a new product. Assign it only to the second website. 1. Send a REST API request to set the tier price for second website. 1. The result should be an empty array with a 200 response. 1. In the Admin, delete Main Website. 1. Send a REST API request to set the tier price for the second website.

Adobe's page lists 2.4.5 - 2.4.6-p13, 2.4.8 - 2.4.8-p3 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 ACSD-69129. On Cloud, add ACSD-69129 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-69129/ 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.