Magento Open Source 2.4.2 release notes

Last update: November 25, 2024

CREATED FOR:

  • Experienced
  • Admin
  • Developer

Magento Open Source 2.4.2 introduces enhancements to performance and security plus significant platform improvements. Security enhancements include expansion of support for the SameSite attribute for all cookies. Elasticsearch 7.9.x and Redis 6.x are now supported.

This release includes over 280 new fixes to core code and 35 security enhancements. It includes the resolution of almost 290 GitHub issues by our community members. These community contributions range from minor clean-up of core code to significant enhancements in GraphQL.

All known issues identified in 2.4.1 have been fixed in this release.

NOTE
Adobe Commerce releases can contain backward-incompatible changes (BICs). To review backward-incompatible changes, see BIC reference. Major backward-incompatible issues are described in BIC highlights. Not all releases introduce major BICs.

Apply AC-3022.patch to continue offering DHL as a shipping carrier

DHL has introduced schema version 6.2 and will deprecate schema version 6.0 in the near future. Adobe Commerce 2.4.4 and earlier versions that support the DHL integration support only version 6.0. Merchants deploying these releases should apply AC-3022.patch at their earliest convenience to continue offering DHL as a shipping carrier. See the Apply a patch to continue offering DHL as shipping carrier Knowledge Base article for information about downloading and installing the patch.

Security patch available

Merchants can now install time-sensitive security fixes without applying the hundreds of functional fixes and enhancements that a full quarterly release provides (for example, 2.4.1-p1). Patch 2.4.0.12 (Composer package 2.4.1-p1) is a security patch that provides fixes for vulnerabilities that have been identified in our previous quarterly release, 2.4.1. All hot fixes that were applied to the 2.4.1 release are included in this security patch. (A hot fix provides a fix to a released version that addresses a specific problem or bug.)

For general information about security patches, see Introducing the New Security Patch Release. For instructions on downloading and applying security patches (including patch 2.4.1-p1), see Quick start on-premises installation. Security patches include security bug fixes only, not the additional security enhancements that are included in the full patch.

Other release information

Although code for these features is bundled with quarterly releases , several of these projects (for example, Progressive Web Applications (PWA) Studio) are also released independently. Bug fixes for these projects are documented in the separate, project-specific release information that is available in the documentation for each project.

Highlights

Look for the following highlights in this release.

Substantial security enhancements

This release includes over 35 security fixes and platform security improvements. All security fixes have been backported to 2.4.1-p1 and 2.3.6-p1.

Over 35 security enhancements that help close remote code execution (RCE) and cross-site scripting (XSS) vulnerabilities

No confirmed attacks related to these issues have occurred to date. However, certain vulnerabilities can potentially be exploited to access customer information or take over administrator sessions. Most of these issues require that an attacker first obtains access to the Admin. As a result, we remind you to take all necessary steps to protect your Admin, including but not limited to these efforts: IP allowlisting, two-factor authentication, use of a VPN, the use of a unique location rather than /admin, and good password hygiene. See Adobe Security Bulletin for a discussion of these fixed issues.

Additional security enhancements

Security improvements for this release include:

  • All core cookies now support the SameSite attribute.

  • The application now displays messages that identify potentially malicious content in product and category description fields when the user tries to save values in these fields.

  • File system operations across components have been standardized and hardened to prevent malicious uploads.

  • Core Content Security Policy (CSP) violations have been fixed.

NOTE
Starting with the 2.3.2 release, we will assign and publish indexed Common Vulnerabilities and Exposures (CVE) numbers with each security bug reported to us by external parties. This allows users to more easily identify unaddressed vulnerabilities in their deployment. You can learn more about CVE identifiers at CVE.

Infrastructure improvements

This release contains enhancements to core quality, which improve the quality of the Framework and these functional areas: Customer Account, Catalog, CMS, OMS, Import/Export, Promotions and Targeting, and Cart and Checkout.

