ACP2E-5009: The data patch that migrates Magento Open Source category and product dates to Content…
The data patch that migrates Magento Open Source category and product dates to Content Staging scheduled updates in Adobe Commerce creates empty scheduled updates for categories, skips all product dates when empty date values remain from a previous run, and makes setup:upgrade very slow on catalogs with many categories and store views. Quality patch ACP2E-5009 for magento/module-catalog-staging applies to Magento Open Source and Adobe Commerce 2.4.5 to 2.4.9. Adobe lists the fix as scheduled for 2.4.10.
Source: Adobe Experience League
- Categories
- Content, Performance
- Components
- magento/module-catalog-staging
- Origin
- adobe-commerce-support
- Since QPT
- 1.1.84
Issue
The data patch that migrates Magento Open Source category and product dates to Content Staging scheduled updates in Adobe Commerce creates empty scheduled updates for categories, skips all product dates when empty date values remain from a previous run, and makes setup:upgrade very slow on catalogs with many categories and store views.
Steps to reproduce
Migration from Magento Open Source: 1. On Magento Open Source, set Schedule Update From and To in the Schedule Design Update section of several categories. Leave To empty on some of them, and use both past and future dates. 1. On several products, set a Special Price with Special Price From and To in Advanced Pricing, and set Set Product as New From and To, using both past and future dates. 1. Install Adobe Commerce on this Magento Open Source database and run bin/magento setup:upgrade. 1. Go to Content > Content Staging > Dashboard and check the scheduled updates created for the categories and products. Open the categories and products and check their Scheduled Changes box. 1. Run the data patch again: remove it from the patch_list table (see Prerequisites), run bin/magento setup:upgrade, and check var/log/exception.log. Performance: 1. On Adobe Commerce, create 180 store views and 8,000 categories. 1. Run time bin/magento setup:upgrade and record the elapsed time. 1. Remove the data patch from the patch_list table (see Prerequisites) and run time bin/magento setup:upgrade again.
Adobe's page lists 2.4.5 - 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-5009. On Cloud, add ACP2E-5009 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-5009/ 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.10
- Magento Open Source
- —
- Adobe Commerce
- 2.4.9, 2.4.8-p5, 2.4.8-p4, 2.4.8-p3, 2.4.8-p2, 2.4.8-p1, 2.4.8, 2.4.7-p10, 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-p15, 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-p17, 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
- vendor/magento/module-catalog-staging/Setup/CatalogProductSetup.php
- vendor/magento/module-catalog-staging/Setup/Patch/Data/MigrateCatalogProducts.php
