Cloud Patches for Commerce

Enhanced QPT CLI wizard/output—Added a warning to the QPT CLI wizard/output that reminds you to verify patch details and requirements if there are dependencies.

Added patches for Commerce 2.4.6:

• Fixed the regexp cache tag validation.
• Improved performance by reducing the number of times the same deployment configurations load.

Added patches for Commerce 2.3.7 to 2.4.6—Fixed an issue that caused an increment by a random value instead of an increment by 1 for the catalog_product_entity_* tables.

Added patches for Commerce 2.4.0 to 2.4.6—Fixed an error stating that The file can't be deleted. Warning!unlink: No such file or directory, which occurred when flushing JS/CSS cache from the Admin.

Fixed an issue caused by applying the B2B Layered navigation patch—For customers that have applied the B2B Layered navigation patch, this fix resolves an Undefined offset error that displays on the Search page after switching the Store view.

Paypal Checkout patch—Fixes an Adobe Commerce 2.3.7 issue with PayPal Express where the previously placed order price is displayed.

Patch category support—Added support for processing patch categories and origin sources assigned to Quality Patches. The categories allow customers to use filters and sorting to find patches more quickly when using the Quality Patches Tool and the Site-wide Analysis Tool (SWAT).

Redis patches for Adobe Commerce 2.3.0 to 2.3.5, 2.4.0—Updated the Redis patches to support adding products to a category when implementing a Level 2 cache.

Braintree VBE patch—Fixes an issue that generated an error when an Administrator tried to view a Braintree Settlement Report.

Now, the ece-patches apply command uses the Unix patch command to apply patches if Git is not available on the host system.

Redis patches for Adobe Commerce 2.3.0 - 2.3.4—Optimize communication and improve performance

• Reduce size of network transfers between Redis and Adobe Commerce
• Fix race conditions on Redis load and write operations
• Rewrite base cache adapter to handle errors on save
• Decrease Redis CPU consumption

Redis patches for Adobe Commerce 2.3.0 - 2.3.5—Improve performance and fix errors

• Fix the Cache lock implementation to prevent infinite locks
• Improve the current locking mechanism
• Implement signed locks to prevent unlock from parallel requests
• Fix the following error that occurs on Redis write operation: OOM command not allowed when used memory > maxmemory
• Fix processing for clean cache by cat_p tag that runs during product updates

Fixed an issue that caused an error when applying the required amzn/amazon-pay-module patch to Adobe Commerce on cloud infrastructure projects with Adobe Commerce v2.2.6 or 2.3.5, which do not include this module. Now, the patching process skips the amzn/amazon-pay-module patch if the module is not installed.

Redis performance improvements—Adds Redis optimization features to Adobe Commerce versions 2.3.3 and 2.3.4. These fixes were included in the Adobe Commerce version 2.3.5 release.

New Relic log enricher—Adds the Monolog ProcessorInterface required to support improvements to New Relic logging capabilities introduced in Cloud Components of Commerce version 1.0.4. This patch is required to deploy Adobe Commerce 2.1.x. If the patch is not applied, the build fails during the di:compile process.

Amazon Pay checkout—Fixes an issue with the Amazon Pay payment widget that prevented customers from changing the payment method on the Review & Payments step during the checkout process.

Product display on Category page—Fixes an issue that prevented products from displaying on the category page in Show all pages view.

Page Builder image upload—Fixes a Page Builder interface issue that sometimes caused the following error when uploading images to the image gallery: Destination folder is not writable or does not exist

Suppress unnecessary sitemap generation warnings—Adds a retry attempt when errors occur during sitemap generation and skips customer email notification in cases where errors can be recovered automatically.

Site performance improvement—Fixes a performance issue with the Magento\Framework\App\DeploymentConfig\Reader::load function, which periodically experienced long load times that affected site performance.

Updated patch assignment for payment method patches to target the payment modules instead of the Magento base package (magento/magento2-base) so that the payment patches are applied only if the payment modules exist.

Updated patches for compatibility with Magento Open Source.

Compatibility updates for magento/magento-cloud-patches

• Updated the symfony and semver version constraints in the composer.json file for compatibility with Adobe Commerce 2.4 and later releases.

• Updated constraints in composer.json for compatibility with ece-tools 2002.0.22 and later 2002.0.x releases.

PayPal Express Checkout—Published on February 12, 2020, this patch resolves an issue that affects orders placed with PayPal Express Checkout where the shipping address for the order specifies a country region that has been manually entered into the text field rather than selected from the drop-down menu on the Shipping page. See the complete patch description on the patch download page.

Application deployment fix—Added a patch to fix an issue that disabled the full page cache during the deployment process. This patch applies to Adobe Commerce 2.3.2 and later releases.

Scope parameter for Async/Bulk API—Updated this patch to fix a syntax error in the composer.json file. This patch applies to Magento Open Source 2.3.1 and 2.3.2. See the complete patch description on the patch download page.

Fix cron deadlocks and improve cron locking—

• Fixes an issue with some cron jobs not running due to an incorrect status value in the cron_schedule table. Now, we use the Adobe Commerce lock framework to check and update cron job status instead of using the cron_schedule table. Cron jobs that have ended with an error status are retried during the next cron run instead of waiting 24 hours.

• Adds a retry operation to avoid deadlock during updates to the data in the cron_schedule table.

Updated magento/magento-cloud-patches to include all available patches for Magento Open Source 2.x—Updated the magento/magento-cloud-patches package to include all Magento Open Source 2.x patches available on the software downloads page. If you copied any Magento Open Source patches into your Adobe Commerce on cloud infrastructure project previously, remove them to avoid conflicts.

Elasticsearch catalog pagination fix —Replaced the Elasticsearch catalog pagination patch delivered in magento/magento-cloud-patches v1.0 with a more effective fix.

Page Builder patches—In Cloud Patches for Commerce 1.0.0, we bundled Page Builder patches to address a known Page Builder remote code execution (RCE) vulnerability, with the initial fix based on Adobe Commerce 2.3.3. We have updated these patches with a more stable implementation based on Adobe Commerce 2.3.4., which includes multiple optimizations for fixing the issue.

If you have the magento/magento-cloud-patches 1.0.0 package, you are still protected from the Page Builder RCE vulnerability issues. If you update to 1.0.1 or later, you have a better implementation of the same fix.

Page Builder security patches for 2.3.1.x and 2.3.2.x releases—Fixes an issue in Page Builder preview that allows unauthenticated users to access some templating methods that can be used to trigger arbitrary code execution over the network (RCE) resulting in global information leaks. This issue can occur when using unsupported versions of Page Builder with Adobe Commerce versions 2.3.1 and 2.3.2.

MSI patches—Fixes issues that caused indexing errors and performance issues when using default inventory settings for managing stock.

Backward Compatibility of new Mail Interfaces-Fixes a backward incompatibility issue caused by the Magento\Framework\Mail\EmailMessageInterface PHP interface introduced in Adobe Commerce v2.3.3. In the scope of this patch, the new EmailMessageInterface inherits from the old MessageInterface, and Adobe Commerce core modules are reverted to depend on MessageInterface.

Catalog pagination does not work on Elasticsearch 6.x—Fixes a critical issue with search result pagination that affects customers using Elasticsearch 6.x as the catalog search engine.