Platform enhancements

  • Elasticsearch 7.9.x is now supported. Although we recommend running Elasticsearch 7.9.x, version 2.4.x remains compatible with Elasticsearch 7.4.x.

  • 2.4.2 has been tested with Varnish 6.4. Version 2.4.x remains compatible with Varnish 6.x.

  • Redis 6.x is now supported. Version 2.4.x remains compatible with Redis 5.x.

  • 2.4.2 is now compatible with Composer 2.x. We recommend that merchants migrate to Composer 2.x. Although you can install this release using Composer 1.x, Composer 1.x will soon reach end-of-life. For an overview of Composer 2.x features, see Composer 2.0 is now available!

The ability to configure an installation to use a split database has been deprecated in this release. Merchants who currently use split database should start planning to revert to or migrate to a single database or use an alternative approach. See the Deprecation of split database functionality in Magento Open Source DevBlog post for an overview of this issue. See Revert from a split database to a single database for migration instructions.

Performance enhancements

This release includes code enhancements that boost API performance and Admin response time for deployments with large catalogs. Multiple scalability enhancements enable 2.4.2 to natively support complex catalogs up to 20x larger than in previous releases.

Adobe Stock Integration

This release includes Adobe Stock Integration v2.1.1.

GraphQL

This release adds GraphQL coverage for the following features:

  • Added support for comparison lists. Shoppers can create and delete comparison lists, and add and remove items to the comparison lists. In addition, shoppers that create a compare list as a guest can log in as a customer and retain their comparison lists.

  • Added the generateCustomerTokenAsAdmin mutation and updated the Customer object to support remote purchasing assistance.

  • Added localization support across stores to support tasks such as changing languages, carts, and currencies.

  • Added support for unions in GraphQL. GitHub-29425

  • The GraphQL schema has been enhanced to optimize product data retrieval for configurable products with many variants.

  • Integer type object IDs have been deprecated in favor of uid attributes of type ID.

  • Added the staging attribute to the ProductInterface and CategoryInterface to determine if a product is staged and to view its associated campaign information.

See the GraphQL Developer Guide for details on these enhancements.

PWA Studio

This release of PWA Studio includes:

  • Internationalization and localization. Venia now provides support for multiple languages and currencies.

  • Improved extensibility framework to support code changes through extensions.

  • Initial components for My Account related features such as Wishlist, Saved Payments, Address Book, and Order History.

  • Various performance optimizations and bug fixes.

For information about enhancements and bug fixes, see PWA Studio releases. See compatibility for a list of PWA Studio versions and their compatible versions.

New Role Resources for Media Gallery. This release provides merchants the ability to limit administrator access to only the Media gallery and to control who can perform these actions:

  • Insert media assets into content

  • Upload assets

  • Edit assets details

  • Delete assets from the Media Gallery

  • Manage folder structure.

Web-optimized images in content. Merchants can now use web-optimized image rendition in content instead of high resolution images. The original image remains unmodified in the Media Gallery, and the image rendition is dynamically generated when the image is inserted in the content.

Functional Testing Framework (MFTF)

MFTF 3.2.1 is now available. This release introduces error tolerance in both tests and test suite generation. Additional enhancements and bug fixes are described in the Functional Testing Framework Changelog.

Vendor Developed Extensions

See the following articles for updates on features and changes for this release:

AWS S3 support enhancements

Amazon Simple Storage Service (AWS S3) support has been enhanced to include support for:

Fixed issues

We have fixed hundreds of issues in the 2.4.2 core code.

Installation, upgrade, deployment

  • Merchants can now successfully upgrade an Open Source deployment that runs MySQL 8.x to a Commerce deployment. Previously, the application threw an exception when AUTO_INCREMENT values reverted to initial values for all tables where row_id was added during upgrade.
  • The application now displays an error message that identifies the path that was used to create the patch if an error occurs when running bin/magento/setup:db:generate-patch. GitHub-27523
  • block_html, full_page, and layout caches are now disabled as expected after bin/magento/setup:upgrade execution. GitHub-28186
  • The minimum required PHP version in bootstrap.php has been updated. GitHub-30004
  • You can now execute bin/magento/setup:upgrade after installing sample data. Previously, when you tried to execute bin/magento/setup:upgrade, the application displayed this error: unable to apply data patch magento\catalogrulesampledata\setup\patch\data\installcatalogrulesampledata for module magento_catalogrulesampledata. The application also displayed this error in the system log: main.ERROR: Sample Data error: Unable to unserialize value. Error: Syntax error. GitHub-30685
  • You can now set a YouTube API key from the command line as expected. Previously, the applicationreturned this error when you tried to execute bin/magento config:sensitive:set catalog/product_video/youtube_api_key: There are no sensitive configurations to fill.
  • The application now honors the maxMessages values that are defined in queue_consumer.xml. Previously, the applicationused only the deployment configuration values. GitHub-29522
  • URL generation for a new store now works as expected when the store is created using bin/magento setup:config:import. Previously, URL rewrites were not generated in production environments. GitHub-30025
  • The application no longer throws an error when you try to change backend-frontname using the ssh container after installing Magento Open Source. GitHub-26762
  • The application no longer displays this question when you run bin/magento setup:install to connect to existing database: Overwrite the existing configuration for db-ssl-verify?[Y/n]. GitHub-29612

