aem-boilerplate-commerce README md at main wfranksadobe aem-boilerplate-commerce

Fixed an issue where gift message sender and recipient fields https://best-adobe-commerce-implementation-partners.com/ were automatically populated with customer names even when no gift message was entered; the fields now remain empty unless the user provides the details. Order State assignment now works as expected.Previously, when assigning custom order statuses, the “Processing” state could disappear from the dropdown after unassigning a status, making it impossible to reassign.AC-15010 When updating the URL key of the product via the REST API, with the “Create Permanent Redirect for URLs if URL Key Changed” setting set to Yes, the product URL rewrites are create a redirect from old URL to a new one.

After this fix, the consumer correctly processes inactive quotes, moves orders from Received to Pending, and adjusts salable quantities as expected. Fixed an issue where the shipping address column in the admin Orders grid did not display the country for international orders. After the fix, the children count remains correct and no longer increments unexpectedly. Fixed an issue where editing an existing scheduled update for a subcategory incorrectly increased the children_count for parent categories in the database. Fixed issue where the order_date field in GraphQL response returned in yyyy-mm-dd format.Now, the order_date is displayed correctly in dd-mm-yyyy format.

The system now saves a new customer address only once if the order failed to be created, preventing the creation of multiple identical addresses in the event of order placement errors. Previously, the discount code/coupon input was disabled, and the button title text displayed as “Cancel coupon”, preventing users from applying discount codes. Previously, the discount amount could vary incorrectly when cart items changed, sometimes resulting in significantly larger discounts than expected.

Previously, email was not sent to customers after successfully updating their email addresses on their accounts. Fixes the issue where concurrent calls to the Reorder GraphQL API result in the same products being added as different rows, leading to data inconsistencies. Fixed issue where field validation on the credit memo page prevented submission even after required custom fields were filled.Now, validation works correctly and the submit button is enabled once all mandatory fields are completed. It improves reliability and developer experience, especially in testing scenarios and long-running processes where glob results must stay up to date. This PR update introduces a way to clear the internal static cache used by \Magento\Framework\Filesystem\Glob, ensuring fresh and accurate results when file structures change. This PR fixes and log the plugin who are actually undeclared and not used (enabled and missing instance).

Administrators can now manage multiple companies from a single account using the storefront company switcher. Company Status fields in GraphQL—The Company.profile GraphQL query now returns Company Status fields. Performance with multiple stores and websites—Improved the performance of the Magento\Store\Model\System\Store class, reducing overhead for merchants running many stores and websites. Multi-site Company GraphQL queries with X-Adobe-Company—Merchants no longer receive an authorization error when including the X-Adobe-Company header in Company GraphQL queries in a multi-site setup.

Previously, the sales rule indexer would fail to complete when there were a large number of combined filter groups, leading to an error message and preventing the application of cart rule conditions. The system now successfully completes the sales rule indexer even with a large number of combined filter groups, ensuring that cart rule conditions are applied to the cart as expected. Previously, once a default was set for a product attribute, there was no way to deselect it, resulting in the attribute always having a default set. Previously, clicking the fetch button would incorrectly create a new payment transaction for an order that had already been paid. Earlier Papal payflow Credit card details saved for later use was not showing up on stored payment method page which is now fixed credit card details are showing up on stored payment method page.

Payment Services now displays descriptions and billing addresses for vaulted cards on the checkout page, giving customers more visibility into their saved payment methods. Payment Services now supports 3D Secure authentication with Google Pay, enhancing security for merchants and customers during payment transactions. Payment Services no longer allows orders to be created from empty quotes. Now, merchants can copy data from the dashboard grids by selecting the content of a single cell.

This enhancement reduced the number of records created in the price index by reducing eSKU multiplication that resulted from shared catalogs. It contains quality and security fixes from prior patch release and security fixes created between the prior full patch release and the security patch release. Merging JavaScript files now works correctly when multiple stores are configured.Previously, files sometimes failed to merge properly in multi-store setups, leading to incomplete or inconsistent results. Previously, when sending an email template for a gift card after an invoice was created from a different store, the owner’s name in the admin configuration settings would not be reflected in the email headers when the customer received the email. Fixed an issue where orders could be placed using a disabled payment method via GraphQL.Now, an error is returned when attempting to set or use an unavailable payment method, preventing the order from being created. The system now adds only the selected products, allowing orders to be created without any unexpected items.