The system now ensures that header processing is only executed once and only if the header value passes validation, enhancing security and preventing potential vulnerabilities. The system now correctly handles database update operations while mview update is running in background, preventing the occurrence of ‘Base table or view not found’ errors. Earlier Customer grid was updated instantly but after the fix Customer grid is updated after cron run but not reflect instantly. Previously, the calculation of image dimensions could result in float numbers, which when implicitly rounded, would cause an error.
Previously, the status message for the maintenance mode command was displayed as “active” or “not active”, which could lead to confusion. Fixed the issue where removing gift wrapping from a cart item using the updateCartItems mutation did not work as expected. Now, when a new coupon invalidates the existing one, the mutation correctly returns the cart with the valid coupon applied. The error message has been removed to improve the storefront UX, ensuring customers can still view their past returns. Fixed the issue where the customer query returned an internal server error when a deleted custom attribute still had a stored value.
As part of the Adobe Commerce 2.4.9 platform updates, all Symfony dependencies have been updated to the latest Symfony LTS 7.4 versions. This migration ensures Adobe Commerce remains compliant with open-source licensing, avoids known TinyMCE 6 vulnerabilities, and delivers a modern, supported editing experience for merchants and developers. This update enhances cache performance and maintainability, and ensures long-term compatibility with https://best-adobe-commerce-cloud-agencies.com/ PHP 8.x and future platform updates. This resolves prior dependency conflicts and ensures a stable, supported stack for functional testing.
- Image upload for configurable product will now work as expected when inventory module is used.
- Previously, if the second or third column of the main menu contained only one group of links, the title of the group was not displayed.
- SAP has released patches to address a maximum-severity security flaw impacting Commerce Cloud (Data Hub Adapter) that could result in arbitrary code execution.
- This migration ensures Adobe Commerce remains compliant with USPS standards, improves system reliability, and future-proofs shipping integrations for merchants.
- Previously, an incorrect type error was thrown when encountering an empty LESS file during deployment.
Purchase orders
Previously, the “Using Default value” message was not displayed, leading to confusion about the status of the selected theme. Previously, for guest user gift-registry items, when returned from the email function, generated an empty blank address, which is incorrect for placing an order. The product ‘last updated at’ column from the admin is updated the proper date time while updating the existing products through the REST API. Previously, the page was not updated to show the new product due to the incorrect cache identities used for the widget in the cache. Previously, faulty code could result in an option having multiple values for the same store view, causing issues when editing products or attributes.
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. Previously, launching a GraphQL query that used GetCustomSelectedOptionAttributes with an integer argument resulted in a type error. The system now correctly handles integer values in the GetCustomSelectedOptionAttributes function when executing a GraphQL query, preventing any type-related errors.
Success message after negotiable quote rename—Adobe Commerce now displays a success message after a negotiable quote or quote template is renamed on the storefront. The system now ensures ADA compliance by removing unsupported CSS properties and replacing them with supported ones in the print.css file. The system now ensures that backend block context is not loaded on the frontend, preventing the creation of unnecessary backend sessions and potential session locks. Previously, the validation would fail even when a file was selected, preventing the form from being submitted. The system now correctly validates the file field in a UI component form, allowing the form to be submitted without error when a file is selected. The system now correctly recognizes JSON column types in the database schema during integration tests, preventing test failures due to a mismatch between the database schema and the declarative schema.
Structural Engineer Standford Rewcastle, hailing from Manitou enjoys watching movies like Nömadak TX and Couponing. Took a trip to Quseir Amra and drives a Mercedes-Benz 540K Special Roadster.