Adobe Stock Integration

  • Added support for reading exif_image.png or exif-image.jpeg metadata. GitHub-1449
  • The content displayed when you click the Default View bookmark for the Media Gallery is no longer filtered. Previously, the default view contained a filter that was applied from url-filter applier. GitHub-1813, GitHub-1789, GitHub-1780
  • Logic has been removed from the WYSIWYG OnInsert controller (Magento\Cms\Controller\Adminhtml\Wysiwyg\Images\OnInsert::execute()) and added to the Model\Wysiwyg\Images\PrepareImage::execute() model. GitHub-1504
  • Area emulation has been removed from the media-content:sync command (\Magento\MediaContentSynchronization\Console\Command\Synchronize::execute). GitHub-1784

Analytics

  • Advanced Reporting now works as expected for multiple environments in the same domain. Previously, CSV files that were generated by Advanced Reporting failed because double quotes were escaped with backslashes rather than with another double quote as required by CSV standard RFC4180.
  • The analytics_collect_data job now runs successfully when using either the default or non-default port to connect to MySQL in env.php. Previously, analytics_collect_data threw an error when you used the non-default port.
  • CSV files that are generated by analytics_collect_data are now properly escaped. Previously, these files were not generated with the correct escaping, which prevented the generation of Inventory reports.

Braintree

  • Shoppers can now use Apple Pay to successfully place an order for virtual products. Previously, the application threw this error: There are no shipping methods available for you right now. Please try again or use an alternative payment method.

  • The default PayPal Express Checkout payment method now works as expected with the Braintree Credit Card payment method. Previously, the application did not display the PayPal button when the Braintree Credit Card payment method was enabled.

Bundle products

  • The application no longer sets prices for fixed-price bundle product child items in quotes.
  • Price sorting now works as expected when bundle products include out-of-stock products. Previously, sorting price in descending order did not display products in order of decreasing price.
  • The application now automatically applies a default quantity of 1 for bundle product options when many options exist. Previously, merchants had to manually assign a default quantity to each option.
  • The order invoice create page now displays the child products for bundle products as expected. GitHub-27350
  • The application now assigns correct product prices when you re-order simple products that are part of a bundle product with a custom price. Previously, setting a custom price on a bundle product resulted in incorrect prices on attached simple products when reordered. GitHub-30343
  • Calling POST /V1/order/{orderId}/ship to ship an order that contains a bundle product now marks the order as complete as expected. Previously, the application displayed this error message: You can't create a shipment without products. GitHub-9762

