This fix, prevents the “Browse to find or drag image here” button to disappear when an image is added in a multiple files image form element. Previously, the sprintf function was incorrectly used with an extra argument, which did not cause any major issues but was not the correct usage. The system now correctly handles empty LESS files during static content deployment, displaying an “LESS file is empty” error message.
- Previously, the checkbox text was displayed in plain text format, ignoring any HTML tags used.
- It covers the onboarding process, the available optimization opportunities and how to auto-optimize at edge.
- Previously, applying certain filters and attempting to export the grid data would result in a failure and an exception being thrown.
- Businesses using Adobe Commerce have reported an increase in average order values, with some cases seeing a growth of up to 12%.
- Previously, running the re-index command resulted in a “Catalog Search index process error during indexation process” error when PHP was compiled with certain versions of libxml.
The system now updates the widget content on a CMS page when a product is set as new and saved, ensuring that the page displays the updated product collection. Regular price is now being displayed on product listing pages for configurable products that have children products with special price. Previously, changing the currency in the frontend did not affect the currency code displayed in the New Product widget.
Default values now sets properly for date and date and time attributes via RestAPI Previously, before this fix, when a customer creates a credit memo from an API request notifying https://best-adobe-commerce-cloud-agencies.com/ send_email, it does not contain the product details grid. After the fix, the async and sync product save rest api operations fail with relevant exception message. Async and sync operations previously failed due to product save errors if sku is missing from payload. The API endpoint is now functioning as intended after the problem with the ID key missing from the API payload has been resolved.
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. Checkout payment page will now retain the selected billing address when address search is enabled. Previously, making parallel requests to add the same product to the cart on Storefront would result in multiple line items for the same SKU. Previously, the system would save a new address each time an order placement attempt was made, regardless of whether the order was successfully created or not. Default shipping address is now being selected event in context of enabled address search. Previously, making parallel requests to add the same product to the cart via the REST API would result in multiple line items for the same SKU.
Level Up Your SEO Skills With Our Free Training
Previously, the authorization transaction was not appearing in the Transaction tab after clicking the “Authorize” button, and no new transaction of type “Authorization” was created. ‘We can now update custom-created order statuses, whereas previously, the status could only be changed if the current status was either “processing” or “fraud.” Previously, the system failed to include multiline translation phrases from JavaScript files and phrases from .phtml files in the translation file, leading to incomplete or incorrect translations. Previously, these buttons were incorrectly floating to the left side of the sticky header. Previously, attempting to add or edit an address without a displayed region field would result in an exception error. Previously to this fix, when rest api /rest/default/V1/products/base-prices was called, the increment id was increased wrongly leaving a gap between values.
The system now ensures that the collections for shipments and credit memos are not pre-loaded when retrieved from an order, allowing for additional filters or orders to be applied to these collections. Previously, when saving a CMS page with an updated design layout, it did not reflect appropriately on the front end. Product videos will now render properly on configurable product details page, if the URL contains selected options. In cases where attributes had a lot of options this resulted in a lengthy and resource consuming operation. After the fix, these buttons now function consistently, even after manual selection, ensuring that all products are properly selected or unselected. Previously, the “Select All”/“Unselect All” buttons for related products didn’t work correctly if a product was manually selected.
This ensures brand consistency and coherent product information for LLMs crawling the internet for your products. Because the enrichment is written directly to your Adobe Commerce catalog, it propagates automatically to all channels that use your commerce catalog as their source of truth; including multiple storefronts, advertising pipelines and any direct LLM product feeds. Yes, human visitors will see the updated product name and description on the storefront, along with all other channels that source from your Commerce catalog. The result is that your product is less likely to be cited when a shopper asks a relevant question, even if your product is the best match for their need. This ensures that every surface where your product appears communicates consistent and high-quality information. A confirmation dialog shows the selected products and the changes being applied.
Allowing Adobe Brand Visibility to access public pages
The system now displays only one validation error message when the ‘Add to Cart’ button is clicked without selecting any checkbox options for a bundled product. Previously, navigating back to the shipping page from the payment page sometimes resulted in an error when trying to teardown the Braintree PayPal components. Previously, attempting to ship to an address from a different country would result in console errors, despite no visible errors on the frontend. Previously, customers were unable to save new payment methods across different websites and were presented with an authorization error message. The system now allows customers to save new card or PayPal account information across multiple websites without encountering authorization errors. Previously, applying certain filters and attempting to export the grid data would result in a failure and an exception being thrown.
Research Assistant III Phil Marlor, hailing from Frontier enjoys watching movies like Topsy-Turvy and Gunsmithing. Took a trip to The Sundarbans and drives a Mustang.