Candles
Standardized the order_id input in mutations and updated the order cancel confirmation email template to expose increment id instead of order id. Fixed an issue where the setShippingAddressesOnCart mutation returned an error when using pickup_location_code without specifying customer_address_id or address. Resolved an issue where the addProductsToCart mutation returned a ‘PRODUCT_NOT_FOUND’ error when using SKUs with different casing. Fixed an issue where fetching a cart containing a bundled product with the only_x_left_in_stock field in the GraphQL query resulted in an internal server error.
Run a complete smoke test from the storefront and, if possible, place a controlled test order. For Adobe Commerce on Cloud, follow your normal Git-based workflow and promote the tested build through the appropriate environments. If your store contains heavily customized functionality, consider performing automated tests as well as manual testing. Adobe Commerce stores frequently contain integrations that modify checkout, catalog, customer, payment, or order functionality. The exact commands required can depend on your deployment architecture and the type of security update being installed. This information helps your development team select the correct security update and identify compatibility risks.
This PR enhanced the cache_invalidate log to include request context and stack trace for full cache purges, improving debugging and visibility.This helps identify the source of unexpected full cache invalidations without changing existing functionality. This PR fixes and log the plugin who are actually undeclared and not used (enabled and missing instance). This prevents unused CSS from being bundled in Community Edition, reducing unnecessary payload and eliminating dead style rules while ensuring proper styling when Commerce modules are enabled. This PR fixes a bug in which multiple concurrent processes spin up to handle the same theme package, depending on how the themes are defined with their parents. The system Magnifier functionality should keep working the way it worked before and magnifierOptions should not be available https://best-adobe-commerce-cloud-agencies.com/ in global scope
- Adobe strongly recommends installing the latest security patches as soon as possible to minimize security risks.
- As the first release under Adobe’s new annual cadence, and a major release with three framework component replacements, it still carries higher compatibility risk than a standard patch release.
- Fast search with accurate results reduces bounce rates and increases order value.
- The new approach separates security from functionality.
- Cyber threats continue to evolve, and attackers often target businesses running outdated software with known vulnerabilities.
Magento 2 Composer and Dependency Management: Patches, Lock Files, and Safe Upgrades in 2026
The system now automatically cleans up the cron_schedule database table, removing entries for jobs that no longer exist in the system. Previously, the date picker was only displayed for the first date field, leaving the remaining fields without a date picker. The system now correctly displays the date picker for all date fields when configuring a product with multiple customizable date options in the admin order creation process.
The system now includes a separate column to display the “Using Default value” message depending on the selected theme in the design configuration page. The system now correctly displays banner images uploaded in newly created folders in the Pagebuilder gallery, eliminating previous console errors. Previously, the acl.xsd file contained a typo and incorrect grammar which could potentially cause confusion. Previously, the price of out-of-stock simple products was not displayed in the “Recently Viewed Product” widget due to a condition in the price loading templates. After the fix configurable products that have child products with long names will not be missed in the storefront.
After the fix, the async and sync product save rest api operations fail with relevant exception message. The issue has been fixed by ensuring correct database entries for the customizable options for a non-default store. The system now supports scope authorized access for REST API admin tokens and Magento_Sales endpoints, ensuring that the REST API only displays orders that admin has access to.
PCI compliance at risk — running PHP 8.1 past its end-of-life date means security vulnerabilities in PHP may not receive fixes, which puts PCI compliance at risk. As a result of decommissioning, all data and assets within the hosted ecommerce environment, including all instances, environments, and branches, will be permanently deleted and cannot be restored. Running unsupported dependency versions may result in a security vulnerability on your Cloud instance that Adobe is unable to resolve.
Accountant III Annadiane Kesey, hailing from Lakefield enjoys watching movies like “Spiders, Part 2: The Diamond Ship, The (Die Spinnen, 2. Teil – Das Brillantenschiff)” and Sketching. Took a trip to Church Village of Gammelstad and drives a Bentley 4 Litre “The Green Hornet”.
Diffusers