Cart and checkout

  • The shipping method estimator now works as expected when custom address attributes are present on the shipping step of the checkout workflow. Previously, the application displayed this error message: {"message":"Error occurred during \"custom_attributes\" processing. A custom attribute is specified with a missing attribute code. Verify the code and try again."} GitHub-27505
  • The application now displays the You have no items in your shopping cart message in the mini cart as expected when a shopper removes the only item in their cart. Previously, cart data was not updated for checkout/cart/removeFailed when a shopper removed the single item, and the application displayed this message: 1 product requires your attention.
  • The application no longer displays the cost of shipping for an order for a non-applicable shipping method. Previously, the application displayed a price of 0 for a non-applicable shipping method in the checkout workflow.
  • A customer’s default billing address is now selected when the My billing and shipping address are the same checkbox on the checkout workflow is unselected.
  • Cart contents are no longer lost when a shopper switches from one store to another in a different domain.
  • Shoppers can now successfully complete an order using Check Out with Multiple Addresses when using multiple shipping methods. Previously, the application displayed this error: There has been an error processing your request. GitHub-30197
  • The application now displays the correct default country on the shipping page of the checkout workflow when the shopper changes the store view from the shopping cart.
  • The application now excludes the current session when cleaning up customer sessions after a post-logout password reset when a guest shopper is logged in. Previously, the applicationemptied the shopping cart when the shopper reset their password.
  • The application now displays the correct default country for a store view when a shopper changes the store view in the shopping cart. Previously, when the store view was changed in the cart, the default country was incorrect.
  • Redundant calls to the /rest/V1/guest-carts/cart_id/totals-information endpoint on the cart have been removed, which has improved cart performance. Previously, when a shopper added a product to the cart and then subsequently viewed the cart, the application called the collectAddressTotals method multiple times.
  • The application no longer displays the Region field for a country in the checkout workflow when the Allow to Choose State if It is Optional for Country setting is disabled. GitHub-30747
  • The application no longer repeats a shipping address in the storefront checkout workflow when an order is re-ordered from the Admin.
  • Corrected problems with the design of AdminMediaGalleryInsertLargeImageFileSizeTest.
  • All new records in the quote table for guests are now assigned a value of 1 in the customer_is_guest field. Previously, for each new guest who added a product into cart, the record was assigned a 0 in thequote.customer_is_guest field.
  • The Submit button on the Review & Payments section of the checkout workflow has been moved to inside <form id="purchaseorder-form"...></form>, which makes implicit form submission possible without altering any JavaScript. GitHub-27925
  • The application no longer displays the Region field on the checkout workflow when the Allow to Choose State if It is Optional for Country setting is disabled. GitHub-30747
  • The application now correctly updates a cart’s item subtotal when a shopper clicks Update Shopping Cart while checking out with multiple addresses. GitHub-30408
  • The application no longer throws an exception when config.xml nodes exist for payment methods that are not currently installed. Previously, the application threw an exception during checkout. GitHub-29555
  • The application now renders product names that contain special characters correctly in the mini cart. GitHub-29075
  • The application now sets the correct discount package for table rate. Previously, the application did not apply a cart rule that set a discount on the cart when it calculated table rate. GitHub-30169

Cart price rule

  • Cart price rules are now applied as expected when order subtotals are calculated without incorporating tax. The new Subtotal (Incl. Tax) option has been added as a cart price rule condition.
  • Applying a price rule with a coupon using GraphQL now works as expected when the Fixed amount discount for whole cart action is used.

