ACSD-52287: The status of archived orders does not change from completed to closed on grid…
The status of archived orders does not change from completed to closed on grid after the credit memo was submitted. Quality patch ACSD-52287 for magento/module-sales-archive applies to Magento Open Source and Adobe Commerce 2.3.7 to 2.4.6-p15.
- Categories
- Order/Checkout
- Components
- magento/module-sales-archive
- Origin
- adobe-commerce-support
- Since QPT
- 1.1.38
Issue
The status of archived orders does not change from completed to closed on grid after the credit memo was submitted.
Steps to reproduce
1. Configure Asynchronous Indexing. * On the Admin sidebar, go to Stores > Settings > Configuration. * In the left panel, expand the Advanced section and choose Developer underneath. * Expand the Grid Settings section. * Set Asynchronous indexing to Yes. * Click Save Config. 1. Configure the Order Archive. * On the Admin sidebar, go to Stores > Settings > Configuration. * In the left panel, expand the Sales section and choose Sales underneath. * Expand the Orders, Invoices, Shipments, Credit Memos Archiving section. * Set Enable Archiving to Yes (Leave rest of the configurations as default). * Click Save Config. 1. Place an order in the frontend. 1. Run the cron for order to appear in the Admin Order Grid. 1. Invoice and Ship the order to update the order status to Complete. 1. Run the cron to update the Sales Order Grid with the latest order status. 1. Archive the order. 1. Go to the Archived order grid. 1. Open the archived order and refund the order offline by creating a Credit Memo to make the Order status: Closed. 1. Run the cron for a few times. 1. Check the Archived order grid for the new order status.
Adobe's page lists 2.3.7 - 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-52287. On Cloud, add ACSD-52287 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-52287/ 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.3.7 <2.4.7
- Magento Open Source
- —
- Adobe Commerce
- 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, 2.4.4-p18, 2.4.4-p17, 2.4.4-p16, 2.4.4-p15, 2.4.4-p14, 2.4.4-p13, 2.4.4-p12, 2.4.4-p11, 2.4.4-p10, 2.4.4-p9, 2.4.4-p8, 2.4.4-p7, 2.4.4-p6, 2.4.4-p5, 2.4.4-p4, 2.4.4-p3, 2.4.4-p2, 2.4.4-p1, 2.4.4, 2.4.3-p3, 2.4.3-p2, 2.4.3-p1, 2.4.3, 2.4.2-p2, 2.4.2-p1, 2.4.2, 2.4.1-p1, 2.4.1, 2.4.0-p1, 2.4.0, 2.3.7-p4, 2.3.7-p3, 2.3.7-p2, 2.3.7-p1, 2.3.7
- vendor/magento/module-sales-archive/Observer/ArchiveGridAsyncUpdateObserver.php (added)
- vendor/magento/module-sales-archive/etc/adminhtml/events.xml
