Skip to content

Commit

Permalink
Merge pull request #617 from AdobeDocs/fix-link
Browse files Browse the repository at this point in the history 
swap out link
  • Loading branch information
@jfrontain
jfrontain authored and GitHub Enterprise committed Aug 1, 2023
2 parents b1983a2 + b6f082a commit 06f29ec
Show file tree
Hide file tree
Showing 2 changed files with 18 additions and 18 deletions.
4 changes: 2 additions & 2 deletions help/release/release-notes/commerce/2-4-5.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -1414,11 +1414,11 @@ Repetitive actions have been replaced with action groups in these tests:

## Known issues

**Issue**: Staged sales rule labels may be mismatched after an upgrade to Adobe Commerce 2.4.6 or later from pre-2.4.5 product versions. **Workaround**: Apply ACSD-50625_2.4.5-P1.patch during upgrade before the Update metadata step. See [salesRules labels issues when upgrade from versions < 2.4.5](https://experienceleague.adobe.com/docs/commerce-knowledge-base/kb/troubleshooting/known-issues-patches-attached/salesRule-labels-upgrade-from-versions-under-2.4.5.html) Knowledge Base article.
**Issue**: Staged sales rule labels may be mismatched after an upgrade to Adobe Commerce 2.4.6 or later from pre-2.4.5 product versions. **Workaround**: Apply ACSD-50625_2.4.5-P1.patch during upgrade before the Update metadata step. See [salesRules labels issues when upgrade from versions < 2.4.5](https://experienceleague.adobe.com/docs/commerce-knowledge-base/kb/troubleshooting/known-issues-patches-attached/salesrule-label-issues-when-upgrade-from-versions-under-2.4.5.html) Knowledge Base article.

General steps for resolving this issue:

1. Download the required patch. See the [salesRules labels issues when upgrade from versions < 2.4.5](https://experienceleague.adobe.com/docs/commerce-knowledge-base/kb/troubleshooting/known-issues-patches-attached/salesRule-labels-upgrade-from-versions-under-2.4.5.html) Knowledge Base article.
1. Download the required patch. See the [salesRules labels issues when upgrade from versions < 2.4.5](https://experienceleague.adobe.com/docs/commerce-knowledge-base/kb/troubleshooting/known-issues-patches-attached/salesrule-label-issues-when-upgrade-from-versions-under-2.4.5.html) Knowledge Base article.
2. Follow the upgrade steps outlined in the Manage packages phase of the upgrade process [Perform an upgrade](https://experienceleague.adobe.com/docs/commerce-operations/upgrade-guide/implementation/perform-upgrade.html).
3. Apply this patch during upgrade after the Manage packages phase and before the Update metadata phase.See [How to apply a composer patch provided by Adobe](https://experienceleague.adobe.com/docs/commerce-knowledge-base/kb/how-to/how-to-apply-a-composer-patch-provided-by-magento.html) .
4. Complete the upgrade process.
Expand Down
32 changes: 16 additions & 16 deletions help/release/release-notes/commerce/2-4-6.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ exl-id: c25f3ad8-da18-421f-a77a-03f1cc9c45e4
---
# Adobe Commerce 2.4.6 release notes

Adobe Commerce 2.4.6 introduces support for PHP 8.2. PHP 8.1 remains fully supported, but support for PHP 7.4 has been removed. It includes significant performance and scalability enhancements. GraphQL operations for bulk cart operations and category tree rendering response have been optimized. This release introduces the Adobe Commerce Extension metapackage.
Adobe Commerce 2.4.6 introduces support for PHP 8.2. PHP 8.1 remains fully supported, but support for PHP 7.4 has been removed. It includes significant performance and scalability enhancements. GraphQL operations for bulk cart operations and category tree rendering response have been optimized. This release introduces the Adobe Commerce Extension metapackage.

This release includes over 300 quality fixes and enhancements. Core Composer dependencies and third-party libraries have been upgraded to the latest versions that are compatible with PHP 8.2.

Expand Down Expand Up @@ -42,7 +42,7 @@ Security improvements for this release improve compliance with the latest securi
* reCAPTCHA validation no longer fails during checkout when unexpected errors occur during payment processing. [GitHub-35093](https://github.com/magento/magento2/issues/35093) <!-- AC-2642 -->

* **New system configuration for requiring email confirmation when an admin user changes their email**. To reduce site vulnerability, a new system configuration setting (disabled by default) was added to require email confirmation when an admin user changes their email: **[!UICONTROL Stores]** > **[!UICONTROL Settings:Configuration]** > **[!UICONTROL Customers]** > **[!UICONTROL Customer Configuration]** > **[!UICONTROL Account Information Options]** > **[!UICONTROL Require email confirmation if an email has been changed]**. When this option is enabled, the application will request email confirmation every time the admin user changes their email address. The following module is affected by this change: `Magento_Customer`. <!-- AC-3064 -->


### Platform enhancements

Expand Down Expand Up @@ -113,14 +113,14 @@ Adobe Commerce 2.4.6 now supports:

This release introduces the Adobe Commerce Extension metapackage v1.1.0, which automatically bundles select Adobe Commerce extensions with this core release. The versions of these extensions that are included in this metapackage are installed when `composer update` is run, simplifying the process of upgrading these extensions when upgrading to the latest core release. These extensions will still maintain independent release schedules.

The Adobe Commerce Extension metapackage for Adobe Commerce 2.4.6 includes these two extensions:
The Adobe Commerce Extension metapackage for Adobe Commerce 2.4.6 includes these two extensions:

* [Bolt Quick Checkout](https://experienceleague.adobe.com/docs/commerce-merchant-services/quick-checkout/overview.html)
* [Adobe I/O Events for Adobe Commerce](https://developer.adobe.com/commerce/events/get-started/)

Future versions of this extension metapackage will contain additional extensions.
Future versions of this extension metapackage will contain additional extensions.

### Adobe I/O Events for Adobe Commerce
### Adobe I/O Events for Adobe Commerce

Adobe I/O Events for Adobe Commerce captures Commerce events and transfers data from Adobe Commerce to other Adobe systems. Developers can build cloud-native apps in Adobe Developer App Builder that subscribe to Commerce events such as inventory updates, order status changes, and price updates. Developers can use this capability to exchange data for the orchestration of the entire buyer journey across their mission-critical systems.

Expand All @@ -147,7 +147,7 @@ The focus of this release has been on creating a storefront experience on Venia

### Adobe Commerce integration with Adobe IMS

The following Adobe IMS modules have been decoupled from the Adobe Commerce 2.4.6 core code and are now packaged as a separate metapackage:
The following Adobe IMS modules have been decoupled from the Adobe Commerce 2.4.6 core code and are now packaged as a separate metapackage:

* `adobe-ims`
* `adobe-ims-api`
Expand Down Expand Up @@ -327,7 +327,7 @@ Screen readers now announce:

<!-- B2B-2453-->

* GraphQL product queries now return only bundle product options within the scope of the store being queried.
* GraphQL product queries now return only bundle product options within the scope of the store being queried.

<!-- B2B-2455-->

Expand All @@ -345,7 +345,7 @@ Screen readers now announce:

<!-- B2B-2471-->

* Corrected defects in `CatalogUrlResolverIdentity` and `CmsUrlResolverIdentity` that prevented caching. This affected route query caching on multiple requests.
* Corrected defects in `CatalogUrlResolverIdentity` and `CmsUrlResolverIdentity` that prevented caching. This affected route query caching on multiple requests.

### Cart and checkout

Expand Down Expand Up @@ -794,15 +794,15 @@ Screen readers now announce:

<!-- B2B-2379-->

* Cart reload is now triggered once only as expected when the cart is initialized by GraphQL mutations. Previously, cart loading triggered unnecessary cart revalidation against stock inventory, which consumed significant resources every time the cart was loaded.
* Cart reload is now triggered once only as expected when the cart is initialized by GraphQL mutations. Previously, cart loading triggered unnecessary cart revalidation against stock inventory, which consumed significant resources every time the cart was loaded.

<!-- AC-1726-->

* Added the `gift_message` type to the `OrderItemInterface`. [GitHub-29418](https://github.com/magento/magento2/issues/29418)

<!-- AC-2454-->

* Product options returned in GraphQL responses now include only the products that are within the catalog to which the user belongs. If the user belongs to a shared catalog, then only products in shared catalogs are returned. If user is a guest or not part of a custom shared catalog, then only products in public catalog are returned.
* Product options returned in GraphQL responses now include only the products that are within the catalog to which the user belongs. If the user belongs to a shared catalog, then only products in shared catalogs are returned. If user is a guest or not part of a custom shared catalog, then only products in public catalog are returned.


### Google ReCAPTCHA
Expand Down Expand Up @@ -1078,7 +1078,7 @@ Screen readers now announce:

<!-- BUNDLE-3147-->

* The `ANDROID_PAY_CARD` constant in `Braintree/Ui/Component/Report/Listing/Column/PaymentType.php` has replaced `GOOGLE_PAY_CARD`. This resolves issues with the Braintree report.
* The `ANDROID_PAY_CARD` constant in `Braintree/Ui/Component/Report/Listing/Column/PaymentType.php` has replaced `GOOGLE_PAY_CARD`. This resolves issues with the Braintree report.

### Return Merchandise Authorizations (RMA)

Expand Down Expand Up @@ -1160,7 +1160,7 @@ Screen readers now announce:

<!-- AC-2363-->

* Added the `price_excl_tax` and `price_excl_tax` types to the output of the `setShippingMethodsOnCart` mutation. [GitHub-31206](https://github.com/magento/magento2/issues/31206)
* Added the `price_excl_tax` and `price_excl_tax` types to the output of the `setShippingMethodsOnCart` mutation. [GitHub-31206](https://github.com/magento/magento2/issues/31206)

<!-- AC-1096-->

Expand Down Expand Up @@ -1234,7 +1234,7 @@ Screen readers now announce:

<!-- AC-6860-->

* Removed non-native `array_first` function from dev dependencies in the MFTF framework.
* Removed non-native `array_first` function from dev dependencies in the MFTF framework.

### Translations and locales

Expand Down Expand Up @@ -1400,14 +1400,14 @@ Screen readers now announce:

## Known issue

**Issue**: Staged sales rule labels may be mismatched after an upgrade to Adobe Commerce 2.4.6 or later from pre-2.4.5 product versions. **Workaround**: Apply ACSD-50625_2.4.5-P1.patch during upgrade before the Update metadata step. See [salesRules labels issues when upgrade from versions < 2.4.5](https://experienceleague.adobe.com/docs/commerce-knowledge-base/kb/troubleshooting/known-issues-patches-attached/salesRule-labels-upgrade-from-versions-under-2.4.5.html) Knowledge Base article.
**Issue**: Staged sales rule labels may be mismatched after an upgrade to Adobe Commerce 2.4.6 or later from pre-2.4.5 product versions. **Workaround**: Apply ACSD-50625_2.4.5-P1.patch during upgrade before the Update metadata step. See [salesRules labels issues when upgrade from versions < 2.4.5](https://experienceleague.adobe.com/docs/commerce-knowledge-base/kb/troubleshooting/known-issues-patches-attached/salesrule-label-issues-when-upgrade-from-versions-under-2.4.5.html) Knowledge Base article.

General steps for resolving this issue:

1. Download the required patch. See the [salesRules labels issues when upgrade from versions < 2.4.5](https://experienceleague.adobe.com/docs/commerce-knowledge-base/kb/troubleshooting/known-issues-patches-attached/salesRule-labels-upgrade-from-versions-under-2.4.5.html) Knowledge Base article.
1. Download the required patch. See the [salesRules labels issues when upgrade from versions < 2.4.5](https://experienceleague.adobe.com/docs/commerce-knowledge-base/kb/troubleshooting/known-issues-patches-attached/salesrule-label-issues-when-upgrade-from-versions-under-2.4.5.html) Knowledge Base article.
2. Follow the upgrade steps outlined in the Manage packages phase of the upgrade process [Perform an upgrade](https://experienceleague.adobe.com/docs/commerce-operations/upgrade-guide/implementation/perform-upgrade.html).
3. Apply this patch during upgrade after the Manage packages phase and before the Update metadata phase.See [How to apply a composer patch provided by Adobe](https://experienceleague.adobe.com/docs/commerce-knowledge-base/kb/how-to/how-to-apply-a-composer-patch-provided-by-magento.html) .
4. Complete the upgrade process.
4. Complete the upgrade process.

**Issue**: You cannot create a credit memo when free shipping is enabled (**[!UICONTROL Stores]** > **[!UICONTROL Configuration]** > **[!UICONTROL Sales]** > **[!UICONTROL Delivery Methods]**) and the displayed shipping price includes tax. When you try to create a credit memo, Adobe Commerce throws this exception: `"Division by zero".vendor/magento/module-sales/Model/Order/Creditmemo/Total/Tax.phpLine 139`. [GitHub-36800](https://github.com/magento/magento2/issues/36800)

Expand Down

0 comments on commit 06f29ec

Please sign in to comment.