Catalog

  • The application now displays all re-enabled products in the storefront as expected. Previously, when a product was disabled and then re-enabled, the application did not display the product until the Varnish page cache was cleared or the store re-indexed because the page cache was not invalidated after re-enabling a product.
  • Partial re-indexing of large catalogs now works as expected. Previously, products randomly disappeared from the storefront category page during re-indexing with the catalogsearch_fulltext partial indexer.
  • Shoppers can now re-order an invoiced order of a product with customizable options as expected. Previously, the application threw this error when a shopper tried to re-order: {"0":"The product's required option(s) weren't entered. Make sure the options are entered and try again.
  • You can now successfully set the Layout setting on the Category Design page to No layout updates. Previously, the applicationreverted to Category - FullWidth when you assigned the No layout updates value.
  • Problems with product sort order on the storefront have been resolved. Previously, when the application indexed product prices, it occasionally set a configurable product’s min_price and max_price to 0 in the catalog_product_index_price table, which affected price sort order on the storefront.
  • The application now successfully updates attributes that are labeled Product Type. Previously, because the product_type attribute was reserved in the code, the application displayed this message when you tried to update a Product Type attribute: An attribute with the same code (product_type) already exists.
  • The application no longer changes the position of an uploaded video in the Images and Videos section of the product details page when you save the product. Previously, the new image position was assigned an index value (position in the list) and if existing image positions were not aligned with their indices values, the new image was misplaced in the list.
  • The Add to Cart functionality now works as expected whenever the Add to Cart button is available to click. Previously, if you clicked this button multiple times while waiting for a product page to load, the application threw this error: Invalid Form Key. Please refresh the page.
  • The application no longer flushes category cache when a merchant adds or removes disabled products to or from a category. Previously, the applicationflushed the cache for related categories despite product status. Categories were also unassigned when a category was saved, which led to flushing of category cache.
  • Catalog product filtering within the All store view scope now works correctly. Previously, products with a status of either Enabled or Disabled were displayed in the grid while filtering only enabled or disabled products.
  • Partial re-indexing no longer results in missed products and empty categories.
  • Re-order now works as expected when Use JavaScript Calendar is enabled (Stores > Configuration > Catalog > Date & Time Custom Options). Previously, when this setting was enabled, the application displayed this error when you tried to re-order the previously placed order from the Admin: Please specify date required option(s).
  • The application now displays the correct currency in multi-site deployments during tier price creation.
  • Product image custom attributes are now correctly escaped. The data-src attribute has the same value as src attribute, as expected. Previously, URL special symbols were escaped.
  • Updating a category through the REST API no longer disables the Use Default Value setting on the Enable Category, Include in Menu, and URL Key attributes.
  • Saving a category now flushes only the block cache that is related to this category. Previously, the applicationflushed the cache for all category blocks.
  • The price of a custom option with a percent price is now converted as expected into the active store’s base currency in multi-store deployments. Previously, the price of a custom option with a percent price was converted incorrectly. GitHub-26432
  • The application now recreates images successfully, and these images are visible in the Admin as expected whenever a merchant sends media gallery data using POST rest/all/V1/products. Previously, the applicationrecreated the images but deleted them when a merchant sent media gallery data via POST rest/all/V1/products if the images were deleted in pub/media but there were still records in media still contained records for these images. As a result, the merchant saw only placeholders in the Admin because the images were created and deleted during the update process.
  • Records are now deleted as expected when you unassigned an item from a website. Previously, images were duplicated when POST rest/all/V1/products was executed.
  • The /V1/categories/{categoryId}/products call now returns a list of all products that belong to the parent category as expected. Previously, if a product belonged to more than one subcategory of the parent category, the application threw this type of error: Internal Error. Details are available in the application log file. Report ID: webapi-5f8579e37db54. GitHub-30461
  • The /V1/products/attributes/:attributeCode/options REST endpoint now supports updating an existing attribute option.
  • The price of a custom option with a percent price is now converted as expected into the active store’s base currency in multi-store deployments. Previously, the price of a custom option with a percent price was converted incorrectly. GitHub-26432
  • Merchants can now successfully save a new attribute during product creation. Previously, the application did not save the attribute and redirected the merchant to the store view home page when they tried to save the attribute. GitHub-30362
  • The product grids on the Sales > Orders and Catalog > Products pages now list all relevant stores, not just the most recently created store. GitHub-29267
  • Product repository now uses store_id when available to save attribute values for an existing product. Previously, the product repository class overrode the product store ID and always assigned the default store ID. GitHub-29933

Catalog Rule

  • Catalog price rules now work as expected with custom options on product detail pages. Previously, product prices on that page did not reflect applicable catalog price rules. GitHub-22856
  • Product and catalog caches now expire as scheduled. Previously, caches expired daily because сron ran the catalogrule_apply_all task once daily, which re-indexed all catalog rules and dependent indexers, and cleared the cache for all products and categories.

Cleanup

Typo and grammar cleanup

  • The title of the Order Failure page has been revised for accuracy. Previously, this page was titled: We received your order!. GitHub-29416
  • Removed unnecessary spaces in app/code/Magento/Contact/view/frontend/templates/form.phtml. GitHub-29779
  • Corrected a typo in the help message for the bin/magento/setup:config:set subcommand. GitHub-28802
  • Corrected grammar in the PHPDoc for the framework/Registry.php file. GitHub-29661
  • Removed extraneous whitespace from app/code/Magento/Catalog/Helper/Product/View.php. GitHub-30601
  • Corrected a typo in a function name in app/code/Magento/Ui/view/base/web/js/form/element/ui-select.js. GitHub-29987
  • Corrected the pluralization of “item” in the mini cart and checkout order summary. GitHub-29920
  • Removed whitespace in inline elements in markup layered navigation filters. GitHub-30448
  • rl has been corrected to url in \Magento\Framework\Filter\Template\Tokenizer\Parameter. GitHub-29185

Code cleanup

  • An extraneous HTML <br> tag has been removed from the Check Data message area of the System > Import page.
  • AccessChangeQuoteControl and its unit tests have been refactored. GitHub-29672
  • Corrected the code style of the return type declaration in app/code/Magento/Captcha/CustomerData/Captcha.php. GitHub-29712
  • Corrected the position of the button list on the New Attribute page.
  • Added the correct block class for the frontend viewModel reference example for the \Magento\Framework\View\Element\Template class. GitHub-30450
  • A redundant fieldset in the Sale Rule form has been removed. GitHub-29599
  • Unnecessary code has been removed from the hierarchy/edit.phtml template.
  • Corrected PHPdoc comment in app/code/Magento/CatalogImportExport/Model/Export/Product.php. GitHub-30833
  • The docblock annotation for the PublisherInterface message has been corrected. GitHub-30190
  • Corrected arguments in the getStatusByState method. GitHub-30173
  • Corrected method description in app/code/Magento/Quote/Model/Cart/Totals/ItemConverter.php. GitHub-30125
  • Removed redundant variable assignments in the same line in multiple files. GitHub-30133
  • Changed @param string $attribute to @param AbstractAttribute|string[]|string $attribute in EntityAbstract.php. GitHub-30191
  • Invalid tags (for example, @package and @subpackage) have been removed from docblocks throughout the code base. GitHub-30061
  • Unused parameters in the construct of the AdvancedPricing class have been removed. GitHub-29531

Configurable products

  • Filtering out-of-stock configurable products by price now displays results within the correct price range.
  • A virtual product no longer changes type when its status is changed from enabled to disabled (or vice versa). Previously, the application changed a product’s type from virtual to simple when its status changed.
  • The getValue() method no longer triggers a fatal error when updating carts.
  • Configurable products that are available on multiple websites no longer show simple child products that are not assigned to the specific website. GitHub-28291
  • Storefront product pages now display tier prices without taxes as expected. GitHub-12225
  • MSRP prices for configurable products are now converted to the chosen currency correctly. Previously, the application displayed prices in the wrong currency and threw this error: Call to a member function setAppliedTaxes() on null. GitHub-26526, GitHub-29603
  • Merchants can now save a store-specific text swatch attribute option label with a value of 0 (zero). Previously, a value of 0 was replaced with the Admin label option value. GitHub-30073

cron

  • The System Message list now accurately reflects product updates after cron has run and the application has updated products as scheduled.
  • An index based on schedule_id and status has been added to the cron_schedule table. GitHub-29601

Custom customer attributes

  • The application now displays customer attributes of type file on the Account Information page after creation. Previously, when you tried to save a new attribute of this type, the application displayed these errors: The "newAttribute" attribute value is empty. Set the attribute and try again and Validation is failed.
  • The application now correctly displays multi-line custom customer attribute values. Previously, not all data was displayed.
  • The application now alerts shoppers when they enter an invalid birth date while creating an account. Previously, the validator disregarded locale settings, and shoppers were redirected to the Create New Customer Account Page with an invalid date error.
  • Custom address attributes are now included as expected in the Payment step of the checkout workflow.
  • Custom address multi-select attributes are now correctly displayed during guest checkout and on the Admin and My Account order details page.
  • You can now delete a leading zero in a custom customer attribute when Input Type is set to Text and Input Validation is set to Numeric Only.
  • The application now successfully exports customer data that includes a custom gender attribute value.

Customer

  • The calendar widget for the storefront customer account page date of birth field now uses the designated store locale.
  • The application no longer saves duplicate entries of a customer address during checkout of a re-order for an existing customer from the Admin.
  • Deleting all addresses from multiple customers from the Admin now deletes all addresses from the customer address list and removes default billing and shipping addresses. Previously, the applicationdeleted the address from the customer address list but did not remove the default billing and shipping addresses.
  • The Admin customer address tab now correctly displays address count after an administrator has performed a mass deletion of addresses. Previously, the application included deleted addresses in its count.
  • The DateTime format for the Date of Birth field on the customer registration page has been corrected. Previously, the leading zero that preceded a single-digit day was missing.
  • Date format validation for the Date of Birth field now works before the shopper clicks the Create an account button. Previously, a shopper could enter a value in an invalid format, and when they clicked the Create an account button, the shopper was redirected to the Create New Customer Account Page with an invalid date error.
  • The application no longer throws a fatal error when an administrator tries to save a new customer account that contains invalid data for an attribute.
  • The application no longer throws a 400 error when a customer tries to access their shopping cart in a deployment where Magento Shipping was previously installed and the default Luma theme is currently deployed. Previously, the application did not filter out section names that were created by previously installed/enabled modules that were not supported in the Admin before sending requests to the server, which generated errors.
  • The application now displays a message as expected when a shopper creates a guest account when the Require Emails Confirmation setting is enabled and Magento\Customer\Controller\Account\CreatePost has been overridden. Previously, the application did not permit this type of customization of the user registration process, and under these conditions, a user’s email confirmation status was considered complete, the new user was automatically logged in, and no error message was shown.
  • The application now assigns a shopper to the correct customer group when the shopper places an order with a non-default customer group in a store where Enable Automatic Assignment to Customer Group is enabled. GitHub-26976
  • The Admin customers grid is now available as expected when the non-default website is deleted in a multi-site deployment when indexes are set to Update by Schedule. Previously, the application did not display the grid and threw this error: [2020-12-09 11:31:54] report.CRITICAL: The website with id 2 that was requested wasn't found. Verify the website and try again. \{"exception":"[object] (Magento\\Framework\\Exception\\NoSuchEntityException(code: 0): The website with id 2 that was requested wasn't found. Verify the website and try again. at /var/www/html/magento24ee/vendor/magento/module-store/Model/WebsiteRepository.php:110)"}

