The MDVA-33106 Magento patch fixes the issue where the rescheduled product changes are erased after the cron
bin/magento cron:run command is executed. This patch is available when the Magento Quality Patch (MQP) tool 1.0.13 is installed. Please note that the issue is scheduled to be fixed in Magento 2.4.2.
Affected products and versions
The patch is created for Magento version:
Magento Commerce Cloud 2.3.5-p2.
Compatible with Magento versions:
Magento Commerce and Magento Commerce Cloud 2.3.0-2.4.1.
Note: the patch might become applicable to other versions with new MQP tool releases. To check if the patch is compatible with your Magento version, run
Steps to reproduce:
- In Magento Admin, go to Catalog > Products and click edit. Notice the Price value, for example 9.99.
- Click Schedule New Update and fill in details:
- Update name is not important.
- Set a date in the future, +1 year for start date and end date.
- Set Price to 1.99.
- Save changes.
- Go to the Content staging dashboard and select grid view to see if scheduled match above.
- Select edit action next to the scheduled update. Data should still match above.
- Change the scheduled date to something closer. Instead of +1 year from now change it to + 1 week or + 1 month.
- Save changes and check if the dates are updated on staging dashboard.
- Wait for a cron job to run.
- Click edit again in the scheduled change and check the price.
Price is 1.99.
Price is 9.99.
Apply the patch
For instructions on how to apply an MQP patch, use the following links depending on your Magento product:
- Magento Commerce: DevDocs Apply patches using Magento Quality Patches Tool.
- Magento Commerce Cloud: DevDocs Upgrades and Patches > Apply patches.
To learn more about Magento Quality Patches, refer to:
- Magento Quality Patches released: a new tool to self-serve quality patches.
- Check if patch is available for your Magento issue using Magento Quality Patches.
For info about other patches available in MQP tool, refer to the Patches available in MQP tool section.