dotdigital

  • Error handling has been improved when retrieving lists of programs from dotdigital Engagement Cloud.

  • The value that is synced in the store name column during guest sync is now the store view name as expected. Previously, the website name was included in this column.

  • Added an array check before looping over order status automations after an order is saved.

  • Resolved issues with Composer upgrades that were the result of the dotdigital module’s dependency on magento/module-authorization.

Downloadable

  • The application no longer lists a downloadable product in My Download Products tab after the order that it belongs to has been partially refunded. GitHub-28388

EAV

  • Custom attributes that use \Magento\Eav\Model\Entity\Attribute\Backend\ArrayBackend now use default values if no value is provided in the payload when a product is created by API call.

Email

  • \Magento\Config\Model\Config\Source\Email\Template::toOptionArray no longer throws an error when setPath() is not called before toOptionArray(). GitHub-29315
  • The application now correctly converts plain text to HTML when you click Return Html Version when loading an email template.
  • Email sent to customers that contain partial invoices now includes accurate item subtotals. Previously, the subtotal in this email was the total of the ordered quantity, not the total amount of the invoiced quantity.
  • The application now sends email reminders to all relevant customers with valid email addresses. Previously, the applicationstopped sending reminder emails to customers after encountering one invalid address.
  • Sending sales email in asynchronous mode now works as expected after a product is removed from a catalog. Previously, asynchronous email sending was blocked, and the application displayed this error: main.ERROR: Cron Job sales_send_order_invoice_emails has an error: Call to a member function getData() on null. Statistics: {"sum":0,"count":1,"realmem":0,"emalloc":0,"realmem_start":73400320,"emalloc_start":37177640} [] []main.CRITICAL: Error when running a cron job {"exception":"[object] (RuntimeException(code: 0): Error when running a cron job at /var/www/html/vendor/magento/module-cron/Observer/ProcessCronQueueObserver.php:327, Error(code: 0): Call to a member function getData() on null at /var/www/html/vendor/magento/module-catalog/Helper/Image.php:502)"} []. GitHub-26878
  • The application no longer copies a customer on order confirmation email when sales_email/order_comment/enabled is disabled and sales_email/order_comment/copy_method is set to bcc. GitHub-29915