- The Payment Provider Gateway documentation uses the Magento 2.3 (now {{site.data.var.ee}} and {{site.data.var.ce}}) of the Braintree module as a
- reference application. The Braintree module was removed in version 2.4.0. The concepts described in this guide are
- still applicable to version 2.4.0, but the code samples are not supported.
-
- You must install Elasticsearch or OpenSearch before installing {{ site.data.var.ee }} or {{ site.data.var.ce }} 2.4.0. See Search engine prerequisites for details.
+ This documentation is for version 2.0 of the framework, which supports Adobe Commerce and Magento Open Source 2.3.x. You can find documentation for version 3.0 here. See find your version if you are unsure about which version you are using.
- PHP 7.3 reached end of support in December 2021 and {{site.data.var.ee}} 2.3.x reaches end of support in September 2022. You may want to consider planning your upgrade now to {{site.data.var.ee}} 2.4.x and PHP 7.4.x to help maintain PCI compliance.
+
+
{{site.data.var.ee}} 2.3 reached end of support in September 2022.
{% endif %}
@@ -52,10 +35,4 @@
{{ page.subtitle }}
{% include layout/github-links.html %}
{% endunless %}
- {% if page.url contains "catalog-service/" %}
-
- Catalog Service for Adobe Commerce is for Beta users only. Onboarding and installation describes how to join the Beta program.
-
{% include layout/version-switcher.html %}
- {% include layout/app-switcher.html %}
-
- {% include layout/quick-search.html %}
+ {% if page.guide_version != "2.4" %}
+ {% include layout/quick-search.html %}
+ {% endif %}
diff --git a/src/_videos/fundamentals/add-a-javascript-module.md b/src/_videos/fundamentals/add-a-javascript-module.md
index 35dd127ad5f..6777a9a7db2 100644
--- a/src/_videos/fundamentals/add-a-javascript-module.md
+++ b/src/_videos/fundamentals/add-a-javascript-module.md
@@ -5,7 +5,7 @@ group: "Fundamentals of Magento 2 Development"
title: "How to Add a JavaScript Module"
thumbnail: "fundamentals/thumbs/add-js-module.png"
menu_order: 1
-migrated_to: https://experienceleague.adobe.com/docs/commerce-learn/tutorials/frontend-development/add-javascript-module.html
+redirect_to: https://experienceleague.adobe.com/docs/commerce-learn/tutorials/frontend-development/add-javascript-module.html
layout: migrated-video
---
diff --git a/src/_videos/fundamentals/add-new-product-attribute.md b/src/_videos/fundamentals/add-new-product-attribute.md
index 8e93c4d106c..9192b655d0c 100644
--- a/src/_videos/fundamentals/add-new-product-attribute.md
+++ b/src/_videos/fundamentals/add-new-product-attribute.md
@@ -5,7 +5,7 @@ group: "Fundamentals of Magento 2 Development"
title: "How to Add a New Product Attribute"
thumbnail: "fundamentals/thumbs/add-attribute.png"
menu_order: 1
-migrated_to: https://experienceleague.adobe.com/docs/commerce-learn/tutorials/backend-development/add-product-attribute.html
+redirect_to: https://experienceleague.adobe.com/docs/commerce-learn/tutorials/backend-development/add-product-attribute.html
layout: migrated-video
---
diff --git a/src/_videos/fundamentals/create-a-new-module.md b/src/_videos/fundamentals/create-a-new-module.md
index b023e2267c4..82f0660d172 100644
--- a/src/_videos/fundamentals/create-a-new-module.md
+++ b/src/_videos/fundamentals/create-a-new-module.md
@@ -5,7 +5,7 @@ group: "Fundamentals of Magento 2 Development"
title: "Create a New Module"
thumbnail: "fundamentals/thumbs/create-new-module.png"
menu_order: 1
-migrated_to: https://experienceleague.adobe.com/docs/commerce-learn/tutorials/backend-development/create-module.html
+redirect_to: https://experienceleague.adobe.com/docs/commerce-learn/tutorials/backend-development/create-module.html
layout: migrated-video
---
diff --git a/src/_videos/fundamentals/create-a-new-page.md b/src/_videos/fundamentals/create-a-new-page.md
index e89c1cede6a..ca9d5025678 100644
--- a/src/_videos/fundamentals/create-a-new-page.md
+++ b/src/_videos/fundamentals/create-a-new-page.md
@@ -5,7 +5,7 @@ group: "Fundamentals of Magento 2 Development"
title: "Create a New Page"
thumbnail: "fundamentals/thumbs/create-new-page.png"
menu_order: 1
-migrated_to: https://experienceleague.adobe.com/docs/commerce-learn/tutorials/frontend-development/create-new-page.html
+redirect_to: https://experienceleague.adobe.com/docs/commerce-learn/tutorials/frontend-development/create-new-page.html
layout: migrated-video
---
diff --git a/src/_videos/fundamentals/index.md b/src/_videos/fundamentals/index.md
index 04278f390f2..1d30d507623 100644
--- a/src/_videos/fundamentals/index.md
+++ b/src/_videos/fundamentals/index.md
@@ -4,7 +4,7 @@ layout: migrated-videos
permalink: "videos/fundamentals/"
title: "Fundamentals of Magento 2 Development"
menu_order: 0
-migrated_to: https://experienceleague.adobe.com/docs/commerce-learn/tutorials/overview.html
+redirect_to: https://experienceleague.adobe.com/docs/commerce-learn/tutorials/overview.html
---
diff --git a/src/catalog-service/index.md b/src/catalog-service/index.md
index 1e82a59315b..2f942b10f38 100644
--- a/src/catalog-service/index.md
+++ b/src/catalog-service/index.md
@@ -2,14 +2,10 @@
group: catalog-service
title: Catalog Service for Adobe Commerce
ee_only: True
-migrated_to: https://experienceleague.adobe.com/docs/commerce-merchant-services/catalog-service/overview.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-merchant-services/catalog-service/overview.html
+status: migrated
---
-{:.bs-callout-info}
-Catalog Service for Adobe Commerce is in Beta release and is available to {{site.data.var.ece}} and {{site.data.var.ee}} customers only. See the Catalog Service [onboarding and installation](
-https://experienceleague.adobe.com/docs/commerce-merchant-services/catalog-service/overview.html) documentation for details about signing up for the program.
-
Catalog Service uses GraphQL queries to provide rich view-model (read-only) catalog data to quickly and fully render product-related content on storefront, including product detail pages and product list pages. Catalog Service, along with [Live Search]({{site.baseurl}}/live-search/overview.html), each implement queries that return information that is not available to the [`products` query]({{site.baseurl}}/guides/v2.4/graphql/queries/products.html) on Adobe Commerce and Magento Open Source. For example, the Catalog Service [`products` query](products.html) treats all products as either simple or complex. Simple products have a single price, while complex products have a price range. The Live Search [`productSearch` query](../live-search/product-search.html) returns detailed facet information.
You run these queries by sending them to the gateway at `https://catalog-service.adobe.io/graphql`.
diff --git a/src/catalog-service/products.md b/src/catalog-service/products.md
index 9ca46e41926..0d94fe04bd0 100644
--- a/src/catalog-service/products.md
+++ b/src/catalog-service/products.md
@@ -2,8 +2,8 @@
group: catalog-service
title: products query
ee_only: True
-migrated_to: https://experienceleague.adobe.com/docs/commerce-merchant-services/catalog-service/graphql/products.html?lang=en
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/catalog-service/queries/products/
+status: migrated
---
The Catalog Service for Adobe Commerce `products` query returns details about the SKUs specified as input. Although this query has the same name as the [`products` query]({{site.baseurl}}/guides/v2.4/graphql/queries/products.html) that is provided with core Adobe Commerce and Magento Open Source, there are some differences.
diff --git a/src/catalog-service/productsearch.md b/src/catalog-service/productsearch.md
index a12b431ff59..0d395898e0c 100644
--- a/src/catalog-service/productsearch.md
+++ b/src/catalog-service/productsearch.md
@@ -2,8 +2,8 @@
group: catalog-service
title: productSearch query
ee_only: True
-migrated_to: https://experienceleague.adobe.com/docs/commerce-merchant-services/catalog-service/graphql/productsearch.html?lang=en
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/catalog-service/queries/product-search/
+status: migrated
---
The Catalog Service for Adobe Commerce `productSearch` query can use LiveSearch to return details about the SKUs specified as input. Although this query is the same as the [`productSearch` query]({{site.baseurl}}/live-search/product-search.html), LiveSearch returns a `productView` object. See the [`productSearch` query]({{site.baseurl}}/live-search/product-search.html) topic for reference information.
diff --git a/src/catalog-service/refine-product.md b/src/catalog-service/refine-product.md
index ef3b2fae0bc..c5318928d7f 100644
--- a/src/catalog-service/refine-product.md
+++ b/src/catalog-service/refine-product.md
@@ -2,8 +2,8 @@
group: catalog-service
title: refineProduct query
ee_only: True
-migrated_to: https://experienceleague.adobe.com/docs/commerce-merchant-services/catalog-service/graphql/refine-product.html?lang=en
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/catalog-service/queries/refine-product/
+status: migrated
---
The `refineProduct` query narrows the results of a `products` query that was run against a complex product. Before you run the `refineProduct` query, you must run the `products` query and construct the response so that it returns a list of `options` within a `ComplexProductView` inline fragment. When a shopper selects a product option (such as size or color) on the storefront, run the `refineProduct` query, specifying the SKU and selected option value IDs as input. Depending on the number of product options the complex product has, you might need to run the `refineProduct` query multiple times, until the shopper has selected a specific variant.
diff --git a/src/cloud/architecture/cloud-architecture.md b/src/cloud/architecture/cloud-architecture.md
index 6199cab8269..65fb22d3593 100644
--- a/src/cloud/architecture/cloud-architecture.md
+++ b/src/cloud/architecture/cloud-architecture.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
redirect_from:
- /cloud/basic-information/cloud-plans.html
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/architecture/cloud-architecture.html
+status: migrated
---
{{site.data.var.ece}} has a Starter and a Pro plan. Each plan has a unique architecture to drive your {{site.data.var.ee}} development and deployment process. Both the Starter plan and the Pro plan architecture deploy databases, web server, and caching servers across multiple environments for end-to-end testing while supporting continuous integration.
diff --git a/src/cloud/architecture/pro-architecture.md b/src/cloud/architecture/pro-architecture.md
index a8359153706..4eede8662d3 100644
--- a/src/cloud/architecture/pro-architecture.md
+++ b/src/cloud/architecture/pro-architecture.md
@@ -7,6 +7,8 @@ redirect_from:
- /cloud/architecture/pro-architecture-legacy.html
functional_areas:
- Cloud
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/architecture/pro-architecture.html
+status: migrated
---
Your {{site.data.var.ece}} Pro architecture supports multiple environments that you can use to develop, test, and launch your store.
diff --git a/src/cloud/architecture/pro-develop-deploy-workflow.md b/src/cloud/architecture/pro-develop-deploy-workflow.md
index f5b74be187a..ac4671f9e0a 100644
--- a/src/cloud/architecture/pro-develop-deploy-workflow.md
+++ b/src/cloud/architecture/pro-develop-deploy-workflow.md
@@ -7,6 +7,8 @@ redirect_from:
- /cloud/trouble/pro-env-management.html
functional_areas:
- Cloud
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/architecture/pro-develop-deploy-workflow.html
+status: migrated
---
The {{site.data.var.ece}} Pro plan includes a single Git repository with a Global Master and three main environments: the **Integration** environment for development and testing, the **Staging** environment for testing with all services, and the **Production** environment for launching and maintaining your live site. See [Pro architecture]({{ site.baseurl }}/cloud/architecture/pro-architecture.html) for an overview.
diff --git a/src/cloud/architecture/scaled-architecture.md b/src/cloud/architecture/scaled-architecture.md
index d57180b15e6..3d8aca9d203 100644
--- a/src/cloud/architecture/scaled-architecture.md
+++ b/src/cloud/architecture/scaled-architecture.md
@@ -3,6 +3,8 @@ group: cloud-guide
title: Scaled architecture
functional_areas:
- Cloud
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/architecture/scaled-architecture.html
+status: migrated
---
The Cloud infrastructure scales according to your resource needs to achieve greater efficiency. The {{site.data.var.ece}} monitors your applications and can adjust capacity to maintain steady, predictable performance. Converting to this architecture helps to mitigate problems, such as latency or large spikes in traffic.
diff --git a/src/cloud/architecture/starter-architecture.md b/src/cloud/architecture/starter-architecture.md
index 4079dddbe18..11659c31d8d 100644
--- a/src/cloud/architecture/starter-architecture.md
+++ b/src/cloud/architecture/starter-architecture.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
redirect_from:
- /cloud/basic-information/starter-architecture.html
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/architecture/starter-architecture.html
+status: migrated
---
Your {{site.data.var.ece}} Starter architecture supports up to **four** environments, including a Master environment that contains the initial project code, the Staging environment, and up to two Integration environments.
diff --git a/src/cloud/architecture/starter-develop-deploy-workflow.md b/src/cloud/architecture/starter-develop-deploy-workflow.md
index d45cc33a822..cbe6e88747a 100644
--- a/src/cloud/architecture/starter-develop-deploy-workflow.md
+++ b/src/cloud/architecture/starter-develop-deploy-workflow.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
redirect_from:
- /cloud/basic-information/starter-develop-deploy-workflow.html
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/architecture/starter-develop-deploy-workflow.html
+status: migrated
---
The {{site.data.var.ece}} includes a single Git repository with a master branch for the Production environment that can be branched to create Staging and Integration environments for testing and development work. You can have up to four active environments, including a `master` environment for your production server. See [Starter architecture]({{ site.baseurl }}/cloud/architecture/starter-architecture.html) for an overview.
diff --git a/src/cloud/before/before-setup-env-2_clone.md b/src/cloud/before/before-setup-env-2_clone.md
index ac8376e2882..d9065492bb5 100644
--- a/src/cloud/before/before-setup-env-2_clone.md
+++ b/src/cloud/before/before-setup-env-2_clone.md
@@ -6,6 +6,8 @@ redirect_from:
functional_areas:
- Cloud
- Setup
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/cli-branches.html
+status: migrated
---
{:.ref-header}
diff --git a/src/cloud/before/before-setup-env-install.md b/src/cloud/before/before-setup-env-install.md
index 1ce7677b736..a58a25f132a 100644
--- a/src/cloud/before/before-setup-env-install.md
+++ b/src/cloud/before/before-setup-env-install.md
@@ -8,6 +8,8 @@ functional_areas:
- Install
- Setup
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/overview.html
+status: migrated
---
{:.ref-header}
diff --git a/src/cloud/before/before-workspace-file-sys-owner.md b/src/cloud/before/before-workspace-file-sys-owner.md
index cb6c14870fc..c6fb56d3f39 100644
--- a/src/cloud/before/before-workspace-file-sys-owner.md
+++ b/src/cloud/before/before-workspace-file-sys-owner.md
@@ -4,6 +4,8 @@ title: Set up the file system owner
functional_areas:
- Cloud
- Setup
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/dev-tools/cloud-cli.html
+status: migrated
---
{:.ref-header}
diff --git a/src/cloud/before/before-workspace-magento-prereqs.md b/src/cloud/before/before-workspace-magento-prereqs.md
index 6c86ae776f5..5cc905dc2ef 100644
--- a/src/cloud/before/before-workspace-magento-prereqs.md
+++ b/src/cloud/before/before-workspace-magento-prereqs.md
@@ -8,6 +8,8 @@ functional_areas:
- Cloud
- Setup
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/overview.html
+status: migrated
---
{:.ref-header}
diff --git a/src/cloud/before/before-workspace-ssh.md b/src/cloud/before/before-workspace-ssh.md
index 5595c54e74a..4c2f8dbe0c3 100644
--- a/src/cloud/before/before-workspace-ssh.md
+++ b/src/cloud/before/before-workspace-ssh.md
@@ -8,6 +8,8 @@ functional_areas:
- Setup
- Security
- Config
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/secure-connections.html
+status: migrated
---
{:.ref-header}
diff --git a/src/cloud/before/before-workspace.md b/src/cloud/before/before-workspace.md
index e4dfe2cc7c6..1f91e7f0a9f 100644
--- a/src/cloud/before/before-workspace.md
+++ b/src/cloud/before/before-workspace.md
@@ -4,6 +4,8 @@ title: Prepare for local environment setup
functional_areas:
- Cloud
- Setup
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/project/overview.html
+status: migrated
---
To develop, deploy, and test {{site.data.var.ece}}, you need to setup your local environment and clone your project's master Git branch. This local environment provides a development system for your custom code, extensions, and configurations to push for active testing in one of the Integration environments.
diff --git a/src/cloud/bk-cloud.md b/src/cloud/bk-cloud.md
index b1f752beebf..48aecd24031 100644
--- a/src/cloud/bk-cloud.md
+++ b/src/cloud/bk-cloud.md
@@ -3,6 +3,8 @@ group: cloud-guide
title: Cloud guide for Commerce
functional_areas:
- Cloud
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/overview.html
+status: migrated
---
{{site.data.var.ece}} is a managed, automated hosting platform for the {{site.data.var.ee}} software. {{site.data.var.ece}} comes with additional features that set it apart from the on-premises {{site.data.var.ee}} and {{site.data.var.ce}} platforms:
diff --git a/src/cloud/cdn/cloud-fastly-custom-response.md b/src/cloud/cdn/cloud-fastly-custom-response.md
index 72d69ac8471..13b6c6ce207 100644
--- a/src/cloud/cdn/cloud-fastly-custom-response.md
+++ b/src/cloud/cdn/cloud-fastly-custom-response.md
@@ -7,6 +7,8 @@ functional_areas:
- Cloud
- Setup
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/cdn/setup-fastly/fastly-custom-response.html
+status: migrated
---
When a request to the Fastly origin fails, Fastly returns default response pages with basic formatting and generic messaging that can be confusing for users. For example, Fastly returns the following default error page when a request to the Fastly origin fails because of a 503 error.
diff --git a/src/cloud/cdn/cloud-fastly.md b/src/cloud/cdn/cloud-fastly.md
index bba630f7f59..8f69c600ad0 100644
--- a/src/cloud/cdn/cloud-fastly.md
+++ b/src/cloud/cdn/cloud-fastly.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Setup
- Security
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/cdn/fastly.html
+status: migrated
---
{:.bs-callout-warning}
diff --git a/src/cloud/cdn/cloud-vcl-custom-snippets.md b/src/cloud/cdn/cloud-vcl-custom-snippets.md
index 5d23bef608f..468918b704c 100644
--- a/src/cloud/cdn/cloud-vcl-custom-snippets.md
+++ b/src/cloud/cdn/cloud-vcl-custom-snippets.md
@@ -6,6 +6,8 @@ redirect_from:
functional_areas:
- Cloud
- Setup
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/cdn/custom-vcl-snippets/fastly-vcl-custom-snippets.html
+status: migrated
---
Fastly supports a customized version of the Varnish Configuration Language (VCL) to customize the Fastly service configuration. For example, you can allow, block, or redirect access for specific users or IPs using VCL code blocks in combination with edge and ACL dictionaries.
diff --git a/src/cloud/cdn/configure-fastly-customize-cache.md b/src/cloud/cdn/configure-fastly-customize-cache.md
index adb556568b1..434e476a6cb 100644
--- a/src/cloud/cdn/configure-fastly-customize-cache.md
+++ b/src/cloud/cdn/configure-fastly-customize-cache.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Setup
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/cdn/setup-fastly/fastly-custom-cache-configuration.html
+status: migrated
---
After you enable and verify the Fastly service in your Staging and Production environments, you can review and customize cache configuration settings like enabling force TLS to redirect HTTP requests to Fastly, updating purge settings, enabling basic authentication to password-protect your site during development, and setting up GeoIP support.
diff --git a/src/cloud/cdn/configure-fastly.md b/src/cloud/cdn/configure-fastly.md
index b757e585e76..70e256aa213 100644
--- a/src/cloud/cdn/configure-fastly.md
+++ b/src/cloud/cdn/configure-fastly.md
@@ -7,6 +7,8 @@ functional_areas:
- Cloud
- Setup
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/cdn/setup-fastly/fastly-configuration.html
+status: migrated
---
[Fastly]({{ site.baseurl }}/cloud/cdn/cloud-fastly.html) is required for {{site.data.var.ece}}, and is used in Staging and Production environments. It works with Varnish to provide fast caching capabilities and a [Content Delivery Network](https://glossary.magento.com/content-delivery-network) (CDN) for static assets. Fastly also provides a Web Application Firewall (WAF) to secure your site and Cloud infrastructure. You must route all incoming site traffic through Fastly to protect your site and Cloud infrastructure from malicious traffic and attacks.
diff --git a/src/cloud/cdn/fastly-image-optimization.md b/src/cloud/cdn/fastly-image-optimization.md
index b6842c2a6cc..74e426b1efa 100644
--- a/src/cloud/cdn/fastly-image-optimization.md
+++ b/src/cloud/cdn/fastly-image-optimization.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Setup
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/cdn/fastly-image-optimization.html
+status: migrated
---
Fastly image optimization (Fastly IO) provides real-time image manipulation and optimization to speed up image delivery and simplify maintenance of image source sets for responsive web applications. Once configured Fastly IO provides the following image optimization features:
diff --git a/src/cloud/cdn/fastly-vcl-allowlist.md b/src/cloud/cdn/fastly-vcl-allowlist.md
index 32644256c4d..2664c101aaf 100644
--- a/src/cloud/cdn/fastly-vcl-allowlist.md
+++ b/src/cloud/cdn/fastly-vcl-allowlist.md
@@ -8,6 +8,8 @@ functional_areas:
redirect_from:
- /cloud/configure/fastly-vcl-whitelist.html
- /cloud/cdn/fastly-vcl-whitelist.html
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/cdn/custom-vcl-snippets/fastly-vcl-allowlist.html
+status: migrated
---
You can use a Fastly Edge ACL list in combination with a custom VCL code snippet to filter incoming requests and allow access by IP address. The ACL list specifies the IP addresses to allow.
diff --git a/src/cloud/cdn/fastly-vcl-badreferer.md b/src/cloud/cdn/fastly-vcl-badreferer.md
index 9e802cee52f..8def84dd62f 100644
--- a/src/cloud/cdn/fastly-vcl-badreferer.md
+++ b/src/cloud/cdn/fastly-vcl-badreferer.md
@@ -6,6 +6,8 @@ redirect_from:
functional_areas:
- Cloud
- Setup
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/cdn/custom-vcl-snippets/fastly-vcl-badreferer.html
+status: migrated
---
The following example shows how to configure [Fastly Edge Dictionary](https://docs.fastly.com/guides/edge-dictionaries/working-with-dictionaries-using-the-api) with a custom VCL snippet to block referral spam from your {{ site.data.var.ece }} site.
diff --git a/src/cloud/cdn/fastly-vcl-blocking.md b/src/cloud/cdn/fastly-vcl-blocking.md
index 7f9e0a5552c..58d395edb22 100644
--- a/src/cloud/cdn/fastly-vcl-blocking.md
+++ b/src/cloud/cdn/fastly-vcl-blocking.md
@@ -4,10 +4,11 @@ title: Custom VCL for blocking requests
redirect_from:
- /cloud/configure/fastly-vcl-blacklist.html
- /cloud/cdn/fastly-vcl-blacklist.html
-
functional_areas:
- Cloud
- Setup
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/cdn/custom-vcl-snippets/fastly-vcl-blocking.html
+status: migrated
---
You can use the Fastly CDN module for Magento 2 to create an Edge ACL with a list of IP addresses that you want to block. Then, you can use that list in combination with a VCL snippet to block incoming requests. The code checks the IP address of the incoming request. If it matches an IP address included in the ACL list, Fastly blocks the request from accessing your site and returns a `403 Forbidden error`. All other client IPs are allowed access.
diff --git a/src/cloud/cdn/fastly-vcl-bypass-to-origin.md b/src/cloud/cdn/fastly-vcl-bypass-to-origin.md
index 792fdd7633c..af5ce4d5469 100644
--- a/src/cloud/cdn/fastly-vcl-bypass-to-origin.md
+++ b/src/cloud/cdn/fastly-vcl-bypass-to-origin.md
@@ -4,6 +4,8 @@ title: Custom VCL to bypass Fastly cache
functional_areas:
- Cloud
- Setup
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/cdn/custom-vcl-snippets/fastly-vcl-bypass-to-origin.html
+status: migrated
---
You can create a custom VCL snippet to bypass the Fastly cache so you can troubleshoot request traffic to the origin server, for example to determine whether site issues are caused by caching, or to troubleshoot headers.
diff --git a/src/cloud/cdn/fastly-vcl-wordpress.md b/src/cloud/cdn/fastly-vcl-wordpress.md
index a2e3705d5fe..2eb8e79f05b 100644
--- a/src/cloud/cdn/fastly-vcl-wordpress.md
+++ b/src/cloud/cdn/fastly-vcl-wordpress.md
@@ -6,6 +6,8 @@ redirect_from:
functional_areas:
- Cloud
- Setup
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/cdn/custom-vcl-snippets/fastly-vcl-wordpress.html
+status: migrated
---
The following procedure describes how to reroute incoming requests from a {{ site.data.var.ee }} store to a separate WordPress site using the Fastly edge module _Other CMS/backend integration_ with an Edge dictionary. You can follow a similar process to reroute requests to other CMS backends.
diff --git a/src/cloud/cdn/fastly-waf-service.md b/src/cloud/cdn/fastly-waf-service.md
index c726d1b6b4d..8399f914de2 100644
--- a/src/cloud/cdn/fastly-waf-service.md
+++ b/src/cloud/cdn/fastly-waf-service.md
@@ -6,6 +6,8 @@ functional_areas:
- Install
- Security
- Compliance
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/cdn/fastly-waf-service.html
+status: migrated
---
Powered by Fastly, the web application firewall (WAF) service for {{ site.data.var.ece }} detects, logs, and blocks malicious request traffic before it can damage your sites or network. The WAF service is available on production environments only.
diff --git a/src/cloud/cdn/trouble-fastly.md b/src/cloud/cdn/trouble-fastly.md
index 3fa38bc0e25..3d5db746e79 100644
--- a/src/cloud/cdn/trouble-fastly.md
+++ b/src/cloud/cdn/trouble-fastly.md
@@ -6,6 +6,8 @@ redirect_from:
functional_areas:
- Cloud
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/cdn/fastly-troubleshooting.html
+status: migrated
---
Use the following information to troubleshoot and manage the Fastly CDN module for Magento 2 in your {{ site.data.var.ece }} project environments. For example, you can investigate response header values and caching behavior to resolve Fastly service and performance issues.
diff --git a/src/cloud/composer-packages/ece-patches.md b/src/cloud/composer-packages/ece-patches.md
index ff1f7058ff1..1deabbc1762 100644
--- a/src/cloud/composer-packages/ece-patches.md
+++ b/src/cloud/composer-packages/ece-patches.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Setup
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/release-notes/ece-tools-package.html
+status: migrated
---
{:.bs-callout-warning}
diff --git a/src/cloud/composer-packages/patch-notes.md b/src/cloud/composer-packages/patch-notes.md
index 9e111f6c3f3..cbdd099331d 100644
--- a/src/cloud/composer-packages/patch-notes.md
+++ b/src/cloud/composer-packages/patch-notes.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Setup
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/release-notes/cloud-tools-suite.html
+status: migrated
---
The release information in this section relates to [Composer packages]({{ site.baseurl }}/cloud/reference/cloud-composer.html) used by {{site.data.var.ece}} only. For general release information, refer to the main {{site.data.var.ee}} [v2.3 Release Notes]({{ site.baseurl }}/guides/v2.3/release-notes/bk-release-notes.html) page.
diff --git a/src/cloud/configure/configuration-overview.md b/src/cloud/configure/configuration-overview.md
index 92637488df9..d3f75bdc9c7 100644
--- a/src/cloud/configure/configuration-overview.md
+++ b/src/cloud/configure/configuration-overview.md
@@ -8,6 +8,8 @@ menu_node: parent
functional_areas:
- Cloud
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure-store/overview.html
+status: migrated
---
The following information walks you through the options for configuring your store on your local and in all environments. You may need to configure files and settings in your local, pushing settings with your code. For specific services, you configure settings directly in Staging and Production environments.
diff --git a/src/cloud/configure/configure-best-practices.md b/src/cloud/configure/configure-best-practices.md
index 4a568802595..d8d34d2ee12 100644
--- a/src/cloud/configure/configure-best-practices.md
+++ b/src/cloud/configure/configure-best-practices.md
@@ -8,6 +8,8 @@ menu_node:
functional_areas:
- Cloud
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure-store/best-practices.html
+status: migrated
---
For detailed information for configuring your store, sites, and websites, you may want to review the [{{site.data.var.ee}} 2.2.x User Guide]({{ site.user_guide_url }}/getting-started.html). This page provides best practices, helpful information, and guidelines for configuring your stores, sites, and more with additional content to post over time and across versions.
@@ -26,7 +28,7 @@ The following are tips to help create, update, and manage promotions and campaig
* A promotion can be part of a campaign. A campaign cannot be a part of a promotion. You can have lists of promotions as price rules to use multiples times, with multiple campaigns.
* When you create a promotion, it will always create an initial campaign that is inactive. It will have a start date but not an end date. You can ignore this initial campaign. You can Schedule a New Update with the correct campaign schedule and make it active.
-* A campaign has a start and end date, not a promotion. The Scheduler that appears when you create a promotion does not configure the start and end dates for the promotion. It allows you so schedule your campaign this promotion is associated with while you are on the promotion’s configuration page.
+* A campaign has a start and end date, not a promotion. The Scheduler that appears when you create a promotion does not configure the start and end dates for the promotion. It allows you so schedule your campaign this promotion is associated with while you are on the promotion's configuration page.
* You cannot directly edit in Staged Content. If you need to edit settings and options in the campaign, you will need to edit the original or a replica and push to overwrite in Staged Content. For example, if you do not an end date for a campaign, you must edit the original and push to update.
## Advanced Pricing and Staged Content {#adv-pricing}
diff --git a/src/cloud/configure/import-url-rewrites.md b/src/cloud/configure/import-url-rewrites.md
index 09116065e17..2f86f1de02b 100644
--- a/src/cloud/configure/import-url-rewrites.md
+++ b/src/cloud/configure/import-url-rewrites.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Setup
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure/routes/redirects.html
+status: migrated
---
You can easily migrate to the {{site.data.var.ece}} platform without losing SEO rankings and traffic. Use the `magento/url-rewrite-import-export` module to redirect traffic from your old, indexed URLs to new URLs.
diff --git a/src/cloud/configure/setup-b2b.md b/src/cloud/configure/setup-b2b.md
index 7a0293dc7e6..a592b784e19 100644
--- a/src/cloud/configure/setup-b2b.md
+++ b/src/cloud/configure/setup-b2b.md
@@ -6,6 +6,8 @@ functional_areas:
- Extensions
- Module
- B2B
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure-store/b2b-module.html
+status: migrated
---
If your customers are companies, you can install the {{site.data.var.b2b}} module to extend your {{site.data.var.ece}} Pro project to accommodate a business-to-business model. Although this topic provides information specific to installing and configuring the B2B module for {{site.data.var.ece}}, you can find additional B2B information in the following guides:
diff --git a/src/cloud/configure/setup-cron-jobs.md b/src/cloud/configure/setup-cron-jobs.md
index 747d2923b89..2562ca416b5 100644
--- a/src/cloud/configure/setup-cron-jobs.md
+++ b/src/cloud/configure/setup-cron-jobs.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Setup
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure/app/properties/crons-property.html
+status: migrated
---
{{site.data.var.ee}} uses cron jobs for numerous features to schedule activities. This topic provides information for configuring crons for `{{site.data.var.ece}}` projects using the [`.magento.app.yaml`]({{ site.baseurl }}/cloud/project/magento-app.html) file.
@@ -189,6 +191,12 @@ Adobe has updated the {{site.data.var.ece}} package to optimize cron processing
You can review cron processing information in the application-level log files for each environment. See [Application logs]({{ site.baseurl }}/cloud/project/log-locations.html#application-logs).
+{:.bs-callout-info}
+Note that on multi-node environments (such as Pro), cron jobs are executed on a randomly selected node. Because `~/var/log` is not shared between nodes, you may need to manually merge logs to get full visibility of cron execution.
+
+{:.bs-callout-info}
+Cron jobs are executed with a different set of environment variables than are available in an SSH session. Notably, `$USER` is not available to cron jobs.
+
See the following {{site.data.var.ee}} Support articles for help troubleshooting cron-related problems:
- [Cron tasks lock tasks from other groups](https://support.magento.com/hc/en-us/articles/360029219812-Cron-tasks-lock-tasks-from-other-groups)
diff --git a/src/cloud/deploy/cloud-deployment-process.md b/src/cloud/deploy/cloud-deployment-process.md
index 8df7740d0b0..e962c40babd 100644
--- a/src/cloud/deploy/cloud-deployment-process.md
+++ b/src/cloud/deploy/cloud-deployment-process.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Deploy
- SCD
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/deploy/process.html
+status: migrated
---
The deployment process begins when you perform a merge, push, or synchronization of your environment, or when you trigger a [manual redeployment]({{ site.baseurl }}/cloud/reference/cli-ref-topic.html#git-commands). The deployment process takes time, but there are ways to optimize deployment that depend on whether you are developing and testing or working with a live site. Most notably, you can control the [static content deployment]({{ site.baseurl }}/cloud/deploy/static-content-deployment.html).
diff --git a/src/cloud/deploy/continuous-deployment.md b/src/cloud/deploy/continuous-deployment.md
index bbaf05c576b..4210ad7d4c5 100644
--- a/src/cloud/deploy/continuous-deployment.md
+++ b/src/cloud/deploy/continuous-deployment.md
@@ -8,6 +8,8 @@ menu_node:
functional_areas:
- Cloud
- Deploy
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/deploy/best-practices.html
+status: migrated
---
Following your branching and development methodologies, you can easily develop new features, configure changes, and add extensions to continuously develop and deploy updates.
diff --git a/src/cloud/deploy/optimize-cloud-deployment.md b/src/cloud/deploy/optimize-cloud-deployment.md
index c1ba5b59b07..38c9cb32076 100644
--- a/src/cloud/deploy/optimize-cloud-deployment.md
+++ b/src/cloud/deploy/optimize-cloud-deployment.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Deploy
- SCD
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/deploy/optimization.html
+status: migrated
---
Site performance can suffer during the deployment process. The length of time a site is in maintenance mode when deploying to a production site depends on many factors, such as environment configuration and the amount of content a site contains. The first best practice for optimizing your Cloud deployment is to [upgrade to use `{{site.data.var.ct}}`]({{ site.baseurl }}/cloud/project/ece-tools-upgrade-project.html) to benefit from the package features, such as commands to create a backup of the database and verify environment configuration.
diff --git a/src/cloud/deploy/reduce-downtime.md b/src/cloud/deploy/reduce-downtime.md
index f560a207df8..370a5ce8334 100644
--- a/src/cloud/deploy/reduce-downtime.md
+++ b/src/cloud/deploy/reduce-downtime.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Deploy
- SCD
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/deploy/reduce-downtime.html
+status: migrated
---
{{site.data.var.ece}} runs the application in [_maintenance_ mode]({{site.baseurl}}/guides/v2.3/config-guide/bootstrap/magento-modes.html#maintenance-mode) during the deploy phase, which takes your site offline until the deployment is complete. The length of time your Production site is in maintenance mode depends on the size of the site, the number of changes applied during the deployment, and the configuration for static content deployment. It is possible to configure your project so that it deploys with a **zero** downtime effect.
diff --git a/src/cloud/deploy/scenario-based-deployment.md b/src/cloud/deploy/scenario-based-deployment.md
index 67c1fb1a8ab..ed4b9e23de5 100644
--- a/src/cloud/deploy/scenario-based-deployment.md
+++ b/src/cloud/deploy/scenario-based-deployment.md
@@ -4,6 +4,8 @@ title: Scenario-based deployment
functional_areas:
- Cloud
- Deploy
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/deploy/scenario-based.html
+status: migrated
---
With `{{site.data.var.ct}}` 2002.1.0 and later, you can use the scenario-based deployment feature to customize the default deployment behavior.
diff --git a/src/cloud/deploy/smart-wizards.md b/src/cloud/deploy/smart-wizards.md
index 2537733dbf1..9059f8ef10e 100644
--- a/src/cloud/deploy/smart-wizards.md
+++ b/src/cloud/deploy/smart-wizards.md
@@ -7,6 +7,8 @@ functional_areas:
- Cloud
- Setup
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/deploy/smart-wizards.html
+status: migrated
---
The smart wizards can help you determine whether your Cloud configuration follows best practices. The available wizards assist with the following configurations:
diff --git a/src/cloud/deploy/static-content-deployment.md b/src/cloud/deploy/static-content-deployment.md
index 20f8b80ffe3..adae1ed2baa 100644
--- a/src/cloud/deploy/static-content-deployment.md
+++ b/src/cloud/deploy/static-content-deployment.md
@@ -4,6 +4,8 @@ title: Static content deployment strategies
functional_areas:
- Cloud
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/deploy/static-content.html
+status: migrated
---
Static content deployment (SCD) has a significant impact on the store deployment process that depends on how much content to generate—such as images, scripts, CSS, videos, themes, locales, and web pages—and when to generate the content. For example, the default strategy generates static content during the [deploy phase]({{ site.baseurl }}/cloud/deploy/cloud-deployment-process.html#-deploy-phase) when the site is in maintenance mode; however, this deployment strategy takes time to write the content directly to the mounted `pub/static` directory. You have several options or strategies to help you improve the deployment time depending on your needs.
diff --git a/src/cloud/docker/docker-config-blackfire-io.md b/src/cloud/docker/docker-config-blackfire-io.md
index 46aa002c9db..c9d449e84d6 100644
--- a/src/cloud/docker/docker-config-blackfire-io.md
+++ b/src/cloud/docker/docker-config-blackfire-io.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Setup
- Configuration
+redirect_to: https://developer.adobe.com/commerce/cloud-tools/docker/test/blackfire/
+status: migrated
---
You can add Blackfire.io to your {{site.data.var.mcd-prod}} environment to fully automate performance testing.
diff --git a/src/cloud/docker/docker-config-sources.md b/src/cloud/docker/docker-config-sources.md
index 9b0e892ea09..5ddb6804c1c 100644
--- a/src/cloud/docker/docker-config-sources.md
+++ b/src/cloud/docker/docker-config-sources.md
@@ -7,6 +7,8 @@ functional_areas:
- Configuration
redirect_from:
- /cloud/reference/docker-config.html
+redirect_to: https://developer.adobe.com/commerce/cloud-tools/docker/configure/configuration-sources/
+status: migrated
---
You can create the Docker Compose configuration to build and deploy the Docker containers for your {{site.data.var.ee}} project from the following sources:
diff --git a/src/cloud/docker/docker-config.md b/src/cloud/docker/docker-config.md
index c703078d2e3..2c3a33247bc 100644
--- a/src/cloud/docker/docker-config.md
+++ b/src/cloud/docker/docker-config.md
@@ -7,6 +7,8 @@ functional_areas:
- Configuration
redirect_from:
- /cloud/reference/docker-config.html
+redirect_to: https://developer.adobe.com/commerce/cloud-tools/docker/configure/
+status: migrated
---
{{site.data.var.mcd-prod}} uses Docker Compose to build and deploy {{site.data.var.ee}} to a multi-container Docker application. You can generate the Docker Compose configuration to build and deploy Docker from the following sources:
diff --git a/src/cloud/docker/docker-containers-cli.md b/src/cloud/docker/docker-containers-cli.md
index 40eb4c6cab6..d59cf7f4c5d 100755
--- a/src/cloud/docker/docker-containers-cli.md
+++ b/src/cloud/docker/docker-containers-cli.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Docker
- Configuration
+redirect_to: https://developer.adobe.com/commerce/cloud-tools/docker/containers/cli/
+status: migrated
---
The following CLI containers, most of which are based on a [PHP-CLI version 7 image], provide `magento-cloud` and `{{site.data.var.ct}}` commands to perform file system operations and interact with the application:
diff --git a/src/cloud/docker/docker-containers-service.md b/src/cloud/docker/docker-containers-service.md
index 6e2877d796d..e46b293e15f 100755
--- a/src/cloud/docker/docker-containers-service.md
+++ b/src/cloud/docker/docker-containers-service.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Docker
- Configuration
+redirect_to: https://developer.adobe.com/commerce/cloud-tools/docker/containers/service/
+status: migrated
---
The following containers provide the services required to build, deploy and run {{site.data.var.ee}} sites.
diff --git a/src/cloud/docker/docker-containers.md b/src/cloud/docker/docker-containers.md
index ae82a137950..792e5017d9c 100644
--- a/src/cloud/docker/docker-containers.md
+++ b/src/cloud/docker/docker-containers.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Setup
- Configuration
+redirect_to: https://developer.adobe.com/commerce/cloud-tools/docker/containers/
+status: migrated
---
The [`{{site.data.var.mcd-package}}` repository][docker-repo] contains build information to create a Docker environment with the required specifications for {{site.data.var.ece}}. The build configuration creates a Docker instance with CLI and service containers required to run {{site.data.var.ece}} in a local Docker environment. You can customize the Docker containers available in the repository and add more as needed.
diff --git a/src/cloud/docker/docker-development-debug.md b/src/cloud/docker/docker-development-debug.md
index 39447d59387..2c0e920ac0e 100644
--- a/src/cloud/docker/docker-development-debug.md
+++ b/src/cloud/docker/docker-development-debug.md
@@ -6,6 +6,8 @@ functional_areas:
- Setup
- Configuration
- Testing
+redirect_to: https://developer.adobe.com/commerce/cloud-tools/docker/test/configure-xdebug/
+status: migrated
---
Xdebug is an extension for debugging your PHP code. {{site.data.var.mcd-prod}} provides a separate container to handle Xdebug requests in the Docker environment. Use this container to enable Xdebug and debug PHP code in your Docker environment without affecting your {{site.data.var.ece}} project configuration.
@@ -122,7 +124,7 @@ You can debug any {{site.data.var.ee}} command or PHP script using the following
{:.procedure}
To debug CLI commands:
-1. In your PhpStorm project, open the **Build, Extension, Deployment** > **Docker** panel, and then click `+` to add a new Docker server and update the following settings:
+1. In your PhpStorm project, open the **Build, Execution, Deployment** > **Docker** panel, and then click `+` to add a new Docker server and update the following settings:
- **Name**—Enter a name for the server, for example `Docker Cloud`.
- **Connect to Docker daemon with**—
diff --git a/src/cloud/docker/docker-development.md b/src/cloud/docker/docker-development.md
index 342f7ee1cc6..ef91cfc1014 100644
--- a/src/cloud/docker/docker-development.md
+++ b/src/cloud/docker/docker-development.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Docker
- Configuration
+redirect_to: https://developer.adobe.com/commerce/cloud-tools/docker/
+status: migrated
---
{{site.data.var.mcd-prod}} provides an option to deploy {{site.data.var.ee}} to a Docker environment for development, testing, and automation tasks. It includes the following features:
diff --git a/src/cloud/docker/docker-extend.md b/src/cloud/docker/docker-extend.md
index 607642cde4a..5f167501a0f 100644
--- a/src/cloud/docker/docker-extend.md
+++ b/src/cloud/docker/docker-extend.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Docker
- Configuration
+redirect_to: https://developer.adobe.com/commerce/cloud-tools/docker/configure/extend-docker-configuration/
+status: migrated
---
You can use the built-in extension mechanism of Docker to specify [multiple compose files]. The following example replaces the default value of the `ENABLE_SENDMAIL` environment variable.
diff --git a/src/cloud/docker/docker-installation.md b/src/cloud/docker/docker-installation.md
index ac860eadf25..3c5903f5613 100644
--- a/src/cloud/docker/docker-installation.md
+++ b/src/cloud/docker/docker-installation.md
@@ -4,6 +4,8 @@ title: Prepare Commerce for Docker
functional_areas:
- Cloud
- Configuration
+redirect_to: https://developer.adobe.com/commerce/cloud-tools/docker/setup/initialize-docker/
+status: migrated
---
{{site.data.var.mcd-prod}} is one of the {{site.data.var.csuite}} packages designed to deploy and manage local {{site.data.var.ee}} Docker environments for both cloud and on-premises projects.
diff --git a/src/cloud/docker/docker-launch.md b/src/cloud/docker/docker-launch.md
index 546a6383e7e..602b7ab314e 100644
--- a/src/cloud/docker/docker-launch.md
+++ b/src/cloud/docker/docker-launch.md
@@ -7,6 +7,8 @@ functional_areas:
- Configuration
redirect_from:
- /cloud/reference/docker-launch.html
+redirect_to: https://developer.adobe.com/commerce/cloud-tools/docker/deploy/
+status: migrated
---
By default, `{{site.data.var.mcd-prod}}` deploys {{site.data.var.ee}} to a read-only file system in the Docker environment. This deployment mirrors the read-only file system in the Production environment. You have the option to deploy a Docker environment in developer mode, which provides an active development environment with full, writable file system permissions.
diff --git a/src/cloud/docker/docker-manage-cron-jobs.md b/src/cloud/docker/docker-manage-cron-jobs.md
index 7ef48dc50fc..b3620a01047 100644
--- a/src/cloud/docker/docker-manage-cron-jobs.md
+++ b/src/cloud/docker/docker-manage-cron-jobs.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Setup
- Configuration
+redirect_to: https://developer.adobe.com/commerce/cloud-tools/docker/configure/manage-cron-jobs/
+status: migrated
---
The [Cron container] runs the scheduled cron jobs automatically based on the cron configuration defined in the [`crons` property of the `.magento.app.yaml` file]({{ site.baseurl }}/cloud/project/magento-app-properties.html#crons), and any custom configuration specified in the `docker-compose-override.yml` file.
diff --git a/src/cloud/docker/docker-manage-database.md b/src/cloud/docker/docker-manage-database.md
index 550ed414b7e..a80b1b01d1d 100644
--- a/src/cloud/docker/docker-manage-database.md
+++ b/src/cloud/docker/docker-manage-database.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Setup
- Configuration
+redirect_to: https://developer.adobe.com/commerce/cloud-tools/docker/configure/manage-database/
+status: migrated
---
The Cloud Docker development environment provides MySQL services through a MariaDB (default) or MySQL database deployed to the [Docker database container][]. You connect to the database using `docker-compose` commands. You can also import data from an existing {{site.data.var.ece}} project into the database container using the `magento-cloud db:dump` command.
diff --git a/src/cloud/docker/docker-mode-developer.md b/src/cloud/docker/docker-mode-developer.md
index 3615e6931c9..a8a2faa3152 100644
--- a/src/cloud/docker/docker-mode-developer.md
+++ b/src/cloud/docker/docker-mode-developer.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Setup
- Docker
+redirect_to: https://developer.adobe.com/commerce/cloud-tools/docker/deploy/developer-mode/
+status: migrated
---
Developer mode supports an active development environment with full, writable file system permissions. This option builds the Docker environment in developer mode and verifies configured service versions.
diff --git a/src/cloud/docker/docker-mode-production.md b/src/cloud/docker/docker-mode-production.md
index c0ab394cff8..9e8eb467bb9 100644
--- a/src/cloud/docker/docker-mode-production.md
+++ b/src/cloud/docker/docker-mode-production.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Setup
- Docker
+redirect_to: https://developer.adobe.com/commerce/cloud-tools/docker/deploy/production-mode/
+status: migrated
---
Production mode is the default configuration setting for launching the Docker environment with read-only filesystem permissions. This option builds the Docker environment in production mode and verifies configured service versions.
diff --git a/src/cloud/docker/docker-multi-website.md b/src/cloud/docker/docker-multi-website.md
index e3630674376..a28a95b695e 100644
--- a/src/cloud/docker/docker-multi-website.md
+++ b/src/cloud/docker/docker-multi-website.md
@@ -6,6 +6,8 @@ functional_areas:
- Setup
- Configuration
- Website
+redirect_to: https://developer.adobe.com/commerce/cloud-tools/docker/configure/multiple-sites/
+status: migrated
---
Cloud Docker supports multiple websites or stores by adding subdomains to your configuration. See [Understanding websites, stores, and store views][].
diff --git a/src/cloud/docker/docker-quick-reference.md b/src/cloud/docker/docker-quick-reference.md
index d5ec54a2827..1e4dac7aba2 100644
--- a/src/cloud/docker/docker-quick-reference.md
+++ b/src/cloud/docker/docker-quick-reference.md
@@ -4,6 +4,8 @@ title: Docker development quick reference
functional_areas:
- Cloud
- Docker
+redirect_to: https://developer.adobe.com/commerce/cloud-tools/docker/quick-reference/
+status: migrated
---
This Quick Reference provides information about using Docker Compose commands, the Docker Compose configuration generator, and the {{site.data.var.mcd-prod}} CLI to configure, deploy, and use your Docker environment for application development. See the following topics for more detailed instructions:
diff --git a/src/cloud/docker/docker-syncing-data.md b/src/cloud/docker/docker-syncing-data.md
index 4a03fa99ff7..f2e44c6bb4d 100755
--- a/src/cloud/docker/docker-syncing-data.md
+++ b/src/cloud/docker/docker-syncing-data.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Setup
- Configuration
+redirect_to: https://developer.adobe.com/commerce/cloud-tools/docker/setup/synchronize-data/
+status: migrated
---
You have the option to launch a Docker environment in [developer mode][set the launch mode], which provides an active development environment with full, writable file system permissions.
diff --git a/src/cloud/docker/docker-test-app-mftf.md b/src/cloud/docker/docker-test-app-mftf.md
index a45c7bd753d..371f76e5775 100644
--- a/src/cloud/docker/docker-test-app-mftf.md
+++ b/src/cloud/docker/docker-test-app-mftf.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
redirect_from:
- /cloud/docker/docker-mftf.html
+redirect_to: https://developer.adobe.com/commerce/cloud-tools/docker/test/application-testing/
+status: migrated
---
In a Cloud Docker development environment, you can use the [Magento Functional Testing Framework (MFTF)][MFTF docs] for Magento application testing. In this environment, you run MFTF commands using the `mftf-command` ([CLI container command]). For example, the following command generates the MFTF tests:
diff --git a/src/cloud/docker/docker-test-magecloud-pkg-code.md b/src/cloud/docker/docker-test-magecloud-pkg-code.md
index acc0685d4a0..d18ea96abc2 100644
--- a/src/cloud/docker/docker-test-magecloud-pkg-code.md
+++ b/src/cloud/docker/docker-test-magecloud-pkg-code.md
@@ -7,6 +7,8 @@ functional_areas:
- Configuration
redirect from:
- /cloud/docker/docker-development-testing.html
+redirect_to: https://developer.adobe.com/commerce/cloud-tools/docker/test/code-testing/
+status: migrated
---
In a {{site.data.var.mcd-prod}} development environment, you can use the integrated test suite in each [{{site.data.var.csuite}}] package for Magento code testing. The test suites, which use the [Codeception testing framework for PHP], provide acceptance tests to validate code intended for contribution to Magento Cloud package repositories.
diff --git a/src/cloud/docker/docker-troubleshooting.md b/src/cloud/docker/docker-troubleshooting.md
index 8b8eba6cfa0..4b769c4dcba 100644
--- a/src/cloud/docker/docker-troubleshooting.md
+++ b/src/cloud/docker/docker-troubleshooting.md
@@ -4,6 +4,8 @@ title: Get support for Magento Cloud Docker
functional_areas:
- Cloud
- Configuration
+redirect_to: https://developer.adobe.com/commerce/cloud-tools/docker/get-support/
+status: migrated
---
{{site.data.var.mcd-prod}} is a Magento Community Engineering project supported by the Magento developer community. You have several options to get support and learn more about {{site.data.var.mcd-prod}} and local development.
diff --git a/src/cloud/docker/docker-upgrade.md b/src/cloud/docker/docker-upgrade.md
index f66b5089197..629ce1d9101 100644
--- a/src/cloud/docker/docker-upgrade.md
+++ b/src/cloud/docker/docker-upgrade.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Configuration
- Upgrade
+redirect_to: https://developer.adobe.com/commerce/cloud-tools/docker/upgrade-docker-package/
+status: migrated
---
We recommend that you use the latest version of {{site.data.var.mcd-prod}}. The version requirement is specified in the `composer.json` file for your project. Use the following instructions for the upgrade process.
diff --git a/src/cloud/env/environment-vars_magento.md b/src/cloud/env/environment-vars_magento.md
index c1c9a831d19..c06f14cfad0 100644
--- a/src/cloud/env/environment-vars_magento.md
+++ b/src/cloud/env/environment-vars_magento.md
@@ -4,6 +4,8 @@ title: ADMIN variables
functional_areas:
- Cloud
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure/env/stage/variables-admin.html
+status: migrated
---
Users that have administrative access to the {{site.data.var.ece}} project can use the following project environment variables to override the configuration settings for the administrative user account to access the Admin UI. See [Change the ADMIN variables]({{ site.baseurl }}/cloud/before/before-setup-env-2_clone.html).
diff --git a/src/cloud/env/environments-ssh.md b/src/cloud/env/environments-ssh.md
index 011271f53b2..973875007b1 100644
--- a/src/cloud/env/environments-ssh.md
+++ b/src/cloud/env/environments-ssh.md
@@ -9,6 +9,8 @@ functional_areas:
- Cloud
- Setup
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/secure-connections.html
+status: migrated
---
SSH, or Secure Shell, is a common protocol used to securely log into remote servers and systems. You will typically use SSH to access your environments directly to enter [CLI commands]({{ site.baseurl }}/cloud/reference/cli-ref-topic.html) for managing your branching, creating variables, and much more. We also support [sFTP](#sftp) (Secure FTP) using your SSH public key.
diff --git a/src/cloud/env/environments-start.md b/src/cloud/env/environments-start.md
index 874d7b7ddfc..7e3bc472e7b 100644
--- a/src/cloud/env/environments-start.md
+++ b/src/cloud/env/environments-start.md
@@ -7,6 +7,8 @@ redirect_from:
- /cloud/howtos/how-to.html
functional_areas:
- Cloud
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/cli-branches.html
+status: migrated
---
To install the `magento-cloud` CLI, see the [Magento Cloud CLI reference]({{ site.baseurl }}/cloud/reference/cli-ref-topic.html). After you install the `magento-cloud` CLI and set up SSH keys for remote access to your cloud infrastructure, you can use `magento-cloud` CLI commands to manage the environments for your {{site.data.var.ece}} projects. For information about the environment architecture, see [Starter architecture]({{ site.baseurl }}/cloud/architecture/starter-architecture.html) or [Pro architecture]({{ site.baseurl }}/cloud/architecture/pro-architecture.html).
diff --git a/src/cloud/env/environments.md b/src/cloud/env/environments.md
index f828249f214..e5e049b3028 100644
--- a/src/cloud/env/environments.md
+++ b/src/cloud/env/environments.md
@@ -5,6 +5,8 @@ redirect_from:
- /cloud/deploy/configure-deploy.html
functional_areas:
- Cloud
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure/overview.html
+status: migrated
---
After fully configuring your store, you need to configure your environments. Environments in {{site.data.var.ece}} include containers with applications, services, and a database to provide a complete system for your {{site.data.var.ee}} application codebase and files.
diff --git a/src/cloud/env/log-handlers.md b/src/cloud/env/log-handlers.md
index da2b835525f..223d73976e4 100644
--- a/src/cloud/env/log-handlers.md
+++ b/src/cloud/env/log-handlers.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Setup
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure/env/log/log-handlers.html
+status: migrated
---
You can configure logging handlers to send messages to a remote logging server. A logging handler pushes build and deploy logs to other systems, similarly to the way you push logs to Slack and email. You can enable a _syslog_ handler, which is ideal for logging messages related to hardware, or a Graylog Extended Log Format (GELF) handler, which is ideal for logging messages from software applications.
diff --git a/src/cloud/env/restore-environment.md b/src/cloud/env/restore-environment.md
index 7a83aafaa21..aeb64fd4a8d 100644
--- a/src/cloud/env/restore-environment.md
+++ b/src/cloud/env/restore-environment.md
@@ -1,6 +1,8 @@
---
title: Restore an environment
group: cloud-guide
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/restore-environment.html
+status: migrated
---
If you encounter issues in your environment and do not have a [valid snapshot]({{ site.baseurl }}/cloud/project/project-webint-snap.html), you can try restoring your environment in one of the following ways:
diff --git a/src/cloud/env/setup-notifications.md b/src/cloud/env/setup-notifications.md
index f807c8cbfde..9bf5d250692 100644
--- a/src/cloud/env/setup-notifications.md
+++ b/src/cloud/env/setup-notifications.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Setup
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure/env/log/set-up-notifications.html
+status: migrated
---
By default, {{site.data.var.ece}} writes build and deploy actions to the `app/var/log/cloud.log` file inside the {{site.data.var.ee}} root application directory. Optionally, you can send logs to a messaging system, such as Slack and email, to receive real-time notifications.
diff --git a/src/cloud/env/variables-build.md b/src/cloud/env/variables-build.md
index 96d14176a2b..6aafd3a75de 100644
--- a/src/cloud/env/variables-build.md
+++ b/src/cloud/env/variables-build.md
@@ -4,6 +4,8 @@ title: Build variables
functional_areas:
- Cloud
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure/env/stage/variables-build.html
+status: migrated
---
The following _build_ variables control actions in the build phase and can inherit and override values from the [Global variables]({{ site.baseurl }}/cloud/env/variables-global.html). Insert these variables in the `build` stage of the `.magento.env.yaml` file:
diff --git a/src/cloud/env/variables-cloud.md b/src/cloud/env/variables-cloud.md
index a29865fa385..4c236c7d756 100644
--- a/src/cloud/env/variables-cloud.md
+++ b/src/cloud/env/variables-cloud.md
@@ -4,6 +4,8 @@ title: Cloud variables
functional_areas:
- Cloud
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure/env/stage/variables-cloud.html
+status: migrated
---
Environment variables that are specific to {{site.data.var.ece}} use the `MAGENTO_CLOUD_*` prefix:
diff --git a/src/cloud/env/variables-deploy.md b/src/cloud/env/variables-deploy.md
index 837e5417f0f..7f012331f4f 100644
--- a/src/cloud/env/variables-deploy.md
+++ b/src/cloud/env/variables-deploy.md
@@ -6,6 +6,8 @@ functional_areas:
- Configuration
redirect_from:
- /cloud/trouble/message-queues.html
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure/env/stage/variables-deploy.html
+status: migrated
---
The following _deploy_ variables control actions in the deploy phase and can inherit and override values from the [Global variables]({{ site.baseurl }}/cloud/env/variables-global.html). Insert these variables in the `deploy` stage of the `.magento.env.yaml` file:
diff --git a/src/cloud/env/variables-global.md b/src/cloud/env/variables-global.md
index ac93dfc59c0..6ff84f7cf75 100644
--- a/src/cloud/env/variables-global.md
+++ b/src/cloud/env/variables-global.md
@@ -4,6 +4,8 @@ title: Global variables
functional_areas:
- Cloud
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure/env/stage/variables-global.html
+status: migrated
---
The following _global_ variables control actions across each phase: build, deploy, and post-deploy. Because global variables impact every phase, you must set them in the `global` stage of the `.magento.env.yaml` file:
diff --git a/src/cloud/env/variables-intro.md b/src/cloud/env/variables-intro.md
index d581b8b15ef..7bcd528261a 100644
--- a/src/cloud/env/variables-intro.md
+++ b/src/cloud/env/variables-intro.md
@@ -4,6 +4,8 @@ title: Environment variables
functional_areas:
- Cloud
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure/env/stage/variables-intro.html
+status: migrated
---
{{site.data.var.ece}} enables you to assign environment variables to override configuration options. The `ece-tools` package sets values in the `env.php` file based on values from [Cloud variables]({{site.baseurl}}/cloud/env/variables-cloud.html), variables set in the Project Web interface, and the `.magento.env.yaml` configuration file. The types of environment variables include:
diff --git a/src/cloud/env/variables-post-deploy.md b/src/cloud/env/variables-post-deploy.md
index 8967034dd2d..0e8b4418265 100644
--- a/src/cloud/env/variables-post-deploy.md
+++ b/src/cloud/env/variables-post-deploy.md
@@ -4,6 +4,8 @@ title: Post-deploy variables
functional_areas:
- Cloud
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure/env/stage/variables-post-deploy.html
+status: migrated
---
The following _post\_deploy_ variables control actions in the post-deploy phase and can inherit and override values from the [Global variables]({{ site.baseurl }}/cloud/env/variables-global.html). Insert these variables in the `post-deploy` stage of the `.magento.env.yaml` file:
diff --git a/src/cloud/env/working-with-variables.md b/src/cloud/env/working-with-variables.md
index ec0440387ad..47d99146feb 100644
--- a/src/cloud/env/working-with-variables.md
+++ b/src/cloud/env/working-with-variables.md
@@ -4,6 +4,8 @@ title: Working with variables
functional_areas:
- Cloud
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure/env/variable-levels.html
+status: migrated
---
Environment variables apply to a specific environment or branch. An environment _inherits_ variable definitions from the parent environment. You can override an inherited value by defining the variable specifically for the environment. For example, to set variables for development, define the variable values in the `.magento.env.yaml` file in the Integration environment. All environments branching from the Integration environment inherit those values. See [Deployment configuration]({{ site.baseurl }}/cloud/project/magento-env-yaml.html) for details about configuring your environment using the `.magento.env.yaml` file.
diff --git a/src/cloud/howtos/custom-theme.md b/src/cloud/howtos/custom-theme.md
index b012fe7b1be..97909e15859 100644
--- a/src/cloud/howtos/custom-theme.md
+++ b/src/cloud/howtos/custom-theme.md
@@ -9,6 +9,8 @@ functional_areas:
- Cloud
- Setup
- Theme
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure-store/custom-theme.html
+status: migrated
---
You can install one or multiple themes to use for one or all of your stores and sites in your project. Themes include multiple static files including images, fonts, CSS, JavaScript, PHP, and more to fully design your stores. You can add the theme by either extracting its code to the file system or using Composer.
diff --git a/src/cloud/howtos/debug.md b/src/cloud/howtos/debug.md
index b385c6defbc..fef7c7541fc 100644
--- a/src/cloud/howtos/debug.md
+++ b/src/cloud/howtos/debug.md
@@ -4,6 +4,8 @@ title: Configure Xdebug
functional_areas:
- Cloud
- Setup
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/test/debug.html
+status: migrated
---
Xdebug is an extension for debugging your PHP. The following explains how to configure Xdebug and PhpStorm to debug in your local environment. You can use the IDE of your choice. See the vendor documentation for those applications for further configuration information.
diff --git a/src/cloud/howtos/install-components.md b/src/cloud/howtos/install-components.md
index ccaab4e5597..2e96767b96c 100644
--- a/src/cloud/howtos/install-components.md
+++ b/src/cloud/howtos/install-components.md
@@ -6,6 +6,8 @@ functional_areas:
- Configuration
- Extensions
- Module
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure-store/extensions.html
+status: migrated
---
You can extend your {{site.data.var.ee}} application capabilities by adding an extension from the [Commerce Marketplace][]. For example, you can add a theme to change the look and feel of your storefront, or you can add a language package to localize your storefront and Admin panel.
diff --git a/src/cloud/howtos/sample-data.md b/src/cloud/howtos/sample-data.md
index a09b38e3f01..9eb2a7ad5f6 100644
--- a/src/cloud/howtos/sample-data.md
+++ b/src/cloud/howtos/sample-data.md
@@ -8,6 +8,8 @@ menu_node:
functional_areas:
- Cloud
- Setup
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/test/sample-data.html
+status: migrated
---
If you need some example data when developing your store, you can install our sample data. This data simulates an active {{site.data.var.ee}} store including customers, products, and other data. This sample data works best with a new "blank site" {{site.data.var.ece}} template installation when creating your project in your Integration environment.
diff --git a/src/cloud/integrations/bitbucket-integration.md b/src/cloud/integrations/bitbucket-integration.md
index d84f3d487f7..ff205a5d9a2 100644
--- a/src/cloud/integrations/bitbucket-integration.md
+++ b/src/cloud/integrations/bitbucket-integration.md
@@ -4,6 +4,8 @@ title: Bitbucket integration
functional_areas:
- Cloud
- Setup
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/dev-tools/integrations/bitbucket.html
+status: migrated
---
You can configure your Bitbucket repository to automatically build and deploy an environment when you push code changes. This integration synchronizes your Bitbucket repository with your {{site.data.var.ece}} account.
diff --git a/src/cloud/integrations/cloud-integrations.md b/src/cloud/integrations/cloud-integrations.md
index 55bd48bf82f..62dee4266f1 100644
--- a/src/cloud/integrations/cloud-integrations.md
+++ b/src/cloud/integrations/cloud-integrations.md
@@ -4,6 +4,8 @@ title: Integrations
functional_areas:
- Cloud
- Setup
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/dev-tools/integrations/overview.html
+status: migrated
---
Integrations are useful for leveraging the functionality of external services—such as Git hosting or Slack bots—and maintaining your current development processes, such as using the code review pull request function in GitHub. You can add the following integrations to your {{site.data.var.ece}} project:
diff --git a/src/cloud/integrations/github-integration.md b/src/cloud/integrations/github-integration.md
index 2fe5ebae0a4..79f06dd232d 100644
--- a/src/cloud/integrations/github-integration.md
+++ b/src/cloud/integrations/github-integration.md
@@ -4,6 +4,8 @@ title: GitHub integration
functional_areas:
- Cloud
- Setup
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/dev-tools/integrations/github.html
+status: migrated
---
The GitHub integration enables you to manage your {{site.data.var.ece}} environments directly from your GitHub repository. The integration manages content already in GitHub and synchronizes it with {{site.data.var.ee}}. Before you begin, your project and environments must be in a GitHub repository.
diff --git a/src/cloud/integrations/gitlab-integration.md b/src/cloud/integrations/gitlab-integration.md
index 3586675f9d2..74d692de0aa 100644
--- a/src/cloud/integrations/gitlab-integration.md
+++ b/src/cloud/integrations/gitlab-integration.md
@@ -4,6 +4,8 @@ title: GitLab integration
functional_areas:
- Cloud
- Setup
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/dev-tools/integrations/gitlab.html
+status: migrated
---
You can configure a GitLab repository to automatically build and deploy an environment when you push code changes. This integration synchronizes your GitLab repository with your {{ site.data.var.ece }} account.
@@ -105,7 +107,7 @@ To enable the GitLab integration:
1. From the terminal, add the GitLab integration to your {{site.data.var.ece}} project:
```bash
- magento-cloud integration:add --type gitlab --project=3txxjf32gtryos --token=qVUfeEn4ouze7A7JH --base-url=https://gitlab.com/ --server-project=my-agency/project-name --build-merge-requests=false --merge-requests-clone-parent-data=false --fetch-branches=true --prune-branches=true
+ magento-cloud integration:add --type gitlab --project=3txxjf32gtryos --token=qVUfeEn4ouze7A7JH #gitleaks:allow --base-url=https://gitlab.com/ --server-project=my-agency/project-name --build-merge-requests=false --merge-requests-clone-parent-data=false --fetch-branches=true --prune-branches=true
```
1. When prompted, enter "Y" to add the integration.
diff --git a/src/cloud/integrations/health-notifications.md b/src/cloud/integrations/health-notifications.md
index 070cebf3cc0..96c162f16a9 100644
--- a/src/cloud/integrations/health-notifications.md
+++ b/src/cloud/integrations/health-notifications.md
@@ -4,6 +4,8 @@ title: Health notifications
functional_areas:
- Cloud
- Setup
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/dev-tools/integrations/health-notifications.html
+status: migrated
---
{{site.data.var.ece}} monitors disk space usage on all applications and services in your Starter environment or your Pro Integration environment. A database disk that runs out of space could cause data corruption. The health status check occurs every 5 minutes and can notify you by email or other external service. There are three low-disk warnings for health notifications:
diff --git a/src/cloud/live/launch-steps.md b/src/cloud/live/launch-steps.md
index 21e1868d672..e980813331f 100644
--- a/src/cloud/live/launch-steps.md
+++ b/src/cloud/live/launch-steps.md
@@ -8,6 +8,8 @@ menu_node:
functional_areas:
- Cloud
- Testing
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/launch/steps.html
+status: migrated
---
{:.ref-header}
diff --git a/src/cloud/live/live-prot.md b/src/cloud/live/live-prot.md
index b0e38130800..9b9709fd6d9 100644
--- a/src/cloud/live/live-prot.md
+++ b/src/cloud/live/live-prot.md
@@ -8,6 +8,8 @@ menu_node:
functional_areas:
- Cloud
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/protective-block.html
+status: migrated
---
{{site.data.var.ece}} has a protective blocking feature that, under certain circumstances, restricts access to websites with security vulnerabilities. We use this partial blocking method to prevent exploitation of known security vulnerabilities.
diff --git a/src/cloud/live/live-sanity-check.md b/src/cloud/live/live-sanity-check.md
index 9a171671901..116803633a9 100644
--- a/src/cloud/live/live-sanity-check.md
+++ b/src/cloud/live/live-sanity-check.md
@@ -4,6 +4,8 @@ title: Build and deploy on local
functional_areas:
- Cloud
- Testing
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/deploy/staging-production.html
+status: migrated
---
Before pushing your code to your [Starter]({{ site.baseurl }}/cloud/architecture/starter-architecture.html) or [Pro]({{ site.baseurl }}/cloud/architecture/pro-architecture.html) Staging and Production environments, you should fully build on your local. Fully testing builds and deploys along with full site testing can reduce the risk of issues or delays for your final site deployment, and expose any issues early for debugging.
diff --git a/src/cloud/live/live.md b/src/cloud/live/live.md
index af3b850e2f3..8ff628ceb93 100644
--- a/src/cloud/live/live.md
+++ b/src/cloud/live/live.md
@@ -3,6 +3,8 @@ group: cloud-guide
title: Site launch
functional_areas:
- Cloud
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/launch/overview.html
+status: migrated
---
When you have completed deployment and testing in Integration and Staging environments, you can begin site launch preparation. First, you should complete all development and testing before working in the Production environment. Feel ready to launch? Review our checklists, best practices, and final steps to launch your site.
diff --git a/src/cloud/live/paypal-onboarding.md b/src/cloud/live/paypal-onboarding.md
index 78b5341af5a..b2ffd3f9a9e 100644
--- a/src/cloud/live/paypal-onboarding.md
+++ b/src/cloud/live/paypal-onboarding.md
@@ -9,6 +9,8 @@ functional_areas:
- Cloud
- Setup
- Services
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure-store/paypal.html
+status: migrated
---
{{site.data.var.ece}} provides an on-boarding tool to configure PayPal Express Checkout accounts directly through the Admin panel. This tool is available for ECE 2.1.8 and later. To better support going live and testing PayPal payment methods, you can enable and configure your PayPal Express Checkout account for sandbox or production accounts.
diff --git a/src/cloud/live/sens-data-initial.md b/src/cloud/live/sens-data-initial.md
index 8e6f941383f..447b05441e8 100644
--- a/src/cloud/live/sens-data-initial.md
+++ b/src/cloud/live/sens-data-initial.md
@@ -4,6 +4,8 @@ title: Example of managing system-specific settings
functional_areas:
- Cloud
- Deploy
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure-store/store-settings.html
+status: migrated
---
Configuration management exports your configurations to a file for pushing across your environments. This file, `config.php`, keeps your configurations consistent across all environments, decreases downtime by moving static deploy to build, and much more. This information details an example for configuring your settings, exporting the file, and deploying it.
diff --git a/src/cloud/live/sens-data-over.md b/src/cloud/live/sens-data-over.md
index 91f9e8ad0ad..1aa2f4b2f20 100644
--- a/src/cloud/live/sens-data-over.md
+++ b/src/cloud/live/sens-data-over.md
@@ -4,6 +4,8 @@ title: Configuration management for store settings
functional_areas:
- Cloud
- Deploy
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure-store/store-settings.html
+status: migrated
---
Configuration management provides a way to deploy across your environments with minimal downtime using [Pipeline deployment][]. {{site.data.var.ece}} provides the build server, build and deploy scripts, and deployment environments.
diff --git a/src/cloud/live/site-launch-checklist.md b/src/cloud/live/site-launch-checklist.md
index ab646e38773..a896100763e 100644
--- a/src/cloud/live/site-launch-checklist.md
+++ b/src/cloud/live/site-launch-checklist.md
@@ -4,10 +4,11 @@ title: Launch checklist
functional_areas:
- Cloud
- Testing
-
redirect_from:
- /common/pdf/magento-commerce-cloud-prelaunch-checklist.pdf
- /cloud/live/go-live-checklist.html
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/launch/checklist.html
+status: migrated
---
Before you deploy to the Production environment, download the [Launch checklist]({{ site.downloads }}/magento-commerce-cloud-prelaunch-checklist.pdf), and use it with these instructions to confirm that you have completed all required configuration and testing. See an overview of the complete deployment process for Starter and Pro at [Deploy your store]({{ site.baseurl }}/cloud/live/stage-prod-live.html).
@@ -46,7 +47,7 @@ To update DNS configuration for site launch:
1. Update the following DNS configuration for your Production site:
- Set all necessary redirects, especially if you are migrating from an existing site
- - Set the zone’s root resource record to address the hostname
+ - Set the zone's root resource record to address the hostname
- Lower the value for the Time-to-Live (TTL) to refresh DNS information to point customers to the correct Production store
We recommend a significantly lower TTL value when switching the DNS record. This value tells the DNS how long to cache the DNS record. When shortened, it refreshes the DNS faster. For example, you can change the TTL value from 3 days to 10 minutes when you are updating your site. Be advised that shortening the TTL value adds load to the DNS infrastructure. You should restore the previous higher value after site launch.
diff --git a/src/cloud/live/stage-prod-live.md b/src/cloud/live/stage-prod-live.md
index be0c83078e2..1afa582275a 100644
--- a/src/cloud/live/stage-prod-live.md
+++ b/src/cloud/live/stage-prod-live.md
@@ -6,6 +6,8 @@ redirect_from:
functional_areas:
- Cloud
- Deploy
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/deploy/staging-production.html
+status: migrated
---
The process for deploying and going live begins with development, continues to Staging, and ends with going live in Production. To provide the best experience for developing, testing, and deploying your store with consistent configurations we provide an end-to-end environment solution. Every environment supports direct URL access to the store and Admin console and SSH access for CLI commands.
diff --git a/src/cloud/live/stage-prod-migrate-prereq.md b/src/cloud/live/stage-prod-migrate-prereq.md
index 0f5247d0ea9..15736850a63 100644
--- a/src/cloud/live/stage-prod-migrate-prereq.md
+++ b/src/cloud/live/stage-prod-migrate-prereq.md
@@ -9,6 +9,8 @@ functional_areas:
- Cloud
- Configuration
- Deploy
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/deploy/staging-production.html
+status: migrated
---
{:.ref-header}
diff --git a/src/cloud/live/stage-prod-migrate.md b/src/cloud/live/stage-prod-migrate.md
index d3fedb181e3..d28c6c9e248 100644
--- a/src/cloud/live/stage-prod-migrate.md
+++ b/src/cloud/live/stage-prod-migrate.md
@@ -4,6 +4,8 @@ title: Deploy code and migrate static files and data
functional_areas:
- Cloud
- Deploy
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/deploy/staging-production.html
+status: migrated
---
{:.ref-header}
diff --git a/src/cloud/live/stage-prod-test.md b/src/cloud/live/stage-prod-test.md
index 30f2df3eb5a..8934a7744fb 100644
--- a/src/cloud/live/stage-prod-test.md
+++ b/src/cloud/live/stage-prod-test.md
@@ -9,6 +9,8 @@ functional_areas:
- Cloud
- Testing
- Deploy
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/test/staging-and-production.html
+status: migrated
---
{:.ref-header}
diff --git a/src/cloud/onboarding/onboarding-tasks.md b/src/cloud/onboarding/onboarding-tasks.md
index 7fc405fda92..36c64d185ca 100644
--- a/src/cloud/onboarding/onboarding-tasks.md
+++ b/src/cloud/onboarding/onboarding-tasks.md
@@ -8,6 +8,8 @@ functional_areas:
redirect_from:
- /cloud/before/before-project-owner.html
- /cloud/onboarding/onboarding-portal.html
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/start/onboarding.html
+status: migrated
---
After your company purchases a {{site.data.var.ece}} subscription, initial project and code access is available only to the person designated as the License Owner (Account Owner).
diff --git a/src/cloud/project/ece-tools-update.md b/src/cloud/project/ece-tools-update.md
index b379495ca68..9f5f5a26ead 100644
--- a/src/cloud/project/ece-tools-update.md
+++ b/src/cloud/project/ece-tools-update.md
@@ -7,12 +7,14 @@ redirect_from:
functional_areas:
- Cloud
- Upgrade
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/dev-tools/ece-tools/update-package.html
+status: migrated
---
An update to the `{{site.data.var.ct}}` package also updates the other [{{site.data.var.csuite}} packages][], which are dependencies for `{{site.data.var.ct}}`. Therefore, you must use a version of {{site.data.var.ece}} that supports the `{{site.data.var.ct}}` package.
{:.bs-callout-warning}
-If you use a version of {{site.data.var.ece}} that does not contain the {{site.data.var.ct}} package, then you must perform a one-time [upgrade][upgrade-project] to your cloud project to remove deprecated packages. To verify the {{site.data.var.ct}} package is installed, retrieve the Commerce version using the `php vendor/bin/ece-tools -V` command at your local project root directory.
+If you use a version of {{site.data.var.ece}} that does not contain the {{site.data.var.ct}} package, then you must perform a one-time [upgrade]({{site.baseurl}}/cloud/project/ece-tools-upgrade-project.html) to your cloud project to remove deprecated packages. To verify the {{site.data.var.ct}} package is installed, retrieve the Commerce template version using the `php vendor/bin/ece-tools -V` command at your local project root directory.
**Prerequisites**:
@@ -32,7 +34,7 @@ To update the `{{site.data.var.ct}}` package:
```
{:.bs-callout-info}
- If you cannot update beyond `{{site.data.var.ct}}` version 2002.0.8, see [Upgrade project][].
+ If you cannot update beyond `{{site.data.var.ct}}` version 2002.0.8, see [Upgrade project]({{site.baseurl}}/cloud/project/ece-tools-upgrade-project.html).
1. Add, commit, and push code changes.
@@ -55,7 +57,6 @@ To update the `{{site.data.var.ct}}` package:
[latest `{{site.data.var.ct}}` release]: {{site.baseurl}}/cloud/release-notes/ece-release-notes.html
[backward incompatible changes]: {{site.baseurl}}/cloud/release-notes/backward-incompatible-changes.html
[Upgrade to use ece-tools]: {{site.baseurl}}/cloud/project/ece-tools-upgrade-project.html
-[upgrade project]: {{site.baseurl}}/cloud/project/ece-tools-upgrade-project.html
[upgrade {{site.data.var.ee}} version]: {{site.baseurl}}/cloud/project/project-upgrade.html
[Upgrades and Patches]: {{site.baseurl}}/cloud/project/project-upgrade-parent.html
[{{site.data.var.csuite}} packages]: {{site.baseurl}}/cloud/release-notes/cloud-tools.html
diff --git a/src/cloud/project/ece-tools-upgrade-project.md b/src/cloud/project/ece-tools-upgrade-project.md
index 0cf39666cd3..5e0e381bb1b 100644
--- a/src/cloud/project/ece-tools-upgrade-project.md
+++ b/src/cloud/project/ece-tools-upgrade-project.md
@@ -4,6 +4,8 @@ title: Upgrade project to use ece-tools
functional_areas:
- Cloud
- Upgrade
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/dev-tools/ece-tools/install-package.html
+status: migrated
---
Adobe deprecated the `magento/magento-cloud-configuration` and `magento/ece-patches` packages in favor of the `{{site.data.var.ct}}` package, which simplifies many cloud processes. If you use an older {{site.data.var.ece}} project that does _not_ contain the `{{site.data.var.ct}}` package, then you must perform a one-time, manual _upgrade_ process to your project.
diff --git a/src/cloud/project/log-locations.md b/src/cloud/project/log-locations.md
index 6fc891c8e9a..efabcc32346 100644
--- a/src/cloud/project/log-locations.md
+++ b/src/cloud/project/log-locations.md
@@ -6,6 +6,8 @@ functional_areas:
- Configuration
redirect_from:
- /cloud/trouble/environments-logs.html
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/test/log-locations.html
+status: migrated
---
Logs for {{site.data.var.ece}} projects are useful for troubleshooting problems related to {{site.data.var.ece}} [build and deploy hooks][hook], cloud services, and the {{site.data.var.ee}} application.
diff --git a/src/cloud/project/magento-app-php-application.md b/src/cloud/project/magento-app-php-application.md
index ddccd6aa298..e9da609abf0 100644
--- a/src/cloud/project/magento-app-php-application.md
+++ b/src/cloud/project/magento-app-php-application.md
@@ -4,7 +4,9 @@ title: PHP application
functional_areas:
- Cloud
- Setup
- - Application
+ - Application
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure/app/php-settings.html
+status: migrated
---
You can choose which [version of PHP]({{ site.baseurl}}/guides/v2.4/install-gde/system-requirements.html) to run in your `.magento.app.yaml` file:
diff --git a/src/cloud/project/magento-app-php-ini.md b/src/cloud/project/magento-app-php-ini.md
index bd19fdc5551..305d1b9e492 100644
--- a/src/cloud/project/magento-app-php-ini.md
+++ b/src/cloud/project/magento-app-php-ini.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Setup
- Application
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure/app/php-settings.html
+status: migrated
---
You can customize the PHP settings for your environment using a `php.ini` file that is appended to the configuration maintained by {{site.data.var.ee}}.
diff --git a/src/cloud/project/magento-app-properties.md b/src/cloud/project/magento-app-properties.md
index fa9c2d17896..766da3c821f 100644
--- a/src/cloud/project/magento-app-properties.md
+++ b/src/cloud/project/magento-app-properties.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Setup
- Application
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure/app/properties/properties.html
+status: migrated
---
Use the following properties to build your application configuration file. The `name`, `type`, `disk`, and one `web` or `worker` block is required.
diff --git a/src/cloud/project/magento-app-variables.md b/src/cloud/project/magento-app-variables.md
index 8cbb62cbefa..12ed81cb875 100644
--- a/src/cloud/project/magento-app-variables.md
+++ b/src/cloud/project/magento-app-variables.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Setup
- Application
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure/app/properties/variables-property.html
+status: migrated
---
The following environment variables are included in the `.magento.app.yaml` file.
diff --git a/src/cloud/project/magento-app-workers.md b/src/cloud/project/magento-app-workers.md
index 53098c92c42..0194175fbee 100644
--- a/src/cloud/project/magento-app-workers.md
+++ b/src/cloud/project/magento-app-workers.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Setup
- Application
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure/app/properties/workers-property.html
+status: migrated
---
You can define zero or multiple work instances for each application. A worker
instance runs as a container, independent from the web instance and without
diff --git a/src/cloud/project/magento-app.md b/src/cloud/project/magento-app.md
index 4441795b534..2cdab8c0e3b 100644
--- a/src/cloud/project/magento-app.md
+++ b/src/cloud/project/magento-app.md
@@ -6,6 +6,8 @@ functional_areas:
- Setup
redirect_from:
- /cloud/project/project-conf-files_magento-app.html
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure/app/configure-app-yaml.html
+status: migrated
---
The `.magento.app.yaml` file controls the way your application builds and deploys. Although {{site.data.var.ece}} supports multiple applications per project, typically, a project has a single application with the `.magento.app.yaml` file at the root of the repository.
diff --git a/src/cloud/project/magento-env-yaml.md b/src/cloud/project/magento-env-yaml.md
index 098754e4c88..ff1bf53bd9d 100644
--- a/src/cloud/project/magento-env-yaml.md
+++ b/src/cloud/project/magento-env-yaml.md
@@ -4,6 +4,8 @@ title: Deployment configuration
functional_areas:
- Cloud
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure/env/configure-env-yaml.html
+status: migrated
---
The `.magento.env.yaml` file uses environment variables to centralize the management of build and deploy actions across all of your environments, including Pro Staging and Production. To configure unique actions in each environment, you must modify this file in each environment.
diff --git a/src/cloud/project/manage-disk-space.md b/src/cloud/project/manage-disk-space.md
index 091b68b3abc..3ab28c0c90e 100644
--- a/src/cloud/project/manage-disk-space.md
+++ b/src/cloud/project/manage-disk-space.md
@@ -4,6 +4,8 @@ title: Manage disk space
functional_areas:
- Cloud
- Storage
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/storage/manage-disk-space.html
+status: migrated
---
You can find the total storage capacity for your Cloud project in your {{site.data.var.ece}} contract and on your [account page](https://accounts.magento.cloud/user). Each project card in your account shows the number of _environments_, the _storage_ capacity in GB, and the number of _users_.
diff --git a/src/cloud/project/monitor-performance.md b/src/cloud/project/monitor-performance.md
index 42fe896ab77..2a456d8f36a 100644
--- a/src/cloud/project/monitor-performance.md
+++ b/src/cloud/project/monitor-performance.md
@@ -4,6 +4,8 @@ title: Monitor performance
functional_areas:
- Cloud
- Storage
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/monitor/performance.html
+status: migrated
---
You can use the following services to monitor performance of your Cloud environments:
diff --git a/src/cloud/project/new-relic.md b/src/cloud/project/new-relic.md
index 36cc642f347..060beb96d27 100644
--- a/src/cloud/project/new-relic.md
+++ b/src/cloud/project/new-relic.md
@@ -6,6 +6,8 @@ functional_areas:
- Integration
- Setup
- Services
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/monitor/new-relic.html
+status: migrated
---
{{ site.data.var.ece }} projects include access to the following New Relic services to help manage, monitor, and troubleshoot your applications and infrastructure by collecting, viewing, and analyzing data from your {{ site.data.var.ece }} project.
diff --git a/src/cloud/project/privatelink-service.md b/src/cloud/project/privatelink-service.md
index 6fe09a09d60..b96b870f2cc 100644
--- a/src/cloud/project/privatelink-service.md
+++ b/src/cloud/project/privatelink-service.md
@@ -4,6 +4,8 @@ title: PrivateLink service
functional_areas:
- Cloud
- Setup
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/privatelink-service.html
+status: migrated
---
{{site.data.var.ece}} supports integration with the [AWS PrivateLink][] or [Azure Private Link][] service to allow Cloud customers to establish secure, private communication between {{site.data.var.ece}} environments and services and applications hosted on external systems. Both the {{site.data.var.ee}} application and external systems must be accessible through private VPC endpoints configured within the same Cloud region (AWS or Azure).
diff --git a/src/cloud/project/profile-database-queries.md b/src/cloud/project/profile-database-queries.md
index 30c4e9c5607..9a6e292e60e 100644
--- a/src/cloud/project/profile-database-queries.md
+++ b/src/cloud/project/profile-database-queries.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Setup
- Services
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/storage/profile-database-queries.html
+status: migrated
---
When making changes to a database, you may find it helpful to run profiling to identify the impact of those changes. Profiling maintains a log of database queries and increases run-time precision.
diff --git a/src/cloud/project/project-enable-mfa-enforcement.md b/src/cloud/project/project-enable-mfa-enforcement.md
index e9cd0c522b1..87ee741a2a7 100644
--- a/src/cloud/project/project-enable-mfa-enforcement.md
+++ b/src/cloud/project/project-enable-mfa-enforcement.md
@@ -6,9 +6,10 @@ functional_areas:
- Configuration
- Security
- Compliance
-
redirect_from:
- /cloud/project/project-enable-mfa-project.html
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/project/multi-factor-authentication.html
+status: migrated
---
For added security, {{site.data.var.ece}} provides multi-factor authentication (MFA) enforcement to manage authentication requirements for SSH access to Cloud environments.
diff --git a/src/cloud/project/project-multi-sites.md b/src/cloud/project/project-multi-sites.md
index 09c8269a408..ca647704fbe 100644
--- a/src/cloud/project/project-multi-sites.md
+++ b/src/cloud/project/project-multi-sites.md
@@ -6,6 +6,8 @@ functional_areas:
- Configuration
- Setup
- Stores
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure-store/multiple-sites.html
+status: migrated
---
You can configure {{site.data.var.ee}} to have multiple websites or stores, such as an English store, a French store, and a German store. See [Understanding websites, stores, and store views]({{ site.baseurl }}/cloud/configure/configure-best-practices.html#sites).
diff --git a/src/cloud/project/project-patch.md b/src/cloud/project/project-patch.md
index 883bfe4cf67..412b36a8631 100644
--- a/src/cloud/project/project-patch.md
+++ b/src/cloud/project/project-patch.md
@@ -4,6 +4,8 @@ title: Apply patches
functional_areas:
- Cloud
- Upgrade
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/upgrade/apply-patches.html
+status: migrated
---
[{{ site.data.var.mcp-prod }}](https://github.com/magento/magento-cloud-patches) and the [Quality Patches Tool](https://github.com/magento/quality-patches) deliver patches to your installed {{site.data.var.ee}} application.
diff --git a/src/cloud/project/project-routes-more-cache.md b/src/cloud/project/project-routes-more-cache.md
index 561979fed61..da84f979ec8 100644
--- a/src/cloud/project/project-routes-more-cache.md
+++ b/src/cloud/project/project-routes-more-cache.md
@@ -4,6 +4,8 @@ title: Caching
functional_areas:
- Cloud
- Setup
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure/routes/caching.html
+status: migrated
---
{{site.data.var.ee}} enables you to use caching in your environment. If you disable caching, {{site.data.var.ee}} directly serves the files.
diff --git a/src/cloud/project/project-routes-more-redir.md b/src/cloud/project/project-routes-more-redir.md
index aaf6530cec3..84bb98abe46 100644
--- a/src/cloud/project/project-routes-more-redir.md
+++ b/src/cloud/project/project-routes-more-redir.md
@@ -4,6 +4,8 @@ title: Redirects
functional_areas:
- Cloud
- Setup
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure/routes/redirects.html
+status: migrated
---
Managing redirection rules is a common requirement for web applications, especially in cases where you do not want to lose incoming links that have changed or been removed over time.
diff --git a/src/cloud/project/project-routes-more-ssi.md b/src/cloud/project/project-routes-more-ssi.md
index 29211c77ffa..26d849afcb4 100644
--- a/src/cloud/project/project-routes-more-ssi.md
+++ b/src/cloud/project/project-routes-more-ssi.md
@@ -4,6 +4,8 @@ title: Server side includes
functional_areas:
- Cloud
- Setup
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure/routes/server-side-includes.html
+status: migrated
---
[Server side includes](https://nginx.org/en/docs/http/ngx_http_ssi_module.html) (SSI) are directives in [HTML](https://glossary.magento.com/html) pages that get evaluated on the server while the pages are being rendered. Use of [server side](https://glossary.magento.com/server-side) includes enables you to add dynamically generated content to an existing HTML page without having to serve the entire page.
diff --git a/src/cloud/project/project-start.md b/src/cloud/project/project-start.md
index 62a3ef1e581..00fe06d4e18 100644
--- a/src/cloud/project/project-start.md
+++ b/src/cloud/project/project-start.md
@@ -4,6 +4,8 @@ title: Project structure
functional_areas:
- Cloud
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/project/file-structure.html
+status: migrated
---
All {{site.data.var.ece}} projects include essential files for credentials and application configuration:
diff --git a/src/cloud/project/project-upgrade-parent.md b/src/cloud/project/project-upgrade-parent.md
index 5d526e711be..db588dbfc10 100644
--- a/src/cloud/project/project-upgrade-parent.md
+++ b/src/cloud/project/project-upgrade-parent.md
@@ -4,6 +4,8 @@ title: Upgrades and patches
functional_areas:
- Cloud
- Upgrade
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/upgrade/best-practices.html
+status: migrated
---
The Upgrades and patches section contains detailed release notes for the `{{site.data.var.ct}}` package, and information on how to upgrade the `{{site.data.var.ct}}` package, upgrade {{site.data.var.ece}}, and apply custom patches and hotfixes.
diff --git a/src/cloud/project/project-upgrade.md b/src/cloud/project/project-upgrade.md
index 77d70cf7dca..cd033e33684 100644
--- a/src/cloud/project/project-upgrade.md
+++ b/src/cloud/project/project-upgrade.md
@@ -4,6 +4,8 @@ title: Upgrade version
functional_areas:
- Cloud
- Upgrade
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/upgrade/commerce-version.html
+status: migrated
---
You can upgrade the core {{site.data.var.ee}} code base to a newer version. Before upgrading your project, review the [service versions][System requirements] information for the latest software version requirements. If you must upgrade from a version older than 2.1, you must upgrade to a supported version first. See [Upgrades and patches] for upgrade path details.
diff --git a/src/cloud/project/project-webint-basic.md b/src/cloud/project/project-webint-basic.md
index 3688f805537..78ab1cf3f60 100644
--- a/src/cloud/project/project-webint-basic.md
+++ b/src/cloud/project/project-webint-basic.md
@@ -4,6 +4,8 @@ title: Configure your project
functional_areas:
- Cloud
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/project/overview.html
+status: migrated
---
For all {{site.data.var.ece}} projects, you can use the [Project Web Interface](https://account.magento.com/customer/account/login/) to perform the following tasks:
diff --git a/src/cloud/project/project-webint-branch.md b/src/cloud/project/project-webint-branch.md
index 41b6b866759..721408ea2fe 100644
--- a/src/cloud/project/project-webint-branch.md
+++ b/src/cloud/project/project-webint-branch.md
@@ -6,6 +6,8 @@ redirect_from:
functional_areas:
- Cloud
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/cli-branches.html
+status: migrated
---
Every {{site.data.var.ece}} *environment* has an associated active Git *branch*. You can manage your environments using either the Project Web Interface, the `magento-cloud` CLI, or Git commands. For more information on Git branches, see [Git documentation](https://git-scm.com/doc).
diff --git a/src/cloud/project/project-webint-snap.md b/src/cloud/project/project-webint-snap.md
index d6ce411876d..c6972425518 100644
--- a/src/cloud/project/project-webint-snap.md
+++ b/src/cloud/project/project-webint-snap.md
@@ -3,6 +3,8 @@ group: cloud-guide
title: Snapshots and backup management
functional_areas:
- Cloud
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/storage/snapshots.html
+status: migrated
---
You can back up and restore specific environments at any time using a snapshot. Snapshot options are available for all Starter environments and Pro Integration environments. The snapshot feature does not apply to the Pro Staging and Production environments.
diff --git a/src/cloud/project/projects.md b/src/cloud/project/projects.md
index b1853f3693c..8a148545fbb 100644
--- a/src/cloud/project/projects.md
+++ b/src/cloud/project/projects.md
@@ -3,6 +3,8 @@ group: cloud-guide
title: Manage your project
functional_areas:
- Cloud
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/project/overview.html
+status: migrated
---
The {{site.data.var.ece}} *project* includes all code in Git branches, associated environments, and *applications*. Applications have *environments* and *services* that run on them including a database, web server, and caching server.
diff --git a/src/cloud/project/routes.md b/src/cloud/project/routes.md
index 733b837ad5e..e9235a95bd8 100644
--- a/src/cloud/project/routes.md
+++ b/src/cloud/project/routes.md
@@ -5,7 +5,9 @@ functional_areas:
- Cloud
- Setup
redirect_from:
- - /cloud/project/project-conf-files_routes.html
+ - /cloud/project/project-conf-files_routes.html
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure/routes/routes-yaml.html
+status: migrated
---
The `routes.yaml` file in the `.magento/routes.yaml` directory defines routes for your {{ site.data.var.ece }} Integration, Staging, and Production environments. Routes determine how the application processes incoming HTTP and HTTPS requests.
diff --git a/src/cloud/project/sendgrid.md b/src/cloud/project/sendgrid.md
index 94fe8be9fbe..cf9b75387ac 100644
--- a/src/cloud/project/sendgrid.md
+++ b/src/cloud/project/sendgrid.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Setup
- Services
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/project/sendgrid.html
+status: migrated
---
The SendGrid Simple Mail Transfer Protocol (SMTP) proxy service provides outbound email authentication and reputation monitoring services, including support for:
diff --git a/src/cloud/project/services-elastic.md b/src/cloud/project/services-elastic.md
index 0dc9d5e7595..ec26542c7e1 100644
--- a/src/cloud/project/services-elastic.md
+++ b/src/cloud/project/services-elastic.md
@@ -7,6 +7,8 @@ functional_areas:
- Search
redirect_from:
- /cloud/project/project-conf-files_services-elastic.html
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure/service/elasticsearch.html
+status: migrated
---
[Elasticsearch](https://www.elastic.co) is an open-source product that enables you to take data from any source, any format, and search and visualize it in real time.
diff --git a/src/cloud/project/services-mysql.md b/src/cloud/project/services-mysql.md
index d1afe35c9f4..b1d11183910 100644
--- a/src/cloud/project/services-mysql.md
+++ b/src/cloud/project/services-mysql.md
@@ -5,7 +5,9 @@ functional_areas:
- Cloud
- Setup
redirect_from:
- - /cloud/project/project-conf-files_services-mysql.html
+ - /cloud/project/project-conf-files_services-mysql.html
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure/service/mysql.html
+status: migrated
---
The `mysql` service provides persistent data storage based on [MariaDB](https://mariadb.com/) versions 10.2 to 10.4, supporting the [XtraDB](https://www.percona.com/software/mysql-database/percona-server/xtradb) storage engine and reimplemented features from MySQL 5.6 and 5.7.
diff --git a/src/cloud/project/services-opensearch.md b/src/cloud/project/services-opensearch.md
index 88075821496..0174007cf72 100644
--- a/src/cloud/project/services-opensearch.md
+++ b/src/cloud/project/services-opensearch.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Setup
- Search
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure/service/opensearch.html
+status: migrated
---
The [OpenSearch](https://www.opensearch.org) service is an open-source fork of Elasticsearch 7.10.2, following the licensing changes for Elasticsearch. See [System requirements]({{ site.baseurl }}/guides/v2.4/install-gde/system-requirements.html) for a list of supported versions.
@@ -80,4 +82,5 @@ opensearch:
configuration:
plugins:
- analysis-icu
- - analysis-phonetic
\ No newline at end of file
+ - analysis-phonetic
+```
diff --git a/src/cloud/project/services-rabbit.md b/src/cloud/project/services-rabbit.md
index d46d814e652..806140bf055 100644
--- a/src/cloud/project/services-rabbit.md
+++ b/src/cloud/project/services-rabbit.md
@@ -5,7 +5,9 @@ functional_areas:
- Cloud
- Setup
redirect_from:
- - /cloud/project/project-conf-files_services-rabbit.html
+ - /cloud/project/project-conf-files_services-rabbit.html
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure/service/rabbitmq.html
+status: migrated
---
The [Message Queue Framework (MQF)]({{ site.baseurl }}/guides/v2.3/config-guide/mq/rabbitmq-overview.html) is a system within {{site.data.var.ee}} that allows a [module](https://glossary.magento.com/module) to publish messages to queues. It also defines the consumers that will receive the messages asynchronously.
diff --git a/src/cloud/project/services-redis.md b/src/cloud/project/services-redis.md
index a7e3164f3cc..a653ab58509 100644
--- a/src/cloud/project/services-redis.md
+++ b/src/cloud/project/services-redis.md
@@ -6,6 +6,8 @@ functional_areas:
- Setup
redirect_from:
- /cloud/project/project-conf-files_services-redis.html
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure/service/redis.html
+status: migrated
---
[Redis](https://redis.io) is an optional, backend cache solution that replaces the Zend Framework [Zend_Cache_Backend_File](https://framework.zend.com/apidoc/1.0/Zend_Cache/Backend/Zend_Cache_Backend_File.html), which {{site.data.var.ee}} uses by default.
diff --git a/src/cloud/project/services.md b/src/cloud/project/services.md
index 80f04d83a9a..49a0bb37e80 100644
--- a/src/cloud/project/services.md
+++ b/src/cloud/project/services.md
@@ -6,6 +6,8 @@ functional_areas:
- Setup
redirect_from:
- /cloud/project/project-conf-files_services.html
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure/service/services-yaml.html
+status: migrated
---
The `services.yaml` file defines the services supported and used by {{site.data.var.ece}}, such as MySQL, Redis, and Elasticsearch or OpenSearch. You do not need to subscribe to external service providers. This file is in the `.magento` directory of your project.
@@ -216,7 +218,7 @@ You can upgrade the installed service version by updating the service configurat
1. Add, commit, and push your code changes.
```bash
- git add -A
+ git add .magento/services.yaml
```
```bash
diff --git a/src/cloud/project/set-cache.md b/src/cloud/project/set-cache.md
index effb8d37aad..370efa81733 100644
--- a/src/cloud/project/set-cache.md
+++ b/src/cloud/project/set-cache.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Setup
- Services
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure/app/set-cache.html
+status: migrated
---
The cache time-to-live (TTL) for your media and static files is set in the `.magento.app.yaml` configuration file using the `expires` key.
diff --git a/src/cloud/project/user-admin.md b/src/cloud/project/user-admin.md
index f91626cf202..8ab90b617c6 100644
--- a/src/cloud/project/user-admin.md
+++ b/src/cloud/project/user-admin.md
@@ -6,12 +6,13 @@ functional_areas:
- Configuration
- Account
- Security
-
redirect_from:
- /cloud/admin/admin-user-admin.html
- /cloud/project/user-admin.html#cloud-role-acct-owner
- /cloud/project/user-admin.html#cloud-role-env
- /cloud/project/user-admin.html#cloud-role-project
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/project/user-access.html
+status: migrated
---
You manage access to {{site.data.var.ece}} projects and certain environment types by adding users and assigning roles. Project level roles provide access to the entire project.
diff --git a/src/cloud/reference/cli-ref-topic.md b/src/cloud/reference/cli-ref-topic.md
index e6448090840..18a530419ab 100644
--- a/src/cloud/reference/cli-ref-topic.md
+++ b/src/cloud/reference/cli-ref-topic.md
@@ -3,6 +3,8 @@ group: cloud-guide
title: Magento Cloud CLI
functional_areas:
- Cloud
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/dev-tools/cloud-cli.html
+status: migrated
---
The `magento-cloud` CLI tool enables developers and system administrators the ability to manage Cloud projects and environments, perform routines and run automation tasks. The `magento-cloud` CLI extends the features and functionality of the Project Web Interface. After you install the `magento-cloud` CLI on your local workstation, you can use it to manage your {{site.data.var.ece}} Starter and Pro Integration environments.
diff --git a/src/cloud/reference/cloud-composer.md b/src/cloud/reference/cloud-composer.md
index 5e150c903c2..34093d4fb2d 100644
--- a/src/cloud/reference/cloud-composer.md
+++ b/src/cloud/reference/cloud-composer.md
@@ -6,6 +6,8 @@ redirect_from:
functional_areas:
- Cloud
- Upgrade
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/overview.html
+status: migrated
---
We use [Composer](https://getcomposer.org/doc) to manage {{site.data.var.ece}} dependencies and upgrades and provide context about the included packages, what the packages do, and how they fit together. We highly recommend experience with Composer.
diff --git a/src/cloud/reference/discover-deploy.md b/src/cloud/reference/discover-deploy.md
index 3744a86250d..3c5de7e5000 100644
--- a/src/cloud/reference/discover-deploy.md
+++ b/src/cloud/reference/discover-deploy.md
@@ -6,6 +6,8 @@ redirect_from:
functional_areas:
- Cloud
- Deploy
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/deploy/best-practices.html
+status: migrated
---
Build and deploy scripts activate when you merge code to a remote environment. These scripts use the environment configuration files and application code to prepare data and configurations to provision Cloud infrastructure and services, and to install or update the {{ site.var.data.ee }} application and third-party and custom extensions in the Cloud environment.
diff --git a/src/cloud/reference/ece-tools-error-reference.md b/src/cloud/reference/ece-tools-error-reference.md
index 739ac89f302..7d1d8900f73 100644
--- a/src/cloud/reference/ece-tools-error-reference.md
+++ b/src/cloud/reference/ece-tools-error-reference.md
@@ -7,6 +7,8 @@ functional_areas:
- Configuration
redirect_from:
- /cloud/reference/error-codes.html
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/dev-tools/ece-tools/error-reference.html
+status: migrated
---
This error message reference provides information to troubleshoot errors that can occur during the {{site.data.var.ece }} build, deploy, and post-deploy processes.
diff --git a/src/cloud/reference/ece-tools-reference.md b/src/cloud/reference/ece-tools-reference.md
index 00ac8e6bc8d..aa306556da0 100644
--- a/src/cloud/reference/ece-tools-reference.md
+++ b/src/cloud/reference/ece-tools-reference.md
@@ -3,6 +3,8 @@ group: cloud-guide
title: ece-tools package
functional_areas:
- Cloud
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/dev-tools/ece-tools/package-overview.html
+status: migrated
---
The `{{site.data.var.ct}}` package is a set of scripts and tools designed to manage and deploy {{site.data.var.ece}} projects. The `{{site.data.var.ct}}` package simplifies many {{site.data.var.ece}} processes, such as deploying to a Docker environment, managing crons, verifying project configuration, and applying Adobe patches and hot fixes. You can view and contribute to the open-source [ece-tools repository on Github](https://github.com/magento/ece-tools).
diff --git a/src/cloud/reference/git-integration.md b/src/cloud/reference/git-integration.md
index 6dde047f137..716e3be023b 100644
--- a/src/cloud/reference/git-integration.md
+++ b/src/cloud/reference/git-integration.md
@@ -3,6 +3,8 @@ group: cloud-guide
title: Git
redirect_from:
- /cloud/project/admin-git-push.html
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/dev-tools/integrations/overview.html
+status: migrated
---
Git is the center of all code management, build, and deployment for your {{site.data.var.ece}} stores and sites. We use Git to provide source control for your code:
diff --git a/src/cloud/release-notes/backward-incompatible-changes.md b/src/cloud/release-notes/backward-incompatible-changes.md
index 6a026427ef2..38eab160421 100644
--- a/src/cloud/release-notes/backward-incompatible-changes.md
+++ b/src/cloud/release-notes/backward-incompatible-changes.md
@@ -1,6 +1,8 @@
---
group: cloud-guide
title: Backward incompatible changes
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/release-notes/backward-incompatible-changes.html
+status: migrated
---
Use the following information to learn about backward incompatible changes that might require you to adjust Cloud configuration and processes for existing Cloud projects when you upgrade to the latest release of the `{{site.data.var.ct}}` package or other {{site.data.var.csuite}} packages.
diff --git a/src/cloud/release-notes/cloud-release-archive.md b/src/cloud/release-notes/cloud-release-archive.md
index 8ef057dece9..d0ea2656f70 100644
--- a/src/cloud/release-notes/cloud-release-archive.md
+++ b/src/cloud/release-notes/cloud-release-archive.md
@@ -3,6 +3,8 @@ group: cloud-guide
title: Release notes archive for ece-tools
functional_areas:
- Cloud
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/release-notes/cloud-release-archive.html
+status: migrated
---
{:.bs-callout-info}
@@ -394,7 +396,7 @@ The `{{site.data.var.ct}}` version 2002.0.17 includes an important security patc
- {:.new}**Docker Compose for Cloud**—Added a command—`docker:build`—to generate a [Docker Compose]({{ site.baseurl }}/cloud/docker/docker-config.html) configuration from the Cloud `{{site.data.var.ct}}` repository.
-- {:.new}**Change Locales**—Now you can [change store locale]({{ site.baseurl }}/cloud/live/sens-data-over.html#change-locales) without the exporting and importing configuration process. While the application is in Production and the SCD_ON_DEMAND is enabled, the store and admin locale options are available.
+- {:.new}**Change Locales**—Now you can [change store locale](https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure-store/store-settings.html#change-locales) without the exporting and importing configuration process. While the application is in Production and the SCD_ON_DEMAND is enabled, the store and admin locale options are available.
- {:.new}**Site map and Robots**—Created a [workflow]({{ site.baseurl }}/cloud/trouble/robots-sitemap.html) to add a `robots.txt` file and generate a `sitemap.xml` file for a single domain configuration without requiring a change to the infrastructure.
diff --git a/src/cloud/release-notes/cloud-tools.md b/src/cloud/release-notes/cloud-tools.md
index 69536362301..062889b3256 100644
--- a/src/cloud/release-notes/cloud-tools.md
+++ b/src/cloud/release-notes/cloud-tools.md
@@ -7,6 +7,8 @@ functional_areas:
- Configuration
redirect_from:
- /cloud/release-notes/CloudReleaseNotes.html
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/release-notes/cloud-tools-suite.html
+status: migrated
---
This release information details the latest improvements to the {{site.data.var.csuite}} packages which are designed to deploy and manage {{site.data.var.ee}} installations and upgrades on the Cloud platform.
diff --git a/src/cloud/release-notes/ece-release-notes.md b/src/cloud/release-notes/ece-release-notes.md
index 6a620b459cd..c1bca4c39b7 100644
--- a/src/cloud/release-notes/ece-release-notes.md
+++ b/src/cloud/release-notes/ece-release-notes.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Setup
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/release-notes/ece-tools-package.html
+status: migrated
---
The [{{site.data.var.ct}}](https://github.com/magento/ece-tools) package is a set of scripts and tools designed to manage and deploy Cloud projects. These release notes describe the latest improvements to this package, which is part of the [{{site.data.var.csuite}}]({{page.baseurl}}/cloud/release-notes/cloud-tools.html).
@@ -21,7 +23,15 @@ The release notes include:
-## v2002.1.12 {#latest}
+## v2002.1.13 {#latest}
+
+Release date: October 27, 2022
+
+- {:.new}**Added support for Adobe I/O Events for Adobe Commerce**. Extension developers can now use the [Adobe I/O Events](https://developer.adobe.com/events/docs/) framework to send Commerce event information from Cloud instances to their applications written for [Adobe App Builder](https://developer.adobe.com/app-builder/docs/overview/). Adobe I/O Events for Adobe Commerce is currently in Partner Preview.
+- {:.new}**Validator for OPcache configuration**—Added a validator to check the OPcache configuration for excluded paths.
+- {:.fix}**Fixed an issue with GraphQL cache configuration**—Now ECE-Tools keeps the GraphQL `id_salt` value in `cache` configuration in the `app/etc/env.php` file.
+
+## v2002.1.12
Release date: September 13, 2022
diff --git a/src/cloud/release-notes/mcc-release-notes.md b/src/cloud/release-notes/mcc-release-notes.md
index 2e7fa5d7d0d..61be5937e96 100644
--- a/src/cloud/release-notes/mcc-release-notes.md
+++ b/src/cloud/release-notes/mcc-release-notes.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Setup
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/release-notes/cloud-components.html
+status: migrated
---
The [Magento Cloud Components](https://github.com/magento/magento-cloud-components) package provides extended {{site.data.var.ee}} core functionality for sites deployed on Cloud infrastructure. This package is a dependency for the {{ site.data.var.ct }} package. These release notes describe the latest improvements to this package, which is a component of [{{ site.data.var.csuite }}]({{ page.baseurl }}/cloud/release-notes/cloud-tools.html).
diff --git a/src/cloud/release-notes/mcd-release-notes.md b/src/cloud/release-notes/mcd-release-notes.md
index 0bb79929759..ac1e187a0d3 100644
--- a/src/cloud/release-notes/mcd-release-notes.md
+++ b/src/cloud/release-notes/mcd-release-notes.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Setup
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/release-notes/cloud-docker.html
+status: migrated
---
The [`{{site.data.var.mcd-package}}`](https://github.com/magento/magento-cloud-docker) package provides functionality and Docker images to deploy {{ site.data.var.ee }} to a local Cloud environment. These release notes describe the latest improvements to this package, which is a component of [{{ site.data.var.csuite }}]({{ page.baseurl }}/cloud/release-notes/cloud-tools.html).
@@ -18,9 +20,15 @@ The release notes include:
-## v1.3.3 {#latest}
+## v1.3.4 {#latest}
-Release date: September, 2022
+Release date: October 27, 2022
+
+- {:.new}**Added new Varnish images**—Added Varnish images for next versions 6.5, 7.0, and 7.1.
+
+## v1.3.3
+
+Release date: September 13, 2022
- {:.new}**Apple M1 (ARM64) support**—Added changes to Docker images to enable support for Apple M1 (ARM64) architecture.
- {:.fix}**Mailhog**—Fixed an issue where the Mailhog service did not catch emails while in developer mode.
diff --git a/src/cloud/release-notes/mcp-release-notes.md b/src/cloud/release-notes/mcp-release-notes.md
index 2b00b45b880..ef0ef1d20cc 100644
--- a/src/cloud/release-notes/mcp-release-notes.md
+++ b/src/cloud/release-notes/mcp-release-notes.md
@@ -5,6 +5,8 @@ functional_areas:
- Cloud
- Setup
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/release-notes/cloud-patches.html
+status: migrated
---
The [Magento Cloud Patches](https://github.com/magento/magento-cloud-patches) package provides a set of required patches which improve the integration of all {{site.data.var.ee}} versions with Cloud environments and supports quick delivery of critical fixes.
@@ -20,7 +22,13 @@ See [Apply patches]({{site.baseurl}}/cloud/project/project-patch.html) for instr
The `{{site.data.var.mcp-package}}` package uses the following version sequence: `..`
-## v1.0.19 {#latest}
+## v1.0.20 {#latest}
+
+Release date: October 27, 2022
+
+- **Added L2 cache improvements patch**—This patch fixes an issue with flushing the local L2 cache for Commerce version 2.4.0 and 2.4.1.
+
+## v1.0.19
Release date: September 13, 2022
diff --git a/src/cloud/requirements/cloud-requirements.md b/src/cloud/requirements/cloud-requirements.md
index 780002e75ce..53d25de3ed6 100644
--- a/src/cloud/requirements/cloud-requirements.md
+++ b/src/cloud/requirements/cloud-requirements.md
@@ -4,6 +4,8 @@ title: Technologies and requirements
functional_areas:
- Cloud
- Install
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/overview.html
+status: migrated
---
This topic describes technologies, knowledge, accounts, and steps to complete when working with your {{site.data.var.ece}} code, environments, stores, and sites. If you are not experienced with a technology, links to information and resources are provided below to help get you started.
@@ -63,7 +65,7 @@ You cannot upgrade the software, but you can [configure the following services](
* [Redis]({{ site.baseurl }}/cloud/project/services-redis.html)
* [RabbitMQ]({{ site.baseurl }}/cloud/project/services-rabbit.html)
* [Elasticsearch]({{ site.baseurl }}/cloud/project/services-elastic.html). Elasticsearch 7.11 and later is not supported for {{site.data.var.ece}}.
-* [OpenSearch]({{ site.baseurl }}/cloud/project/services-opensearch.html). Adobe Commerce and Magento Open Source versions 2.4.4, 2.4.3-p2, and 2.3.7-p3 support the OpenSearch service.
+* [OpenSearch]({{ site.baseurl }}/cloud/project/services-opensearch.html). Adobe Commerce and Magento Open Source versions 2.3.7-p3, 2.4.3-p2, 2.4.4 and later support the OpenSearch service.
{:.bs-callout-info}
See [System requirements]({{ site.baseurl }}/guides/v2.4/install-gde/system-requirements.html) in the _Installation guide_ for recommended versions.
diff --git a/src/cloud/setup/first-time-deploy.md b/src/cloud/setup/first-time-deploy.md
index 8eeaba4acdf..77b9caa64e4 100644
--- a/src/cloud/setup/first-time-deploy.md
+++ b/src/cloud/setup/first-time-deploy.md
@@ -7,6 +7,8 @@ functional_areas:
- Cloud
- Setup
- Deploy
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/launch/overview.html
+status: migrated
---
{:.ref-header}
diff --git a/src/cloud/setup/first-time-setup-import-first-steps.md b/src/cloud/setup/first-time-setup-import-first-steps.md
index d22054edfcd..ea52ad0188c 100755
--- a/src/cloud/setup/first-time-setup-import-first-steps.md
+++ b/src/cloud/setup/first-time-setup-import-first-steps.md
@@ -4,6 +4,8 @@ title: Import existing code into a project
functional_areas:
- Cloud
- Setup
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/deploy/staging-production.html
+status: migrated
---
You can create a {{site.data.var.ece}} project from a blank template or by importing existing code. We recommend starting with a blank template first, and then importing existing code on top of it.
diff --git a/src/cloud/setup/first-time-setup-import-import.md b/src/cloud/setup/first-time-setup-import-import.md
index 3aacc27b7be..123d8ec8a6a 100755
--- a/src/cloud/setup/first-time-setup-import-import.md
+++ b/src/cloud/setup/first-time-setup-import-import.md
@@ -4,6 +4,8 @@ title: Import code
functional_areas:
- Cloud
- Setup
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/deploy/staging-production.html
+status: migrated
---
Use the following instructions to import your {{site.data.var.ee}} code into a current {{ site.data.var.ece }} environment.
diff --git a/src/cloud/setup/first-time-setup-import-prepare.md b/src/cloud/setup/first-time-setup-import-prepare.md
index c2aaf7b1258..cb3549f1509 100755
--- a/src/cloud/setup/first-time-setup-import-prepare.md
+++ b/src/cloud/setup/first-time-setup-import-prepare.md
@@ -4,6 +4,8 @@ title: Prepare your existing system
functional_areas:
- Cloud
- Setup
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/project/overview.html
+status: migrated
---
You need to prepare your existing {{site.data.var.ee}} implementation to import it into a new {{site.data.var.ece}} project. This includes updating and adding files, transferring media files, and migrating data.
diff --git a/src/cloud/setup/first-time-setup.md b/src/cloud/setup/first-time-setup.md
index 050bad062dc..896bf30372b 100644
--- a/src/cloud/setup/first-time-setup.md
+++ b/src/cloud/setup/first-time-setup.md
@@ -6,6 +6,8 @@ redirect_from:
functional_areas:
- Cloud
- Setup
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/overview.html
+status: migrated
---
{{site.data.var.ece}} environments are **Read Only**, including all Starter environments and all Pro Integration, Staging, and Production environments. In a local development environment, you can write and test code prior to pushing it to an Integration environment for further testing and deployment to Staging and Production. You must develop in a local workspace using a cloned Integration environment and push changes to the remote, read-only {{site.data.var.ece}} Git repository. You can choose one of two methods:
diff --git a/src/cloud/trouble/robots-sitemap.md b/src/cloud/trouble/robots-sitemap.md
index bfcd2fa5133..ec98155c9e8 100644
--- a/src/cloud/trouble/robots-sitemap.md
+++ b/src/cloud/trouble/robots-sitemap.md
@@ -4,6 +4,8 @@ title: Add site map and search engine robots
functional_areas:
- Cloud
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure-store/robots-sitemap.html
+status: migrated
---
An attempt to generate and write the `sitemap.xml` file to the root directory results in the following error:
diff --git a/src/cloud/trouble/trouble.md b/src/cloud/trouble/trouble.md
index 260911ef711..19fe59b6ff6 100644
--- a/src/cloud/trouble/trouble.md
+++ b/src/cloud/trouble/trouble.md
@@ -4,6 +4,8 @@ title: Troubleshooting
functional_areas:
- Cloud
- Help
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/deploy/best-practices.html
+status: migrated
---
The troubleshooting topics help to resolve specific issues with your {{site.data.var.ece}} project. Before submitting a Support ticket, check the following:
diff --git a/src/cloud/trouble/trouble_comp-deploy-fail.md b/src/cloud/trouble/trouble_comp-deploy-fail.md
index 74b596c9ed0..1e7e9959f26 100644
--- a/src/cloud/trouble/trouble_comp-deploy-fail.md
+++ b/src/cloud/trouble/trouble_comp-deploy-fail.md
@@ -4,6 +4,8 @@ title: Component deployment failure
functional_areas:
- Cloud
- Deploy
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/deploy/recover-failed-deployment.html
+status: migrated
---
This topic discusses how to recover from a failed component deployment. Typical examples include components that have dependencies that are not met by your environment, such as incompatible PHP versions.
diff --git a/src/cloud/trouble/troubleshoot-deployment.md b/src/cloud/trouble/troubleshoot-deployment.md
index cd92f0a4436..0864c3da314 100644
--- a/src/cloud/trouble/troubleshoot-deployment.md
+++ b/src/cloud/trouble/troubleshoot-deployment.md
@@ -7,6 +7,8 @@ redirect_to: https://support.magento.com/hc/en-us/articles/4411647469965
functional_areas:
- Cloud
- Deploy
+redirect_to: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/deploy/recover-failed-deployment.html
+status: migrated
---
This topic discusses how to recover if you deployed the {{site.data.var.ee}} application with the incorrect [authentication keys]({{ site.baseurl }}/guides/v2.3/install-gde/prereq/connect-auth.html). For example, you might have used the keys for another account or you might have used {{site.data.var.ce}} keys instead of {{site.data.var.ee}} keys.
diff --git a/src/codelinks/attributes.md b/src/codelinks/attributes.md
index b5d8b3238a8..56b3fbe2dec 100644
--- a/src/codelinks/attributes.md
+++ b/src/codelinks/attributes.md
@@ -1,6 +1,9 @@
---
layout: full-width
title: Retrieving detailed attributes
+group: rest-api
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/attributes
+status: migrated
---
Swagger and other types of code-generated documentation erroneously indicate several APIs that
diff --git a/src/community/best-practices.md b/src/community/best-practices.md
index 5797b84c2f4..9e68a2e3448 100644
--- a/src/community/best-practices.md
+++ b/src/community/best-practices.md
@@ -3,8 +3,8 @@ group: community
title: Community contributed best practices
redirect_from:
- /community/resources/best-practices.html
-migrated_to: https://developer.adobe.com/commerce/contributor/community/best-practices/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/contributor/community/best-practices/
+status: migrated
---
This section covers a broad scope of Community contributed best and leading practices, common solutions, and recommendations for Magento.
diff --git a/src/community/contribution-day-organizer-handbook.md b/src/community/contribution-day-organizer-handbook.md
index 210dd189703..7b5d3b9abbd 100644
--- a/src/community/contribution-day-organizer-handbook.md
+++ b/src/community/contribution-day-organizer-handbook.md
@@ -3,8 +3,8 @@ group: community
title: Contribution Day Organizer's Handbook
redirect_from:
- /community/resources/contribution-day-organizer-handbook.html
-migrated_to: https://developer.adobe.com/commerce/contributor/community/organizer-handbook/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/contributor/community/organizer-handbook/
+status: migrated
---
Thank you for taking the time to organize a Magento Contribution Day! This handbook aims to answer any questions you have on the matter, but if you still have questions feel free to email the Community Engineering team: `engcom@adobe.com`.
diff --git a/src/community/contribution-programs.md b/src/community/contribution-programs.md
index 6ea1d834d4c..1895b9c804e 100644
--- a/src/community/contribution-programs.md
+++ b/src/community/contribution-programs.md
@@ -1,8 +1,8 @@
---
group: community
title: Contribution programs
-migrated_to: https://developer.adobe.com/commerce/contributor/community/contribution-programs/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/contributor/community/contribution-programs/
+status: migrated
---
Adobe is pleased to provide a Solution Partners program for partners.
diff --git a/src/community/resources.md b/src/community/resources.md
index 7506faa2a6e..8097cb8cdc2 100644
--- a/src/community/resources.md
+++ b/src/community/resources.md
@@ -3,8 +3,8 @@ group: community
title: Community Resources
redirect_from:
- /community/resources/resources.html
-migrated_to: https://developer.adobe.com/commerce/contributor/community/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/contributor/community/
+status: migrated
---
## Magento DevBlog
diff --git a/src/community/support.md b/src/community/support.md
index 28cd1b0c753..5af5faee635 100644
--- a/src/community/support.md
+++ b/src/community/support.md
@@ -5,8 +5,8 @@ subgroup: resources
title: Adobe Commerce Support
redirect_from:
- /community/resources/support.html
-migrated_to: https://developer.adobe.com/commerce/contributor/community/support/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/contributor/community/support/
+status: migrated
---
If you have issues, receive error messages, or need additional How To's, see our [{{site.data.var.ee}} Support Knowledge Base](https://support.magento.com). The knowledge base includes a growing amount of troubleshooting, how to, and FAQ articles for Magento 2 Commerce, Commerce (Cloud), and Open Source. We are constantly adding new content for Magento platform, services, modules, and much more.
diff --git a/src/compliance/industry-compliance.md b/src/compliance/industry-compliance.md
index 883fd948f9c..140b9e86a0e 100644
--- a/src/compliance/industry-compliance.md
+++ b/src/compliance/industry-compliance.md
@@ -1,6 +1,8 @@
---
group: compliance
title: Industry Compliance
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/security-and-compliance/overview.html
+status: migrated
---
Merchants are obligated to meet industry guidelines for maintaining a secure environment, legal requirements in their jurisdiction, and best practices for online commerce. To learn more from a business perspective, see the [Industry Compliance](https://docs.magento.com/m2/ee/user_guide/stores/compliance-industry.html) section in the _{{site.data.var.ee}} User Guide_.
diff --git a/src/compliance/privacy/__adobe-privacy-js-library.md b/src/compliance/privacy/__adobe-privacy-js-library.md
index f78b83205ce..012527d65ca 100644
--- a/src/compliance/privacy/__adobe-privacy-js-library.md
+++ b/src/compliance/privacy/__adobe-privacy-js-library.md
@@ -1,6 +1,8 @@
---
group: compliance
title: Adobe Privacy JavaScript Library
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/security-and-compliance/privacy/adobe-javascript-library.html
+status: migrated
---
diff --git a/src/compliance/privacy/ccpa.md b/src/compliance/privacy/ccpa.md
index 24b23cb5f29..55fb45d7d94 100644
--- a/src/compliance/privacy/ccpa.md
+++ b/src/compliance/privacy/ccpa.md
@@ -1,6 +1,8 @@
---
group: compliance
title: California Consumer Privacy Act
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/security-and-compliance/privacy/ccpa.html
+status: migrated
---
{:.bs-callout-info}
diff --git a/src/compliance/privacy/gdpr.md b/src/compliance/privacy/gdpr.md
index 9d152ac9a69..56dc5a614c9 100644
--- a/src/compliance/privacy/gdpr.md
+++ b/src/compliance/privacy/gdpr.md
@@ -1,6 +1,8 @@
---
group: compliance
title: General Data Protection Regulation
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/security-and-compliance/privacy/gdpr.html
+status: migrated
---
{: .bs-callout-info}
diff --git a/src/compliance/privacy/magento-privacy-js-library.md b/src/compliance/privacy/magento-privacy-js-library.md
index 938294172a6..8c0a798880c 100644
--- a/src/compliance/privacy/magento-privacy-js-library.md
+++ b/src/compliance/privacy/magento-privacy-js-library.md
@@ -1,6 +1,8 @@
---
group: compliance
title: Privacy JavaScript Library
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/security-and-compliance/privacy/javascript-library.html
+status: migrated
---
diff --git a/src/compliance/privacy/pi-data-reference-m1.md b/src/compliance/privacy/pi-data-reference-m1.md
index 4089c3240e0..b58b8d326b6 100644
--- a/src/compliance/privacy/pi-data-reference-m1.md
+++ b/src/compliance/privacy/pi-data-reference-m1.md
@@ -1,6 +1,8 @@
---
group: compliance
title: Personal Information Reference (Magento 1.x)
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/security-and-compliance/reference/data-m1.html
+status: migrated
---
{: .bs-callout-info}
diff --git a/src/compliance/privacy/pi-data-reference-m2.md b/src/compliance/privacy/pi-data-reference-m2.md
index ef2cfc509a5..554bf2d6d3a 100644
--- a/src/compliance/privacy/pi-data-reference-m2.md
+++ b/src/compliance/privacy/pi-data-reference-m2.md
@@ -1,6 +1,8 @@
---
group: compliance
title: Personal Information Reference (Magento 2.x)
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/security-and-compliance/reference/data-m2.html
+status: migrated
---
{: .bs-callout-info}
@@ -57,7 +59,7 @@ Magento 2 can be figured to store the following customer attributes:
- Name Suffix
{:.bs-callout-info}
-In keeping with current security and privacy best practices, be sure you are aware of any potential legal and security risks associated with the storage of customers’ full date of birth (month, day, year) along with other personal identifiers, such as full name, before collecting or processing such data.
+In keeping with current security and privacy best practices, be sure you are aware of any potential legal and security risks associated with the storage of customers' full date of birth (month, day, year) along with other personal identifiers, such as full name, before collecting or processing such data.
#### `customer_entity` and 'customer_entity' references
diff --git a/src/contributor-guide/backward-compatible-development/index.md b/src/contributor-guide/backward-compatible-development/index.md
index e63cb3d9ddd..f436d0c73c5 100644
--- a/src/contributor-guide/backward-compatible-development/index.md
+++ b/src/contributor-guide/backward-compatible-development/index.md
@@ -4,8 +4,8 @@ title: Backward compatible development
redirect_from:
- guides/v2.3/contributor-guide/backward-compatible-development/index.html
- guides/v2.4/contributor-guide/backward-compatible-development/index.html
-migrated_to: https://developer.adobe.com/commerce/contributor/guides/code-contributions/backward-compatibility-policy/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/contributor/guides/code-contributions/backward-compatibility-policy/
+status: migrated
---
This page describes rules and best practices for backward compatible development.
diff --git a/src/contributor-guide/contributing.md b/src/contributor-guide/contributing.md
index 24cb585e2aa..54ada9763ae 100644
--- a/src/contributor-guide/contributing.md
+++ b/src/contributor-guide/contributing.md
@@ -4,8 +4,8 @@ title: Code Contributions
redirect_from:
- guides/v2.3/contributor-guide/contributing.html
- guides/v2.4/contributor-guide/contributing.html
-migrated_to: https://developer.adobe.com/commerce/contributor/guides/code-contributions/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/contributor/guides/code-contributions/
+status: migrated
---
{:.bs-callout-tip}
diff --git a/src/contributor-guide/contributing_dod.md b/src/contributor-guide/contributing_dod.md
index c6e0b85ffe8..256bf662319 100644
--- a/src/contributor-guide/contributing_dod.md
+++ b/src/contributor-guide/contributing_dod.md
@@ -4,8 +4,8 @@ title: Commerce Definition of Done
redirect_from:
- guides/v2.3/contributor-guide/contributing_dod.html
- guides/v2.4/contributor-guide/contributing_dod.html
-migrated_to: https://developer.adobe.com/commerce/contributor/guides/code-contributions/definition-of-done/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/contributor/guides/code-contributions/definition-of-done/
+status: migrated
---
## Overview
diff --git a/src/contributor-guide/contributors.md b/src/contributor-guide/contributors.md
index 288600a861f..bc0c284db78 100644
--- a/src/contributor-guide/contributors.md
+++ b/src/contributor-guide/contributors.md
@@ -5,8 +5,8 @@ redirect_from:
- contributor-guide/quarterly-contributors.html
- guides/v2.3/contributor-guide/contributors.html
- guides/v2.4/contributor-guide/contributors.html
-migrated_to: https://developer.adobe.com/commerce/contributor/guides/contributors/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/contributor/guides/contributors/
+status: migrated
---
Many thanks to our community members, partners, and Magento fans who contribute to our open source projects.
diff --git a/src/contributor-guide/maintainer-handbook.md b/src/contributor-guide/maintainer-handbook.md
index 959f995f8fc..9d15e877c77 100644
--- a/src/contributor-guide/maintainer-handbook.md
+++ b/src/contributor-guide/maintainer-handbook.md
@@ -1,8 +1,8 @@
---
group: contributor-guide
title: Maintainer's Handbook
-migrated_to: https://developer.adobe.com/commerce/contributor/guides/maintainers/handbook/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/contributor/guides/maintainers/handbook/
+status: migrated
---
This document describes activities performed by a community maintainer, provides some insight and description of the tools integrated within GitHub to assist our maintainers.
diff --git a/src/contributor-guide/maintainers.md b/src/contributor-guide/maintainers.md
index 3ae9a9d8b84..926bc94f6b4 100644
--- a/src/contributor-guide/maintainers.md
+++ b/src/contributor-guide/maintainers.md
@@ -4,8 +4,8 @@ title: Maintainers
redirect_from:
- guides/v2.3/contributor-guide/maintainers.html
- guides/v2.4/contributor-guide/maintainers.html
-migrated_to: https://developer.adobe.com/commerce/contributor/guides/maintainers/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/contributor/guides/maintainers/
+status: migrated
---
Magento trusts our active community members to review pull requests and accept or reject proposed code changes. [Community Maintainers](https://magento.com/magento-contributors#maintainers) take part in discussions, reviews, and help process pull requests.
diff --git a/src/contributor-guide/phpstorm-code-inspections.md b/src/contributor-guide/phpstorm-code-inspections.md
index b3973863762..c78dc123333 100644
--- a/src/contributor-guide/phpstorm-code-inspections.md
+++ b/src/contributor-guide/phpstorm-code-inspections.md
@@ -1,8 +1,8 @@
---
group: contributor-guide
title: PHPStorm plugin code inspections
-migrated_to: https://developer.adobe.com/commerce/contributor/guides/code-contributions/phpstorm-code-inspections/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/contributor/guides/code-contributions/phpstorm-code-inspections/
+status: migrated
---
The PHPStorm plugin is a tool created by the community to optimize routine coding operations and improve the {{site.data.var.ee}} development experience. The plugin is compatible with the IntelliJ IDEA Ultimate and PhpStorm IDEs. The functionality includes {{site.data.var.ee}} specific code generation shortcuts, code inspections, autocomplete functionality for configuration files, MFTF tests, and RequireJS.
diff --git a/src/contributor-guide/processing-workflow.md b/src/contributor-guide/processing-workflow.md
index bf285c2d371..d4412880a27 100644
--- a/src/contributor-guide/processing-workflow.md
+++ b/src/contributor-guide/processing-workflow.md
@@ -1,8 +1,8 @@
---
group: contributor-guide
title: GitHub issue processing workflow
-migrated_to: https://developer.adobe.com/commerce/contributor/guides/code-contributions/processing-workflow/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/contributor/guides/code-contributions/processing-workflow/
+status: migrated
---
The GitHub issue workflow ensures that issues are clear, well written, and thoroughly vetted. Following these procedures allows valid issues to get the attention they deserve.
diff --git a/src/contributor-guide/pull-request-tests.md b/src/contributor-guide/pull-request-tests.md
index 791584dbcfa..c3f38673646 100644
--- a/src/contributor-guide/pull-request-tests.md
+++ b/src/contributor-guide/pull-request-tests.md
@@ -1,8 +1,8 @@
---
group: contributor-guide
title: Pull Request Tests
-migrated_to: https://developer.adobe.com/commerce/contributor/guides/code-contributions/pull-request-tests/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/contributor/guides/code-contributions/pull-request-tests/
+status: migrated
---
## Magento Automated Testing
diff --git a/src/contributor-guide/templates/basic_template.md b/src/contributor-guide/templates/basic_template.md
index ed42a7e7d7f..55bf6a4f83a 100644
--- a/src/contributor-guide/templates/basic_template.md
+++ b/src/contributor-guide/templates/basic_template.md
@@ -4,6 +4,7 @@ title: Basic template
redirect_from:
- guides/v2.3/contributor-guide/templates/basic_template.html
- guides/v2.4/contributor-guide/templates/basic_template.html
+redirect_to: https://developer.adobe.com/commerce/contributor/guides/doc-contributions/
---
Introductory text that gives an overview of the topic you will be writing about.
diff --git a/src/contributor-guide/templates/tutorial-template-first.md b/src/contributor-guide/templates/tutorial-template-first.md
index 4f5a0cceab6..469fb60c6e3 100644
--- a/src/contributor-guide/templates/tutorial-template-first.md
+++ b/src/contributor-guide/templates/tutorial-template-first.md
@@ -10,6 +10,7 @@ return_to:
redirect_from:
- guides/v2.3/contributor-guide/templates/tutorial-template-first.html
- guides/v2.4/contributor-guide/templates/tutorial-template-first.html
+redirect_to: https://developer.adobe.com/commerce/contributor/guides/doc-contributions/
---
A tutorial provides procedural information spread across multiple pages. It contains several design elements that differ from standard topics:
diff --git a/src/contributor-guide/templates/tutorial-template-last.md b/src/contributor-guide/templates/tutorial-template-last.md
index 26f77830ff8..b59760ec96d 100644
--- a/src/contributor-guide/templates/tutorial-template-last.md
+++ b/src/contributor-guide/templates/tutorial-template-last.md
@@ -10,6 +10,7 @@ return_to:
redirect_from:
- guides/v2.3/contributor-guide/templates/tutorial-template-last.html
- guides/v2.4/contributor-guide/templates/tutorial-template-last.html
+redirect_to: https://developer.adobe.com/commerce/contributor/guides/doc-contributions/
---
The last page of a tutorial should acknowledge the reader has completed the tutorial and provide links to related information. Otherwise, add the content as you see fit.
diff --git a/src/contributor-guide/templates/tutorial-template-middle.md b/src/contributor-guide/templates/tutorial-template-middle.md
index 0157ee8c497..4cccf4a263b 100644
--- a/src/contributor-guide/templates/tutorial-template-middle.md
+++ b/src/contributor-guide/templates/tutorial-template-middle.md
@@ -10,6 +10,7 @@ return_to:
redirect_from:
- guides/v2.3/contributor-guide/templates/tutorial-template-middle.html
- guides/v2.4/contributor-guide/templates/tutorial-template-middle.html
+redirect_to: https://developer.adobe.com/commerce/contributor/guides/doc-contributions/
---
Add the content for each step as you see fit.
diff --git a/src/extensions/amazon-sales/index.md b/src/extensions/amazon-sales/index.md
index a4a5e35ec6b..5078d4af978 100644
--- a/src/extensions/amazon-sales/index.md
+++ b/src/extensions/amazon-sales/index.md
@@ -1,8 +1,8 @@
---
group: extensions
title: Install Amazon Sales Channel
-migrated_to: https://experienceleague.adobe.com/docs/commerce-channels/amazon/getting-started/install.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-channels/amazon/getting-started/install.html
+status: migrated
---
{: .bs-callout-warning }
diff --git a/src/extensions/amazon-sales/release-notes/index.md b/src/extensions/amazon-sales/release-notes/index.md
index be746ad0da0..3496fc5d88e 100644
--- a/src/extensions/amazon-sales/release-notes/index.md
+++ b/src/extensions/amazon-sales/release-notes/index.md
@@ -1,8 +1,8 @@
---
group: extensions
title: Amazon Sales Channel Release Notes
-migrated_to: https://experienceleague.adobe.com/docs/commerce-channels/amazon/release-notes.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-channels/amazon/release-notes.html
+status: migrated
---
{: .bs-callout-warning }
Amazon Sales Channel versions 4.0.0 and 4.1.0 are only supported for {{site.data.var.ee}} 2.3.x versions. Amazon Sales Channel version 4.2.0 is compatible with {{site.data.var.ee}} 2.3.x versions but is only supported for {{site.data.var.ee}} 2.4.x versions.
diff --git a/src/extensions/b2b/index.md b/src/extensions/b2b/index.md
index 8f1ee7d2efc..45ba91c15a7 100644
--- a/src/extensions/b2b/index.md
+++ b/src/extensions/b2b/index.md
@@ -4,8 +4,8 @@ title: Install B2B
ee_only: true
redirect_from:
- guides/v2.3/comp-mgr/install-extensions/b2b-installation.html
-migrated_to: https://experienceleague.adobe.com/docs/commerce-admin/b2b/install.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-admin/b2b/install.html
+status: migrated
---
{:.bs-callout-warning}
diff --git a/src/extensions/index.md b/src/extensions/index.md
index d0d2e5f02b5..90633b4a2ef 100644
--- a/src/extensions/index.md
+++ b/src/extensions/index.md
@@ -1,8 +1,8 @@
---
group: extensions
title: Introduction
-migrated_to: https://experienceleague.adobe.com/docs/commerce-admin/start/resources/extensions.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-admin/start/resources/extensions.html
+status: migrated
---
Extensions allow you to add custom features, functionality, services, and integrations to your Admin and storefront. Extension developers package and install custom code as extensions, modules, components, addons, etc. You can design and develop extensions or purchase and install extensions from the Commerce Marketplace or third-party providers.
diff --git a/src/extensions/inventory-management/index.md b/src/extensions/inventory-management/index.md
index 1e357becc36..091507b3835 100644
--- a/src/extensions/inventory-management/index.md
+++ b/src/extensions/inventory-management/index.md
@@ -2,8 +2,8 @@
group: extensions
title: Install Inventory Management
redirect_from: guides/v2.3/comp-mgr/install-extensions/inventory-management-installation.html
-migrated_to: https://experienceleague.adobe.com/docs/commerce-admin/inventory/get-started/install-update.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-admin/inventory/get-started/install-update.html
+status: migrated
---
{{site.data.var.im}} modules provide all inventory features and options for Single and Multi Source merchants to manage product quantities and stock for sales channels. These features are available in 2.3.x {{site.data.var.ce}}, {{site.data.var.ee}}, and {{site.data.var.ece}}.
diff --git a/src/extensions/vendor/vendor.md b/src/extensions/vendor/vendor.md
index 239728c9e22..5ac61b61124 100644
--- a/src/extensions/vendor/vendor.md
+++ b/src/extensions/vendor/vendor.md
@@ -5,8 +5,8 @@ permalink: extensions/vendor/
redirect_from:
- /extensions/vendor/yotpo/release-notes.html
- /extensions/vendor/dotdigital/release-notes.html
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/upgrade-guide/modules/upgrade.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/upgrade-guide/modules/upgrade.html
+status: migrated
---
{:.bs-callout-warning}
diff --git a/src/feed.xml b/src/feed.xml
deleted file mode 100644
index 0b1408515cd..00000000000
--- a/src/feed.xml
+++ /dev/null
@@ -1,25 +0,0 @@
----
-layout: none
----
-
-
-
-
- {{ site.title | xml_escape }}
- {{ site.description | xml_escape }}
- {{ site.url }}
-
- {{ site.time | date_to_rfc822 }}
- {{ site.time | date_to_rfc822 }}
- Jekyll v{{ jekyll.version }}
- {% assign sorted_pages = site.html_pages | where_exp: "page", "page.tag != 'omit'"| sort:"last_modified_at" | reverse %}
- {% for page in sorted_pages limit: 100 %}
-
- {{ page.title | xml_escape }}
- {{ page.content | xml_escape | strip_html | truncatewords: 75 }}
- {{ page.url | prepend: site.url }}
- {{ page.last_modified_at | date_to_rfc822 }}
-
- {% endfor %}
-
-
diff --git a/src/guides/v2.3/config-guide/cli/config-cli-subcommands-catalog-sync.md b/src/guides/v2.3/config-guide/cli/config-cli-subcommands-catalog-sync.md
index 8b3df767d61..746b59ea695 100644
--- a/src/guides/v2.3/config-guide/cli/config-cli-subcommands-catalog-sync.md
+++ b/src/guides/v2.3/config-guide/cli/config-cli-subcommands-catalog-sync.md
@@ -1,8 +1,6 @@
---
group: configuration-guide
title: Catalog Sync
-migrated_to: https://experienceleague.adobe.com/docs/commerce-merchant-services/user-guides/catalog-sync.html
-layout: migrated
---
Adobe Commerce and Magento Open Source compiles catalog data into tables using indexers. This process is automatically [triggered by several events]({{ site.user_guide_url }}/system/index-management-events.html), such as changes to a product's price or inventory levels. To allow some Commerce services to use that catalog data, a catalog sync process runs hourly. The catalog sync process exports product data from the Commerce server to Commerce services, which are deployed as SaaS, on an ongoing basis. For example, the [Product Recommendations]({{ site.user_guide_url }}/marketing/product-recommendations.html) feature needs up-to-date catalog information so that it can accurately return recommendations with correct names, pricing, and availability. Use the command-line interface to trigger the catalog sync and reindex product data for consumption by Commerce services.
@@ -24,7 +22,7 @@ Command options:
bin/magento saas:resync --feed [no-reindex]
```
-The following table explains this command’s parameters and descriptions.
+The following table explains this command's parameters and descriptions.
|Parameter|Description|Required?|
|---| ---| ---|
diff --git a/src/guides/v2.3/config-guide/cli/config-cli-subcommands-index.md b/src/guides/v2.3/config-guide/cli/config-cli-subcommands-index.md
index f10b9fb3dea..e4943462d39 100644
--- a/src/guides/v2.3/config-guide/cli/config-cli-subcommands-index.md
+++ b/src/guides/v2.3/config-guide/cli/config-cli-subcommands-index.md
@@ -113,7 +113,7 @@ Reindexing all indexers can take a long time for stores with large numbers of pr
### Reindexing in parallel mode
-Indexers are scoped and multi-threaded to support reindexing in parallel mode. It parallelizes by the indexer’s dimension and executes across multiple threads, reducing processing time.
+Indexers are scoped and multi-threaded to support reindexing in parallel mode. It parallelizes by the indexer's dimension and executes across multiple threads, reducing processing time.
In this context, `dimension` is the scope of the reindexing, for instance a `website` or just a specific `customer_group`.
@@ -233,7 +233,7 @@ Catalog Search: Update on Save
### Configure indexers
{:.bs-callout-info}
-Before switching indexer modes, we recommend putting your website to [maintenance]({{ page.baseurl }}/install-gde/install/cli/install-cli-subcommands-maint.html) mode and [disable cron]({{ site.baseurl }}/cloud/configure/setup-cron-jobs.html#disable-cron-jobs). This will ensure you do not suffer database locks.
+Before switching indexer modes, we recommend putting your website to [maintenance]({{ page.baseurl }}/install-gde/install/cli/install-cli-subcommands-maint.html) mode and [disable cron](https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure/app/properties/crons-property.html#disable-cron-jobs). This will ensure you do not suffer database locks.
To specify the indexer configuration:
diff --git a/src/guides/v2.3/config-guide/mq/manage-message-queues.md b/src/guides/v2.3/config-guide/mq/manage-message-queues.md
index 7d117a9c2a4..c0ba4d57ae2 100644
--- a/src/guides/v2.3/config-guide/mq/manage-message-queues.md
+++ b/src/guides/v2.3/config-guide/mq/manage-message-queues.md
@@ -39,7 +39,7 @@ You can also use a process manager such as [Supervisor](https://supervisord.org/
* Each consumer processes 10000 messages and then terminates
{:.bs-callout-info}
-If your {{ site.data.var.ee }} store is hosted on the Cloud platform, use the [`CRON_CONSUMERS_RUNNER`]({{ site.baseurl }}/cloud/env/variables-deploy.html#cron_consumers_runner) to configure the `consumers_runner` cron job.
+If your {{ site.data.var.ee }} store is hosted on the Cloud platform, use the [`CRON_CONSUMERS_RUNNER`](https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure/env/stage/variables-deploy.html#cron_consumers_runner) to configure the `consumers_runner` cron job.
#### Specific configuration
@@ -63,7 +63,7 @@ Edit the `/app/etc/env.php` file to configure the cron job `consumers_runner`.
* `consumers` - An array of strings specifying which consumer(s) to run. An empty array runs *all* consumers.
{:.bs-callout-info}
- If your {{ site.data.var.ee }} store is hosted on the Cloud platform, use the [`CONSUMERS_WAIT_FOR_MAX_MESSAGES`]({{ site.baseurl }}/cloud/env/variables-deploy.html#consumers_wait_for_max_messages) to configure how consumers process messages from the message queue.
+ If your {{ site.data.var.ee }} store is hosted on the Cloud platform, use the [`CONSUMERS_WAIT_FOR_MAX_MESSAGES`](https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure/env/stage/variables-deploy.html#consumers_wait_for_max_messages) to configure how consumers process messages from the message queue.
{% include config/message-queue-consumers.md %}
diff --git a/src/guides/v2.3/config-guide/multi-site/change-increment-id.md b/src/guides/v2.3/config-guide/multi-site/change-increment-id.md
index 8ff231223f0..c626400c00a 100644
--- a/src/guides/v2.3/config-guide/multi-site/change-increment-id.md
+++ b/src/guides/v2.3/config-guide/multi-site/change-increment-id.md
@@ -77,5 +77,5 @@ Before executing the `ALTER TABLE` query on a production environment of {{site.d
[Set up a remote MySQL database connection]: {{ page.baseurl }}/install-gde/prereq/mysql_remote.html
[Create a DB backup]: https://support.magento.com/hc/en-us/articles/360003254334
[Create database dump on Cloud]: https://support.magento.com/hc/en-us/articles/360003254334
-[SSH to your environment]: {{site.baseurl}}/cloud/env/environments-ssh.html#ssh
+[SSH to your environment]: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/secure-connections.html
[any supported version]: {{ page.baseurl }}/install-gde/prereq/mysql.html
diff --git a/src/guides/v2.3/index.html b/src/guides/v2.3/index.html
index d0aa4b4174b..895220e4409 100644
--- a/src/guides/v2.3/index.html
+++ b/src/guides/v2.3/index.html
@@ -3,7 +3,7 @@
---
-
PHP 7.3 reached end of support in December 2021 and {{site.data.var.ee}} 2.3.x reaches end of support in September 2022. You may want to consider planning your upgrade now to {{site.data.var.ee}} 2.4.x and PHP 7.4.x to help maintain PCI compliance.
+
{{site.data.var.ee}} 2.3 reached end of support in September 2022.
` tag to achieve some visual effect. You might also need to tweak some [JavaScript](https://glossary.magento.com/javascript/) to cope with different HTML markup. This change is more demanding than simply extending Magento CSS, but is still within the grasp of smaller projects and leaner teams.
+
+### Replace Magento-Provided CSS
+
+Rather than edit the default CSS provided by Magento, you might decide to replace all the default storefront CSS code with your own. This strategy avoids tying a project to the Magento-provided CSS, but puts a greater burden on project development and integration. It also allows the use of different CSS tools or technologies not provided with Magento. Partners who build their own set of CSS libraries could reuse these libraries on different customer projects. (These unique CSS libraries may help differentiate a partner from others in the market.)
+
+In addition to replacing CSS files, you might need to replace small amounts of HTML and JavaScript.
+
+### Replace Magento-Provided CSS, HTML, and JavaScript
+
+Delivering a sharply different shopping experience than the default Magento installation provides is a more substantial task. However, the tradeoff might be a more complicated experience integrating additional extensions into your installation in the future.
+
+{:.bs-callout-tip}
+ Any customization of your storefront will work optimally, and provide the easiest path for later upgrades, if you follow the best practice of consistently compartmentalizing code by type. For example, keep all HTML in [PHTML](https://glossary.magento.com/phtml) files; keep all JavaScript in JavaScript files.
+
+{:.ref-header}
+Related topics
+
+[Extensibility and modularity][]
+
+[Global extensibility features][]
+
+[Admin Pattern Library][]
+
+[Overview of UI components][]
+
+[Frontend Developer Guide][]
+
+[JavaScript Developer Guide][]
+
+
+
+[Extensibility and modularity]:{{page.baseurl}}/architecture/extensibility.html
+[Global extensibility features]: {{page.baseurl}}/architecture/global_extensibility_features.html
+[Admin Pattern Library]: {{page.baseurl}}/pattern-library/bk-pattern.html
+[Overview of UI components]: {{page.baseurl}}/ui_comp_guide/bk-ui_comps.html
+[Frontend Developer Guide]: {{page.baseurl}}/frontend-dev-guide/bk-frontend-dev-guide.html
+[JavaScript Developer Guide]: {{page.baseurl}}/javascript-dev-guide/bk-javascript-dev-guide.html
+[Commerce Marketplace]: https://marketplace.magento.com/
diff --git a/src/guides/v2.4/architecture/global_extensibility_features.md b/src/guides/v2.4/architecture/global_extensibility_features.md
index 13193818ba7..01535b08282 100644
--- a/src/guides/v2.4/architecture/global_extensibility_features.md
+++ b/src/guides/v2.4/architecture/global_extensibility_features.md
@@ -1,8 +1,8 @@
---
group: architecture-guide
title: Global features that support extensibility
-migrated_to: https://developer.adobe.com/commerce/php/architecture/modules/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/architecture/modules/
+status: migrated
---
## Overview
diff --git a/src/guides/v2.4/architecture/security_intro.md b/src/guides/v2.4/architecture/security_intro.md
index 8e2bf9f1865..0320c59c27c 100644
--- a/src/guides/v2.4/architecture/security_intro.md
+++ b/src/guides/v2.4/architecture/security_intro.md
@@ -4,8 +4,8 @@ subgroup: Architectural Basics
title: Security overview
menu_title: Security
menu_order:
-migrated_to: https://developer.adobe.com/commerce/php/architecture/basics/security/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/architecture/basics/security/
+status: migrated
---
The security of your data and digital experiences is our priority. To better protect {{site.data.var.ee}} and {{site.data.var.ce}} installations from the physical layer up, we have implemented hundreds of processes and controls to help us comply with [industry-accepted standards][1], regulations, and certifications. To help protect installations from the software layer down, we build in security measures that are based on the [Adobe Secure Product Lifecyle][2].
diff --git a/src/guides/v2.4/architecture/storefront_customization.md b/src/guides/v2.4/architecture/storefront_customization.md
index eef679c8f2e..b2f18980236 100644
--- a/src/guides/v2.4/architecture/storefront_customization.md
+++ b/src/guides/v2.4/architecture/storefront_customization.md
@@ -2,8 +2,8 @@
group: architecture-guide
title: Storefront customization strategies
menu_title: Storefront customization strategies
-migrated_to: https://developer.adobe.com/commerce/php/architecture/basics/frontend-customization/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/architecture/basics/frontend-customization/
+status: migrated
---
## Overview
diff --git a/src/guides/v2.4/b2b/bk-b2b.md b/src/guides/v2.4/b2b/bk-b2b.md
index 3559eb4f7d9..8468afda646 100644
--- a/src/guides/v2.4/b2b/bk-b2b.md
+++ b/src/guides/v2.4/b2b/bk-b2b.md
@@ -10,8 +10,8 @@ ee_only: True
functional_areas:
- B2B
- Integration
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/b2b/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/b2b/
+status: migrated
---
Unlike the standard business-to-consumer model, {{site.data.var.b2b}} (Business to Business) is designed to meet the needs of sellers (Magento merchants) whose customers are primarily companies—possibly with complex organizational structures and multiple users with various roles and levels of permission.
diff --git a/src/guides/v2.4/b2b/company-credit.md b/src/guides/v2.4/b2b/company-credit.md
index ce7c258dcf8..5396ed667c8 100644
--- a/src/guides/v2.4/b2b/company-credit.md
+++ b/src/guides/v2.4/b2b/company-credit.md
@@ -10,8 +10,8 @@ level3_subgroup: credit
functional_areas:
- B2B
- Integration
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/b2b/company-credit
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/b2b/company-credit
+status: migrated
---
Company credit allows company members to purchase items on credit. This is a feature specific to {{site.data.var.b2b}} that is used only for transactions between companies. The seller allocates an amount (or the credit limit) to a company and then company members can purchase items using this amount with the Payment on Account method. The credit amount used by a company is sent to the seller offline. Then the seller creates a Reimburse transaction in the system to adjust the company balance.
diff --git a/src/guides/v2.4/b2b/company-object.md b/src/guides/v2.4/b2b/company-object.md
index b6287a490e7..9e4f61bfd14 100644
--- a/src/guides/v2.4/b2b/company-object.md
+++ b/src/guides/v2.4/b2b/company-object.md
@@ -10,8 +10,8 @@ level3_subgroup: company
functional_areas:
- B2B
- Integration
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/b2b/company-object
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/b2b/company-object
+status: migrated
---
## Manage company objects
diff --git a/src/guides/v2.4/b2b/company-structures.md b/src/guides/v2.4/b2b/company-structures.md
index 914fd781cde..68970b199ab 100644
--- a/src/guides/v2.4/b2b/company-structures.md
+++ b/src/guides/v2.4/b2b/company-structures.md
@@ -5,8 +5,8 @@ ee_only: true
functional_areas:
- B2B
- Integration
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/b2b/company-structures
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/b2b/company-structures
+status: migrated
---
{{site.data.var.b2b}} allows company users to be assigned to company teams and hierarchies.
diff --git a/src/guides/v2.4/b2b/company-users.md b/src/guides/v2.4/b2b/company-users.md
index e0afdcd1154..2963f429877 100644
--- a/src/guides/v2.4/b2b/company-users.md
+++ b/src/guides/v2.4/b2b/company-users.md
@@ -5,8 +5,8 @@ ee_only: true
functional_areas:
- B2B
- Integration
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/b2b/company-users
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/b2b/company-users
+status: migrated
---
A company user is a customer (buyer) that is assigned extended attributes that identify the company the user belongs to. Use the `POST /V1/customers` call, which is included with {{site.data.var.ce}} and {{site.data.var.ee}}, to create the user. After the user is created, you can use the `PUT /V1/customers/:customer_id` call to set their company data with the `company_attributes` extended attributes.
diff --git a/src/guides/v2.4/b2b/company.md b/src/guides/v2.4/b2b/company.md
index 988e8f59d46..a2dba22821a 100644
--- a/src/guides/v2.4/b2b/company.md
+++ b/src/guides/v2.4/b2b/company.md
@@ -10,8 +10,8 @@ level3_subgroup: company
functional_areas:
- B2B
- Integration
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/b2b/company
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/b2b/company
+status: migrated
---
The `Company` module allows multiple buyers that belong to the same company to view product prices and make purchases based on the shared catalog assigned to this company. A company can contain a hierarchy of users and teams, with roles and permissions assigned at any level.
diff --git a/src/guides/v2.4/b2b/credit-manage.md b/src/guides/v2.4/b2b/credit-manage.md
index ad6c2d6eea6..4cf43264bfd 100644
--- a/src/guides/v2.4/b2b/credit-manage.md
+++ b/src/guides/v2.4/b2b/credit-manage.md
@@ -5,8 +5,8 @@ ee_only: true
functional_areas:
- B2B
- Integration
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/b2b/credit-manage
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/b2b/credit-manage
+status: migrated
---
The company credit entity operates with the following attributes:
diff --git a/src/guides/v2.4/b2b/extensions.md b/src/guides/v2.4/b2b/extensions.md
index 3118cbc2793..25f663f90bf 100644
--- a/src/guides/v2.4/b2b/extensions.md
+++ b/src/guides/v2.4/b2b/extensions.md
@@ -8,8 +8,8 @@ menu_node: parent
ee_only: True
functional_areas:
- B2B
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/b2b/extensions
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/b2b/extensions
+status: migrated
---
See [Module Reference Guide]({{ page.baseurl }}/mrg/intro.html) for information about each {{site.data.var.b2b}} module.
diff --git a/src/guides/v2.4/b2b/integrations.md b/src/guides/v2.4/b2b/integrations.md
index 881b7d8b58c..5b9527b380d 100644
--- a/src/guides/v2.4/b2b/integrations.md
+++ b/src/guides/v2.4/b2b/integrations.md
@@ -9,8 +9,8 @@ ee_only: True
functional_areas:
- B2B
- Integration
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/b2b/integrations
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/b2b/integrations
+status: migrated
---
This topic lists the REST endpoints and services that are provided with {{site.data.var.b2b}}.
diff --git a/src/guides/v2.4/b2b/negotiable-checkout.md b/src/guides/v2.4/b2b/negotiable-checkout.md
index 8f97747f17f..2c0cd5484d6 100644
--- a/src/guides/v2.4/b2b/negotiable-checkout.md
+++ b/src/guides/v2.4/b2b/negotiable-checkout.md
@@ -5,8 +5,8 @@ ee_only: true
functional_areas:
- B2B
- Integration
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/b2b/negotiable-checkout
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/b2b/negotiable-checkout
+status: migrated
---
When the seller and buyer user agree on the quoted products and their prices, the negotiated quote is ready to be converted to an order.
diff --git a/src/guides/v2.4/b2b/negotiable-manage.md b/src/guides/v2.4/b2b/negotiable-manage.md
index 15d8085364f..0049b569124 100644
--- a/src/guides/v2.4/b2b/negotiable-manage.md
+++ b/src/guides/v2.4/b2b/negotiable-manage.md
@@ -10,8 +10,8 @@ level3_subgroup: nq
functional_areas:
- B2B
- Integration
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/b2b/negotiable-manage
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/b2b/negotiable-manage
+status: migrated
---
This topic describes the calls required to initiate a negotiable quote and to prepare it to be converted to an order.
diff --git a/src/guides/v2.4/b2b/negotiable-order-workflow.md b/src/guides/v2.4/b2b/negotiable-order-workflow.md
index d259a37b7ec..d6e6ffb0e57 100644
--- a/src/guides/v2.4/b2b/negotiable-order-workflow.md
+++ b/src/guides/v2.4/b2b/negotiable-order-workflow.md
@@ -2,8 +2,8 @@
group: b2b-developer-guide
title: Place a negotiable quote order
ee_only: true
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/b2b/negotiable-order-workflow
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/b2b/negotiable-order-workflow
+status: migrated
---
This topic describes how REST calls can be used to place items in a shopping cart, initiate and complete the process of negotiating a quote, and reimbursing the buyer's credit upon receipt of payment.
diff --git a/src/guides/v2.4/b2b/negotiable-quote.md b/src/guides/v2.4/b2b/negotiable-quote.md
index 820181da91f..40775cd9709 100644
--- a/src/guides/v2.4/b2b/negotiable-quote.md
+++ b/src/guides/v2.4/b2b/negotiable-quote.md
@@ -10,8 +10,8 @@ level3_subgroup: nq
functional_areas:
- B2B
- Integration
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/b2b/negotiable-quote
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/b2b/negotiable-quote
+status: migrated
---
Negotiable quotes are a mechanism that allows a company user (buyer) and a seller (admin user) to negotiate product and/or shipping prices before the company user places an order. Its functionality is available for companies only.
diff --git a/src/guides/v2.4/b2b/negotiable-update.md b/src/guides/v2.4/b2b/negotiable-update.md
index a9589e93c3d..c459a297da0 100644
--- a/src/guides/v2.4/b2b/negotiable-update.md
+++ b/src/guides/v2.4/b2b/negotiable-update.md
@@ -5,8 +5,8 @@ ee_only: true
functional_areas:
- B2B
- Integration
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/b2b/negotiable-update
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/b2b/negotiable-update
+status: migrated
---
Sellers and buyers can edit a negotiable quote at various times during the quote's lifecycle. Both use the `PUT /V1/negotiableQuote/:quoteId` call to update the quote. This call is defined in the
diff --git a/src/guides/v2.4/b2b/roles.md b/src/guides/v2.4/b2b/roles.md
index 59627354eb4..3d6ba1d0c2f 100644
--- a/src/guides/v2.4/b2b/roles.md
+++ b/src/guides/v2.4/b2b/roles.md
@@ -5,8 +5,8 @@ menu_title: Manage company roles
ee_only: True
functional_areas:
- B2B
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/b2b/roles
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/b2b/roles
+status: migrated
---
Within a company, customers may have different job roles, levels of responsibility, and access to information about their company. {{site.data.var.b2b}} defines several types of system resources, and the Company Admin (or an integration that operates on the behalf of the Company Admin) grants or denies access to these resources using company roles. The Company Admin has access to all resources.
diff --git a/src/guides/v2.4/b2b/shared-cat-company.md b/src/guides/v2.4/b2b/shared-cat-company.md
index 7f2c35b3610..db45fd872c2 100644
--- a/src/guides/v2.4/b2b/shared-cat-company.md
+++ b/src/guides/v2.4/b2b/shared-cat-company.md
@@ -6,8 +6,8 @@ functional_areas:
- B2B
- Catalog
- Integration
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/b2b/shared-cat-company
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/b2b/shared-cat-company
+status: migrated
---
A shared catalog must be assigned to one or more companies before it can be accessed by the company users.
diff --git a/src/guides/v2.4/b2b/shared-cat-manage.md b/src/guides/v2.4/b2b/shared-cat-manage.md
index 8da9c146d43..a5b1db84c80 100644
--- a/src/guides/v2.4/b2b/shared-cat-manage.md
+++ b/src/guides/v2.4/b2b/shared-cat-manage.md
@@ -6,8 +6,8 @@ functional_areas:
- B2B
- Catalog
- Integration
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/b2b/shared-cat-manage
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/b2b/shared-cat-manage
+status: migrated
---
## Manage custom shared catalogs
diff --git a/src/guides/v2.4/b2b/shared-cat-product-assign.md b/src/guides/v2.4/b2b/shared-cat-product-assign.md
index 25061a60aac..502398b0506 100644
--- a/src/guides/v2.4/b2b/shared-cat-product-assign.md
+++ b/src/guides/v2.4/b2b/shared-cat-product-assign.md
@@ -6,8 +6,8 @@ functional_areas:
- B2B
- Catalog
- Integration
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/b2b/shared-cat-product-assign
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/b2b/shared-cat-product-assign
+status: migrated
---
The shared catalog configuration process includes assigning categories and products to the shared catalog. To assign these items to a shared catalog, the following conditions must be met:
diff --git a/src/guides/v2.4/b2b/shared-catalog.md b/src/guides/v2.4/b2b/shared-catalog.md
index 608fc0551cc..d276271ab17 100644
--- a/src/guides/v2.4/b2b/shared-catalog.md
+++ b/src/guides/v2.4/b2b/shared-catalog.md
@@ -11,8 +11,8 @@ functional_areas:
- B2B
- Catalog
- Integration
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/b2b/shared-catalog
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/b2b/shared-catalog
+status: migrated
---
A shared catalog is an entity that allows a seller to set special rules for the products that company users (buyers) can purchase. By using shared catalogs, a seller can apply different pricing levels for different companies. Also, shared catalogs allow a seller to configure the visibility of categories and products specifically for different companies.
diff --git a/src/guides/v2.4/bk-get-started-magento.md b/src/guides/v2.4/bk-get-started-magento.md
deleted file mode 120000
index fc226b2f75e..00000000000
--- a/src/guides/v2.4/bk-get-started-magento.md
+++ /dev/null
@@ -1 +0,0 @@
-../v2.3/bk-get-started-magento.md
\ No newline at end of file
diff --git a/src/guides/v2.4/bk-get-started-magento.md b/src/guides/v2.4/bk-get-started-magento.md
new file mode 100644
index 00000000000..61c818e3d3e
--- /dev/null
+++ b/src/guides/v2.4/bk-get-started-magento.md
@@ -0,0 +1,38 @@
+---
+group: web-api
+title: Getting started with Magento
+menu_title: Getting started with Magento
+menu_order: 1
+menu_node:
+functional_areas:
+ - Integration
+redirect_to: https://developer.adobe.com/commerce/docs
+status: migrated
+---
+
+## Getting started with Magento {#highlights}
+
+Welcome to Magento 2.0 documentation! And welcome to Magento 2.0!
+
+Here we explain the Magento platform and components from the perspective of several audiences: merchants, web store developers (frontend developers), [extension](https://glossary.magento.com/extension) developers, system administrators, installers, and integrators.
+
+Magento is a highly-customizable eCommerce platform and content management system that is primarily used to build online storefronts or websites for selling merchandise.
+
+Magento is written using the [PHP](https://glossary.magento.com/php) programming language, and leverages elements of the Zend framework and the model-view-controller architecture. Magento runs on the MySQL relational database, and Magento schema and tables are included in the Magento installation package.
+
+## Help improve this documentation {#help}
+
+Magento 2.0 product documentation is hosted on GitHub, and we welcome your
+feedback there.
+
+Click the **Edit this page on GitHub** link at the top of a documentation page to
+open the file in our GitHub repository, where you are invited to suggest changes
+by creating pull requests, or open a discussion by creating an issue.
+
+For more information, see our [Contributors Guide](https://github.com/magento/devdocs/blob/master/.github/CONTRIBUTING.md).
+
+{:.ref-header}
+Related topics
+
+* [Release Notes]({{ page.baseurl }}/release-notes/bk-release-notes.html)
+* [Architecture Guide]({{ page.baseurl }}/architecture/bk-architecture.html)
diff --git a/src/guides/v2.4/coding-standards/bk-coding-standards.md b/src/guides/v2.4/coding-standards/bk-coding-standards.md
index deb6a7c26a4..73370ce17a6 100644
--- a/src/guides/v2.4/coding-standards/bk-coding-standards.md
+++ b/src/guides/v2.4/coding-standards/bk-coding-standards.md
@@ -8,8 +8,8 @@ menu_order: 1
menu_node: parent
functional_areas:
- Standards
-migrated_to: https://developer.adobe.com/commerce/php/coding-standards/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/coding-standards/
+status: migrated
---
diff --git a/src/guides/v2.4/coding-standards/code-standard-demarcation.md b/src/guides/v2.4/coding-standards/code-standard-demarcation.md
index b4063afe2ab..55377085871 100644
--- a/src/guides/v2.4/coding-standards/code-standard-demarcation.md
+++ b/src/guides/v2.4/coding-standards/code-standard-demarcation.md
@@ -7,8 +7,8 @@ menu_title: Code demarcation standard
menu_order: 1
functional_areas:
- Standards
-migrated_to: https://developer.adobe.com/commerce/php/coding-standards/code-demarcation/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/coding-standards/code-demarcation/
+status: migrated
---
Magento core developers must follow the Magento code demarcation standard.
diff --git a/src/guides/v2.4/coding-standards/code-standard-html.md b/src/guides/v2.4/coding-standards/code-standard-html.md
index b365851d0ee..f31f5516aba 100644
--- a/src/guides/v2.4/coding-standards/code-standard-html.md
+++ b/src/guides/v2.4/coding-standards/code-standard-html.md
@@ -7,8 +7,8 @@ menu_title: HTML style guide
menu_order: 9
functional_areas:
- Standards
-migrated_to: https://developer.adobe.com/commerce/php/coding-standards/html-style-guide/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/coding-standards/html-style-guide/
+status: migrated
---
This style guide defines Magento internal requirements for [HTML](https://glossary.magento.com/html) code style for teams that develop Less and [CSS](https://glossary.magento.com/css) code. We recommend that developers who create extensions and customizations also use these standards.
diff --git a/src/guides/v2.4/coding-standards/code-standard-javascript.md b/src/guides/v2.4/coding-standards/code-standard-javascript.md
index 32893623af1..db846e56ab8 100644
--- a/src/guides/v2.4/coding-standards/code-standard-javascript.md
+++ b/src/guides/v2.4/coding-standards/code-standard-javascript.md
@@ -4,8 +4,8 @@ title: JavaScript coding standard
landing-page: Coding standards
functional_areas:
- Standards
-migrated_to: https://developer.adobe.com/commerce/php/coding-standards/js/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/coding-standards/js/
+status: migrated
---
Use Magento's [ESLint Rules][eslint-rules] to make sure your code adheres to Magento's coding standards.
diff --git a/src/guides/v2.4/coding-standards/code-standard-jquery-widgets.md b/src/guides/v2.4/coding-standards/code-standard-jquery-widgets.md
index b1356567b63..6251a40ecdb 100644
--- a/src/guides/v2.4/coding-standards/code-standard-jquery-widgets.md
+++ b/src/guides/v2.4/coding-standards/code-standard-jquery-widgets.md
@@ -7,8 +7,8 @@ menu_title: jQuery widget coding standard
menu_order: 7
functional_areas:
- Standards
-migrated_to: https://developer.adobe.com/commerce/php/coding-standards/jquery-widgets/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/coding-standards/jquery-widgets/
+status: migrated
---
In the Magento system, all jQuery UI widgets and interactions are built on a simple, reusable base---the [jQuery UI Widget Factory][jquery-ui-widget-factory].
diff --git a/src/guides/v2.4/coding-standards/code-standard-less.md b/src/guides/v2.4/coding-standards/code-standard-less.md
index 444abf23e73..a747e323a55 100644
--- a/src/guides/v2.4/coding-standards/code-standard-less.md
+++ b/src/guides/v2.4/coding-standards/code-standard-less.md
@@ -7,8 +7,8 @@ menu_title: Less coding standard
menu_order: 8
functional_areas:
- Standards
-migrated_to: https://developer.adobe.com/commerce/php/coding-standards/less/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/coding-standards/less/
+status: migrated
---
This standard defines Magento internal requirements for code formatting and style for teams that develop Less and [CSS](https://glossary.magento.com/css) code.
diff --git a/src/guides/v2.4/coding-standards/code-standard-php.md b/src/guides/v2.4/coding-standards/code-standard-php.md
index 158c5678285..8793480bf2a 100644
--- a/src/guides/v2.4/coding-standards/code-standard-php.md
+++ b/src/guides/v2.4/coding-standards/code-standard-php.md
@@ -7,8 +7,8 @@ menu_title: PHP coding standard
menu_order: 2
functional_areas:
- Standards
-migrated_to: https://developer.adobe.com/commerce/php/coding-standards/php/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/coding-standards/php/
+status: migrated
---
The Magento core development team uses the [Magento Coding Standard](https://github.com/magento/magento-coding-standard). We recommend that developers who create extensions and customizations also use this standard.
diff --git a/src/guides/v2.4/coding-standards/contributing.md b/src/guides/v2.4/coding-standards/contributing.md
index e412d28bd5d..085f714ac5b 100644
--- a/src/guides/v2.4/coding-standards/contributing.md
+++ b/src/guides/v2.4/coding-standards/contributing.md
@@ -7,8 +7,8 @@ menu_title: Contributing
menu_order: 10
functional_areas:
- Standards
-migrated_to: https://developer.adobe.com/commerce/php/coding-standards/contributing/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/coding-standards/contributing/
+status: migrated
---
Like many large projects, Magento has coding standards.
diff --git a/src/guides/v2.4/coding-standards/docblock-standard-general.md b/src/guides/v2.4/coding-standards/docblock-standard-general.md
index 073b8d10963..996a0cb373a 100644
--- a/src/guides/v2.4/coding-standards/docblock-standard-general.md
+++ b/src/guides/v2.4/coding-standards/docblock-standard-general.md
@@ -4,8 +4,8 @@ subgroup: 01_Coding standards
title: DocBlock standard
functional_areas:
- Standards
-migrated_to: https://developer.adobe.com/commerce/php/coding-standards/docblock/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/coding-standards/docblock/
+status: migrated
---
This standard defines Magento requirements and conventions for adding inline code documentation, known as *DocBlock*s.
diff --git a/src/guides/v2.4/coding-standards/docblock-standard-javascript.md b/src/guides/v2.4/coding-standards/docblock-standard-javascript.md
index 73b6eaf4d2d..94ba5acc3f6 100644
--- a/src/guides/v2.4/coding-standards/docblock-standard-javascript.md
+++ b/src/guides/v2.4/coding-standards/docblock-standard-javascript.md
@@ -7,8 +7,8 @@ menu_title: JavaScript DocBlock standard
menu_order: 6
functional_areas:
- Standards
-migrated_to: https://developer.adobe.com/commerce/php/coding-standards/js/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/coding-standards/js/
+status: migrated
---
## Introduction {#frontend-dev-guide-javascript-js-coding-docblock-overview}
diff --git a/src/guides/v2.4/coding-standards/technical-guidelines.md b/src/guides/v2.4/coding-standards/technical-guidelines.md
index cda367a9bb0..33ddf701fc2 100644
--- a/src/guides/v2.4/coding-standards/technical-guidelines.md
+++ b/src/guides/v2.4/coding-standards/technical-guidelines.md
@@ -3,8 +3,8 @@ group: coding-standards
functional_areas:
- Standards
title: Technical Guidelines
-migrated_to: https://developer.adobe.com/commerce/php/coding-standards/technical-guidelines/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/coding-standards/technical-guidelines/
+status: migrated
---
## About this document
diff --git a/src/guides/v2.4/coding-standards/technical-vision/index.md b/src/guides/v2.4/coding-standards/technical-vision/index.md
index e82c922d474..a45e78cbd39 100644
--- a/src/guides/v2.4/coding-standards/technical-vision/index.md
+++ b/src/guides/v2.4/coding-standards/technical-vision/index.md
@@ -1,8 +1,8 @@
---
group: coding-standards
title: Magento technical vision
-migrated_to: https://developer.adobe.com/commerce/php/architecture/technical-vision/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/architecture/technical-vision/
+status: migrated
---
The Magento technical vision is a collection of documents that describe the desired state of the Magento platform.
diff --git a/src/guides/v2.4/coding-standards/technical-vision/webapi.md b/src/guides/v2.4/coding-standards/technical-vision/webapi.md
index 73efbd21430..87222985929 100644
--- a/src/guides/v2.4/coding-standards/technical-vision/webapi.md
+++ b/src/guides/v2.4/coding-standards/technical-vision/webapi.md
@@ -1,8 +1,8 @@
---
group: coding-standards
title: Web API technical vision
-migrated_to: https://developer.adobe.com/commerce/php/architecture/technical-vision/web-api/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/architecture/technical-vision/web-api/
+status: migrated
---
Web API is crucial for Magento because of the need to integrate with order management, customer management, and other enterprise management software systems.
diff --git a/src/guides/v2.4/comp-mgr/bk-compman-upgrade-guide.md b/src/guides/v2.4/comp-mgr/bk-compman-upgrade-guide.md
index 7b230d405d5..ec5a4346402 100644
--- a/src/guides/v2.4/comp-mgr/bk-compman-upgrade-guide.md
+++ b/src/guides/v2.4/comp-mgr/bk-compman-upgrade-guide.md
@@ -3,8 +3,8 @@ group: software-update-guide
title: Commerce upgrade overview
functional_areas:
- Upgrade
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/upgrade-guide/overview.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/upgrade-guide/overview.html
+status: migrated
---
+
+
+
+
+
+ ...
+ ```
+
+### Run all tests in a API functional test suite
+
+**Syntax:**
+
+```bash
+vendor/bin/phpunit -c dev/tests/api-functional/phpunit_graphql.xml dev/tests/api-functional/testsuite///.php
+```
+
+**Example:**
+
+To run all tests from [dev/tests/api-functional/testsuite/Magento/GraphQl/Customer/GenerateCustomerTokenTest.php]({{ site.mage2bloburl }}/2.3.1/dev/tests/api-functional/testsuite/Magento/GraphQl/Customer/GenerateCustomerTokenTest.php), run the following command:
+
+```bash
+vendor/bin/phpunit -c dev/tests/api-functional/phpunit_graphql.xml dev/tests/api-functional/testsuite/Magento/GraphQl/Customer/GenerateCustomerTokenTest.php
+```
+
+### Run a single test in a API functional test suite
+
+**Syntax:**
+
+```bash
+vendor/bin/phpunit -c dev/tests/api-functional/phpunit_graphql.xml --filter dev/tests/api-functional/testsuite///.php
+```
+
+**Example:**
+
+To run `testGenerateCustomerValidToken` test from [dev/tests/api-functional/testsuite/Magento/GraphQl/Customer/GenerateCustomerTokenTest.php]({{ site.mage2bloburl }}/2.3.1/dev/tests/api-functional/testsuite/Magento/GraphQl/Customer/GenerateCustomerTokenTest.php), run the following command:
+
+```bash
+vendor/bin/phpunit -c dev/tests/api-functional/phpunit_graphql.xml --filter testGenerateCustomerValidToken dev/tests/api-functional/testsuite/Magento/GraphQl/Customer/GenerateCustomerTokenTest.php
+```
+
+### Run a selected group of tests in an API functional test suite
+
+Use the `@group` directive in the test annotation to add the ability to run a group tests.
+
+**Syntax:**
+
+```bash
+vendor/bin/phpunit -c dev/tests/api-functional/phpunit_graphql.xml --group dev/tests/api-functional/testsuite///.php
+```
+
+**Example:**
+
+The `testGetCartTotalsWithNoAddressSet` test is marked with `@group recent`:
+
+```php
+ Settings > **Sales** > **Sales** > **Reorder** > **Allow Reorder** field must be set to **Yes** to enable reorders. You must provide a customer authorization token with the call.
diff --git a/src/guides/v2.4/graphql/mutations/request-negotiable-quote.md b/src/guides/v2.4/graphql/mutations/request-negotiable-quote.md
index 6552f445b1e..690ea0ed942 100644
--- a/src/guides/v2.4/graphql/mutations/request-negotiable-quote.md
+++ b/src/guides/v2.4/graphql/mutations/request-negotiable-quote.md
@@ -2,6 +2,8 @@
group: graphql
title: requestNegotiableQuote mutation
b2b_only: true
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/b2b/negotiable-quote/mutations/request/
+status: migrated
---
The `requestNegotiableQuote` mutation initiates a negotiable quote on behalf of a company user. The company user must add all products to the cart before requesting a negotiable quote. Once the request is submitted, company users cannot add new products to the quote.
diff --git a/src/guides/v2.4/graphql/mutations/request-password-reset-email.md b/src/guides/v2.4/graphql/mutations/request-password-reset-email.md
index 67af3eb88d4..02f47d968de 100644
--- a/src/guides/v2.4/graphql/mutations/request-password-reset-email.md
+++ b/src/guides/v2.4/graphql/mutations/request-password-reset-email.md
@@ -3,6 +3,8 @@ group: graphql
title: requestPasswordResetEmail mutation
contributor_name: Atwix
contributor_link: https://www.atwix.com/
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/customer/mutations/request-password-reset-email/
+status: migrated
---
The `requestPasswordResetEmail` mutation triggers the password reset email by the provided email address. Use it to initiate the process to reset the registered customer's password before calling the [resetPassword]({{page.baseurl}}/graphql/mutations/reset-password.html) mutation.
@@ -14,7 +16,7 @@ When the customer clicks the `Set a New Password` button, Magento sends an email
The URL has the following format:
```text
-https:///customer/account/createPassword/?token=gh80pkjGdsPyiXc0sUUXswX1uGN7crUr
+https:///customer/account/createPassword/?token=gh80pkjGdsPyiXc0sUUXswX1uGN7crUr #gitleaks:allow
```
Use the value of the token in the `resetPassword` mutation.
diff --git a/src/guides/v2.4/graphql/mutations/request-return.md b/src/guides/v2.4/graphql/mutations/request-return.md
index 8a45fa251b5..46d9700a7d8 100644
--- a/src/guides/v2.4/graphql/mutations/request-return.md
+++ b/src/guides/v2.4/graphql/mutations/request-return.md
@@ -2,6 +2,8 @@
group: graphql
title: requestReturn mutation
ee_only: true
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/orders/mutations/request-return/
+status: migrated
---
The `requestReturn` mutation initiates a buyer's request to return an item for replacement or refund. The merchant subsequently decides whether to accept or reject the request.
diff --git a/src/guides/v2.4/graphql/mutations/reset-password.md b/src/guides/v2.4/graphql/mutations/reset-password.md
index b3d6c693407..3f2116c0ca7 100644
--- a/src/guides/v2.4/graphql/mutations/reset-password.md
+++ b/src/guides/v2.4/graphql/mutations/reset-password.md
@@ -3,6 +3,8 @@ group: graphql
title: resetPassword mutation
contributor_name: Atwix
contributor_link: https://www.atwix.com/
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/customer/mutations/reset-password/
+status: migrated
---
The `resetPassword` mutation resets customer password using a reset password token and the customer's email address. Use it to set a new password for the registered customer after calling the [requestPasswordResetEmail]({{page.baseurl}}/graphql/mutations/request-password-reset-email.html) mutation.
@@ -21,7 +23,7 @@ The following call sets a new customer password.
mutation {
resetPassword(
email: "roni_cost@example.com",
- resetPasswordToken: "gh80pkjGdsPyiXc0sUUXswX1uGN7crUr",
+ resetPasswordToken: "gh80pkjGdsPyiXc0sUUXswX1uGN7crUr", #gitleaks:allow
newPassword: "new_password"
)
}
diff --git a/src/guides/v2.4/graphql/mutations/revoke-customer-token.md b/src/guides/v2.4/graphql/mutations/revoke-customer-token.md
index 92da45ead05..13a47b605d1 100644
--- a/src/guides/v2.4/graphql/mutations/revoke-customer-token.md
+++ b/src/guides/v2.4/graphql/mutations/revoke-customer-token.md
@@ -1,6 +1,8 @@
---
group: graphql
title: revokeCustomerToken mutation
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/customer/mutations/revoke-token/
+status: migrated
---
Use the `revokeCustomerToken` mutation to revokes the customer's token.
diff --git a/src/guides/v2.4/graphql/mutations/send-email-to-friend.md b/src/guides/v2.4/graphql/mutations/send-email-to-friend.md
deleted file mode 120000
index 9994c9aafac..00000000000
--- a/src/guides/v2.4/graphql/mutations/send-email-to-friend.md
+++ /dev/null
@@ -1 +0,0 @@
-../../../v2.3/graphql/mutations/send-email-to-friend.md
\ No newline at end of file
diff --git a/src/guides/v2.4/graphql/mutations/send-email-to-friend.md b/src/guides/v2.4/graphql/mutations/send-email-to-friend.md
new file mode 100644
index 00000000000..f2796c80729
--- /dev/null
+++ b/src/guides/v2.4/graphql/mutations/send-email-to-friend.md
@@ -0,0 +1,155 @@
+---
+group: graphql
+title: sendEmailToFriend mutation
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/customer/mutations/send-email-to-friend/
+status: migrated
+---
+
+Use the `sendEmailToFriend` mutation to allow Magento to send a message on behalf of a customer to the specified email addresses.
+
+{:.bs-callout-info}
+The **Stores** > **Configuration** > **Catalog** > **Email to a friend** > **Enabled** field must be set to **Yes** to implement this mutation.
+
+## Syntax
+
+```graphql
+mutation {
+ sendEmailToFriend(
+ input: SendEmailToFriendInput
+ ) {
+ SendEmailToFriendOutput
+ }
+}
+```
+
+## Example usage
+
+The following example sends a message to two friends.
+
+**Request:**
+
+```graphql
+mutation {
+ sendEmailToFriend(
+ input: {
+ product_id: 10
+ sender: {
+ name: "Veronica Cost"
+ email: "roni_cost@example.com"
+ message: "Sarah needs this! http://luma.example.com/savvy-shoulder-tote.html"
+ }
+ recipients: [
+ { name: "Amie Franklin", email: "afranklin@example.com" }
+ { name: "Tomoko", email: "tomoko@example.com" }
+ ]
+ }
+ ) {
+ sender {
+ name
+ email
+ }
+ recipients {
+ name
+ email
+ }
+ }
+}
+```
+
+**Response:**
+
+```json
+{
+ "data": {
+ "sendEmailToFriend": {
+ "sender": {
+ "name": "Veronica Cost",
+ "email": "roni_cost@example.com",
+ },
+ "recipients": [
+ {
+ "name": "Amie Franklin",
+ "email": "afranklin@example.com"
+ },
+ {
+ "name": "Tomoko",
+ "email": "tomoko@example.com"
+ }
+ ]
+ }
+ }
+}
+```
+
+## Input attributes
+
+The `SendEmailToFriendInput` object contains the following attributes:
+
+Attribute | Data Type | Description
+--- | --- | ---
+`product_id` | Int! | The ID of the product that the customer is referencing
+`recipients` | [SendEmailToFriendRecipientInput]! | An array containing information about each recipient
+`sender` | SendEmailToFriendSenderInput! | Information about the customer and the content of the message
+
+### SendEmailToFriendRecipientInput object {#SendEmailToFriendRecipientInput}
+
+The `SendEmailToFriendRecipientInput` object must contain the following attributes:
+
+Attribute | Data Type | Description
+--- | --- | ---
+`email` | String! | The email address of the recipient
+`name` | String! | The name of the recipient
+
+### SendEmailToFriendSenderInput object {#SendEmailToFriendSenderInput}
+
+The `SendEmailToFriendSenderInput` object must contain the following attributes:
+
+Attribute | Data Type | Description
+--- | --- | ---
+`email` | String! | The email address of the sender
+`message` | String! | The text of the message to be sent
+`name` | String! | The name of the sender
+
+## Output attributes
+
+The `SendEmailToFriendOutput` object contains the following attributes:
+
+Attribute | Data Type | Description
+--- | --- | ---
+`recipients` | [SendEmailToFriendRecipient] | An array containing information about each recipient
+`sender` | SendEmailToFriendSender | Information about the customer and the content of the message
+
+### SendEmailToFriendRecipient object
+
+The `SendEmailToFriendRecipientInput` object can contain the following attributes:
+
+Attribute | Data Type | Description
+--- | --- | ---
+`email` | String | The email address of the recipient
+`name` | String | The name of the recipient
+
+### SendEmailToFriendSender object
+
+The `SendEmailToFriendSender` object can contain the following attributes:
+
+Attribute | Data Type | Description
+--- | --- | ---
+`email` | String | The email address of the sender
+`message` | String | The text of the message
+`name` | String | The name of the sender
+
+## Errors
+
+Some errors occur because the **Email a friend** feature is not properly configured. Go to **Stores** > **Configuration** > **Catalog** > **Email to a friend** in the Admin to adjust the settings.
+
+Error | Description
+--- | ---
+`"Email to a Friend" is not enabled.` | "Email to a Friend" is disabled. To activate it, use the Admin to set the **Enabled** field to **Yes**.
+`Please provide Name of sender.` | The value specified in the `input`.`sender`.`name` argument is empty.
+`Please provide Email of sender.` | The value specified in the `input`.`sender`.`email` argument is empty.
+`Please provide Message.` | The value specified in the `input`.`sender`.`message` argument is empty.
+`Please provide Name for all of recipients.` | The value specified in the `input`.`recipients`[].`name` argument is empty.
+`Please provide Email for all of recipients.` | The value specified in the `input`.`recipients`[].`email` argument is empty.
+`The current customer isn't authorized.` | "Email to a Friend" is available for registered users only. To make it available for guests, use the Admin to set the **Allow for Guests** option to **Yes**.
+`The product that was requested doesn't exist. Verify the product and try again.` | The product specified in the `product_id` argument is not visible in the current website.
+`You can't send messages more than XXX times an hour.` | The user cannot send more messages in an hour than specified in the **Max Products Sent in 1 Hour** option in the Admin.
diff --git a/src/guides/v2.4/graphql/mutations/send-negotiable-quote-for-review.md b/src/guides/v2.4/graphql/mutations/send-negotiable-quote-for-review.md
index eaac73b8934..1a5f336c2e9 100644
--- a/src/guides/v2.4/graphql/mutations/send-negotiable-quote-for-review.md
+++ b/src/guides/v2.4/graphql/mutations/send-negotiable-quote-for-review.md
@@ -2,6 +2,8 @@
group: graphql
title: sendNegotiableQuoteForReview mutation
b2b_only: true
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/b2b/negotiable-quote/mutations/send-for-review/
+status: migrated
---
The `sendNegotiableQuoteForReview` mutation sends the negotiable quote to the seller for review. If the mutation is successful, the buyer cannot modify the quote until the merchant accepts the request.
diff --git a/src/guides/v2.4/graphql/mutations/set-billing-address.md b/src/guides/v2.4/graphql/mutations/set-billing-address.md
index 03ef0bb87ce..9b992c1a535 100644
--- a/src/guides/v2.4/graphql/mutations/set-billing-address.md
+++ b/src/guides/v2.4/graphql/mutations/set-billing-address.md
@@ -1,6 +1,8 @@
---
group: graphql
title: setBillingAddressOnCart mutation
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/cart/mutations/set-billing-address/
+status: migrated
---
The `setBillingAddressOnCart` mutation sets the billing address for a specific cart. If you set the `same_as_shipping` attribute to `true`, Magento assigns the billing address to be the same as the shipping address.
diff --git a/src/guides/v2.4/graphql/mutations/set-gift-options.md b/src/guides/v2.4/graphql/mutations/set-gift-options.md
index 75028af855c..26cbc93fa0b 100644
--- a/src/guides/v2.4/graphql/mutations/set-gift-options.md
+++ b/src/guides/v2.4/graphql/mutations/set-gift-options.md
@@ -2,6 +2,8 @@
group: graphql
title: setGiftOptionsOnCart mutation
ee_only: true
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/cart/mutations/set-gift-options/
+status: migrated
---
The `setGiftOptionsOnCart` mutation allows the buyer to set the following gift options on the cart level:
diff --git a/src/guides/v2.4/graphql/mutations/set-guest-email.md b/src/guides/v2.4/graphql/mutations/set-guest-email.md
index d2b17dac1e8..d4855b3d74b 100644
--- a/src/guides/v2.4/graphql/mutations/set-guest-email.md
+++ b/src/guides/v2.4/graphql/mutations/set-guest-email.md
@@ -3,6 +3,8 @@ group: graphql
title: setGuestEmailOnCart mutation
redirect from:
- /guides/v2.3/graphql/reference/quote-set-guest-email.html
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/cart/mutations/set-guest-email/
+status: migrated
---
For guest customers, you must assign an email to the cart before you place the order.
@@ -52,7 +54,7 @@ The `SetGuestEmailOnCartInput` object must contain the following attributes.
Attribute | Data Type | Description
--- | --- | ---
-`cart_id` | String! | The unique ID that identifies the customer’s cart
+`cart_id` | String! | The unique ID that identifies the customer's cart
`email` | String! | The guest user's email
## Output attributes
diff --git a/src/guides/v2.4/graphql/mutations/set-negotiable-quote-billing-address.md b/src/guides/v2.4/graphql/mutations/set-negotiable-quote-billing-address.md
index 845b4f3a6b1..569a4a8c9d3 100644
--- a/src/guides/v2.4/graphql/mutations/set-negotiable-quote-billing-address.md
+++ b/src/guides/v2.4/graphql/mutations/set-negotiable-quote-billing-address.md
@@ -2,6 +2,8 @@
group: graphql
title: setNegotiableQuoteBillingAddress mutation
b2b_only: true
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/b2b/negotiable-quote/mutations/set-billing-address/
+status: migrated
---
The `setNegotiableQuoteBillingAddress` mutation assigns the billing address for the specified negotiable quote. You can assign an address from the company user's address book, or define a new one. The negotiable quote must be in the UPDATED state to successfully set the billing address.
diff --git a/src/guides/v2.4/graphql/mutations/set-negotiable-quote-payment-method.md b/src/guides/v2.4/graphql/mutations/set-negotiable-quote-payment-method.md
index 972a887337e..cf0a59ba07f 100644
--- a/src/guides/v2.4/graphql/mutations/set-negotiable-quote-payment-method.md
+++ b/src/guides/v2.4/graphql/mutations/set-negotiable-quote-payment-method.md
@@ -2,6 +2,8 @@
group: graphql
title: setNegotiableQuotePaymentMethod mutation
b2b_only: true
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/b2b/negotiable-quote/mutations/set-payment-method/
+status: migrated
---
The `setNegotiableQuotePaymentMethod` mutation defines which payment method to apply to the cart. The negotiable quote must be in the UPDATED state to successfully apply the payment method.
diff --git a/src/guides/v2.4/graphql/mutations/set-negotiable-quote-shipping-address.md b/src/guides/v2.4/graphql/mutations/set-negotiable-quote-shipping-address.md
index 90e9abac931..60619190376 100644
--- a/src/guides/v2.4/graphql/mutations/set-negotiable-quote-shipping-address.md
+++ b/src/guides/v2.4/graphql/mutations/set-negotiable-quote-shipping-address.md
@@ -2,6 +2,8 @@
group: graphql
title: setNegotiableQuoteShippingAddress mutation
b2b_only: true
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/b2b/negotiable-quote/mutations/set-shipping-address/
+status: migrated
---
The `setNegotiableQuoteShippingAddress` mutation assigns the shipping address for the specified negotiable quote. You can assign an address from the company user's address book, or define a new one. The negotiable quote must be in the UPDATED state to successfully set a shipping address.
diff --git a/src/guides/v2.4/graphql/mutations/set-negotiable-quote-shipping-methods.md b/src/guides/v2.4/graphql/mutations/set-negotiable-quote-shipping-methods.md
index 1cd7fe257c1..903bc025e4e 100644
--- a/src/guides/v2.4/graphql/mutations/set-negotiable-quote-shipping-methods.md
+++ b/src/guides/v2.4/graphql/mutations/set-negotiable-quote-shipping-methods.md
@@ -2,6 +2,8 @@
group: graphql
title: setNegotiableQuoteShippingMethods mutation
b2b_only: true
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/b2b/negotiable-quote/mutations/set-shipping-methods/
+status: migrated
---
The `setNegotiableQuoteShippingMethods` mutation sets one or more delivery methods on a negotiable quote. By default, the following delivery methods are supported:
diff --git a/src/guides/v2.4/graphql/mutations/set-payment-method.md b/src/guides/v2.4/graphql/mutations/set-payment-method.md
index b9864052420..b8f8db8cc38 100644
--- a/src/guides/v2.4/graphql/mutations/set-payment-method.md
+++ b/src/guides/v2.4/graphql/mutations/set-payment-method.md
@@ -1,6 +1,8 @@
---
group: graphql
title: setPaymentMethodOnCart mutation
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/cart/mutations/set-payment-method/
+status: migrated
---
The `setPaymentMethodOnCart` mutation defines which payment method to apply to the cart. Magento GraphQL supports the following offline payment methods:
@@ -82,7 +84,7 @@ The `SetPaymentMethodOnCartInput` object must contain the following attributes:
Attribute | Data Type | Description
--- | --- | ---
-`cart_id` | String! | The unique ID that identifies the customer’s cart
+`cart_id` | String! | The unique ID that identifies the customer's cart
`payment_method` | [PaymentMethodInput!](#PaymentMethodInput) | An object containing the payment method code
### PaymentMethodInput attributes {#PaymentMethodInput}
diff --git a/src/guides/v2.4/graphql/mutations/set-payment-place-order.md b/src/guides/v2.4/graphql/mutations/set-payment-place-order.md
index 44092928d2b..98ba62de374 100644
--- a/src/guides/v2.4/graphql/mutations/set-payment-place-order.md
+++ b/src/guides/v2.4/graphql/mutations/set-payment-place-order.md
@@ -3,6 +3,8 @@ group: graphql
title: setPaymentMethodAndPlaceOrder mutation
contributor_name: Something Digital
contributor_link: https://www.somethingdigital.com/
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/cart/mutations/set-payment-place-order/
+status: migrated
---
{:.bs-callout-warning}
@@ -77,7 +79,7 @@ The `placeOrderInput` object must contain the following attribute:
Attribute | Data Type | Description
--- | --- | ---
-`cart_id` | String! | The unique ID that identifies the customer’s cart
+`cart_id` | String! | The unique ID that identifies the customer's cart
`payment_method` | [PaymentMethodInput!](#PaymentMethodInput) | The payment method data for the cart
### PaymentMethodInput attributes {#PaymentMethodInput}
diff --git a/src/guides/v2.4/graphql/mutations/set-shipping-address.md b/src/guides/v2.4/graphql/mutations/set-shipping-address.md
index 32798fd5525..0f45bbb07e0 100644
--- a/src/guides/v2.4/graphql/mutations/set-shipping-address.md
+++ b/src/guides/v2.4/graphql/mutations/set-shipping-address.md
@@ -1,6 +1,8 @@
---
group: graphql
title: setShippingAddressesOnCart mutation
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/cart/mutations/set-shipping-address/
+status: migrated
---
The `setShippingAddressesOnCart` mutation sets one or more shipping addresses on a specific cart. The shipping address does not need to be specified in the following circumstances:
diff --git a/src/guides/v2.4/graphql/mutations/set-shipping-method.md b/src/guides/v2.4/graphql/mutations/set-shipping-method.md
index 6e29429c8aa..82c2fdbd3aa 100644
--- a/src/guides/v2.4/graphql/mutations/set-shipping-method.md
+++ b/src/guides/v2.4/graphql/mutations/set-shipping-method.md
@@ -1,6 +1,8 @@
---
group: graphql
title: setShippingMethodsOnCart mutation
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/cart/mutations/set-shipping-method/
+status: migrated
---
The `setShippingMethodsOnCart` mutation sets one or more delivery methods on a cart. By default, Magento GraphQL supports the following delivery methods:
diff --git a/src/guides/v2.4/graphql/mutations/share-gift-registry.md b/src/guides/v2.4/graphql/mutations/share-gift-registry.md
index d6f45d92aa2..0d261cd6899 100644
--- a/src/guides/v2.4/graphql/mutations/share-gift-registry.md
+++ b/src/guides/v2.4/graphql/mutations/share-gift-registry.md
@@ -3,6 +3,8 @@ group: graphql
title: shareGiftRegistry mutation
ee_only: true
contributor_name: EY
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/gift-registry/mutations/share/
+status: migrated
---
The `shareGiftRegistry` mutation sends an invitation to a list email addresses to shop from the customer's gift registry.
diff --git a/src/guides/v2.4/graphql/mutations/subscribe-email-to-newsletter.md b/src/guides/v2.4/graphql/mutations/subscribe-email-to-newsletter.md
index d92fc5d8e24..2862255c1d1 100644
--- a/src/guides/v2.4/graphql/mutations/subscribe-email-to-newsletter.md
+++ b/src/guides/v2.4/graphql/mutations/subscribe-email-to-newsletter.md
@@ -3,6 +3,8 @@ group: graphql
title: subscribeEmailToNewsletter mutation
contributor_name: Atwix
contributor_link: https://www.atwix.com/
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/customer/mutations/subscribe-email-to-newsletter/
+status: migrated
---
The `subscribeEmailToNewsletter` mutation allows guests and registered customers to sign up to receive newsletters.
diff --git a/src/guides/v2.4/graphql/mutations/update-cart-items.md b/src/guides/v2.4/graphql/mutations/update-cart-items.md
index 5226d045bea..896d54a73ed 100644
--- a/src/guides/v2.4/graphql/mutations/update-cart-items.md
+++ b/src/guides/v2.4/graphql/mutations/update-cart-items.md
@@ -1,6 +1,8 @@
---
group: graphql
title: updateCartItems mutation
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/cart/mutations/update-items/
+status: migrated
---
The `updateCartItems` mutation allows you to modify items in the specified cart. You can also replace the current quantity of one or more cart items with the specified quantities. The mutation does not perform calculations to determine the quantity of cart items.
diff --git a/src/guides/v2.4/graphql/mutations/update-company-role.md b/src/guides/v2.4/graphql/mutations/update-company-role.md
index 7a53a57a5fe..0ff8ac13a74 100644
--- a/src/guides/v2.4/graphql/mutations/update-company-role.md
+++ b/src/guides/v2.4/graphql/mutations/update-company-role.md
@@ -4,6 +4,8 @@ title: updateCompanyRole mutation
contributor_name: Atwix
contributor_link: https://www.atwix.com/
b2b_only: true
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/b2b/company/mutations/update-role/
+status: migrated
---
Use the `updateCompanyRole` mutation to update the company role and permissions.
diff --git a/src/guides/v2.4/graphql/mutations/update-company-structure.md b/src/guides/v2.4/graphql/mutations/update-company-structure.md
index 2224b530eeb..4fc787d1bbb 100644
--- a/src/guides/v2.4/graphql/mutations/update-company-structure.md
+++ b/src/guides/v2.4/graphql/mutations/update-company-structure.md
@@ -4,6 +4,8 @@ title: updateCompanyStructure mutation
contributor_name: Atwix
contributor_link: https://www.atwix.com/
b2b_only: true
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/b2b/company/mutations/update-structure/
+status: migrated
---
Use the `updateCompanyStructure` mutation to change the parent node of a company team.
diff --git a/src/guides/v2.4/graphql/mutations/update-company-team.md b/src/guides/v2.4/graphql/mutations/update-company-team.md
index e8a6edc4052..74106a9ef16 100644
--- a/src/guides/v2.4/graphql/mutations/update-company-team.md
+++ b/src/guides/v2.4/graphql/mutations/update-company-team.md
@@ -4,6 +4,8 @@ title: updateCompanyTeam mutation
contributor_name: Atwix
contributor_link: https://www.atwix.com/
b2b_only: true
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/b2b/company/mutations/update-team/
+status: migrated
---
Use the `updateCompanyTeam` mutation to update the company team data.
diff --git a/src/guides/v2.4/graphql/mutations/update-company-user.md b/src/guides/v2.4/graphql/mutations/update-company-user.md
index 6b13ee43053..eda27705e28 100644
--- a/src/guides/v2.4/graphql/mutations/update-company-user.md
+++ b/src/guides/v2.4/graphql/mutations/update-company-user.md
@@ -4,6 +4,8 @@ title: updateCompanyUser mutation
contributor_name: Atwix
contributor_link: https://www.atwix.com/
b2b_only: true
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/b2b/company/mutations/update-user/
+status: migrated
---
Use the `updateCompanyUser` mutation to update an existing company user.
diff --git a/src/guides/v2.4/graphql/mutations/update-company.md b/src/guides/v2.4/graphql/mutations/update-company.md
index 16a44a47228..ea583f430ea 100644
--- a/src/guides/v2.4/graphql/mutations/update-company.md
+++ b/src/guides/v2.4/graphql/mutations/update-company.md
@@ -2,6 +2,8 @@
group: graphql
title: updateCompany mutation
b2b_only: true
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/b2b/company/mutations/update/
+status: migrated
---
The `updateCompany` mutation allows you to update a company's address as well as top-level string attributes such as the name, legal name, and email. You cannot update the administrator or other objects such as teams, roles, or resources with this mutation.
diff --git a/src/guides/v2.4/graphql/mutations/update-customer-address.md b/src/guides/v2.4/graphql/mutations/update-customer-address.md
index 8f8c555b730..133df6b7131 100644
--- a/src/guides/v2.4/graphql/mutations/update-customer-address.md
+++ b/src/guides/v2.4/graphql/mutations/update-customer-address.md
@@ -1,6 +1,8 @@
---
group: graphql
title: updateCustomerAddress mutation
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/customer/mutations/update-address/
+status: migrated
---
Use the `updateCustomerAddress` mutation to update the customer's address.
@@ -51,7 +53,7 @@ The `updateCustomerAddress` object contains the following inputs:
Attribute | Data Type | Description
--- | --- | ---
`id` | Int! | The ID assigned to the address object
-`CustomerAddressInput` | [CustomerAddress](#customerAddressInput)| An array containing the customer’s shipping and billing addresses
+`CustomerAddressInput` | [CustomerAddress](#customerAddressInput)| An array containing the customer's shipping and billing addresses
{% include graphql/customer-address-input-24.md %}
diff --git a/src/guides/v2.4/graphql/mutations/update-customer-email.md b/src/guides/v2.4/graphql/mutations/update-customer-email.md
index 4619b4bfd95..eb7a6f91973 100644
--- a/src/guides/v2.4/graphql/mutations/update-customer-email.md
+++ b/src/guides/v2.4/graphql/mutations/update-customer-email.md
@@ -1,6 +1,8 @@
---
group: graphql
title: updateCustomerEmail mutation
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/customer/mutations/update-email/
+status: migrated
---
Use the `updateCustomerEmail` mutation to change the email address for the logged-in customer.
diff --git a/src/guides/v2.4/graphql/mutations/update-customer-v2.md b/src/guides/v2.4/graphql/mutations/update-customer-v2.md
index fee2fc29b1a..6f1d959c13a 100644
--- a/src/guides/v2.4/graphql/mutations/update-customer-v2.md
+++ b/src/guides/v2.4/graphql/mutations/update-customer-v2.md
@@ -1,6 +1,8 @@
---
group: graphql
title: updateCustomerV2 mutation
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/customer/mutations/update-v2/
+status: migrated
---
The `updateCustomerV2` mutation updates the personal information in an existing customer account. Use the [`updateCustomerEmail` mutation]({{page.baseurl}}/graphql/mutations/update-customer-email.html) to update the customer's email address.
@@ -57,17 +59,17 @@ The following table lists the attributes you can use as input for the `updateCus
Attribute | Data Type | Description
--- | --- | ---
`allow_remote_shopping_assistance` | Boolean | Indicates whether the customer has enabled remote shopping assistance
-`date_of_birth` | String | The customer’s date of birth. In keeping with current security and privacy best practices, be sure you are aware of any potential legal and security risks associated with the storage of customers’ full date of birth (month, day, year) along with other personal identifiers, such as full name, before collecting or processing such data.
-`dob` | String | Deprecated. Use `date_of_birth` instead. The customer’s date of birth
-`firstname` | String | The customer’s first name
+`date_of_birth` | String | The customer's date of birth. In keeping with current security and privacy best practices, be sure you are aware of any potential legal and security risks associated with the storage of customers' full date of birth (month, day, year) along with other personal identifiers, such as full name, before collecting or processing such data.
+`dob` | String | Deprecated. Use `date_of_birth` instead. The customer's date of birth
+`firstname` | String | The customer's first name
`gender` | Int | The customer's gender (Male - 1, Female - 2)
`is_subscribed` | Boolean | Indicates whether the customer subscribes to the store's newsletter
-`lastname` | String | The customer’s last name
-`middlename` | String | The customer’s middle name
+`lastname` | String | The customer's last name
+`middlename` | String | The customer's middle name
`password` | String | The customer's password
`prefix` | String | An honorific, such as Dr., Mr., or Mrs.
`suffix` | String | A value such as Sr., Jr., or III
-`taxvat` | String | The customer’s Tax/VAT number (for corporate customers)
+`taxvat` | String | The customer's Tax/VAT number (for corporate customers)
## Output attributes
diff --git a/src/guides/v2.4/graphql/mutations/update-customer.md b/src/guides/v2.4/graphql/mutations/update-customer.md
index 91851e84897..ad31efeb9e7 100644
--- a/src/guides/v2.4/graphql/mutations/update-customer.md
+++ b/src/guides/v2.4/graphql/mutations/update-customer.md
@@ -1,6 +1,8 @@
---
group: graphql
title: updateCustomer mutation
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/customer/mutations/update/
+status: migrated
---
{:.bs-callout-warning}
diff --git a/src/guides/v2.4/graphql/mutations/update-gift-registry-items.md b/src/guides/v2.4/graphql/mutations/update-gift-registry-items.md
index 29ebe2757a0..2f7443fdb97 100644
--- a/src/guides/v2.4/graphql/mutations/update-gift-registry-items.md
+++ b/src/guides/v2.4/graphql/mutations/update-gift-registry-items.md
@@ -2,6 +2,8 @@
group: graphql
title: updateGiftRegistryItems mutation
ee_only: true
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/gift-registry/mutations/update-items/
+status: migrated
---
The `updateGiftRegistryItems` mutation modifies the requested quantity of an item in the specified gift registry. It can also change the description of the item.
diff --git a/src/guides/v2.4/graphql/mutations/update-gift-registry-registrants.md b/src/guides/v2.4/graphql/mutations/update-gift-registry-registrants.md
index c13e2033ce9..cfaf8cce379 100644
--- a/src/guides/v2.4/graphql/mutations/update-gift-registry-registrants.md
+++ b/src/guides/v2.4/graphql/mutations/update-gift-registry-registrants.md
@@ -2,6 +2,8 @@
group: graphql
title: updateGiftRegistryRegistrants mutation
ee_only: true
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/gift-registry/mutations/update-registrants/
+status: migrated
---
The `updateGiftRegistryRegistrants` mutation updates properties of one or more registrants of the specified gify registry.
diff --git a/src/guides/v2.4/graphql/mutations/update-gift-registry.md b/src/guides/v2.4/graphql/mutations/update-gift-registry.md
index 70bd2788cef..831c3dd3559 100644
--- a/src/guides/v2.4/graphql/mutations/update-gift-registry.md
+++ b/src/guides/v2.4/graphql/mutations/update-gift-registry.md
@@ -2,6 +2,8 @@
group: graphql
title: updateGiftRegistry mutation
ee_only: true
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/gift-registry/mutations/update/
+status: migrated
---
The `updateGiftRegistry` mutation modifies properties of specified gift registry. It does not update the items in a gift registry or registrants. Use the `updateGiftRegistryItems` or `updateGiftRegistryRegistrants` mutation to modify gift registry items or registrants.
diff --git a/src/guides/v2.4/graphql/mutations/update-negotiable-quote-quantities.md b/src/guides/v2.4/graphql/mutations/update-negotiable-quote-quantities.md
index 37be9537537..0d02d09a060 100644
--- a/src/guides/v2.4/graphql/mutations/update-negotiable-quote-quantities.md
+++ b/src/guides/v2.4/graphql/mutations/update-negotiable-quote-quantities.md
@@ -2,6 +2,8 @@
group: graphql
title: updateNegotiableQuoteQuantities mutation
b2b_only: true
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/b2b/negotiable-quote/mutations/update-quantities/
+status: migrated
---
The `updateNegotiableQuoteQuantities` mutation changes the quantity of one or more products in an active negotiable quote.
diff --git a/src/guides/v2.4/graphql/mutations/update-products-in-wishlist.md b/src/guides/v2.4/graphql/mutations/update-products-in-wishlist.md
index 44eb8701b39..4acd3884842 100644
--- a/src/guides/v2.4/graphql/mutations/update-products-in-wishlist.md
+++ b/src/guides/v2.4/graphql/mutations/update-products-in-wishlist.md
@@ -1,7 +1,8 @@
---
group: graphql
title: updateProductsInWishlist mutation
-
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/wishlist/mutations/update-products/
+status: migrated
---
The `updateProductsInWishlist` mutation changes the quantity, description and option information for the specified items in the customer's wish list.
diff --git a/src/guides/v2.4/graphql/mutations/update-requisition-list-items.md b/src/guides/v2.4/graphql/mutations/update-requisition-list-items.md
index 5c2efc01367..dfe10ba82e4 100644
--- a/src/guides/v2.4/graphql/mutations/update-requisition-list-items.md
+++ b/src/guides/v2.4/graphql/mutations/update-requisition-list-items.md
@@ -3,6 +3,8 @@ group: graphql
title: updateRequisitionListItems mutation
b2b_only: true
contributor_name: EY
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/b2b/requisition-list/mutations/update-items/
+status: migrated
---
The `updateRequisitionListItems` mutation updates products in a requisition list.
diff --git a/src/guides/v2.4/graphql/mutations/update-requisition-list.md b/src/guides/v2.4/graphql/mutations/update-requisition-list.md
index eb3d9b59bb1..7d44c6a04ad 100644
--- a/src/guides/v2.4/graphql/mutations/update-requisition-list.md
+++ b/src/guides/v2.4/graphql/mutations/update-requisition-list.md
@@ -4,6 +4,8 @@ title: updateRequisitionList mutation
b2b_only: true
contributor_name: Zilker Technology
contributor_link: https://www.ztech.io/
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/b2b/requisition-list/mutations/update/
+status: migrated
---
The `updateRequisitionList` mutation updates the name and, optionally, the description of a requisition list.
diff --git a/src/guides/v2.4/graphql/mutations/update-wishlist.md b/src/guides/v2.4/graphql/mutations/update-wishlist.md
index 5438f4c8af2..61c25aedbde 100644
--- a/src/guides/v2.4/graphql/mutations/update-wishlist.md
+++ b/src/guides/v2.4/graphql/mutations/update-wishlist.md
@@ -2,6 +2,8 @@
group: graphql
title: updateWishlist mutation
ee_only: true
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/wishlist/mutations/update/
+status: migrated
---
The `updateWishlist` mutation updates the properties of a wish list. {{site.data.var.ee}} allows customers to change the name and visibility of wish lists.
diff --git a/src/guides/v2.4/graphql/payment-methods/braintree-vault.md b/src/guides/v2.4/graphql/payment-methods/braintree-vault.md
deleted file mode 120000
index 0a54640157b..00000000000
--- a/src/guides/v2.4/graphql/payment-methods/braintree-vault.md
+++ /dev/null
@@ -1 +0,0 @@
-../../../v2.3/graphql/payment-methods/braintree-vault.md
\ No newline at end of file
diff --git a/src/guides/v2.4/graphql/payment-methods/braintree-vault.md b/src/guides/v2.4/graphql/payment-methods/braintree-vault.md
new file mode 100644
index 00000000000..53a9b022b50
--- /dev/null
+++ b/src/guides/v2.4/graphql/payment-methods/braintree-vault.md
@@ -0,0 +1,93 @@
+---
+group: graphql
+title: Braintree Vault payment method
+contributor_name: Something Digital
+contributor_link: https://www.somethingdigital.com/
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/payment-methods/braintree-vault/
+status: migrated
+---
+
+Braintree Vault is a payment gateway that processes debit and credit card payments from the Magento_Vault.
+
+## Braintree Vault workflow
+
+The following diagram shows the workflow for placing an order when Braintree Vault is the selected payment method.
+
+
+
+1. Use the [`customerPaymentTokens`]({{page.baseurl}}/graphql/queries/customer-payment-tokens.html) query to retrieve
+ the payment tokens the customer has stored in the vault.
+
+1. Magento returns an array of payment tokens.
+
+1. The client renders the token information, and the customer selects a payment method.
+
+ When the customer selects a stored payment method, the PWA uses the [`setPaymentMethodOnCart`]({{page.baseurl}}/graphql/mutations/set-payment-method.html) mutation to set the payment method to [`braintree_cc_vault`](#braintree_cc_vault-object). The vaulted public hash is passed with other optional properties in the `braintree_cc_vault`.
+
+1. Magento returns a `Cart` object.
+
+1. The client runs the [`placeOrder`]({{page.baseurl}}/graphql/mutations/place-order.html) mutation.
+
+1. Magento sends an authorization request to the gateway.
+
+1. The gateway sends the response to Magento.
+
+1. Magento creates an order and sends an order ID in response to the `placeOrder` mutation.
+
+## `setPaymentMethodOnCart` mutation
+
+When you set the payment method to Braintree in the [`setPaymentMethodOnCart`]({{page.baseurl}}/graphql/mutations/set-payment-method.html)
+mutation, the `payment_method` object must contain a [`braintree_cc_vault`](#braintree_cc_vault-object) object.
+
+### braintree_cc_vault object
+
+The `braintree_cc_vault` object must contain the following attributes:
+
+Attribute | Data Type | Description
+--- | --- | ---
+`public_hash` | String! | Required input for Magento_Vault public hash for the selected stored payment method
+`device_data` | String | Optional. JSON-encoded device data for Kount integration
+
+### Example Usage
+
+The following example shows the `setPaymentMethodOnCart` mutation constructed for the Braintree Vault payment method.
+
+**Request:**
+
+```graphql
+mutation {
+ setPaymentMethodOnCart(
+ input: {
+ cart_id: "IeTUiU0oCXjm0uRqGCOuhQ2AuQatogjG"
+ payment_method: {
+ code: "braintree_cc_vault"
+ braintree_cc_vault: { public_hash: "fake-public-hash" }
+ }
+ }
+ ) {
+ cart {
+ selected_payment_method {
+ code
+ title
+ }
+ }
+ }
+}
+```
+
+**Response:**
+
+```json
+{
+ "data": {
+ "setPaymentMethodOnCart": {
+ "cart": {
+ "selected_payment_method": {
+ "code": "braintree_cc_vault"
+ "title": "Stored Cards"
+ }
+ }
+ }
+ }
+}
+```
diff --git a/src/guides/v2.4/graphql/payment-methods/braintree.md b/src/guides/v2.4/graphql/payment-methods/braintree.md
deleted file mode 120000
index 8298a8957ee..00000000000
--- a/src/guides/v2.4/graphql/payment-methods/braintree.md
+++ /dev/null
@@ -1 +0,0 @@
-../../../v2.3/graphql/payment-methods/braintree.md
\ No newline at end of file
diff --git a/src/guides/v2.4/graphql/payment-methods/braintree.md b/src/guides/v2.4/graphql/payment-methods/braintree.md
new file mode 100644
index 00000000000..a20d42a213f
--- /dev/null
+++ b/src/guides/v2.4/graphql/payment-methods/braintree.md
@@ -0,0 +1,102 @@
+---
+group: graphql
+title: Braintree payment method
+contributor_name: Something Digital
+contributor_link: https://www.somethingdigital.com/
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/payment-methods/braintree/
+status: migrated
+---
+
+Braintree is a payment gateway that processes debit and credit card payments.
+
+## Braintree workflow
+
+The following diagram shows the workflow for placing an order when Braintree is the selected payment method.
+
+
+
+1. The PWA client calls the [`createBraintreeClientToken`]({{page.baseurl}}/graphql/mutations/create-braintree-client-token.html) mutation to generate the client token.
+
+1. Magento forwards the request to Braintree.
+
+1. Braintree returns the token to Magento.
+
+1. Magento forwards the token to the client.
+
+1. The PWA client uses the token to initialize the [Braintree hosted fields](https://developers.braintreepayments.com/guides/hosted-fields/overview/javascript/v3). These fields collect and tokenize payment information via a secure iframe. This process occurs over several steps.
+
+ - On the checkout page, the customer selects **Credit Card** as the payment method and enters payment information using the Braintree hosted fields. Then the customer clicks **Place Order**.
+
+ - The client requests the Braintree SDK tokenize the user-input payment information.
+
+1. The Braintree SDK submits the payment information to Braintree client-side and returns a [payment token](https://braintree.github.io/braintree-web/3.46.0/HostedFields.html#tokenize) (nonce) to the client.
+
+1. The client extracts the payment nonce from the [Tokenized Payload](https://braintree.github.io/braintree-web/3.46.0/HostedFields.html#~tokenizePayload).
+
+ The client uses the [`setPaymentMethodOnCart`]({{page.baseurl}}/graphql/mutations/set-payment-method.html) mutation to set the payment method to `braintree`. The payment method nonce is passed with other required and optional properties in the [`braintree`](#braintree-object) object.
+
+1. Magento returns a `Cart` object.
+
+1. The client uses the [`placeOrder`]({{page.baseurl}}/graphql/mutations/place-order.html) mutation.
+
+1. Magento sends an authorization request to Braintree.
+
+1. Braintree sends the response to Magento.
+
+1. Magento creates an order and sends an order ID in response to the `placeOrder` mutation.
+
+## `setPaymentMethodOnCart` mutation
+
+When you set the payment method to Braintree in the [`setPaymentMethodOnCart`]({{page.baseurl}}/graphql/mutations/set-payment-method.html) mutation, the `payment_method` object must contain a `braintree` object.
+
+### braintree object
+
+The `braintree` object must contain the following attributes:
+
+Attribute | Data Type | Description
+--- | --- | ---
+`payment_method_nonce` | String! | The one-time payment token generated by Braintree payment gateway based on card details. Required field for sale transactions
+`is_active_payment_token_enabler` | Boolean! | States whether a customer-entered credit/debit card should be tokenized for later usage. Required only if Vault is enabled for Braintree payment integration
+`device_data` | String | Optional. Contains a fingerprint provided by the Braintree JS SDK. It should be sent with sale transaction details to the Braintree payment gateway. Specify a value only if Kount (advanced fraud protection) is enabled for Braintree payment integration
+
+## Example Usage
+
+The following example shows the `setPaymentMethodOnCart` mutation constructed for the Braintree payment method.
+
+**Request:**
+
+```text
+mutation {
+ setPaymentMethodOnCart(input: {
+ cart_id: "IeTUiU0oCXjm0uRqGCOuhQ2AuQatogjG"
+ payment_method: {
+ code: "braintree"
+ braintree: {
+ payment_method_nonce: "fake-nonce"
+ is_active_payment_token_enabler: false
+ }
+ }
+ }) {
+ cart {
+ selected_payment_method {
+ code
+ }
+ }
+}
+```
+
+**Response:**
+
+```json
+{
+ "data": {
+ "setPaymentMethodOnCart": {
+ "cart": {
+ "selected_payment_method": {
+ "code": "braintree"
+ }
+ }
+ }
+ }
+}
+```
diff --git a/src/guides/v2.4/graphql/payment-methods/hosted-pro.md b/src/guides/v2.4/graphql/payment-methods/hosted-pro.md
deleted file mode 120000
index 0eab792a21b..00000000000
--- a/src/guides/v2.4/graphql/payment-methods/hosted-pro.md
+++ /dev/null
@@ -1 +0,0 @@
-../../../v2.3/graphql/payment-methods/hosted-pro.md
\ No newline at end of file
diff --git a/src/guides/v2.4/graphql/payment-methods/hosted-pro.md b/src/guides/v2.4/graphql/payment-methods/hosted-pro.md
new file mode 100644
index 00000000000..3322bfb5253
--- /dev/null
+++ b/src/guides/v2.4/graphql/payment-methods/hosted-pro.md
@@ -0,0 +1,71 @@
+---
+group: graphql
+title: PayPal Website Payments Pro Hosted Solution payment method
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/payment-methods/hosted-pro/
+status: migrated
+---
+
+PayPal's [Website Payments Pro Hosted Solution](https://developer.paypal.com/docs/classic/paypal-payments-pro/integration-guide/) allows merchants to accept credit cards, debit cards, and PayPal payments directly on their websites. The merchant must be based in the United Kingdom to create a new integration with this payment method. PayPal continues to support merchants with existing integrations outside the UK.
+
+This payment method is applicable to Direct Payment and Express Checkout implementations of the Website Payments Pro Hosted Solution.
+
+PayPal's product name for this payment method varies from country to country. [PayPal Website Payments
+Pro Hosted Solution Integration Guide](https://www.paypalobjects.com/webstatic/en_GB/developer/docs/pdf/hostedsolution_uk.pdf) provides more information.
+
+## Website Payments Pro Hosted Solution workflow
+
+The following diagram shows the workflow for placing an order when Website Payments Pro Hosted Solution is the selected payment method.
+
+
+
+{% include graphql/payment-methods/hosted-pro-workflow.md %}
+
+## `setPaymentMethodOnCart` mutation
+
+When you set the payment method for a Website Payments Pro Hosted Solution, you must set the `code` attribute to `hosted_pro`. In addition, the payload must contain a `hosted_pro` object, which defines the following attributes:
+
+{% include graphql/payment-methods/hosted-pro-attributes.md %}
+
+### Example usage
+
+The following example shows the `setPaymentMethodOnCart` mutation constructed for the Website Payments Pro Hosted Solution payment method.
+
+**Request:**
+
+```graphql
+mutation {
+ setPaymentMethodOnCart(input: {
+ cart_id: "H87OmEkvusP7ZPkd2634pQFxY4dKI3a4"
+ payment_method: {
+ code: "hosted_pro"
+ hosted_pro: {
+ cancel_url: "paypal/hostedpro/cancel"
+ return_url: "paypal/hostedpro/return"
+ }
+ }
+ })
+ {
+ cart {
+ selected_payment_method {
+ code
+ }
+ }
+ }
+}
+```
+
+**Response:**
+
+```json
+{
+ "data": {
+ "setPaymentMethodOnCart": {
+ "cart": {
+ "selected_payment_method": {
+ "code": "hosted_pro",
+ }
+ }
+ }
+ }
+}
+```
diff --git a/src/guides/v2.4/graphql/payment-methods/klarna.md b/src/guides/v2.4/graphql/payment-methods/klarna.md
index 35640708522..b76b883e64d 100644
--- a/src/guides/v2.4/graphql/payment-methods/klarna.md
+++ b/src/guides/v2.4/graphql/payment-methods/klarna.md
@@ -3,6 +3,8 @@ group: graphql
title: Klarna payment method
contributor_name: Klarna
contributor_link: https://www.klarna.com/
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/payment-methods/klarna/
+status: migrated
---
Klarna Payments enables your consumers to try before they buy, finance purchases on your store with Klarna, or let them pay directly. Klarna offers these payment methods through a widget that you can add inline on your checkout page.
@@ -106,7 +108,7 @@ mutation {
payment_method: {
code: "klarna_pay_later"
klarna: {
- authorization_token: "e9abc610-6748-256f-a506-355626551326"
+ authorization_token: "e9abc610-6748-256f-a506-355626551326" #gitleaks:allow
}
}
}) {
diff --git a/src/guides/v2.4/graphql/payment-methods/payflow-express.md b/src/guides/v2.4/graphql/payment-methods/payflow-express.md
deleted file mode 120000
index f735667dbbe..00000000000
--- a/src/guides/v2.4/graphql/payment-methods/payflow-express.md
+++ /dev/null
@@ -1 +0,0 @@
-../../../v2.3/graphql/payment-methods/payflow-express.md
\ No newline at end of file
diff --git a/src/guides/v2.4/graphql/payment-methods/payflow-express.md b/src/guides/v2.4/graphql/payment-methods/payflow-express.md
new file mode 100644
index 00000000000..c9f84dc7801
--- /dev/null
+++ b/src/guides/v2.4/graphql/payment-methods/payflow-express.md
@@ -0,0 +1,82 @@
+---
+group: graphql
+title: Express Checkout for other PayPal solutions
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/payment-methods/payflow-express/
+status: migrated
+---
+
+Set the payment method code to `payflow_express` to process Express Checkout transactions when the payment method is set to any of the following:
+
+- Payflow Link
+- Payflow Pro
+- Payments Advanced
+- Payments Pro
+
+PayPal Express Checkout enables customers to pay by credit card or from the security of their personal PayPal accounts. During checkout, the customer is redirected to the secure PayPal site to complete the payment information. The customer is then returned to the store to complete the remainder of the checkout process.
+
+From a GraphQL integration standpoint, this payment method is identical to the [PayPal Express Checkout]({{page.baseurl}}/graphql/payment-methods/payflow-link.html) payment method, with the exception that in the `setPaymentMethodOnCart` mutation, the payment method `code` is set to `payflow_express`.
+
+## PayPal Express Checkout workflow
+
+The following diagram shows the workflow for placing an order when `payflow_express` is the specified payment method.
+
+
+
+The following steps describe the flow of calls required to complete a typical PayPal Express Checkout authorization. A successful purchase requires that you send three mutations to PayPal, and the buyer must approve the purchase by logging in to PayPal.
+
+{% include graphql/payment-methods/paypal-express-checkout-workflow.md %}
+
+## `setPaymentMethodOnCart` mutation
+
+When you set the payment method to one of the Express Checkout payment solutions discussed in this topic, you must set the `code` attribute to `payflow_express`. In addition, the payload must contain a `payflow_express` object, which defines the following attributes:
+
+{% include graphql/payment-methods/paypal-express-checkout-attributes.md %}
+
+### Example usage
+
+The following example shows the `setPaymentMethodOnCart` mutation with the `code` set to `payflow_express`.
+
+**Request:**
+
+```graphql
+mutation {
+ setPaymentMethodOnCart(input: {
+ cart_id: "rMQdWEecBZr4SVWZwj2AF6y0dNCKQ8uH"
+ payment_method: {
+ code: "payflow_express"
+ payflow_express: {
+ payer_id: ""
+ token: ""
+ }
+ }
+ }) {
+ cart {
+ selected_payment_method {
+ code
+ }
+ }
+ }
+}
+```
+
+**Response:**
+
+```json
+{
+ "data": {
+ "setPaymentMethodOnCart": {
+ "cart": {
+ "selected_payment_method": {
+ "code": "payflow_express",
+ }
+ }
+ }
+ }
+}
+```
+
+## Related topics
+
+- [`createPaypalExpressToken` mutation]({{page.baseurl}}/graphql/mutations/create-paypal-express-token.html)
+- [`placeOrder` mutation]({{page.baseurl}}/graphql/mutations/place-order.html)
+- [`setPaymentMethodOnCart` mutation]({{page.baseurl}}/graphql/mutations/set-payment-method.html)
diff --git a/src/guides/v2.4/graphql/payment-methods/payflow-link.md b/src/guides/v2.4/graphql/payment-methods/payflow-link.md
deleted file mode 120000
index 4409a28e216..00000000000
--- a/src/guides/v2.4/graphql/payment-methods/payflow-link.md
+++ /dev/null
@@ -1 +0,0 @@
-../../../v2.3/graphql/payment-methods/payflow-link.md
\ No newline at end of file
diff --git a/src/guides/v2.4/graphql/payment-methods/payflow-link.md b/src/guides/v2.4/graphql/payment-methods/payflow-link.md
new file mode 100644
index 00000000000..881a06242db
--- /dev/null
+++ b/src/guides/v2.4/graphql/payment-methods/payflow-link.md
@@ -0,0 +1,70 @@
+---
+group: graphql
+title: PayPal Payflow Link payment method
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/payment-methods/payflow-link/
+status: migrated
+---
+
+PayPal [PayFlow Link](https://developer.paypal.com/docs/classic/payflow/integration-guide/) is available for merchants in the United States and Canada only. Customers are not required to have a personal PayPal account. Instead, customers enter their credit card information in a form that is hosted by PayPal.
+
+The Payflow gateway uses a secure token to send non-credit card transaction data to the Payflow server for storage in a way that cannot be intercepted and manipulated maliciously. This token secures the data for a one-time transaction and is valid for 30 minutes. When the PWA client runs the `placeOrder` mutation, Magento requests a secure token. The Payflow server returns the token as a string of up to 32 alphanumeric characters.
+
+## Payflow Link workflow
+
+The following diagram shows the workflow for placing an order when Payflow Link is the selected payment method.
+
+
+
+{% include graphql/payment-methods/payflow-link-workflow.md %}
+
+## Additional Payment information
+
+When you set the payment method to Payflow Link in the [`setPaymentMethodOnCart`]({{page.baseurl}}/graphql/mutations/set-payment-method.html) mutation, the `payment_method` object must contain a `payflow_link` object, which defines the following objects:
+
+{% include graphql/payment-methods/payflow-link-attributes.md %}
+
+### Example usage
+
+The following example shows the `setPaymentMethodOnCart` mutation constructed for the Payflow Link payment method.
+
+**Request:**
+
+```graphql
+mutation {
+ setPaymentMethodOnCart(input: {
+ payment_method: {
+ code: "payflow_link"
+ payflow_link: {
+ return_url: "paypal/action/return.html"
+ error_url: "paypal/action/error.html"
+ cancel_url: "paypal/action/cancel.html"
+ }
+ }
+ cart_id: "IeTUiU0oCXjm0uRqGCOuhQ2AuQatogjG"
+ }) {
+ cart {
+ selected_payment_method {
+ code
+ title
+ }
+ }
+ }
+}
+```
+
+**Response:**
+
+```json
+{
+ "data": {
+ "setPaymentMethodOnCart": {
+ "cart": {
+ "selected_payment_method": {
+ "code": "payflow_link",
+ "title": "PayPal Payflow Link"
+ }
+ }
+ }
+ }
+}
+```
diff --git a/src/guides/v2.4/graphql/payment-methods/payflow-pro-vault.md b/src/guides/v2.4/graphql/payment-methods/payflow-pro-vault.md
index 0bb3b3d8ae5..15daaedd12b 100644
--- a/src/guides/v2.4/graphql/payment-methods/payflow-pro-vault.md
+++ b/src/guides/v2.4/graphql/payment-methods/payflow-pro-vault.md
@@ -1,6 +1,8 @@
---
group: graphql
title: PayPal Payflow Pro Vault payment method
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/payment-methods/payflow-pro-vault/
+status: migrated
---
PayPal Payflow Pro Vault payment method processes credit and debit card payments using information stored in the Magento vault. This payment method is available for customers of the United States, Canada, Australia, and New Zealand.
diff --git a/src/guides/v2.4/graphql/payment-methods/payflow-pro.md b/src/guides/v2.4/graphql/payment-methods/payflow-pro.md
index 8f507033fd0..918e16fafcc 100644
--- a/src/guides/v2.4/graphql/payment-methods/payflow-pro.md
+++ b/src/guides/v2.4/graphql/payment-methods/payflow-pro.md
@@ -1,6 +1,8 @@
---
group: graphql
title: PayPal Payflow Pro payment method
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/payment-methods/payflow-pro/
+status: migrated
---
Payflow Pro is a payment gateway that processes debit and credit card payments. It is available for customers of the United States, Canada, Australia, and New Zealand.
diff --git a/src/guides/v2.4/graphql/payment-methods/payments-advanced.md b/src/guides/v2.4/graphql/payment-methods/payments-advanced.md
deleted file mode 120000
index f60772b003e..00000000000
--- a/src/guides/v2.4/graphql/payment-methods/payments-advanced.md
+++ /dev/null
@@ -1 +0,0 @@
-../../../v2.3/graphql/payment-methods/payments-advanced.md
\ No newline at end of file
diff --git a/src/guides/v2.4/graphql/payment-methods/payments-advanced.md b/src/guides/v2.4/graphql/payment-methods/payments-advanced.md
new file mode 100644
index 00000000000..3c9a2d86674
--- /dev/null
+++ b/src/guides/v2.4/graphql/payment-methods/payments-advanced.md
@@ -0,0 +1,74 @@
+---
+group: graphql
+title: PayPal Payments Advanced payment method
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/payment-methods/payments-advanced/
+status: migrated
+---
+
+The PayPal Payments Advanced payment solution allows merchants to enable their online stores to collect payments directly via credit card or from the PayPal Credit service. If Payments Advanced has been configured to implement Express Checkout, use the [PayPal Express Checkout for Payflow payment method]({{page.baseurl}}/graphql/payment-methods/payflow-express.html) instead.
+
+From a GraphQL integration standpoint, PayPal Payments Advanced payment method is identical to the PayPal [Payflow Link]({{page.baseurl}}/graphql/payment-methods/payflow-link.html) payment method, with the exception of the payment method `code`. The PayPal [Payments Advanced documentation](https://developer.paypal.com/docs/classic/products/paypal-payments-advanced/) describes other ways in which the payment methods differ.
+
+PayPal Payments Advanced is available in the US and Canada only.
+
+## PayPal Payments Advanced workflow
+
+The following diagram shows the workflow for placing an order when Payments Advanced is the selected payment method.
+
+
+
+{% include graphql/payment-methods/payflow-link-workflow.md %}
+
+## Additional Payment information
+
+## `setPaymentMethodOnCart` mutation
+
+When you set the payment method to PayPal Payments Advanced, you must set the `code` attribute to `payflow_advanced`. In addition, the payload must contain a `payflow_link` object, which defines the following attributes:
+
+{% include graphql/payment-methods/payflow-link-attributes.md %}
+
+### Example usage
+
+The following example shows the `setPaymentMethodOnCart` mutation constructed for the Payments Advanced payment method.
+
+**Request:**
+
+```graphql
+mutation {
+ setPaymentMethodOnCart(input: {
+ payment_method: {
+ code: "payflow_advanced"
+ payflow_link: {
+ return_url: "paypal/action/return.html"
+ error_url: "paypal/action/error.html"
+ cancel_url: "paypal/action/cancel.html"
+ }
+ }
+ cart_id: "IeTUiU0oCXjm0uRqGCOuhQ2AuQatogjG"
+ }) {
+ cart {
+ selected_payment_method {
+ code
+ title
+ }
+ }
+ }
+}
+```
+
+**Response:**
+
+```json
+{
+ "data": {
+ "setPaymentMethodOnCart": {
+ "cart": {
+ "selected_payment_method": {
+ "code": "payflow_advanced",
+ "title": "Credit Card"
+ }
+ }
+ }
+ }
+}
+```
diff --git a/src/guides/v2.4/graphql/payment-methods/paypal-express-checkout.md b/src/guides/v2.4/graphql/payment-methods/paypal-express-checkout.md
deleted file mode 120000
index 769b290df2b..00000000000
--- a/src/guides/v2.4/graphql/payment-methods/paypal-express-checkout.md
+++ /dev/null
@@ -1 +0,0 @@
-../../../v2.3/graphql/payment-methods/paypal-express-checkout.md
\ No newline at end of file
diff --git a/src/guides/v2.4/graphql/payment-methods/paypal-express-checkout.md b/src/guides/v2.4/graphql/payment-methods/paypal-express-checkout.md
new file mode 100644
index 00000000000..b8c3714403b
--- /dev/null
+++ b/src/guides/v2.4/graphql/payment-methods/paypal-express-checkout.md
@@ -0,0 +1,80 @@
+---
+group: graphql
+title: PayPal Express Checkout payment method
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/payment-methods/paypal-express-checkout/
+status: migrated
+---
+
+The PayPal Express Checkout payment method enables customers to pay by credit card or from the security of their personal PayPal accounts. During checkout, the customer is redirected to the secure PayPal site to complete the payment information. The customer is then returned to the store to complete the remainder of the checkout process.
+
+Some alternate PayPal solutions have the same GraphQL workflow when Express Checkout is enabled. The information in this topic also applies to the following PayPal solutions:
+
+- Payments Standard
+- Website Payments Standard
+
+## PayPal Express Checkout workflow
+
+The following diagram shows the workflow for placing an order when PayPal Express Checkout is the selected payment method.
+
+
+
+The following steps describe the flow of calls required to complete a typical PayPal Express Checkout authorization. A successful purchase requires that you send three mutations to PayPal, and the buyer must approve the purchase by logging in to PayPal.
+
+{% include graphql/payment-methods/paypal-express-checkout-workflow.md %}
+
+## `setPaymentMethodOnCart` mutation
+
+When you set the payment method to Express Checkout, you must set the `code` attribute to `paypal_express`. In addition, the payload must contain a `paypal_express` object, which defines the following attributes:
+
+{% include graphql/payment-methods/paypal-express-checkout-attributes.md %}
+
+### Example usage
+
+The following example shows the `setPaymentMethodOnCart` mutation constructed for the PayPal Express payment method.
+
+**Request:**
+
+```graphql
+mutation {
+ setPaymentMethodOnCart(input: {
+ cart_id: "rMQdWEecBZr4SVWZwj2AF6y0dNCKQ8uH"
+ payment_method: {
+ code: "paypal_express"
+ paypal_express: {
+ payer_id: ""
+ token: ""
+ }
+ }
+ }) {
+ cart {
+ selected_payment_method {
+ code
+ title
+ }
+ }
+ }
+}
+```
+
+**Response:**
+
+```json
+{
+ "data": {
+ "setPaymentMethodOnCart": {
+ "cart": {
+ "selected_payment_method": {
+ "code": "paypal_express",
+ "title": "PayPal Express Checkout"
+ }
+ }
+ }
+ }
+}
+```
+
+## Related topics
+
+- [`createPaypalExpressToken` mutation]({{page.baseurl}}/graphql/mutations/create-paypal-express-token.html)
+- [`placeOrder` mutation]({{page.baseurl}}/graphql/mutations/place-order.html)
+- [`setPaymentMethodOnCart` mutation]({{page.baseurl}}/graphql/mutations/set-payment-method.html)
diff --git a/src/guides/v2.4/graphql/protected-mutations.md b/src/guides/v2.4/graphql/protected-mutations.md
index cebafe54f0d..77994f6908a 100644
--- a/src/guides/v2.4/graphql/protected-mutations.md
+++ b/src/guides/v2.4/graphql/protected-mutations.md
@@ -1,6 +1,8 @@
---
group: graphql
title: Protected mutations
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/usage/protected-mutations/
+status: migrated
---
If CAPTCHA or reCAPTCHA is enabled on pages requiring shopper input, then in most cases, the corresponding mutations that send requests to the Magento server must include an HTTP header that contains a value entered by the shopper (for CAPTCHA) or generated by the Google API (for reCAPTCHA). However, if you specify an integration authorization token in the header of the mutation, then you do not supply a header specific to CAPTCHA or reCAPTCHA.
diff --git a/src/guides/v2.4/graphql/queries/attributes-metadata.md b/src/guides/v2.4/graphql/queries/attributes-metadata.md
index 64ee467ac9d..25255523a1c 100644
--- a/src/guides/v2.4/graphql/queries/attributes-metadata.md
+++ b/src/guides/v2.4/graphql/queries/attributes-metadata.md
@@ -2,6 +2,8 @@
group: graphql
title: attributesMetadata query
pwa_only: True
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/store/queries/attributes-metadata/
+status: migrated
---
The `attributesMetadata` query returns everything available in [`customAttributeMetadata`]({{page.baseurl}}/graphql/queries/custom-attribute-metadata.html) but also inclues additional information such as `data_type`, `sort_order`, and `ui_input` data, that can be used for filtering, searching and layered navigation. The information returned in `customAttributeMetadata` is in a different format when returned in `attributesMetadata`.
diff --git a/src/guides/v2.4/graphql/queries/available-stores.md b/src/guides/v2.4/graphql/queries/available-stores.md
index 6c99298a215..8cb17d469f8 100644
--- a/src/guides/v2.4/graphql/queries/available-stores.md
+++ b/src/guides/v2.4/graphql/queries/available-stores.md
@@ -1,6 +1,8 @@
---
group: graphql
title: availableStores query
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/store/queries/available-stores/
+status: migrated
---
The `availableStores` query returns configuration information about multiple store views. Use this query to implement a store switcher.
diff --git a/src/guides/v2.4/graphql/queries/cart.md b/src/guides/v2.4/graphql/queries/cart.md
index 8837dd4ddd1..35e8e706036 100644
--- a/src/guides/v2.4/graphql/queries/cart.md
+++ b/src/guides/v2.4/graphql/queries/cart.md
@@ -1,6 +1,8 @@
---
group: graphql
title: cart query
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/cart/queries/cart/
+status: migrated
---
Use the `cart` query to retrieve information about a particular cart.
diff --git a/src/guides/v2.4/graphql/queries/categories.md b/src/guides/v2.4/graphql/queries/categories.md
index 504387b16dc..130b0fcee3f 100644
--- a/src/guides/v2.4/graphql/queries/categories.md
+++ b/src/guides/v2.4/graphql/queries/categories.md
@@ -1,6 +1,8 @@
---
group: graphql
title: categories query
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/products/queries/categories/
+status: migrated
---
The `categories` query returns a list of categories that match the specified filter. This query differs from the `categoryList` query in that it supports pagination.
diff --git a/src/guides/v2.4/graphql/queries/category-list.md b/src/guides/v2.4/graphql/queries/category-list.md
index 4f42e6495d3..67492f8e454 100644
--- a/src/guides/v2.4/graphql/queries/category-list.md
+++ b/src/guides/v2.4/graphql/queries/category-list.md
@@ -1,6 +1,8 @@
---
group: graphql
title: categoryList query
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/products/queries/category-list/
+status: migrated
---
The `categoryList` query searches for categories that match the criteria specified in filters. It replaces the deprecated `category` query, which allowed you to search by category ID only.
diff --git a/src/guides/v2.4/graphql/queries/category.md b/src/guides/v2.4/graphql/queries/category.md
index 84b646e9166..365a22ad1bc 100644
--- a/src/guides/v2.4/graphql/queries/category.md
+++ b/src/guides/v2.4/graphql/queries/category.md
@@ -1,6 +1,8 @@
---
group: graphql
title: category query
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/products/queries/category/
+status: migrated
---
{:.bs-callout-warning}
diff --git a/src/guides/v2.4/graphql/queries/checkout-agreements.md b/src/guides/v2.4/graphql/queries/checkout-agreements.md
deleted file mode 120000
index f4529978c3e..00000000000
--- a/src/guides/v2.4/graphql/queries/checkout-agreements.md
+++ /dev/null
@@ -1 +0,0 @@
-../../../v2.3/graphql/queries/checkout-agreements.md
\ No newline at end of file
diff --git a/src/guides/v2.4/graphql/queries/checkout-agreements.md b/src/guides/v2.4/graphql/queries/checkout-agreements.md
new file mode 100644
index 00000000000..f402313d8e4
--- /dev/null
+++ b/src/guides/v2.4/graphql/queries/checkout-agreements.md
@@ -0,0 +1,73 @@
+---
+group: graphql
+title: checkoutAgreements query
+contributor_name: Something Digital
+contributor_link: https://www.somethingdigital.com/
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/checkout/queries/agreements/
+status: migrated
+---
+
+The `checkoutAgreements` query retrieves checkout agreements. The query will always return an empty array when the
+**Enable Terms and Conditions** option is set to **No**. (The config path is `checkout/options/enable_agreements`.)
+
+## Syntax
+
+`{checkoutAgreements {CheckoutAgreement}}`
+
+## Example usage
+
+The following query returns enabled checkout agreements.
+
+**Request:**
+
+```graphql
+{
+ checkoutAgreements {
+ agreement_id
+ checkbox_text
+ content
+ content_height
+ is_html
+ mode
+ name
+ }
+}
+```
+
+**Response:**
+
+```json
+{
+ "data": {
+ "checkoutAgreements": [
+ {
+ "agreement_id": 1,
+ "checkbox_text": "I agree to the terms of sale",
+ "content": "
Agreement Contents
\r\n
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
",
+ "content_height": "22px",
+ "is_html": true,
+ "mode": "AUTO",
+ "name": "My Agreement"
+ }
+ ]
+ }
+}
+```
+
+## Output attributes
+
+The `CheckoutAgreements` object contains an array of [`CheckoutAgreement`](#checkoutAgreementAttributes) objects.
+
+### CheckoutAgreement attributes {#checkoutAgreementAttributes}
+
+The `CheckoutAgreement` object provides the following attributes:
+
+Attribute | Data type | Description
+--- | --- | ---
+`agreement_id` | Integer! | Checkout Agreement identifier
+`checkbox_text` | String! | Label of the Checkout Agreement checkbox
+`content` | String! | The content of the Checkout Agreement. The value can be in plain text or in HTML
+`content_height` | String | CSS height of Checkout Agreement
+`is_html` | Boolean! | Is Checkout Agreement content in HTML format
+`mode` | String! | Indicates whether terms and conditions are applied manually (`MANUAL`) or automatically (`AUTO`)
+`name` | String! | Checkout Agreement name
diff --git a/src/guides/v2.4/graphql/queries/cms-blocks.md b/src/guides/v2.4/graphql/queries/cms-blocks.md
deleted file mode 120000
index ebffd2829cf..00000000000
--- a/src/guides/v2.4/graphql/queries/cms-blocks.md
+++ /dev/null
@@ -1 +0,0 @@
-../../../v2.3/graphql/queries/cms-blocks.md
\ No newline at end of file
diff --git a/src/guides/v2.4/graphql/queries/cms-blocks.md b/src/guides/v2.4/graphql/queries/cms-blocks.md
new file mode 100644
index 00000000000..06b1619da50
--- /dev/null
+++ b/src/guides/v2.4/graphql/queries/cms-blocks.md
@@ -0,0 +1,72 @@
+---
+group: graphql
+title: cmsBlocks query
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/store/queries/cms-blocks/
+status: migrated
+---
+
+The `cmsBlocks` query returns information about blocks that were developed with the Magento Content Management System (CMS).
+
+## Syntax
+
+Return the contents of one or more CMS blocks:
+
+`cmsBlocks(identifiers: [String]): CmsBlocks`
+
+## Example usage
+
+The following query returns information about the `login-data` block:
+
+**Request:**
+
+```graphql
+{
+ cmsBlocks(identifiers: "login-data") {
+ items {
+ identifier
+ title
+ content
+ }
+ }
+}
+```
+
+**Response:**
+
+```json
+{
+ "data": {
+ "cmsBlocks": {
+ "items": [
+ {
+ "identifier": "login-data",
+ "title": "Login Info Block",
+ "content": "
\n
Try Demo Customer Access
\n
Email:roni_cost@example.com
\n
Password:roni_cost3@example.com
\n
"
+ }
+ ]
+ }
+ }
+}
+```
+
+## Input attributes
+
+Attribute | Data type | Description
+--- | --- | ---
+`id` | Int | Deprecated. Use `identifier` instead.
+`identifiers` | [String] | An array containing a comma-separated list of block identifiers
+
+## Output attributes
+
+The `CmsBlocks` object contains an array of `items`, each of which can contain a `CmsBlock` object.
+
+### CmsBlock attributes
+
+{% include graphql/cms-block-object.md %}
+
+## Errors
+
+Error | Description
+--- | ---
+`The CMS block with the "XXXX" ID doesn't exist` | The specified CMS block ID is invalid.
+`"identifiers" of CMS blocks should be specified"` | The `identifiers` array parameter is required for identifying the CMS blocks.
diff --git a/src/guides/v2.4/graphql/queries/cms-page.md b/src/guides/v2.4/graphql/queries/cms-page.md
deleted file mode 120000
index c428050eab2..00000000000
--- a/src/guides/v2.4/graphql/queries/cms-page.md
+++ /dev/null
@@ -1 +0,0 @@
-../../../v2.3/graphql/queries/cms-page.md
\ No newline at end of file
diff --git a/src/guides/v2.4/graphql/queries/cms-page.md b/src/guides/v2.4/graphql/queries/cms-page.md
new file mode 100644
index 00000000000..f6e85402e36
--- /dev/null
+++ b/src/guides/v2.4/graphql/queries/cms-page.md
@@ -0,0 +1,92 @@
+---
+group: graphql
+title: cmsPage query
+redirect_from:
+ - /guides/v2.3/graphql/reference/cms.html
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/store/queries/cms-page/
+status: migrated
+---
+
+The `cmsPage` query returns information about content pages that were developed with the Magento Content Management System (CMS).
+
+## Syntax
+
+Return the contents of a CMS page:
+
+`cmsPage(identifier: String): CmsPage`
+
+## Example usage
+
+You must include the CMS page identifier value to retrieve the content of a specific CMS page. The following query returns information about the "404 Not Found" CMS page:
+
+**Request:**
+
+```graphql
+{
+ cmsPage(identifier: "no-route") {
+ identifier
+ url_key
+ title
+ content
+ content_heading
+ page_layout
+ meta_title
+ meta_description
+ meta_keywords
+ }
+}
+```
+
+**Response:**
+
+```json
+{
+ "data": {
+ "cmsPage": {
+ "identifier": "no-route"
+ "url_key": "no-route",
+ "title": "404 Not Found",
+ "content": "
\r\n
The page you requested was not found, and we have a fine guess why.
\r\n
\r\n
\r\n
If you typed the URL directly, please make sure the spelling is correct.
\r\n
If you clicked on a link to get here, the link is outdated.
\r\n
\r\n
\r\n
\r\n
What can you do?
\r\n
Have no fear, help is near! There are many ways you can get back on track with Magento Store.
\r\n",
+ "content_heading": "Whoops, our bad...",
+ "page_layout": "2columns-right",
+ "meta_title": null,
+ "meta_description": "Page description",
+ "meta_keywords": "Page keywords"
+ }
+ }
+}
+```
+
+## Input attributes
+
+Attribute | Data type | Description
+--- | --- | ---
+`id` | Int | Deprecated. Use `identifier` instead.
+`identifier` | String | The identifier of a CMS page
+
+## Output attributes
+
+The `CmsPage` object can contain the following attributes:
+
+Attribute | Data type | Description
+--- | --- | ---
+`content` | String | The content of the CMS page in raw HTML
+`content_heading` | String | The heading that displays at the top of the CMS page
+`identifier` | String | The identifier of the CMS page
+`meta_description` | String | A brief description of the page for search results listings
+`meta_keywords` | String | A set of keywords that search engines can use to index the page
+`meta_title` | String | A page title that is indexed by search engines and appears in search results listings
+`page_layout` | String | The design layout of the page, indicating the number of columns and navigation features used on the page
+`title` | String | The name that appears in the breadcrumb trail navigation and in the browser title bar and tab
+`url_key` |String | The URL key of the CMS page, which is often based on the `content_heading`
+
+## Related topics
+
+[cmsBlocks query]({{page.baseurl}}/graphql/queries/cms-blocks.html)
+
+## Errors
+
+Error | Description
+--- | ---
+`The CMS page with the "XXXX" ID doesn't exist` | The specified CMS page ID is invalid.
+`Page id/identifier should be specified"` | The `identifier` parameter is required for identifying the CMS page.
\ No newline at end of file
diff --git a/src/guides/v2.4/graphql/queries/company.md b/src/guides/v2.4/graphql/queries/company.md
index 11e6dd0a324..522a5b1905e 100644
--- a/src/guides/v2.4/graphql/queries/company.md
+++ b/src/guides/v2.4/graphql/queries/company.md
@@ -2,6 +2,8 @@
group: graphql
title: company query
b2b_only: true
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/b2b/company/queries/company/
+status: migrated
---
The `company` query returns details about the user's company. The request must include the customer token of a company user.
diff --git a/src/guides/v2.4/graphql/queries/compare-list.md b/src/guides/v2.4/graphql/queries/compare-list.md
index abb8badea66..f714026cf92 100644
--- a/src/guides/v2.4/graphql/queries/compare-list.md
+++ b/src/guides/v2.4/graphql/queries/compare-list.md
@@ -3,6 +3,8 @@ group: graphql
title: compareList query
contributor_name: Atwix
contributor_link: https://www.atwix.com/
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/products/queries/compare-list/
+status: migrated
---
The `compareList` query retrieves information about a list of products so that the shopper can compare those products.
diff --git a/src/guides/v2.4/graphql/queries/custom-attribute-metadata.md b/src/guides/v2.4/graphql/queries/custom-attribute-metadata.md
index 63fa33fb703..7dd81d081bc 100644
--- a/src/guides/v2.4/graphql/queries/custom-attribute-metadata.md
+++ b/src/guides/v2.4/graphql/queries/custom-attribute-metadata.md
@@ -3,6 +3,8 @@ group: graphql
title: customAttributeMetadata query
redirect_from:
- /guides/v2.3/graphql/reference/custom-attribute-metadata.html
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/store/queries/custom-attribute-metadata/
+status: migrated
---
The `customAttributeMetadata` query returns the attribute type, given an attribute code and entity type. All entity attributes can be added to an equivalent GraphQL type, including custom, extension, and EAV (which have precedence set in that order for collisions). The GraphQL query consumer does not have the ability to know a field's attribute type.
diff --git a/src/guides/v2.4/graphql/queries/customer-cart.md b/src/guides/v2.4/graphql/queries/customer-cart.md
index 89f38ce82f3..b101f321855 100644
--- a/src/guides/v2.4/graphql/queries/customer-cart.md
+++ b/src/guides/v2.4/graphql/queries/customer-cart.md
@@ -1,6 +1,8 @@
---
group: graphql
title: customerCart query
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/customer/queries/cart/
+status: migrated
---
The `customerCart` query returns the active cart for the logged-in customer. If the cart does not exist, the query creates one. The customer's authorization token must be specified in the headers.
diff --git a/src/guides/v2.4/graphql/queries/customer-downloadable-products.md b/src/guides/v2.4/graphql/queries/customer-downloadable-products.md
deleted file mode 120000
index 45e175e75c9..00000000000
--- a/src/guides/v2.4/graphql/queries/customer-downloadable-products.md
+++ /dev/null
@@ -1 +0,0 @@
-../../../v2.3/graphql/queries/customer-downloadable-products.md
\ No newline at end of file
diff --git a/src/guides/v2.4/graphql/queries/customer-downloadable-products.md b/src/guides/v2.4/graphql/queries/customer-downloadable-products.md
new file mode 100644
index 00000000000..2356cbc362a
--- /dev/null
+++ b/src/guides/v2.4/graphql/queries/customer-downloadable-products.md
@@ -0,0 +1,85 @@
+---
+group: graphql
+title: customerDownloadableProducts query
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/customer/queries/downloadable-products/
+status: migrated
+---
+
+Use the `customerDownloadableProducts` query to retrieve the list of purchased downloadable products for the logged-in customer.
+
+## Syntax
+
+`{customerDownloadableProducts: {CustomerDownloadableProducts}}`
+
+## Example usage
+
+The following example returns the list of purchased downloadable products for the logged-in customer.
+
+**Request:**
+
+```graphql
+{
+ customerDownloadableProducts {
+ items {
+ date
+ download_url
+ order_increment_id
+ remaining_downloads
+ status
+ }
+ }
+}
+```
+
+**Response:**
+
+```json
+{
+ "data": {
+ "customerDownloadableProducts": {
+ "items": [
+ {
+ "date": "2019-03-04 20:48:32",
+ "download_url": "https:///downloadable/download/link/id/MC44NTcwMTEwMCAxNTUxNzMyNTEyMTExNTE%2C/",
+ "order_increment_id": "000000004",
+ "remaining_downloads": "Unlimited",
+ "status": "pending"
+ },
+ {
+ "date": "2019-03-04 20:48:32",
+ "download_url": "https:///downloadable/download/link/id/MC44NzM0OTkwMCAxNTUxNzMyNTEyMjEyNTA%2C/",
+ "order_increment_id": "000000004",
+ "remaining_downloads": "Unlimited",
+ "status": "pending"
+ }
+ ]
+ }
+ }
+}
+```
+
+## Output attributes
+
+The `CustomerDownloadableProducts` object contains the following attribute.
+
+Attribute | Type | Description
+--- | --- | ---
+`items` | [[CustomerDownloadableProduct]](#custDownloadProduct) | List of purchased downloadable items
+
+### CustomerDownloadableProduct object {#custDownloadProduct}
+
+The `CustomerDownloadableProduct` object contains the following attributes:
+
+Attribute | Type | Description
+--- | --- | ---
+`date` | String | The date and time the purchase was made
+`download_url` | String | The fully qualified URL to the download file
+`order_increment_id` | String | The purchase order ID
+`remaining_downloads` | String | Determines the number of times the customer can download the product
+`status` | String | Determines the stage in the order workflow when the download becomes available. Options are `Pending` and `Invoiced`
+
+## Errors
+
+Error | Description
+--- | ---
+`The current customer isn't authorized.` | The current customer is not currently logged in, or the customer's token does not exist in the `oauth_token` table.
diff --git a/src/guides/v2.4/graphql/queries/customer-orders.md b/src/guides/v2.4/graphql/queries/customer-orders.md
index 1c21b33d0d2..7c8beec8c5a 100644
--- a/src/guides/v2.4/graphql/queries/customer-orders.md
+++ b/src/guides/v2.4/graphql/queries/customer-orders.md
@@ -1,6 +1,8 @@
---
group: graphql
title: customerOrders query
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/customer/queries/orders/
+status: migrated
---
{:.bs-callout-warning}
The `customerOrders` query has been deprecated. Specify the `orders` object in the [`customer`]({{page.baseurl}}/graphql/queries/customer.html) query instead.
diff --git a/src/guides/v2.4/graphql/queries/customer-payment-tokens.md b/src/guides/v2.4/graphql/queries/customer-payment-tokens.md
deleted file mode 120000
index 2bad27bf423..00000000000
--- a/src/guides/v2.4/graphql/queries/customer-payment-tokens.md
+++ /dev/null
@@ -1 +0,0 @@
-../../../v2.3/graphql/queries/customer-payment-tokens.md
\ No newline at end of file
diff --git a/src/guides/v2.4/graphql/queries/customer-payment-tokens.md b/src/guides/v2.4/graphql/queries/customer-payment-tokens.md
new file mode 100644
index 00000000000..223c0a88da5
--- /dev/null
+++ b/src/guides/v2.4/graphql/queries/customer-payment-tokens.md
@@ -0,0 +1,77 @@
+---
+group: graphql
+title: customerPaymentTokens query
+redirect_from:
+ - /guides/v2.3/graphql/reference/vault.html
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/checkout/queries/customer-payment-tokens/
+status: migrated
+---
+
+When the [vault]({{page.baseurl}}/payments-integrations/vault/vault-intro.html) feature is supported by a payment integration and enabled, customers have the option during checkout to save their credit card information. (Braintree supports the vault feature. Third-party payment integrations may support this feature as well.) During subsequent checkouts, the customer is presented with a list of saved payment options. If Instant Purchase is enabled, customers can even by-pass the two-step checkout process and place the order from the product page.
+
+The `customerPaymentTokens` query returns an array of stored payment methods. Use the [deletePaymentToken mutation]({{page.baseurl}}/graphql/mutations/delete-payment-token.html) to delete a payment token from the system.
+
+{:.bs-callout-info}
+You must specify the customer's authorization token in the header of the call.
+
+## Syntax
+
+`{customerPaymentTokens{CustomerPaymentTokens}}`
+
+## Example usage
+
+The following example returns all the current customer's payment tokens. The `public_hash` output values will be unique to your application.
+
+**Request:**
+
+```graphql
+query {
+ customerPaymentTokens {
+ items {
+ details
+ public_hash
+ payment_method_code
+ type
+ }
+ }
+}
+```
+
+**Response:**
+
+```json
+{
+ "data": {
+ "customerPaymentTokens": {
+ "items": [
+ {
+ "details": "{\"type\":\"VI\",\"maskedCC\":\"1111\",\"expirationDate\":\"09\\/2022\"}",
+ "public_hash": "377c1514e0...",
+ "payment_method_code": "braintree",
+ "type": "card"
+ },
+ {
+ "details": "{\"type\":\"DI\",\"maskedCC\":\"1117\",\"expirationDate\":\"11\\/2023\"}",
+ "public_hash": "f5816fe2ab...",
+ "payment_method_code": "braintree",
+ "type": "card"
+ }
+ ]
+ }
+ }
+}
+```
+
+## Output attributes
+
+{% include graphql/customer-payment-tokens.md %}
+
+## Errors
+
+Error | Description
+--- | ---
+`The current customer isn't authorized.` | The current customer is not currently logged in, or the customer's token does not exist in the `oauth_token` table.
+
+## Related topics
+
+[deletePaymentToken mutation]({{page.baseurl}}/graphql/mutations/delete-payment-token.html)
diff --git a/src/guides/v2.4/graphql/queries/customer.md b/src/guides/v2.4/graphql/queries/customer.md
index b40a33857ac..146752f6a08 100644
--- a/src/guides/v2.4/graphql/queries/customer.md
+++ b/src/guides/v2.4/graphql/queries/customer.md
@@ -1,6 +1,8 @@
---
group: graphql
title: customer query
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/customer/queries/customer/
+status: migrated
---
The `customer` query returns information about the logged-in customer, store credit history and customer's wishlist.
diff --git a/src/guides/v2.4/graphql/queries/directory-countries.md b/src/guides/v2.4/graphql/queries/directory-countries.md
deleted file mode 120000
index 240782c64cc..00000000000
--- a/src/guides/v2.4/graphql/queries/directory-countries.md
+++ /dev/null
@@ -1 +0,0 @@
-../../../v2.3/graphql/queries/directory-countries.md
\ No newline at end of file
diff --git a/src/guides/v2.4/graphql/queries/directory-countries.md b/src/guides/v2.4/graphql/queries/directory-countries.md
new file mode 100644
index 00000000000..5fec3b6aefc
--- /dev/null
+++ b/src/guides/v2.4/graphql/queries/directory-countries.md
@@ -0,0 +1,147 @@
+---
+group: graphql
+title: countries query
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/store/queries/countries/
+status: migrated
+---
+
+The `countries` query returns all countries in which the entity can do business.
+
+Use the [country]({{page.baseurl}}/graphql/queries/directory-country.html) query if you want to retrieve information about a specific country.
+
+## Syntax
+
+`{countries {Countries}}`
+
+## Example usage
+
+The following query returns all countries listed for the current instance of Magento:
+
+**Request:**
+
+```graphql
+query {
+ countries {
+ id
+ two_letter_abbreviation
+ three_letter_abbreviation
+ full_name_locale
+ full_name_english
+ available_regions {
+ id
+ code
+ name
+ }
+ }
+}
+```
+
+**Response:**
+
+In this example, the response is intentionally truncated. The `available_regions` attribute value will be null if the country does not have any regions available. Otherwise, it contains an array of the country's regions.
+
+```json
+{
+ "data": {
+ "countries": [
+ {
+ "id": "AD",
+ "two_letter_abbreviation": "AD",
+ "three_letter_abbreviation": "AND",
+ "full_name_locale": "Andorra",
+ "full_name_english": "Andorra",
+ "available_regions": null
+ },
+ {
+ "id": "AE",
+ "two_letter_abbreviation": "AE",
+ "three_letter_abbreviation": "ARE",
+ "full_name_locale": "United Arab Emirates",
+ "full_name_english": "United Arab Emirates",
+ "available_regions": null
+ },
+ {
+ "id": "AF",
+ "two_letter_abbreviation": "AF",
+ "three_letter_abbreviation": "AFG",
+ "full_name_locale": "Afghanistan",
+ "full_name_english": "Afghanistan",
+ "available_regions": null
+ },
+ {
+ "id": "AG",
+ "two_letter_abbreviation": "AG",
+ "three_letter_abbreviation": "ATG",
+ "full_name_locale": "Antigua and Barbuda",
+ "full_name_english": "Antigua and Barbuda",
+ "available_regions": null
+ },
+ {
+ "id": "AT",
+ "two_letter_abbreviation": "AT",
+ "three_letter_abbreviation": "AUT",
+ "full_name_locale": "Austria",
+ "full_name_english": "Austria",
+ "available_regions": [
+ {
+ "id": 102,
+ "code": "BL",
+ "name": "Burgenland"
+ },
+ {
+ "id": 99,
+ "code": "KN",
+ "name": "Kärnten"
+ },
+ {
+ "id": 96,
+ "code": "NO",
+ "name": "Niederösterreich"
+ },
+ {
+ "id": 97,
+ "code": "OO",
+ "name": "Oberösterreich"
+ },
+ {
+ "id": 98,
+ "code": "SB",
+ "name": "Salzburg"
+ },
+ {
+ "id": 100,
+ "code": "ST",
+ "name": "Steiermark"
+ },
+ {
+ "id": 101,
+ "code": "TI",
+ "name": "Tirol"
+ },
+ {
+ "id": 103,
+ "code": "VB",
+ "name": "Vorarlberg"
+ },
+ {
+ "id": 95,
+ "code": "WI",
+ "name": "Wien"
+ }
+ ]
+ }
+ ]
+ }
+}
+```
+
+## Output attributes
+
+The query returns an array of `Country` objects.
+
+{% include graphql/country-output.md %}
+
+## Related topics
+
+* [country query]({{page.baseurl}}/graphql/queries/directory-country.html)
+* [currency query]({{page.baseurl}}/graphql/queries/directory-currency.html)
diff --git a/src/guides/v2.4/graphql/queries/directory-country.md b/src/guides/v2.4/graphql/queries/directory-country.md
deleted file mode 120000
index da126200098..00000000000
--- a/src/guides/v2.4/graphql/queries/directory-country.md
+++ /dev/null
@@ -1 +0,0 @@
-../../../v2.3/graphql/queries/directory-country.md
\ No newline at end of file
diff --git a/src/guides/v2.4/graphql/queries/directory-country.md b/src/guides/v2.4/graphql/queries/directory-country.md
new file mode 100644
index 00000000000..76d6da0eea1
--- /dev/null
+++ b/src/guides/v2.4/graphql/queries/directory-country.md
@@ -0,0 +1,123 @@
+---
+group: graphql
+title: country query
+redirect_from:
+ - /guides/v2.3/graphql/reference/directory.html
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/store/queries/country/
+status: migrated
+---
+
+Use the `country` query to retrieve information about a specific country.
+
+Use the [countries]({{page.baseurl}}/graphql/queries/directory-countries.html) query to retrieve a list of countries available in the system.
+
+## Syntax
+
+`{country(id: String) {Country}}`
+
+## Example usage
+
+The following query uses a two-letter abbreviation for the country ID (id: "AU"), which returns information about Australia.
+
+**Request:**
+
+```graphql
+query {
+ country(id: "AU") {
+ id
+ two_letter_abbreviation
+ three_letter_abbreviation
+ full_name_locale
+ full_name_english
+ available_regions {
+ id
+ code
+ name
+ }
+ }
+}
+```
+
+**Response:**
+
+```json
+{
+ "data": {
+ "country": {
+ "id": "AU",
+ "two_letter_abbreviation": "AU",
+ "three_letter_abbreviation": "AUS",
+ "full_name_locale": "Australia",
+ "full_name_english": "Australia",
+ "available_regions": [
+ {
+ "id": 569,
+ "code": "ACT",
+ "name": "Australian Capital Territory"
+ },
+ {
+ "id": 570,
+ "code": "NSW",
+ "name": "New South Wales"
+ },
+ {
+ "id": 576,
+ "code": "NT",
+ "name": "Northern Territory"
+ },
+ {
+ "id": 572,
+ "code": "QLD",
+ "name": "Queensland"
+ },
+ {
+ "id": 573,
+ "code": "SA",
+ "name": "South Australia"
+ },
+ {
+ "id": 574,
+ "code": "TAS",
+ "name": "Tasmania"
+ },
+ {
+ "id": 571,
+ "code": "VIC",
+ "name": "Victoria"
+ },
+ {
+ "id": 575,
+ "code": "WA",
+ "name": "Western Australia"
+ }
+ ]
+ }
+ }
+}
+```
+
+## Input attributes
+
+The `country` query requires the following input:
+
+Attribute | Data type | Description
+--- | --- | ---
+`id` | String | A unique ID for the country
+
+## Output attributes
+
+The query returns a single `Country` object.
+
+{% include graphql/country-output.md %}
+
+## Related topics
+
+* [countries query]({{page.baseurl}}/graphql/queries/directory-countries.html)
+* [currency query]({{page.baseurl}}/graphql/queries/directory-currency.html)
+
+## Errors
+
+Error | Description
+--- | ---
+`Country \"id\" value should be specified"` | The Country ID value must be specified to find the mapped country.
+`The country isn't available` | There is no country mapped to the given country ID.
diff --git a/src/guides/v2.4/graphql/queries/directory-currency.md b/src/guides/v2.4/graphql/queries/directory-currency.md
deleted file mode 120000
index 1dc930ee2c5..00000000000
--- a/src/guides/v2.4/graphql/queries/directory-currency.md
+++ /dev/null
@@ -1 +0,0 @@
-../../../v2.3/graphql/queries/directory-currency.md
\ No newline at end of file
diff --git a/src/guides/v2.4/graphql/queries/directory-currency.md b/src/guides/v2.4/graphql/queries/directory-currency.md
new file mode 100644
index 00000000000..b19eda85995
--- /dev/null
+++ b/src/guides/v2.4/graphql/queries/directory-currency.md
@@ -0,0 +1,90 @@
+---
+group: graphql
+title: currency query
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/store/queries/currency/
+status: migrated
+---
+
+Use the `currency` query to return information about the store's currency configuration.
+
+## Syntax
+
+`{currency {Currency}}`
+
+## Example usage
+
+The following query returns currency information for an instance of Magento that is configured for multiple currencies, USD and EUR. The default (base) currency for the store is US Dollar (USD). The response includes a list of currencies in the `available_currency_codes` attribute as well as a set of exchange rates.
+
+**Request:**
+
+```graphql
+query {
+ currency {
+ base_currency_code
+ base_currency_symbol
+ default_display_currency_code
+ default_display_currency_symbol
+ available_currency_codes
+ exchange_rates {
+ currency_to
+ rate
+ }
+ }
+}
+```
+
+**Response:**
+
+```json
+{
+ "data": {
+ "currency": {
+ "base_currency_code": "USD",
+ "base_currency_symbol": "$",
+ "default_display_currency_code": "USD",
+ "default_display_currency_symbol": "$",
+ "available_currency_codes": [
+ "EUR",
+ "USD"
+ ],
+ "exchange_rates": [
+ {
+ "currency_to": "EUR",
+ "rate": 0.7067
+ },
+ {
+ "currency_to": "USD",
+ "rate": 1
+ }
+ ]
+ }
+ }
+}
+```
+
+## Output attributes
+
+The `currency` object provides the following attributes:
+
+Attribute | Data type | Description
+--- | --- | ---
+`available_currency_codes` | [String] | An array of three-letter currency codes accepted by the store, such as `USD` and `EUR`
+`base_currency_code` | String | The base currency set for the store, such as USD
+`base_currency_symbol` | String | The symbol for the specified base currency, such as $
+`default_display_currency_code` | String | Specifies if the currency code is set as the store's default
+`default_display_currency_symbol` | String | Specifies if the currency symbol is set as the store's default
+`exchange_rates` | [[ExchangeRate]](#exchangeRateAttributes) | An array of exchange rates specified in the store
+
+## Exchange rate attributes {#exchangeRateAttributes}
+
+The `ExchangeRate` object provides the following attributes:
+
+Attribute | Data type | Description
+--- | --- | ---
+`currency_to` | String | Specifies the store's default currency to exchange to
+`rate` | Float | The exchange rate for the store's default currency
+
+## Related topics
+
+* [countries query]({{page.baseurl}}/graphql/queries/directory-countries.html)
+* [country query]({{page.baseurl}}/graphql/queries/directory-country.html)
diff --git a/src/guides/v2.4/graphql/queries/dynamic-blocks.md b/src/guides/v2.4/graphql/queries/dynamic-blocks.md
index 64ae600a89b..bf0c219d1c4 100644
--- a/src/guides/v2.4/graphql/queries/dynamic-blocks.md
+++ b/src/guides/v2.4/graphql/queries/dynamic-blocks.md
@@ -1,6 +1,8 @@
---
group: graphql
title: dynamicBlocks query
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/store/queries/dynamic-blocks/
+status: migrated
---
The `dynamicBlocks` query returns a list of dynamic blocks that have been placed in a Dynamic Blocks Rotator inline widget and meet the specified criteria.
diff --git a/src/guides/v2.4/graphql/queries/get-hosted-pro-url.md b/src/guides/v2.4/graphql/queries/get-hosted-pro-url.md
index f04f8d07374..4dd25f1eeab 100644
--- a/src/guides/v2.4/graphql/queries/get-hosted-pro-url.md
+++ b/src/guides/v2.4/graphql/queries/get-hosted-pro-url.md
@@ -1,6 +1,8 @@
---
group: graphql
title: getHostedProUrl query
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/checkout/queries/get-hosted-pro-url/
+status: migrated
---
The `getHostedProUrl` query is required to complete a transaction when the [PayPal Website Payments Pro Hosted Solution payment method]({{page.baseurl}}/graphql/payment-methods/hosted-pro.html) is selected. The query retrieves a PayPal-generated URL that the PWA client connects to, enabling the customer to enter their PayPal credentials and complete the transaction. Run this query after you [set the payment method]({{ page.baseurl}}/graphql/mutations/set-payment-method.html) and [place the order]({{ page.baseurl}}/graphql/mutations/place-order.html).
@@ -41,7 +43,7 @@ The `getHostedProUrl` query must contain the following attribute:
Attribute | Data type | Description
--- | --- | ---
-`cart_id` | String! | The unique ID that identifies the customer’s cart
+`cart_id` | String! | The unique ID that identifies the customer's cart
## Output attributes
diff --git a/src/guides/v2.4/graphql/queries/get-payflow-link-token.md b/src/guides/v2.4/graphql/queries/get-payflow-link-token.md
index 5c27a09300e..9dc4034b9d3 100644
--- a/src/guides/v2.4/graphql/queries/get-payflow-link-token.md
+++ b/src/guides/v2.4/graphql/queries/get-payflow-link-token.md
@@ -1,6 +1,8 @@
---
group: graphql
title: getPayflowLinkToken query
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/checkout/queries/get-payflow-link-token/
+status: migrated
---
The `getPayflowLinkToken` query retrieves PayPal payment credentials for a PayPal Payflow transaction. You must run this query after you [set the payment method]({{ page.baseurl}}/graphql/mutations/set-payment-method.html) and [place the order]({{ page.baseurl}}/graphql/mutations/place-order.html).
diff --git a/src/guides/v2.4/graphql/queries/gift-registry-email-search.md b/src/guides/v2.4/graphql/queries/gift-registry-email-search.md
index cb6a1a5b716..925dc51d36f 100644
--- a/src/guides/v2.4/graphql/queries/gift-registry-email-search.md
+++ b/src/guides/v2.4/graphql/queries/gift-registry-email-search.md
@@ -1,7 +1,9 @@
---
group: graphql
title: giftRegistryEmailSearch query
-ee_only: true
+ee_only: true
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/gift-registry/queries/email-search/
+status: migrated
---
The `giftRegistryEmailSearch` query returns a list of gift registries that match the specified registrant email address. The query does not return registries based on owner email address.
diff --git a/src/guides/v2.4/graphql/queries/gift-registry-id-search.md b/src/guides/v2.4/graphql/queries/gift-registry-id-search.md
index 7c3732c8bb4..de10dabc7c4 100644
--- a/src/guides/v2.4/graphql/queries/gift-registry-id-search.md
+++ b/src/guides/v2.4/graphql/queries/gift-registry-id-search.md
@@ -1,7 +1,9 @@
---
group: graphql
title: giftRegistryIdSearch query
-ee_only: true
+ee_only: true
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/gift-registry/queries/id-search/
+status: migrated
---
The `giftRegistryIdSearch` query returns a list of gift registries that match the specified registry ID. The ID is included in the email Magento sends to invitees on behalf of the registrant.
diff --git a/src/guides/v2.4/graphql/queries/gift-registry-type-search.md b/src/guides/v2.4/graphql/queries/gift-registry-type-search.md
index bde323f9b55..e020b4d515b 100644
--- a/src/guides/v2.4/graphql/queries/gift-registry-type-search.md
+++ b/src/guides/v2.4/graphql/queries/gift-registry-type-search.md
@@ -1,7 +1,9 @@
---
group: graphql
title: giftRegistryTypeSearch query
-ee_only: true
+ee_only: true
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/gift-registry/queries/type-search/
+status: migrated
---
The `giftRegistryTypeSearch` query returns a list of gift registries that match the specified registrant name and, optionally, registry type ID. Use the [`giftRegistryTypes` query]({{page.baseurl}}/graphql/queries/gift-registry-types.html) to return list of registry type IDs.
diff --git a/src/guides/v2.4/graphql/queries/gift-registry-types.md b/src/guides/v2.4/graphql/queries/gift-registry-types.md
index 2ed0d882836..4a9ab32efff 100644
--- a/src/guides/v2.4/graphql/queries/gift-registry-types.md
+++ b/src/guides/v2.4/graphql/queries/gift-registry-types.md
@@ -4,6 +4,8 @@ title: giftRegistryTypes query
ee_only: true
contributor_name: Zilker Technology
contributor_link: https://www.ztech.io/
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/gift-registry/queries/types/
+status: migrated
---
The `giftRegistryTypes` query returns a list of available gift registry types.
diff --git a/src/guides/v2.4/graphql/queries/gift-registry.md b/src/guides/v2.4/graphql/queries/gift-registry.md
index 96109278b78..a072340655c 100644
--- a/src/guides/v2.4/graphql/queries/gift-registry.md
+++ b/src/guides/v2.4/graphql/queries/gift-registry.md
@@ -3,6 +3,8 @@ group: graphql
title: giftRegistry query
ee_only: true
contributor_name: EY
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/gift-registry/queries/gift-registry/
+status: migrated
---
The `giftRegistry` query retrieves details about the specified gift registry. Use the [`customer` query]({{page.baseurl}}/graphql/queries/customer.html) to return a list of valid `uid` values.
diff --git a/src/guides/v2.4/graphql/queries/giftcard-account.md b/src/guides/v2.4/graphql/queries/giftcard-account.md
deleted file mode 120000
index 0e2db624430..00000000000
--- a/src/guides/v2.4/graphql/queries/giftcard-account.md
+++ /dev/null
@@ -1 +0,0 @@
-../../../v2.3/graphql/queries/giftcard-account.md
\ No newline at end of file
diff --git a/src/guides/v2.4/graphql/queries/giftcard-account.md b/src/guides/v2.4/graphql/queries/giftcard-account.md
new file mode 100644
index 00000000000..7ade4057e8a
--- /dev/null
+++ b/src/guides/v2.4/graphql/queries/giftcard-account.md
@@ -0,0 +1,80 @@
+---
+group: graphql
+title: giftCardAccount query
+ee_only: True
+redirect from:
+ - /guides/v2.3/graphql/reference/quote-giftcard-account.html
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/customer/queries/giftcard-account/
+status: migrated
+---
+
+The `giftCardAccount` query returns information for a specific gift card.
+
+## Syntax
+
+ `giftCardAccount(code: String!): GiftCardAccount`
+
+## Example usage
+
+The following example returns information about the `01PNC9L76H4H` gift card code.
+
+**Request:**
+
+```graphql
+query {
+ giftCardAccount(input: {gift_card_code: "01PNC9L76H4H"}){
+ code
+ balance {
+ currency
+ value
+ }
+ expiration_date
+ }
+}
+```
+
+**Response:**
+
+```json
+{
+ "data": {
+ "giftCardAccount": {
+ "code": "01PNC9L76H4H",
+ "balance": {
+ "currency": "USD",
+ "value": 25
+ },
+ "expiration_date": null
+ }
+ }
+}
+```
+
+## Input attributes
+
+The `giftCardAccount` query requires the `gift_card_code`.
+
+### GiftCardAccount object {#GiftCardAccount}
+
+The `GiftCardAccount` object must contain the following attribute:
+
+Attribute | Data Type | Description
+--- | --- | ---
+`gift_card_code` | String! | The gift card code
+
+## Output attributes
+
+The `GiftCardAccount` object returns the following attributes:
+
+Attribute | Data Type | Description
+--- | --- | ---
+`balance` | Money | Returns the currency and remaining balance of the gift card
+`code` | String | Returns the gift card code
+`expiration_date` | String | Returns the date when the gift card expires, if any
+
+## Errors
+
+Error | Description
+--- | ---
+`Gift card not found` | The specified `gift_card_code` value does not exist in the `giftcardaccount` table, or the full amount has already been redeemed.
+`Field GiftCardAccountInput.gift_card_code of required type String! was not provided` | The value specified in the `GiftCardAccountInput.gift_card_code` argument is empty.
diff --git a/src/guides/v2.4/graphql/queries/index.md b/src/guides/v2.4/graphql/queries/index.md
index 3091dbd39f2..d23ea8f6e1d 100644
--- a/src/guides/v2.4/graphql/queries/index.md
+++ b/src/guides/v2.4/graphql/queries/index.md
@@ -4,6 +4,8 @@ title: Using queries
redirect_from:
- /guides/v2.3/graphql/search-pagination.html
- /guides/v2.3/graphql/queries.html
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/usage/
+status: migrated
---
A GraphQL query retrieves data from the Magento server in a similar manner as a REST GET call. The current set of Magento GraphQL queries allow a mobile app or browser to render a wide variety of information, including the following:
diff --git a/src/guides/v2.4/graphql/queries/is-company-admin-email-available.md b/src/guides/v2.4/graphql/queries/is-company-admin-email-available.md
index 040ff3fdc17..76e91c40633 100644
--- a/src/guides/v2.4/graphql/queries/is-company-admin-email-available.md
+++ b/src/guides/v2.4/graphql/queries/is-company-admin-email-available.md
@@ -2,6 +2,8 @@
group: graphql
title: isCompanyAdminEmailAvailable query
b2b_only: true
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/b2b/company/queries/is-company-admin-email-available/
+status: migrated
---
The `isCompanyAdminEmailAvailable` query checks whether the specified email can be used to create a company administrator account. If the email matches an existing customer or another company administrator account, the query returns a `false` value. A value of `true` indicates the email address can be used to create a company administrator account.
diff --git a/src/guides/v2.4/graphql/queries/is-company-email-available.md b/src/guides/v2.4/graphql/queries/is-company-email-available.md
index c687083e8ee..35a70cb5761 100644
--- a/src/guides/v2.4/graphql/queries/is-company-email-available.md
+++ b/src/guides/v2.4/graphql/queries/is-company-email-available.md
@@ -2,6 +2,8 @@
group: graphql
title: isCompanyEmailAvailable query
b2b_only: true
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/b2b/company/queries/is-company-email-available/
+status: migrated
---
The `isCompanyEmailAvailable` query checks whether the specified email is valid for company registration. The specified email can be the same as an existing customer or company administrator. If the email matches an existing company email, the query returns a `false` value.
diff --git a/src/guides/v2.4/graphql/queries/is-company-role-name-available.md b/src/guides/v2.4/graphql/queries/is-company-role-name-available.md
index 3b531fb283e..596fe95e7a4 100644
--- a/src/guides/v2.4/graphql/queries/is-company-role-name-available.md
+++ b/src/guides/v2.4/graphql/queries/is-company-role-name-available.md
@@ -4,6 +4,8 @@ title: isCompanyRoleNameAvailable query
contributor_name: Atwix
contributor_link: https://www.atwix.com/
b2b_only: true
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/b2b/company/queries/is-company-role-name-available/
+status: migrated
---
The `isCompanyRoleNameAvailable` query checks whether a company role name is valid for creating into a company.
diff --git a/src/guides/v2.4/graphql/queries/is-company-user-email-available.md b/src/guides/v2.4/graphql/queries/is-company-user-email-available.md
index 2366bdfd987..2324973379f 100644
--- a/src/guides/v2.4/graphql/queries/is-company-user-email-available.md
+++ b/src/guides/v2.4/graphql/queries/is-company-user-email-available.md
@@ -2,6 +2,8 @@
group: graphql
title: isCompanyUserEmailAvailable query
b2b_only: true
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/b2b/company/queries/is-company-user-email-available/
+status: migrated
---
The `isCompanyUserEmailAvailable` query checks whether an email is valid for registering a company user. The query returns a `false` value if the specified email matches the email of an existing customer or a company administrator.
diff --git a/src/guides/v2.4/graphql/queries/is-email-available.md b/src/guides/v2.4/graphql/queries/is-email-available.md
deleted file mode 120000
index c223077f5b6..00000000000
--- a/src/guides/v2.4/graphql/queries/is-email-available.md
+++ /dev/null
@@ -1 +0,0 @@
-../../../v2.3/graphql/queries/is-email-available.md
\ No newline at end of file
diff --git a/src/guides/v2.4/graphql/queries/is-email-available.md b/src/guides/v2.4/graphql/queries/is-email-available.md
new file mode 100644
index 00000000000..efcf8c09f2d
--- /dev/null
+++ b/src/guides/v2.4/graphql/queries/is-email-available.md
@@ -0,0 +1,61 @@
+---
+group: graphql
+title: isEmailAvailable query
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/b2b/company/queries/is-company-email-available/
+status: migrated
+---
+
+The `isEmailAvailable` query checks whether the specified email has already been used to create a customer account. A value of `true` indicates the email address is available, and the customer can use the email address to create an account.
+
+## Syntax
+
+`{isEmailAvailable (email): {IsEmailAvailableOutput}}`
+
+## Example usage
+
+The following example checks whether the email address `customer@example.com` is available to create a customer account.
+
+**Request:**
+
+```graphql
+{
+ isEmailAvailable(email: "customer@example.com") {
+ is_email_available
+ }
+}
+```
+
+**Response:**
+
+```json
+{
+ "data": {
+ "isEmailAvailable": {
+ "is_email_available": true
+ }
+ }
+}
+```
+
+## Input attribute
+
+Attribute | Data Type | Description
+--- | --- | ---
+`email` | String! | The email address to check
+
+## Output attribute
+
+Attribute | Data Type | Description
+--- | --- | ---
+`is_email_available` | Boolean | A value of `true` indicates the email address is available, and the customer can use the email address to create an account
+
+## Related topics
+
+[customer query]({{page.baseurl}}/graphql/queries/customer.html)
+
+## Errors
+
+Error | Description
+--- | ---
+`Email is invalid` | The given email-id is not in a proper format.
+`Field isEmailAvailable.email of required type String! was not provided` | The value specified in the `isEmailAvailable.email` argument is empty.
diff --git a/src/guides/v2.4/graphql/queries/negotiable-quote.md b/src/guides/v2.4/graphql/queries/negotiable-quote.md
index 0844d146ea5..a8735f3c98b 100644
--- a/src/guides/v2.4/graphql/queries/negotiable-quote.md
+++ b/src/guides/v2.4/graphql/queries/negotiable-quote.md
@@ -1,7 +1,9 @@
---
group: graphql
title: negotiableQuote query
-b2b_only: true
+b2b_only: true
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/b2b/negotiable-quote/queries/quote/
+status: migrated
---
The `negotiableQuote` query retrieves details about the specified negotiable quote. Use the [`negotiableQuotes` query]({{page.baseurl}}/graphql/queries/negotiable-quotes.html) to return a list of valid `uid` values.
diff --git a/src/guides/v2.4/graphql/queries/negotiable-quotes.md b/src/guides/v2.4/graphql/queries/negotiable-quotes.md
index 835dd961c57..495e01b46a1 100644
--- a/src/guides/v2.4/graphql/queries/negotiable-quotes.md
+++ b/src/guides/v2.4/graphql/queries/negotiable-quotes.md
@@ -1,7 +1,9 @@
---
group: graphql
title: negotiableQuotes query
-b2b_only: true
+b2b_only: true
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/b2b/negotiable-quote/queries/quotes/
+status: migrated
---
The `negotiableQuotes` query returns a list of negotiable quotes that can be viewed by the logged-in customer, including quotes created by the customer or by subordinates in the company hierarchy.
diff --git a/src/guides/v2.4/graphql/queries/pickup-locations.md b/src/guides/v2.4/graphql/queries/pickup-locations.md
index b6c211a800e..8c693fb5711 100644
--- a/src/guides/v2.4/graphql/queries/pickup-locations.md
+++ b/src/guides/v2.4/graphql/queries/pickup-locations.md
@@ -3,6 +3,8 @@ group: graphql
title: pickupLocations query
contributor_name: Oleksandr Kravchuk
contributor_link: https://github.com/swnsma
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/cart/queries/pickup-locations/
+status: migrated
---
Use the `pickupLocations` query to retrieve a list of available pickup locations.
diff --git a/src/guides/v2.4/graphql/queries/product-review-ratings-metadata.md b/src/guides/v2.4/graphql/queries/product-review-ratings-metadata.md
index b96031381af..f73cc568c0d 100644
--- a/src/guides/v2.4/graphql/queries/product-review-ratings-metadata.md
+++ b/src/guides/v2.4/graphql/queries/product-review-ratings-metadata.md
@@ -1,6 +1,8 @@
---
group: graphql
title: productReviewRatingsMetadata query
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/products/queries/product-review-ratings-metadata/
+status: migrated
---
The `productReviewRatingsMetadata` query returns the active ratings attributes and the values each rating can have. In Luma, these values are one star through five stars.
diff --git a/src/guides/v2.4/graphql/queries/products.md b/src/guides/v2.4/graphql/queries/products.md
index 9b5b0880c51..069f4e147de 100644
--- a/src/guides/v2.4/graphql/queries/products.md
+++ b/src/guides/v2.4/graphql/queries/products.md
@@ -1,6 +1,8 @@
---
group: graphql
title: products query
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/products/queries/products/
+status: migrated
---
The `products` query allows you to search for catalog items.
diff --git a/src/guides/v2.4/graphql/queries/recaptcha-v3-config.md b/src/guides/v2.4/graphql/queries/recaptcha-v3-config.md
index d197b3fa770..46931a704df 100644
--- a/src/guides/v2.4/graphql/queries/recaptcha-v3-config.md
+++ b/src/guides/v2.4/graphql/queries/recaptcha-v3-config.md
@@ -2,6 +2,8 @@
group: graphql
title: recaptchaV3Config query
pwa_only: True
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/store/queries/recaptcha-v3-config/
+status: migrated
---
The `recaptchaV3Config` query returns information about the reCaptcha V3 configuration.
diff --git a/src/guides/v2.4/graphql/queries/route.md b/src/guides/v2.4/graphql/queries/route.md
index de46f0cf9e5..25d98bc69bf 100644
--- a/src/guides/v2.4/graphql/queries/route.md
+++ b/src/guides/v2.4/graphql/queries/route.md
@@ -1,6 +1,8 @@
---
group: graphql
title: routes query
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/products/queries/route/
+status: migrated
---
A merchant can reconfigure (rewrite) the URL to any product, category, or CMS page. When the rewrite goes into effect, any links that point to the previous URL are redirected to the new address.
diff --git a/src/guides/v2.4/graphql/queries/store-config.md b/src/guides/v2.4/graphql/queries/store-config.md
index 740e0166b62..29919a19cda 100644
--- a/src/guides/v2.4/graphql/queries/store-config.md
+++ b/src/guides/v2.4/graphql/queries/store-config.md
@@ -1,6 +1,8 @@
---
group: graphql
title: storeConfig query
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/store/queries/store-config/
+status: migrated
---
The `storeConfig` query defines information about a store's configuration. You can query a non-default store by [changing the header]({{ page.baseurl }}/graphql/send-request.html) in your GraphQL request.
diff --git a/src/guides/v2.4/graphql/queries/url-resolver.md b/src/guides/v2.4/graphql/queries/url-resolver.md
index 3022f670900..c0b97764102 100644
--- a/src/guides/v2.4/graphql/queries/url-resolver.md
+++ b/src/guides/v2.4/graphql/queries/url-resolver.md
@@ -1,6 +1,8 @@
---
group: graphql
title: urlResolver query
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/products/queries/url-resolver/
+status: migrated
---
{:.bs-callout-warning}
diff --git a/src/guides/v2.4/graphql/queries/wishlist.md b/src/guides/v2.4/graphql/queries/wishlist.md
deleted file mode 120000
index 43f9b091f29..00000000000
--- a/src/guides/v2.4/graphql/queries/wishlist.md
+++ /dev/null
@@ -1 +0,0 @@
-../../../v2.3/graphql/queries/wishlist.md
\ No newline at end of file
diff --git a/src/guides/v2.4/graphql/queries/wishlist.md b/src/guides/v2.4/graphql/queries/wishlist.md
new file mode 100644
index 00000000000..84b69c472c6
--- /dev/null
+++ b/src/guides/v2.4/graphql/queries/wishlist.md
@@ -0,0 +1,101 @@
+---
+group: graphql
+title: wishlist query
+redirect_from:
+ - /guides/v2.3/graphql/reference/wishlist.html
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/wishlist/queries/wishlist/
+status: migrated
+---
+
+{:.bs-callout-warning}
+The `wishlist` query has been deprecated. Wish list information is now provided by the [customer]({{page.baseurl}}/graphql/queries/customer.html) query.
+
+Use the `wishlist` query to retrieve information about a customer's wish list. [Authorization tokens]({{page.baseurl}}/graphql/authorization-tokens.html) describes how to supply an authorization token for a specific customer.
+
+## Syntax
+
+`wishlist: WishlistOutput`
+
+## Example usage
+
+The following query returns the customer's wish list:
+
+**Request:**
+
+```graphql
+{
+ wishlist {
+ items_count
+ name
+ sharing_code
+ updated_at
+ items {
+ id
+ qty
+ description
+ added_at
+ product {
+ sku
+ name
+ }
+ }
+ }
+}
+```
+
+**Response:**
+
+```json
+{
+ "data": {
+ "wishlist": {
+ "items_count": 2,
+ "name": "Wish List",
+ "sharing_code": "KAXDj0HlM7Y2s58mllsVhSJvRj4fWIZj",
+ "updated_at": "2019-02-13 22:47:45",
+ "items": [
+ {
+ "id": 1,
+ "qty": 1,
+ "description": "My first priority",
+ "added_at": "2019-02-20 14:38:02",
+ "product": {
+ "sku": "MJ09",
+ "name": "Taurus Elements Shell"
+ }
+ },
+ {
+ "id": 2,
+ "qty": 1,
+ "description": null,
+ "added_at": "2019-02-20 14:38:28",
+ "product": {
+ "sku": "MSH11",
+ "name": "Arcadio Gym Short"
+ }
+ }
+ ]
+ }
+ }
+}
+```
+
+## Output attributes
+
+Attribute | Data type | Description
+--- | --- | ---
+`items` | [WishlistItem](#wishlistitem) | An array of items in the customer's wish list
+`items_count` | Int | The number of items in the wish list
+`name` | String | When multiple wish lists are enabled, the name the customer assigns to the wish list
+`sharing_code` | String | An encrypted code that Magento uses to link to the wish list
+`updated_at` | String | The time of the last modification to the wish list
+
+### Wish list item attributes {#wishlistitem}
+
+Attribute | Data type | Description
+--- | --- | ---
+`added_at` | String | The time when the customer added the item to the wish list
+`description` | String | The customer's comment about this item
+`id` | Int | The wish list item ID
+`product` | [ProductInterface]({{ page.baseurl }}/graphql/interfaces/product-interface.html) | The ProductInterface contains attributes that are common to all types of products. Note that descriptions may not be available for custom and EAV attributes
+`qty` | Float | The quantity of this wish list item
diff --git a/src/guides/v2.4/graphql/release-notes.md b/src/guides/v2.4/graphql/release-notes.md
index cc4bd99a796..9b1bfe1c7bb 100644
--- a/src/guides/v2.4/graphql/release-notes.md
+++ b/src/guides/v2.4/graphql/release-notes.md
@@ -1,6 +1,8 @@
---
group: graphql
title: Release Notes
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/release-notes/
+status: migrated
---
{:.bs-callout-info}
diff --git a/src/guides/v2.4/graphql/security-configuration.md b/src/guides/v2.4/graphql/security-configuration.md
index 32546df3ba5..6987f7162a4 100644
--- a/src/guides/v2.4/graphql/security-configuration.md
+++ b/src/guides/v2.4/graphql/security-configuration.md
@@ -1,6 +1,8 @@
---
group: graphql
title: GraphQL security configuration
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/usage/security-configuration/
+status: migrated
---
The Framework and `GraphQl` module `di.xml` files define several security-related configuration values that you should review to ensure they align with types of mutations and queries that you run.
diff --git a/src/guides/v2.4/graphql/send-request.md b/src/guides/v2.4/graphql/send-request.md
index 828f2525ad6..26027992f5c 100644
--- a/src/guides/v2.4/graphql/send-request.md
+++ b/src/guides/v2.4/graphql/send-request.md
@@ -1,6 +1,8 @@
---
group: graphql
title: GraphQL requests
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/usage/headers/
+status: migrated
---
Magento GraphQL supports the HTTP GET and POST methods. You can send a query as a GET or POST request. Mutations must be POST requests. You can optionally send a GET query request in a URL. In these requests, you must specify `query` as the query string. You might need to encode the query, as shown below:
diff --git a/src/guides/v2.4/graphql/tutorials/checkout/checkout-add-product-to-cart.md b/src/guides/v2.4/graphql/tutorials/checkout/checkout-add-product-to-cart.md
deleted file mode 120000
index ddfa6d87854..00000000000
--- a/src/guides/v2.4/graphql/tutorials/checkout/checkout-add-product-to-cart.md
+++ /dev/null
@@ -1 +0,0 @@
-../../../../v2.3/graphql/tutorials/checkout/checkout-add-product-to-cart.md
\ No newline at end of file
diff --git a/src/guides/v2.4/graphql/tutorials/checkout/checkout-add-product-to-cart.md b/src/guides/v2.4/graphql/tutorials/checkout/checkout-add-product-to-cart.md
new file mode 100644
index 00000000000..35088b77ec4
--- /dev/null
+++ b/src/guides/v2.4/graphql/tutorials/checkout/checkout-add-product-to-cart.md
@@ -0,0 +1,169 @@
+---
+layout: tutorial
+group: graphql
+title: Step 3. Add products to the cart
+subtitle: GraphQL checkout tutorial
+level3_subgroup: graphql-checkout
+return_to:
+ title: GraphQL Overview
+ url: graphql/index.html
+menu_order: 30
+functional_areas:
+ - Integration
+contributor_name: Atwix
+contributor_link: https://www.atwix.com/
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/tutorials/checkout/add-product-to-cart/
+status: migrated
+---
+
+GraphQL supports all product types, but this tutorial only demonstrates how to add a simple product and a virtual product to the shopping cart. You can find more details and examples in the following topics:
+
+- [Bundle products]({{ page.baseurl }}/graphql/mutations/add-bundle-products.html)
+- [Configurable products]({{ page.baseurl }}/graphql/mutations/add-configurable-products.html)
+- [Downloadable products]({{ page.baseurl }}/graphql/mutations/add-downloadable-products.html)
+- [Simple and grouped products]({{ page.baseurl }}/graphql/mutations/add-simple-products.html)
+- [Virtual products]({{ page.baseurl }}/graphql/mutations/add-virtual-products.html)
+
+[Product interface implementations]({{ page.baseurl }}/graphql/interfaces/product-interface-implementations.html) also describes how to create queries that access product interfaces.
+
+Use the `updateCartItems` mutation to update shopping cart items and `removeItemFromCart` to remove a product from the shopping cart.
+
+{:.bs-callout-info}
+If you add a product to the shopping cart as a registered customer, be sure to send the customer's authorization token in the `Authorization` parameter of the header. See [Authorization tokens]({{page.baseurl}}/graphql/authorization-tokens.html) for more details.
+
+## Add a simple product into the shopping cart
+
+The following mutation adds a simple product into the shopping cart.
+
+Replace `{ CART_ID }` with the unique shopping cart ID from [Step 2. Create empty cart]({{ page.baseurl }}/graphql/tutorials/checkout/checkout-add-product-to-cart.html).
+
+In this example, we will add the Aim Analog Watch (SKU 24-MG04) from the default Luma catalog to the cart. The SKU identifies the product to be added.
+
+**Request:**
+
+```graphql
+mutation {
+ addSimpleProductsToCart(
+ input: {
+ cart_id: "{ CART_ID }"
+ cart_items: [
+ {
+ data: {
+ quantity: 1
+ sku: "24-MG04"
+ }
+ }
+ ]
+ }
+ ) {
+ cart {
+ items {
+ id
+ product {
+ sku
+ stock_status
+ }
+ quantity
+ }
+ }
+ }
+}
+```
+
+**Response:**
+
+```json
+{
+ "data": {
+ "addSimpleProductsToCart": {
+ "cart": {
+ "items": [
+ {
+ "id": "5",
+ "product": {
+ "sku": "24-MG04",
+ "stock_status": "IN_STOCK"
+ },
+ "quantity": 1
+ }
+ ]
+ }
+ }
+ }
+}
+```
+
+## Add a virtual product into the shopping cart
+
+The following mutation adds a virtual product into the shopping cart.
+In this example, we add the Beginner's Yoga video downloadable product (SKU 240-LV04).
+
+**Request:**
+
+```graphql
+mutation {
+ addVirtualProductsToCart(
+ input: {
+ cart_id: "{ CART_ID }"
+ cart_items: [
+ {
+ data: {
+ quantity: 1
+ sku: "240-LV04"
+ }
+ }
+ ]
+ }
+ ) {
+ cart {
+ items {
+ id
+ product {
+ sku
+ stock_status
+ }
+ quantity
+ }
+ }
+ }
+}
+```
+
+**Response:**
+
+```json
+{
+ "data": {
+ "addVirtualProductsToCart": {
+ "cart": {
+ "items": [
+ {
+ "id": "5",
+ "product": {
+ "sku": "24-MG04",
+ "stock_status": "IN_STOCK"
+ },
+ "quantity": 1
+ },
+ {
+ "id": "6",
+ "product": {
+ "sku": "240-LV04",
+ "stock_status": "IN_STOCK"
+ },
+ "quantity": 1
+ }
+ ]
+ }
+ }
+ }
+}
+```
+
+The response lists all items currently in the cart, including the just-added video download.
+
+## Verify this step {#verify-step}
+
+1. Sign in as a customer to the website using the email `john.doe@example.com` and password `b1b2b3l@w+`.
+
+1. Go to the shopping cart. All the items you added are displayed.
diff --git a/src/guides/v2.4/graphql/tutorials/checkout/checkout-billing-address.md b/src/guides/v2.4/graphql/tutorials/checkout/checkout-billing-address.md
deleted file mode 120000
index 56078d8be81..00000000000
--- a/src/guides/v2.4/graphql/tutorials/checkout/checkout-billing-address.md
+++ /dev/null
@@ -1 +0,0 @@
-../../../../v2.3/graphql/tutorials/checkout/checkout-billing-address.md
\ No newline at end of file
diff --git a/src/guides/v2.4/graphql/tutorials/checkout/checkout-billing-address.md b/src/guides/v2.4/graphql/tutorials/checkout/checkout-billing-address.md
new file mode 100644
index 00000000000..cc1d140504f
--- /dev/null
+++ b/src/guides/v2.4/graphql/tutorials/checkout/checkout-billing-address.md
@@ -0,0 +1,116 @@
+---
+layout: tutorial
+group: graphql
+title: Step 5. Set billing address
+subtitle: GraphQL checkout tutorial
+level3_subgroup: graphql-checkout
+return_to:
+ title: GraphQL Overview
+ url: graphql/index.html
+menu_order: 50
+functional_areas:
+ - Integration
+contributor_name: Atwix
+contributor_link: https://www.atwix.com/
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/tutorials/checkout/set-billing-address/
+status: migrated
+---
+
+{:.bs-callout-tip}
+You must always set the billing address to place an order.
+
+Use the [setBillingAddressOnCart]({{ page.baseurl }}/graphql/mutations/set-billing-address.html) mutation to set a billing address.
+
+## Add a billing address to the cart
+
+Similar to the shipping address, add a billing address to the cart. `{ CART_ID }` is the unique shopping cart ID from [Step 2. Create empty cart]({{ page.baseurl }}/graphql/tutorials/checkout/checkout-add-product-to-cart.html). The street address is also different, so we can see that different addresses are being created.
+
+Send the customer's authorization token in the `Authorization` parameter of the header. See [Authorization tokens]({{page.baseurl}}/graphql/authorization-tokens.html) for more information.
+
+**Request:**
+
+```graphql
+mutation {
+ setBillingAddressOnCart(
+ input: {
+ cart_id: "{ CART_ID }"
+ billing_address: {
+ address: {
+ firstname: "John"
+ lastname: "Doe"
+ company: "Company Name"
+ street: ["64 Strawberry Dr", "Beverly Hills"]
+ city: "Los Angeles"
+ region: "CA"
+ region_id: 12
+ postcode: "90210"
+ country_code: "US"
+ telephone: "123-456-0000"
+ save_in_address_book: true
+ }
+ }
+ }
+ ) {
+ cart {
+ billing_address {
+ firstname
+ lastname
+ company
+ street
+ city
+ region{
+ code
+ label
+ }
+ postcode
+ telephone
+ country {
+ code
+ label
+ }
+ }
+ }
+ }
+}
+```
+
+**Response:**
+
+```json
+{
+ "data": {
+ "setBillingAddressOnCart": {
+ "cart": {
+ "billing_address": {
+ "firstname": "John",
+ "lastname": "Doe",
+ "company": "Company Name",
+ "street": [
+ "64 Strawberry Dr",
+ "Beverly Hills"
+ ],
+ "city": "Los Angeles",
+ "region": {
+ "code": "CA",
+ "label": "California"
+ },
+ "postcode": "90210",
+ "telephone": "123-456-0000",
+ "country": {
+ "code": "US",
+ "label": "US"
+ }
+ }
+ }
+ }
+ }
+}
+```
+
+## Verify this step {#verify-step}
+
+1. Sign in as a customer to the website using the email `john.doe@example.com` and password `b1b2b3l@w+`.
+
+1. Go to Checkout.
+
+1. Go to the Review & Payments step. The Billing Address form is populated with the address details you entered.
diff --git a/src/guides/v2.4/graphql/tutorials/checkout/checkout-coupon.md b/src/guides/v2.4/graphql/tutorials/checkout/checkout-coupon.md
deleted file mode 120000
index 7a8fd221659..00000000000
--- a/src/guides/v2.4/graphql/tutorials/checkout/checkout-coupon.md
+++ /dev/null
@@ -1 +0,0 @@
-../../../../v2.3/graphql/tutorials/checkout/checkout-coupon.md
\ No newline at end of file
diff --git a/src/guides/v2.4/graphql/tutorials/checkout/checkout-coupon.md b/src/guides/v2.4/graphql/tutorials/checkout/checkout-coupon.md
new file mode 100644
index 00000000000..f8de3b09f40
--- /dev/null
+++ b/src/guides/v2.4/graphql/tutorials/checkout/checkout-coupon.md
@@ -0,0 +1,135 @@
+---
+layout: tutorial
+group: graphql
+title: Step 7. Apply a coupon
+subtitle: GraphQL checkout tutorial
+level3_subgroup: graphql-checkout
+return_to:
+ title: GraphQL Overview
+ url: graphql/index.html
+menu_order: 70
+functional_areas:
+ - Integration
+contributor_name: Atwix
+contributor_link: https://www.atwix.com/
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/tutorials/checkout/apply-coupon/
+status: migrated
+---
+
+Use [applyCouponToCart]({{ page.baseurl }}/graphql/mutations/apply-coupon.html) to apply a discount coupon to the specified `cart_id`.
+
+`{ CART_ID }` is the unique shopping cart ID from [Step 2. Create empty cart]({{ page.baseurl }}/graphql/tutorials/checkout/checkout-add-product-to-cart.html).
+
+`{ COUPON_CODE }` is an existing Magento coupon code. It cannot be generated with GraphQL.
+
+## Create a coupon
+
+Coupons must be generated from the Admin.
+
+Creating a coupon is described in [Coupon Codes]({{ site.user_guide_url }}/marketing/price-rules-cart-coupon.html).
+For the purpose of this tutorial, create a Cart Price Rule with:
+
+For **Rule Information**:
+
+- **Rule Name**: Watch Coupon
+- **Active**: Yes
+- **Websites**: Main Website
+- **Customer Groups**: Select all of them
+- **Coupon**: Specific Coupon
+- **Coupon Code**: Watch20
+- **Uses per Coupon**: 5
+- **Uses per Customer**: 5
+
+For **Actions**
+
+- **Apply**: Percent of product price discount
+- **Discount Amount**: 20
+
+Save this rule.
+The **Coupon Code** value is the name of the coupon the end user enters.
+To verify the coupon works, create an order with a product using guest checkout.
+When checking out, enter `Watch20` in the Apply Discount Code field and press the Apply Discount button.
+The discount should be applied in the cart.
+
+When the coupon is set up, we can apply it via GraphQL. Replace the `{ CART_ID }` with your generated ID and replace the `{ COUPON_CODE }` with `Watch20` below.
+
+For logged-in customers, send the customer's authorization token in the `Authorization` parameter of the header. See [Authorization tokens]({{page.baseurl}}/graphql/authorization-tokens.html) for more information.
+
+**Request:**
+
+```graphql
+mutation {
+ applyCouponToCart(
+ input: {
+ cart_id: "{ CART_ID }"
+ coupon_code: "{ COUPON_CODE }"
+ }
+ ) {
+ cart {
+ applied_coupons {
+ code
+ }
+ }
+ }
+}
+```
+
+**Response:**
+
+```json
+{
+ "data": {
+ "applyCouponToCart": {
+ "cart": {
+ "applied_coupons": [
+ {
+ "code": "Watch20"
+ }
+ ]
+ }
+ }
+ }
+}
+```
+
+## Verify this step {#verify-step}
+
+1. Sign in as a customer to the website using the email `john.doe@example.com` and password `b1b2b3l@w+`.
+
+1. Go to Checkout.
+
+1. The discount is displayed in the Order Summary block.
+
+## Remove a coupon
+
+Use [removeCouponFromCart]({{ page.baseurl }}/graphql/mutations/remove-coupon.html) to remove a discount coupon from the shopping cart.
+
+**Request:**
+
+```graphql
+mutation {
+ removeCouponFromCart(input: { cart_id: "{ CART_ID }" }) {
+ cart {
+ applied_coupons {
+ code
+ }
+ }
+ }
+}
+```
+
+**Response:**
+
+```json
+{
+ "data": {
+ "removeCouponFromCart": {
+ "cart": {
+ "applied_coupons": {
+ "applied_coupon": null
+ }
+ }
+ }
+ }
+}
+```
diff --git a/src/guides/v2.4/graphql/tutorials/checkout/checkout-customer.md b/src/guides/v2.4/graphql/tutorials/checkout/checkout-customer.md
deleted file mode 120000
index 511b23e4bd1..00000000000
--- a/src/guides/v2.4/graphql/tutorials/checkout/checkout-customer.md
+++ /dev/null
@@ -1 +0,0 @@
-../../../../v2.3/graphql/tutorials/checkout/checkout-customer.md
\ No newline at end of file
diff --git a/src/guides/v2.4/graphql/tutorials/checkout/checkout-customer.md b/src/guides/v2.4/graphql/tutorials/checkout/checkout-customer.md
new file mode 100644
index 00000000000..7c9d8cdba0e
--- /dev/null
+++ b/src/guides/v2.4/graphql/tutorials/checkout/checkout-customer.md
@@ -0,0 +1,102 @@
+---
+layout: tutorial
+group: graphql
+title: Step 1. Create a customer
+subtitle: GraphQL checkout tutorial
+level3_subgroup: graphql-checkout
+return_to:
+ title: GraphQL Overview
+ url: graphql/index.html
+menu_order: 10
+functional_areas:
+ - Integration
+contributor_name: Atwix
+contributor_link: https://www.atwix.com/
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/tutorials/checkout/create-customer/
+status: migrated
+---
+
+This step creates a customer account and generates an authentication token for that customer. You can skip this step if you want to perform this tutorial as a guest user.
+
+## Create a customer
+
+Use the `createCustomer` mutation to register the new customer account in the store.
+
+**Request:**
+
+```graphql
+mutation {
+ createCustomer(
+ input: {
+ firstname: "John"
+ lastname: "Doe"
+ email: "john.doe@example.com"
+ password: "b1b2b3l@w+"
+ is_subscribed: true
+ }
+ ) {
+ customer {
+ firstname
+ lastname
+ email
+ is_subscribed
+ }
+ }
+}
+```
+
+**Response:**
+
+```json
+{
+ "data": {
+ "createCustomer": {
+ "customer": {
+ "firstname": "John",
+ "lastname": "Doe",
+ "email": "john.doe@example.com",
+ "is_subscribed": true
+ }
+ }
+ }
+}
+```
+
+The [`createCustomer`]({{ page.baseurl }}/graphql/mutations/create-customer.html) mutation describes additional parameters.
+
+## Generate an authentication token for the customer
+
+To place an order as a customer, you must obtain an authorization token by calling the `generateCustomerToken` mutation. You must include the customer's email and password as input.
+
+**Request:**
+
+```graphql
+mutation {
+ generateCustomerToken(email: "john.doe@example.com", password: "b1b2b3l@w+") {
+ token
+ }
+}
+```
+
+**Response:**
+
+```json
+{
+ "data": {
+ "generateCustomerToken": {
+ "token": "zuo7zor5jfldft2nmu2gtylnm8ui7e8t" #gitleaks:allow
+ }
+ }
+}
+```
+
+## Specify an Authorization header
+
+To send requests on behalf of the customer, you must supply the generated token as a header in your GraphQL browser.
+The name of the header is `Authorization` and the value is `Bearer `.
+
+[Authorization tokens]({{page.baseurl}}/graphql/authorization-tokens.html) describes the mutation further.
+
+## Verify this step {#verify-step}
+
+Sign in as a customer to the website using the email `john.doe@example.com` and password `b1b2b3l@w+`. You should be successfully logged in.
diff --git a/src/guides/v2.4/graphql/tutorials/checkout/checkout-payment-method.md b/src/guides/v2.4/graphql/tutorials/checkout/checkout-payment-method.md
deleted file mode 120000
index b5dd0f3b50e..00000000000
--- a/src/guides/v2.4/graphql/tutorials/checkout/checkout-payment-method.md
+++ /dev/null
@@ -1 +0,0 @@
-../../../../v2.3/graphql/tutorials/checkout/checkout-payment-method.md
\ No newline at end of file
diff --git a/src/guides/v2.4/graphql/tutorials/checkout/checkout-payment-method.md b/src/guides/v2.4/graphql/tutorials/checkout/checkout-payment-method.md
new file mode 100644
index 00000000000..31c4ae3fab6
--- /dev/null
+++ b/src/guides/v2.4/graphql/tutorials/checkout/checkout-payment-method.md
@@ -0,0 +1,107 @@
+---
+layout: tutorial
+group: graphql
+title: Step 9. Set the payment method
+subtitle: GraphQL checkout tutorial
+level3_subgroup: graphql-checkout
+return_to:
+ title: GraphQL Overview
+ url: graphql/index.html
+menu_order: 90
+functional_areas:
+ - Integration
+contributor_name: Atwix
+contributor_link: https://www.atwix.com/
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/tutorials/checkout/set-payment-method/
+status: migrated
+---
+
+{:.bs-callout-tip}
+You must always set a payment method for an order.
+
+Use the following `cart` query to determine which payment methods which are available for your order.
+
+`{ CART_ID }` is the unique shopping cart ID from [Step 2. Create empty cart]({{ page.baseurl }}/graphql/tutorials/checkout/checkout-add-product-to-cart.html).
+
+For logged-in customers, send the customer's authorization token in the `Authorization` parameter of the header. See [Authorization tokens]({{page.baseurl}}/graphql/authorization-tokens.html) for more information.
+
+**Request:**
+
+```graphql
+query {
+ cart(cart_id: "{ CART_ID }") {
+ available_payment_methods {
+ code
+ title
+ }
+ }
+}
+```
+
+**Response:**
+
+```json
+{
+ "data": {
+ "cart": {
+ "available_payment_methods": [
+ {
+ "code": "checkmo",
+ "title": "Check / Money order"
+ }
+ ]
+ }
+ }
+}
+```
+
+### Set payment method on cart {#setPaymentMethodOnCart}
+
+Use the `setPaymentMethodOnCart` mutation to set the payment method for your order. The value `checkmo` ("Check / Money order" payment method code) was returned in the query.
+
+Send the customer's authorization token in the `Authorization` parameter of the header. See [Authorization tokens]({{page.baseurl}}/graphql/authorization-tokens.html) for more information.
+
+**Request:**
+
+```graphql
+mutation {
+ setPaymentMethodOnCart(input: {
+ cart_id: "{ CART_ID }"
+ payment_method: {
+ code: "checkmo"
+ }
+ }) {
+ cart {
+ selected_payment_method {
+ code
+ }
+ }
+ }
+}
+```
+
+**Response:**
+
+If the operation is successful, the response contains the code of the selected payment method.
+
+```json
+{
+ "data": {
+ "setPaymentMethodOnCart": {
+ "cart": {
+ "selected_payment_method": {
+ "code": "checkmo"
+ }
+ }
+ }
+ }
+}
+```
+
+## Verify this step {#verify-step}
+
+1. Sign in as a customer to the website using the email `john.doe@example.com` and password `b1b2b3l@w+`.
+
+1. Go to Checkout.
+
+1. The selected payment method is displayed in the Payment Method section on the Review & Payments step.
diff --git a/src/guides/v2.4/graphql/tutorials/checkout/checkout-place-order.md b/src/guides/v2.4/graphql/tutorials/checkout/checkout-place-order.md
deleted file mode 120000
index 9eaf3d88d5b..00000000000
--- a/src/guides/v2.4/graphql/tutorials/checkout/checkout-place-order.md
+++ /dev/null
@@ -1 +0,0 @@
-../../../../v2.3/graphql/tutorials/checkout/checkout-place-order.md
\ No newline at end of file
diff --git a/src/guides/v2.4/graphql/tutorials/checkout/checkout-place-order.md b/src/guides/v2.4/graphql/tutorials/checkout/checkout-place-order.md
new file mode 100644
index 00000000000..5117a71c6f1
--- /dev/null
+++ b/src/guides/v2.4/graphql/tutorials/checkout/checkout-place-order.md
@@ -0,0 +1,55 @@
+---
+layout: tutorial
+group: graphql
+title: Step 10. Place the order
+subtitle: GraphQL checkout tutorial
+level3_subgroup: graphql-checkout
+return_to:
+ title: GraphQL Overview
+ url: graphql/index.html
+menu_order: 100
+functional_areas:
+ - Integration
+contributor_name: Atwix
+contributor_link: https://www.atwix.com/
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/tutorials/checkout/place-order/
+status: migrated
+---
+
+The `placeOrder` mutation places an order.
+
+`{ CART_ID }` is the unique shopping cart ID from [Step 2. Create empty cart]({{ page.baseurl }}/graphql/tutorials/checkout/checkout-add-product-to-cart.html).
+
+Send the customer's authorization token in the `Authorization` parameter of the header. See [Authorization tokens]({{page.baseurl}}/graphql/authorization-tokens.html) for more information.
+
+**Request:**
+
+```graphql
+mutation {
+ placeOrder(input: {cart_id: "{ CART_ID }"}) {
+ order {
+ order_number
+ }
+ }
+}
+```
+
+**Response:**
+
+```json
+{
+ "data": {
+ "placeOrder": {
+ "order": {
+ "order_number": "000000001"
+ }
+ }
+ }
+}
+```
+
+## Verify this step {#verify-step}
+
+1. Sign in as a customer to the website using the email `john.doe@example.com` and password `b1b2b3l@w+`.
+
+1. Go to **My Account** > **My Orders**. The order you created is displayed. The order is also displayed on the Orders grid (**Sales** > **Orders**) in the Admin.
diff --git a/src/guides/v2.4/graphql/tutorials/checkout/checkout-quote-email.md b/src/guides/v2.4/graphql/tutorials/checkout/checkout-quote-email.md
deleted file mode 120000
index 31a16a35c28..00000000000
--- a/src/guides/v2.4/graphql/tutorials/checkout/checkout-quote-email.md
+++ /dev/null
@@ -1 +0,0 @@
-../../../../v2.3/graphql/tutorials/checkout/checkout-quote-email.md
\ No newline at end of file
diff --git a/src/guides/v2.4/graphql/tutorials/checkout/checkout-quote-email.md b/src/guides/v2.4/graphql/tutorials/checkout/checkout-quote-email.md
new file mode 100644
index 00000000000..3aa2acba4b9
--- /dev/null
+++ b/src/guides/v2.4/graphql/tutorials/checkout/checkout-quote-email.md
@@ -0,0 +1,57 @@
+---
+layout: tutorial
+group: graphql
+title: Step 8. Set email on the cart (guest customers only)
+subtitle: GraphQL checkout tutorial
+level3_subgroup: graphql-checkout
+return_to:
+ title: GraphQL Overview
+ url: graphql/index.html
+menu_order: 80
+functional_areas:
+ - Integration
+contributor_name: Atwix
+contributor_link: https://www.atwix.com/
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/tutorials/checkout/set-email-address/
+status: migrated
+---
+
+{:.bs-callout-tip}
+Skip this step if you placed the order as a registered customer.
+
+If you place an order as a guest user, you must set a quote email address. Use the `setGuestEmailOnCart` mutation query for that.
+
+`{ CART_ID }` is the unique shopping cart ID from [Step 2. Create empty cart]({{ page.baseurl }}/graphql/tutorials/checkout/checkout-add-product-to-cart.html).
+
+**Request:**
+
+```graphql
+mutation {
+ setGuestEmailOnCart(input: {
+ cart_id: "{ CART_ID }"
+ email: "guest@example.com"
+ }) {
+ cart {
+ email
+ }
+ }
+}
+```
+
+**Response:**
+
+```json
+{
+ "data": {
+ "setGuestEmailOnCart": {
+ "cart": {
+ "email": "guest@example.com"
+ }
+ }
+ }
+}
+```
+
+## Verify this step {#verify-step}
+
+There are no additional verification steps. `quote`.`customer_email` is displayed for administrator on back-end side.
diff --git a/src/guides/v2.4/graphql/tutorials/checkout/checkout-shipping-address.md b/src/guides/v2.4/graphql/tutorials/checkout/checkout-shipping-address.md
deleted file mode 120000
index 82715c4f308..00000000000
--- a/src/guides/v2.4/graphql/tutorials/checkout/checkout-shipping-address.md
+++ /dev/null
@@ -1 +0,0 @@
-../../../../v2.3/graphql/tutorials/checkout/checkout-shipping-address.md
\ No newline at end of file
diff --git a/src/guides/v2.4/graphql/tutorials/checkout/checkout-shipping-address.md b/src/guides/v2.4/graphql/tutorials/checkout/checkout-shipping-address.md
new file mode 100644
index 00000000000..4dbfe2f8b9d
--- /dev/null
+++ b/src/guides/v2.4/graphql/tutorials/checkout/checkout-shipping-address.md
@@ -0,0 +1,145 @@
+---
+layout: tutorial
+group: graphql
+title: Step 4. Set the shipping address
+subtitle: GraphQL checkout tutorial
+level3_subgroup: graphql-checkout
+return_to:
+ title: GraphQL Overview
+ url: graphql/index.html
+menu_order: 40
+functional_areas:
+ - Integration
+contributor_name: Atwix
+contributor_link: https://www.atwix.com/
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/tutorials/checkout/set-shipping-address/
+status: migrated
+---
+
+Use the [setShippingAddressesOnCart]({{ page.baseurl }}/graphql/mutations/set-shipping-address.html) mutation to set a shipping address.
+
+## Add shipping address to the cart
+
+In this step, we use the `setShippingAddressesOnCart` mutation to add a shipping address to the cart.
+
+If using guest checkout, run the following example.
+
+If using a logged in customer, send the customer's authorization token in the `Authorization` parameter of the header. See [Authorization tokens]({{page.baseurl}}/graphql/authorization-tokens.html) for more information.
+
+**Request:**
+
+```graphql
+mutation {
+ setShippingAddressesOnCart(
+ input: {
+ cart_id: "{ CART_ID }"
+ shipping_addresses: [
+ {
+ address: {
+ firstname: "John"
+ lastname: "Doe"
+ company: "Company Name"
+ street: ["3320 N Crescent Dr", "Beverly Hills"]
+ city: "Los Angeles"
+ region: "CA"
+ region_id: 12
+ postcode: "90210"
+ country_code: "US"
+ telephone: "123-456-0000"
+ save_in_address_book: false
+ }
+ }
+ ]
+ }
+ ) {
+ cart {
+ shipping_addresses {
+ firstname
+ lastname
+ company
+ street
+ city
+ region {
+ code
+ label
+ }
+ postcode
+ telephone
+ country {
+ code
+ label
+ }
+ available_shipping_methods{
+ carrier_code
+ carrier_title
+ method_code
+ method_title
+ }
+ }
+ }
+ }
+}
+```
+
+**Response:**
+
+`setShippingAddressesOnCart` returns the new address details.
+
+```json
+{
+ "data": {
+ "setShippingAddressesOnCart": {
+ "cart": {
+ "shipping_addresses": [
+ {
+ "firstname": "John",
+ "lastname": "Doe",
+ "company": "Company Name",
+ "street": [
+ "3320 N Crescent Dr",
+ "Beverly Hills"
+ ],
+ "city": "Los Angeles",
+ "region": {
+ "code": "CA",
+ "label": "California"
+ },
+ "postcode": "90210",
+ "telephone": "123-456-0000",
+ "country": {
+ "code": "US",
+ "label": "US"
+ },
+ "available_shipping_methods": [
+ {
+ "carrier_code": "flatrate",
+ "carrier_title": "Flat Rate",
+ "method_code": "flatrate",
+ "method_title": "Fixed"
+ },
+ {
+ "carrier_code": "tablerate",
+ "carrier_title": "Best Way",
+ "method_code": "bestway",
+ "method_title": "Table Rate"
+ }
+ ]
+ }
+ ]
+ }
+ }
+ }
+}
+```
+
+`{ CART_ID }` is the unique shopping cart ID from [Step 2. Create empty cart]({{ page.baseurl }}/graphql/tutorials/checkout/checkout-add-product-to-cart.html).
+
+Note the `available_shipping_methods` in the response. We will use this information in a later step.
+
+## Verify this step {#verify-step}
+
+1. Sign in as a customer to the website using the email `john.doe@example.com` and password `b1b2b3l@w+`.
+
+1. Go to Checkout.
+
+1. On the Shipping step, the Shipping Address form contains the address details you entered.
diff --git a/src/guides/v2.4/graphql/tutorials/checkout/checkout-shipping-method.md b/src/guides/v2.4/graphql/tutorials/checkout/checkout-shipping-method.md
index 41a29eff096..aff6c334c1a 100644
--- a/src/guides/v2.4/graphql/tutorials/checkout/checkout-shipping-method.md
+++ b/src/guides/v2.4/graphql/tutorials/checkout/checkout-shipping-method.md
@@ -12,6 +12,8 @@ functional_areas:
- Integration
contributor_name: Atwix
contributor_link: https://www.atwix.com/
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/tutorials/checkout/set-delivery-method/
+status: migrated
---
The `setShippingMethodsOnCart` mutation defines the delivery methods for your order. It requires these input parameters:
diff --git a/src/guides/v2.4/graphql/tutorials/checkout/checkout-shopping-cart.md b/src/guides/v2.4/graphql/tutorials/checkout/checkout-shopping-cart.md
deleted file mode 120000
index 9842eb8c462..00000000000
--- a/src/guides/v2.4/graphql/tutorials/checkout/checkout-shopping-cart.md
+++ /dev/null
@@ -1 +0,0 @@
-../../../../v2.3/graphql/tutorials/checkout/checkout-shopping-cart.md
\ No newline at end of file
diff --git a/src/guides/v2.4/graphql/tutorials/checkout/checkout-shopping-cart.md b/src/guides/v2.4/graphql/tutorials/checkout/checkout-shopping-cart.md
new file mode 100644
index 00000000000..29dce682589
--- /dev/null
+++ b/src/guides/v2.4/graphql/tutorials/checkout/checkout-shopping-cart.md
@@ -0,0 +1,80 @@
+---
+layout: tutorial
+group: graphql
+title: Step 2. Create an empty cart
+subtitle: GraphQL checkout tutorial
+level3_subgroup: graphql-checkout
+return_to:
+ title: GraphQL Overview
+ url: graphql/index.html
+menu_order: 20
+functional_areas:
+ - Integration
+contributor_name: Atwix
+contributor_link: https://www.atwix.com/
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/tutorials/checkout/create-cart/
+status: migrated
+---
+The procedure for creating a cart varies for logged-in customers and guests.
+
+The `customerCart` query returns the active cart for the logged-in customer. If the cart does not exist, the query creates one. You must specify the customer's authorization token in the headers. Otherwise, the query fails. ["Get customer authorization token"]({{ page.baseurl }}/graphql/authorization-tokens.html) describes these tokens.
+
+For guests, use the [`createEmptyCart`]({{page.baseurl}}/graphql/mutations/create-empty-cart.html) mutation to create an empty shopping cart and generate a cart ID for a guest user. If the guest later logs in as a customer, use the [`mergeCarts`]({{page.baseurl}}/graphql/mutations/merge-carts.html) mutation to transfer the contents of the guest cart into the customer's cart.
+
+## Create a customer cart
+
+The customer created in the previous step does not have an active cart. The following query creates an empty cart and returns the cart ID. You must specify the customer's authorization token in the headers of the call.
+
+**Request:**
+
+```graphql
+{
+ customerCart{
+ id
+ }
+}
+```
+
+**Response:**
+
+```json
+{
+ "data": {
+ "customerCart": {
+ "id": "pXVxnNg4PFcK1lD60O5evqF7f4SkiRR1"
+ }
+ }
+}
+```
+
+In the subsequent tutorial steps, the unique shopping cart identifier `pXVxnNg4PFcK1lD60O5evqF7f4SkiRR1` will be listed as `{ CART_ID }`.
+Copy the value of the id attribute. Use this value in subsequent steps wherever the { CART_ID } variable is specified.
+
+## Create a guest cart
+
+The following example creates an empty cart for a guest. Do not include an authorization token on any call made on behalf of a guest.
+
+**Request:**
+
+```graphql
+mutation {
+ createEmptyCart
+}
+```
+
+**Response:**
+
+```json
+{
+ "data": {
+ "createEmptyCart": "A7jCcOmUjjCh7MxDIzu1SeqdqETqEa5h"
+ }
+}
+```
+
+In the subsequent tutorial steps, the unique shopping cart identifier `A7jCcOmUjjCh7MxDIzu1SeqdqETqEa5h` will be listed as `{ CART_ID }`.
+Copy the value of the id attribute. Use this value in subsequent steps wherever the { CART_ID } variable is specified.
+
+## Verify this step {#verify-step}
+
+There are no additional verification steps. The value of `id` is not displayed on the website or in the Admin.
diff --git a/src/guides/v2.4/graphql/tutorials/checkout/index.md b/src/guides/v2.4/graphql/tutorials/checkout/index.md
index 130a844d374..eb16072af32 100644
--- a/src/guides/v2.4/graphql/tutorials/checkout/index.md
+++ b/src/guides/v2.4/graphql/tutorials/checkout/index.md
@@ -12,6 +12,8 @@ functional_areas:
- Integration
contributor_name: Atwix
contributor_link: https://www.atwix.com/
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/tutorials/checkout/
+status: migrated
---
This tutorial describes how to place an order through GraphQl. Customers can make purchases in two ways:
diff --git a/src/guides/v2.4/graphql/unions.md b/src/guides/v2.4/graphql/unions.md
index 4ae16a4c161..3a5d710d188 100644
--- a/src/guides/v2.4/graphql/unions.md
+++ b/src/guides/v2.4/graphql/unions.md
@@ -1,6 +1,8 @@
---
group: graphql
title: Unions
+redirect_to: https://developer.adobe.com/commerce/webapi/graphql/schema/b2b/negotiable-quote/unions/
+status: migrated
---
A GraphQL union represents an object that could be one of several data types, but there is no guarantee that the data types contain fields in common. Use an inline fragment to return details about each possible data type.
diff --git a/src/guides/v2.4/howdoi/admin/customize_admin.md b/src/guides/v2.4/howdoi/admin/customize_admin.md
index 632a504a629..e066cb09036 100644
--- a/src/guides/v2.4/howdoi/admin/customize_admin.md
+++ b/src/guides/v2.4/howdoi/admin/customize_admin.md
@@ -1,8 +1,8 @@
---
group: how-do-i
title: Customize the design
-migrated_to: https://developer.adobe.com/commerce/php/tutorials/admin/custom-admin-design/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/tutorials/admin/custom-admin-design/
+status: migrated
---
Learn how to customize (add, delete, change) the configuration options available in the Admin. These options define the various aspects of storefront design.
diff --git a/src/guides/v2.4/howdoi/checkout/checkout-add-custom-carrier.md b/src/guides/v2.4/howdoi/checkout/checkout-add-custom-carrier.md
index 81426ab828d..d586a0e09a3 100644
--- a/src/guides/v2.4/howdoi/checkout/checkout-add-custom-carrier.md
+++ b/src/guides/v2.4/howdoi/checkout/checkout-add-custom-carrier.md
@@ -10,8 +10,8 @@ menu_order: 5
level3_subgroup: checkout-tutorial
functional_areas:
- Checkout
-migrated_to: https://developer.adobe.com/commerce/php/tutorials/frontend/custom-checkout/add-shipping-carrier/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/tutorials/frontend/custom-checkout/add-shipping-carrier/
+status: migrated
---
This topic describes how to add a custom shipping carrier.
diff --git a/src/guides/v2.4/howdoi/checkout/checkout_address.md b/src/guides/v2.4/howdoi/checkout/checkout_address.md
index 1f394e609c3..fce4c5a2830 100644
--- a/src/guides/v2.4/howdoi/checkout/checkout_address.md
+++ b/src/guides/v2.4/howdoi/checkout/checkout_address.md
@@ -8,8 +8,8 @@ menu_order: 11
level3_subgroup: checkout-tutorial
functional_areas:
- Checkout
-migrated_to: https://developer.adobe.com/commerce/php/tutorials/frontend/custom-checkout/add-address-renderer/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/tutorials/frontend/custom-checkout/add-address-renderer/
+status: migrated
---
This topic describes how to implement a custom shipping address renderer.
diff --git a/src/guides/v2.4/howdoi/checkout/checkout_carrier.md b/src/guides/v2.4/howdoi/checkout/checkout_carrier.md
index 40c3ff341fe..68a9ee08183 100644
--- a/src/guides/v2.4/howdoi/checkout/checkout_carrier.md
+++ b/src/guides/v2.4/howdoi/checkout/checkout_carrier.md
@@ -8,8 +8,8 @@ menu_order: 6
level3_subgroup: checkout-tutorial
functional_areas:
- Checkout
-migrated_to: https://developer.adobe.com/commerce/php/tutorials/frontend/custom-checkout/add-carrier-validation/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/tutorials/frontend/custom-checkout/add-carrier-validation/
+status: migrated
---
This topic describes how to add shipping address validations for a custom [shipping carrier](https://glossary.magento.com/shipping-carrier) to the Magento [checkout](https://glossary.magento.com/checkout). This is an essential part of the bigger task of adding a custom shipping method to your Magento store.
diff --git a/src/guides/v2.4/howdoi/checkout/checkout_custom_checkbox.md b/src/guides/v2.4/howdoi/checkout/checkout_custom_checkbox.md
index c4d7fa6e539..f6dfc87aa0f 100644
--- a/src/guides/v2.4/howdoi/checkout/checkout_custom_checkbox.md
+++ b/src/guides/v2.4/howdoi/checkout/checkout_custom_checkbox.md
@@ -8,8 +8,8 @@ menu_order: 90
level3_subgroup: checkout-tutorial
functional_areas:
- Checkout
-migrated_to: https://developer.adobe.com/commerce/php/tutorials/frontend/custom-checkout/add-checkbox/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/tutorials/frontend/custom-checkout/add-checkbox/
+status: migrated
---
This topic describes how to add a custom field that influences other fields on the checkout page.
diff --git a/src/guides/v2.4/howdoi/checkout/checkout_customize.md b/src/guides/v2.4/howdoi/checkout/checkout_customize.md
index a2b5a8c34c2..a123ab85da6 100755
--- a/src/guides/v2.4/howdoi/checkout/checkout_customize.md
+++ b/src/guides/v2.4/howdoi/checkout/checkout_customize.md
@@ -8,8 +8,8 @@ menu_order: 2
level3_subgroup: checkout-tutorial
functional_areas:
- Checkout
-migrated_to: https://developer.adobe.com/commerce/php/tutorials/frontend/custom-checkout/customize-view/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/tutorials/frontend/custom-checkout/customize-view/
+status: migrated
---
This topic contains the basic information about how to customize the view of an existing [checkout](https://glossary.magento.com/checkout) step. In the Magento application, checkout is implemented using UI components. You can customize each step by [changing the JavaScript implementation or template](#change-component) for a component, [adding](#add), [disabling](#disable), or [removing](#remove) a component.
diff --git a/src/guides/v2.4/howdoi/checkout/checkout_edit_form.md b/src/guides/v2.4/howdoi/checkout/checkout_edit_form.md
index b8f6ecaa9e5..2996499173c 100644
--- a/src/guides/v2.4/howdoi/checkout/checkout_edit_form.md
+++ b/src/guides/v2.4/howdoi/checkout/checkout_edit_form.md
@@ -8,8 +8,8 @@ menu_order: 8
level3_subgroup: checkout-tutorial
functional_areas:
- Checkout
-migrated_to: https://developer.adobe.com/commerce/php/tutorials/frontend/custom-checkout/add-template/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/tutorials/frontend/custom-checkout/add-template/
+status: migrated
---
This topic describes how to replace the [HTML](https://glossary.magento.com/html) template for a form field on the [Checkout](https://glossary.magento.com/checkout) page. You might need to replace the template in order to add elements displayed with the field, change the [CSS](https://glossary.magento.com/css) class assigned to it, add attributes and so on.
diff --git a/src/guides/v2.4/howdoi/checkout/checkout_form.md b/src/guides/v2.4/howdoi/checkout/checkout_form.md
index f095f59dc0e..31dd0e8d071 100644
--- a/src/guides/v2.4/howdoi/checkout/checkout_form.md
+++ b/src/guides/v2.4/howdoi/checkout/checkout_form.md
@@ -8,8 +8,8 @@ menu_order: 9
level3_subgroup: checkout-tutorial
functional_areas:
- Checkout
-migrated_to: https://developer.adobe.com/commerce/php/tutorials/frontend/custom-checkout/add-form/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/tutorials/frontend/custom-checkout/add-form/
+status: migrated
---
This topic describes how to add a custom input form (implemented as a UI component) to the [Checkout](https://glossary.magento.com/checkout) page.
diff --git a/src/guides/v2.4/howdoi/checkout/checkout_new_field.md b/src/guides/v2.4/howdoi/checkout/checkout_new_field.md
index b7fcdfdb32d..da41f126abd 100644
--- a/src/guides/v2.4/howdoi/checkout/checkout_new_field.md
+++ b/src/guides/v2.4/howdoi/checkout/checkout_new_field.md
@@ -8,8 +8,8 @@ menu_order: 9
level3_subgroup: checkout-tutorial
functional_areas:
- Checkout
-migrated_to: https://developer.adobe.com/commerce/php/tutorials/frontend/custom-checkout/add-address-field/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/tutorials/frontend/custom-checkout/add-address-field/
+status: migrated
---
You can add new fields to default [checkout](https://glossary.magento.com/checkout) forms, such as shipping address or billing address forms. To illustrate this ability, this topic describes adding a field to the shipping address form.
diff --git a/src/guides/v2.4/howdoi/checkout/checkout_new_step.md b/src/guides/v2.4/howdoi/checkout/checkout_new_step.md
index 5e297b2d99a..3383bb0477c 100644
--- a/src/guides/v2.4/howdoi/checkout/checkout_new_step.md
+++ b/src/guides/v2.4/howdoi/checkout/checkout_new_step.md
@@ -8,8 +8,8 @@ menu_order: 1
level3_subgroup: checkout-tutorial
functional_areas:
- Checkout
-migrated_to: https://developer.adobe.com/commerce/php/tutorials/frontend/custom-checkout/add-new-step/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/tutorials/frontend/custom-checkout/add-new-step/
+status: migrated
---
This topic describes how to create the [frontend](https://glossary.magento.com/frontend) part of the component, implementing a checkout step, and how to add it to the checkout flow.
diff --git a/src/guides/v2.4/howdoi/checkout/checkout_order.md b/src/guides/v2.4/howdoi/checkout/checkout_order.md
index 6507d863f27..0bd68cf11f3 100644
--- a/src/guides/v2.4/howdoi/checkout/checkout_order.md
+++ b/src/guides/v2.4/howdoi/checkout/checkout_order.md
@@ -8,8 +8,8 @@ menu_order: 4
level3_subgroup: checkout-tutorial
functional_areas:
- Checkout
-migrated_to: https://developer.adobe.com/commerce/php/tutorials/frontend/custom-checkout/add-order-validation/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/tutorials/frontend/custom-checkout/add-order-validation/
+status: migrated
---
This topic describes how to add custom validations to be performed before the order is placed during [checkout](https://glossary.magento.com/checkout). Namely, the validations which are performed after a shopper clicks the **Place Order** button. Writing the validation logic itself is not covered in this topic.
diff --git a/src/guides/v2.4/howdoi/checkout/checkout_overview.md b/src/guides/v2.4/howdoi/checkout/checkout_overview.md
index c9869b4c155..fbd2dc47c64 100644
--- a/src/guides/v2.4/howdoi/checkout/checkout_overview.md
+++ b/src/guides/v2.4/howdoi/checkout/checkout_overview.md
@@ -9,8 +9,8 @@ level3_subgroup: checkout-tutorial
menu_order: 0
functional_areas:
- Checkout
-migrated_to: https://developer.adobe.com/commerce/php/tutorials/frontend/custom-checkout/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/tutorials/frontend/custom-checkout/
+status: migrated
---
Magento [checkout](https://glossary.magento.com/checkout) is implemented using the [UI components]({{ page.baseurl }}/ui_comp_guide/bk-ui_comps.html).
diff --git a/src/guides/v2.4/howdoi/checkout/checkout_payment.md b/src/guides/v2.4/howdoi/checkout/checkout_payment.md
index 380532910c3..323d648fb2a 100644
--- a/src/guides/v2.4/howdoi/checkout/checkout_payment.md
+++ b/src/guides/v2.4/howdoi/checkout/checkout_payment.md
@@ -8,8 +8,8 @@ menu_order: 3
level3_subgroup: checkout-tutorial
functional_areas:
- Checkout
-migrated_to: https://developer.adobe.com/commerce/php/tutorials/frontend/custom-checkout/add-payment-method/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/tutorials/frontend/custom-checkout/add-payment-method/
+status: migrated
---
Out of the box, Magento [checkout](https://glossary.magento.com/checkout) consists of two steps:
diff --git a/src/guides/v2.4/howdoi/checkout/checkout_payment_new_field.md b/src/guides/v2.4/howdoi/checkout/checkout_payment_new_field.md
index 1d872d4e6c0..3d69fe8dced 100644
--- a/src/guides/v2.4/howdoi/checkout/checkout_payment_new_field.md
+++ b/src/guides/v2.4/howdoi/checkout/checkout_payment_new_field.md
@@ -10,8 +10,8 @@ menu_order: 101
level3_subgroup: checkout-tutorial
functional_areas:
- Checkout
-migrated_to: https://developer.adobe.com/commerce/php/tutorials/frontend/custom-checkout/add-payment-field/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/tutorials/frontend/custom-checkout/add-payment-field/
+status: migrated
---
This topic describes how to add a custom field to an offline payment method in the payment step of the checkout. The custom field allows the buyer to enter a comment about a purchase order.
diff --git a/src/guides/v2.4/howdoi/checkout/checkout_shipping_methods.md b/src/guides/v2.4/howdoi/checkout/checkout_shipping_methods.md
index 9a0fd60646a..0a4f9f2024a 100644
--- a/src/guides/v2.4/howdoi/checkout/checkout_shipping_methods.md
+++ b/src/guides/v2.4/howdoi/checkout/checkout_shipping_methods.md
@@ -6,8 +6,8 @@ title: Customize the list of shipping methods
subtitle: Customize Checkout
menu_order: 100
level3_subgroup: checkout-tutorial
-migrated_to: https://developer.adobe.com/commerce/php/tutorials/frontend/custom-checkout/add-shipping-methods/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/tutorials/frontend/custom-checkout/add-shipping-methods/
+status: migrated
---
This topic describes how to customize list of shipping methods displayed on the checkout page.
diff --git a/src/guides/v2.4/howdoi/checkout/checkout_zip.md b/src/guides/v2.4/howdoi/checkout/checkout_zip.md
index a012b9b6e90..1352eee3320 100644
--- a/src/guides/v2.4/howdoi/checkout/checkout_zip.md
+++ b/src/guides/v2.4/howdoi/checkout/checkout_zip.md
@@ -8,8 +8,8 @@ menu_order: 7
level3_subgroup: checkout-tutorial
functional_areas:
- Checkout
-migrated_to: https://developer.adobe.com/commerce/php/tutorials/frontend/custom-checkout/add-input-mask/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/tutorials/frontend/custom-checkout/add-input-mask/
+status: migrated
---
This topic describes how a developer can add custom input masks.
diff --git a/src/guides/v2.4/howdoi/custom-attributes/introduction.md b/src/guides/v2.4/howdoi/custom-attributes/introduction.md
index bef35d58acc..83a1471902c 100644
--- a/src/guides/v2.4/howdoi/custom-attributes/introduction.md
+++ b/src/guides/v2.4/howdoi/custom-attributes/introduction.md
@@ -8,8 +8,8 @@ level3_subgroup: custom-attributes
menu_order: 1
contributor_name: Adarsh Manickam
contributor_link: https://github.com/drpayyne
-migrated_to: https://developer.adobe.com/commerce/php/tutorials/admin/custom-text-field-attribute/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/tutorials/admin/custom-text-field-attribute/
+status: migrated
---
The tutorials under this section guide Magento developers on setting up and configuring custom attributes.
diff --git a/src/guides/v2.4/howdoi/custom-attributes/text-field.md b/src/guides/v2.4/howdoi/custom-attributes/text-field.md
index 76e4280bd61..1cde0383bcb 100644
--- a/src/guides/v2.4/howdoi/custom-attributes/text-field.md
+++ b/src/guides/v2.4/howdoi/custom-attributes/text-field.md
@@ -8,8 +8,8 @@ level3_subgroup: custom-attributes
menu_order: 2
contributor_name: Adarsh Manickam
contributor_link: https://github.com/drpayyne
-migrated_to: https://developer.adobe.com/commerce/php/tutorials/admin/custom-text-field-attribute/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/tutorials/admin/custom-text-field-attribute/
+status: migrated
---
## Overview
diff --git a/src/guides/v2.4/howdoi/customize-form-configuration.md b/src/guides/v2.4/howdoi/customize-form-configuration.md
index ebaf86baa33..6fa1ce919e7 100644
--- a/src/guides/v2.4/howdoi/customize-form-configuration.md
+++ b/src/guides/v2.4/howdoi/customize-form-configuration.md
@@ -7,8 +7,8 @@ subtitle: Customize Product Creation Form
menu_node:
level3_subgroup: product-creation-form
menu_order: 2
-migrated_to: https://developer.adobe.com/commerce/php/tutorials/admin/custom-product-creation-form/configuration/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/tutorials/admin/custom-product-creation-form/configuration/
+status: migrated
---
Customizing the form config file (that is, declarative customization) is preferable for changes like introducing new fields, field sets and modals.
diff --git a/src/guides/v2.4/howdoi/customize-modifier-class.md b/src/guides/v2.4/howdoi/customize-modifier-class.md
index e76437e7972..a068047af85 100644
--- a/src/guides/v2.4/howdoi/customize-modifier-class.md
+++ b/src/guides/v2.4/howdoi/customize-modifier-class.md
@@ -7,8 +7,8 @@ subtitle: Customize Product Creation Form
menu_node:
level3_subgroup: product-creation-form
menu_order: 3
-migrated_to: https://developer.adobe.com/commerce/php/tutorials/admin/custom-product-creation-form/modifier-class/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/tutorials/admin/custom-product-creation-form/modifier-class/
+status: migrated
---
[Modifier classes]({{ page.baseurl }}/ui_comp_guide/concepts/ui_comp_modifier_concept.html) should be used when static declaration is not applicable. For example, in cases when additional data should be loaded from database. Also, modifier is a place where you add validations to display only certain fields for certain product types.
diff --git a/src/guides/v2.4/howdoi/customize_product.md b/src/guides/v2.4/howdoi/customize_product.md
index 8bafe8e0ee8..9b9f30231b0 100644
--- a/src/guides/v2.4/howdoi/customize_product.md
+++ b/src/guides/v2.4/howdoi/customize_product.md
@@ -7,8 +7,8 @@ menu_title: Initial Tasks
menu_node:
level3_subgroup: product-creation-form
menu_order: 1
-migrated_to: https://developer.adobe.com/commerce/php/tutorials/admin/custom-product-creation-form/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/tutorials/admin/custom-product-creation-form/
+status: migrated
---
This tutorial describes how developers can customize the product creation form used on the product creation and product edit pages in [Admin](https://glossary.magento.com/admin). The product creation form is implemented using the [form UI component]({{ page.baseurl }}/ui_comp_guide/components/ui-form.html).
diff --git a/src/guides/v2.4/howdoi/php/php_clear-dirs.md b/src/guides/v2.4/howdoi/php/php_clear-dirs.md
index 7ccc60ad591..66e9de7fb41 100644
--- a/src/guides/v2.4/howdoi/php/php_clear-dirs.md
+++ b/src/guides/v2.4/howdoi/php/php_clear-dirs.md
@@ -5,8 +5,8 @@ title: Clear directories during development
menu_title: Clear directories during development
menu_node:
menu_order: 200
-migrated_to: https://developer.adobe.com/commerce/php/development/components/clear-directories/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/php/development/components/clear-directories/
+status: migrated
---
#### Contents
diff --git a/src/guides/v2.4/install-gde/bk-install-guide.md b/src/guides/v2.4/install-gde/bk-install-guide.md
index 7bc4dd86125..a1acc0e06d9 100644
--- a/src/guides/v2.4/install-gde/bk-install-guide.md
+++ b/src/guides/v2.4/install-gde/bk-install-guide.md
@@ -7,8 +7,8 @@ functional_areas:
- Setup
redirect_from:
- /guides/v2.4/install-gde/continue-to-install.html
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/overview.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/overview.html
+status: migrated
---
You are among the 240,000 merchants worldwide who put their trust in our eCommerce software. We have gathered some information to help you get started with Magento and with your Magento installation.
diff --git a/src/guides/v2.4/install-gde/composer.md b/src/guides/v2.4/install-gde/composer.md
index dff0ca00823..4c499f3ba0a 100644
--- a/src/guides/v2.4/install-gde/composer.md
+++ b/src/guides/v2.4/install-gde/composer.md
@@ -6,8 +6,8 @@ functional_areas:
- Setup
redirect_from:
- guides/v2.4/install-gde/prereq/zip_install.html
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/composer.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/composer.html
+status: migrated
---
{% include install/composer-overview.md %}
diff --git a/src/guides/v2.4/install-gde/continue-to-verify_cli.md b/src/guides/v2.4/install-gde/continue-to-verify_cli.md
index d6bb6e5ced4..71f27fbe5c7 100644
--- a/src/guides/v2.4/install-gde/continue-to-verify_cli.md
+++ b/src/guides/v2.4/install-gde/continue-to-verify_cli.md
@@ -5,8 +5,8 @@ functional_areas:
- System
- Setup
redirect_from: /guides/v2.3/install-gde/continue-to-verify.html
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/next-steps/verify.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/next-steps/verify.html
+status: migrated
---
## Now that you've finished your installation
diff --git a/src/guides/v2.4/install-gde/contrib-git.md b/src/guides/v2.4/install-gde/contrib-git.md
index 0478c1bb7e7..4af1ff54d15 100644
--- a/src/guides/v2.4/install-gde/contrib-git.md
+++ b/src/guides/v2.4/install-gde/contrib-git.md
@@ -4,8 +4,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://developer.adobe.com/commerce/contributor/guides/install/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/contributor/guides/install/
+status: migrated
---
If you are a code or documentation contributor, this install guide is for you! Use Composer to install Magento, then switch over to a released version and update any installation dependencies.
diff --git a/src/guides/v2.4/install-gde/install-flow-diagram.md b/src/guides/v2.4/install-gde/install-flow-diagram.md
index d6025b3bcd3..30e3fd55734 100644
--- a/src/guides/v2.4/install-gde/install-flow-diagram.md
+++ b/src/guides/v2.4/install-gde/install-flow-diagram.md
@@ -4,8 +4,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/overview.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/overview.html
+status: migrated
---
The following diagram provides a high-level overview of installing the Magento software:
diff --git a/src/guides/v2.4/install-gde/install/cli/dev_add-update.md b/src/guides/v2.4/install-gde/install/cli/dev_add-update.md
index ac18dc83aa9..3fda5b98b7b 100644
--- a/src/guides/v2.4/install-gde/install/cli/dev_add-update.md
+++ b/src/guides/v2.4/install-gde/install/cli/dev_add-update.md
@@ -6,8 +6,8 @@ menu_order: 5
menu_node:
functional_areas:
- Upgrade
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/upgrade-guide/developer/manage-modules.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/upgrade-guide/developer/manage-modules.html
+status: migrated
---
A contributing developer updates components by specifying components and their versions in Magento's `composer.json`.
diff --git a/src/guides/v2.4/install-gde/install/cli/dev_downgrade.md b/src/guides/v2.4/install-gde/install/cli/dev_downgrade.md
index 9f4afccffd4..12482b5f366 100644
--- a/src/guides/v2.4/install-gde/install/cli/dev_downgrade.md
+++ b/src/guides/v2.4/install-gde/install/cli/dev_downgrade.md
@@ -4,8 +4,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://developer.adobe.com/commerce/contributor/guides/install/change-version/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/contributor/guides/install/change-version/
+status: migrated
---
This topic discusses how a contributing developer can change versions of the Magento software after cloning the `develop` branch. This might be necessary to perform some tasks that require a specific Magento version other than `develop`.
diff --git a/src/guides/v2.4/install-gde/install/cli/dev_reinstall.md b/src/guides/v2.4/install-gde/install/cli/dev_reinstall.md
index b8893c8bd19..a9b32f7f6f1 100644
--- a/src/guides/v2.4/install-gde/install/cli/dev_reinstall.md
+++ b/src/guides/v2.4/install-gde/install/cli/dev_reinstall.md
@@ -8,8 +8,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/uninstall.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/uninstall.html
+status: migrated
---
A contributing developer reinstalls Magento by updating `composer.json` to specify the Magento product version and component versions desired and runs `composer update`.
diff --git a/src/guides/v2.4/install-gde/install/cli/extensions.md b/src/guides/v2.4/install-gde/install/cli/extensions.md
index aff024b61ba..0ca645d1e8c 100644
--- a/src/guides/v2.4/install-gde/install/cli/extensions.md
+++ b/src/guides/v2.4/install-gde/install/cli/extensions.md
@@ -1,8 +1,8 @@
---
group: installation-guide
title: Install an extension
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/extensions.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/extensions.html
+status: migrated
---
Code that extends or customizes {{site.data.var.ee}} and {{site.data.var.ce}} behavior is called an extension. You can optionally package and distribute extensions on the [Commerce Marketplace](https://marketplace.magento.com) or another extension distribution system.
diff --git a/src/guides/v2.4/install-gde/install/cli/install-cli-adminurl.md b/src/guides/v2.4/install-gde/install/cli/install-cli-adminurl.md
index 7fbc3767f77..9e778339587 100644
--- a/src/guides/v2.4/install-gde/install/cli/install-cli-adminurl.md
+++ b/src/guides/v2.4/install-gde/install/cli/install-cli-adminurl.md
@@ -4,8 +4,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/admin-uri.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/admin-uri.html
+status: migrated
---
## First steps {#instgde-cli-before}
diff --git a/src/guides/v2.4/install-gde/install/cli/install-cli-backup.md b/src/guides/v2.4/install-gde/install/cli/install-cli-backup.md
index 571e3357946..b6843b5de25 100644
--- a/src/guides/v2.4/install-gde/install/cli/install-cli-backup.md
+++ b/src/guides/v2.4/install-gde/install/cli/install-cli-backup.md
@@ -4,8 +4,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/backup.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/backup.html
+status: migrated
---
## Overview of backup {#instgde-cli-uninst-back-over}
diff --git a/src/guides/v2.4/install-gde/install/cli/install-cli-install.md b/src/guides/v2.4/install-gde/install/cli/install-cli-install.md
index a4ed79935e6..4350207b13b 100644
--- a/src/guides/v2.4/install-gde/install/cli/install-cli-install.md
+++ b/src/guides/v2.4/install-gde/install/cli/install-cli-install.md
@@ -7,8 +7,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/install.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/install.html
+status: migrated
---
## Before you start your installation {#instgde-install-cli-prereq}
diff --git a/src/guides/v2.4/install-gde/install/cli/install-cli-sample-data-clone.md b/src/guides/v2.4/install-gde/install/cli/install-cli-sample-data-clone.md
index 43f13fb5050..cfe73a812de 100644
--- a/src/guides/v2.4/install-gde/install/cli/install-cli-sample-data-clone.md
+++ b/src/guides/v2.4/install-gde/install/cli/install-cli-sample-data-clone.md
@@ -5,8 +5,8 @@ functional_areas:
- System
- Setup
redirect_from: /guides/v2.4/install-gde/install/web/install-web-sample-data-clone.html
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/next-steps/sample-data/git-repositories.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/next-steps/sample-data/git-repositories.html
+status: migrated
---
{% include install/sampledata/sample-data-clone-24.md %}
diff --git a/src/guides/v2.4/install-gde/install/cli/install-cli-sample-data-composer.md b/src/guides/v2.4/install-gde/install/cli/install-cli-sample-data-composer.md
index 62d19fca42b..e5ed32d012c 100644
--- a/src/guides/v2.4/install-gde/install/cli/install-cli-sample-data-composer.md
+++ b/src/guides/v2.4/install-gde/install/cli/install-cli-sample-data-composer.md
@@ -5,8 +5,8 @@ functional_areas:
- System
- Setup
redirect_from: /guides/v2.4/install-gde/install/web/install-web-sample-data-composer.html
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/next-steps/sample-data/composer-packages.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/next-steps/sample-data/composer-packages.html
+status: migrated
---
{% include install/sampledata/sample-data-composer.md %}
diff --git a/src/guides/v2.4/install-gde/install/cli/install-cli-sample-data-other.md b/src/guides/v2.4/install-gde/install/cli/install-cli-sample-data-other.md
index c8ea9d5807b..1e4440fc17e 100644
--- a/src/guides/v2.4/install-gde/install/cli/install-cli-sample-data-other.md
+++ b/src/guides/v2.4/install-gde/install/cli/install-cli-sample-data-other.md
@@ -8,8 +8,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/next-steps/sample-data/remove-or-update.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/next-steps/sample-data/remove-or-update.html
+status: migrated
---
{% include install/sampledata/sample-data-other-cmds.md %}
diff --git a/src/guides/v2.4/install-gde/install/cli/install-cli-sample-data.md b/src/guides/v2.4/install-gde/install/cli/install-cli-sample-data.md
index f5cd999c50e..a07465079c4 100644
--- a/src/guides/v2.4/install-gde/install/cli/install-cli-sample-data.md
+++ b/src/guides/v2.4/install-gde/install/cli/install-cli-sample-data.md
@@ -5,8 +5,8 @@ functional_areas:
- System
- Setup
redirect_from: /guides/v2.4/install-gde/install/web/install-web-sample-data.html
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/next-steps/sample-data/overview.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/next-steps/sample-data/overview.html
+status: migrated
---
{% include install/sampledata/sample-data-intro.md %}
diff --git a/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-admin.md b/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-admin.md
index 5fd6f13db01..001e862abfd 100644
--- a/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-admin.md
+++ b/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-admin.md
@@ -4,8 +4,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/admin.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/admin.html
+status: migrated
---
## First steps
diff --git a/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-consumers.md b/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-consumers.md
index 45424439d2f..37ecf13a584 100644
--- a/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-consumers.md
+++ b/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-consumers.md
@@ -4,8 +4,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/message-consumers.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/message-consumers.html
+status: migrated
---
Before you run this command, you must do all of the following *or* you must [install the Magento software]({{ page.baseurl }}/install-gde/install/cli/install-cli-install.html):
diff --git a/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-db-status.md b/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-db-status.md
index 51eb5f62eb7..5bf326f13f0 100644
--- a/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-db-status.md
+++ b/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-db-status.md
@@ -8,8 +8,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/database-status.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/database-status.html
+status: migrated
---
## First steps {#instgde-cli-before}
diff --git a/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-db-upgr.md b/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-db-upgr.md
index ef32d406188..5770cc7b3d4 100644
--- a/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-db-upgr.md
+++ b/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-db-upgr.md
@@ -4,8 +4,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/database-upgrade.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/database-upgrade.html
+status: migrated
---
## First steps {#instgde-cli-before}
diff --git a/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-db.md b/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-db.md
index 8c526f8517a..2448ebc4c45 100644
--- a/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-db.md
+++ b/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-db.md
@@ -4,8 +4,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/database.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/database.html
+status: migrated
---
## First steps {#instgde-cli-before}
diff --git a/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-deployment.md b/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-deployment.md
index bd064e7af97..6c8c8220763 100644
--- a/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-deployment.md
+++ b/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-deployment.md
@@ -5,8 +5,8 @@ functional_areas:
- System
- Setup
- Deploy
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/deployment.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/deployment.html
+status: migrated
---
## First steps {#instgde-cli-before}
diff --git a/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-enable.md b/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-enable.md
index 3e1e698ed7b..a37c55a256a 100644
--- a/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-enable.md
+++ b/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-enable.md
@@ -4,8 +4,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/manage-modules.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/manage-modules.html
+status: migrated
---
## First steps {#instgde-cli-before}
diff --git a/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-lock.md b/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-lock.md
index 679772111ad..d8ae74e1afe 100644
--- a/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-lock.md
+++ b/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-lock.md
@@ -4,8 +4,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/lock-provider.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/lock-provider.html
+status: migrated
---
## First steps {#instgde-cli-before}
diff --git a/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-maint.md b/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-maint.md
index 7151f910efc..4bcbc0bad7d 100644
--- a/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-maint.md
+++ b/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-maint.md
@@ -8,8 +8,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/maintenance-mode.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/maintenance-mode.html
+status: migrated
---
The following guide refers to a standard Magento maintenance mode page. If you need to use a custom maintenance page, see [Create the custom maintenance page](https://experienceleague.adobe.com/docs/commerce-operations/upgrade-guide/troubleshooting/maintenance-mode-options.html) topic.
@@ -88,9 +88,7 @@ bin/magento maintenance:allow-ips .. [--none]
## Multi-store setups
-To set up multiple stores, each with a different layout and localized content, create a skin for each and put it into `pub/errors/{name}` where `{name}` is the store code. To distinguish between stores and websites with the same instance, use `pub/errors/{type}-{name}` where `{type}` is either `store` or `website` and matches the `MAGE_RUN_TYPE` in your server configuration.
-
-Another option is to pass the `$_GET['skin']` parameter to the intended processor. This method requires a specific configuration on your server.
+If you want to set up multiple stores, each with a different layout and localized content, pass the `$_GET['skin']` parameter to the intended processor.
In the following example, we are using a `503` type error template file, which requires localized content.
diff --git a/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-store.md b/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-store.md
index b303174991b..c1b6d50a203 100644
--- a/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-store.md
+++ b/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands-store.md
@@ -4,8 +4,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/store.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/store.html
+status: migrated
---
## First steps {#instgde-cli-before}
diff --git a/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands.md b/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands.md
index 43312ef3b2f..8b96cad489c 100644
--- a/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands.md
+++ b/src/guides/v2.4/install-gde/install/cli/install-cli-subcommands.md
@@ -8,8 +8,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/composer.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/composer.html
+status: migrated
---
## Before you start your installation {#instgde-install-cli-prereq}
diff --git a/src/guides/v2.4/install-gde/install/cli/install-cli-theme-uninstall.md b/src/guides/v2.4/install-gde/install/cli/install-cli-theme-uninstall.md
index 02f3bb73593..608ba451701 100644
--- a/src/guides/v2.4/install-gde/install/cli/install-cli-theme-uninstall.md
+++ b/src/guides/v2.4/install-gde/install/cli/install-cli-theme-uninstall.md
@@ -4,8 +4,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/themes.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/themes.html
+status: migrated
---
## Prerequisite {#instgde-install-uninst-theme-prereq}
diff --git a/src/guides/v2.4/install-gde/install/cli/install-cli-uninstall-langpk.md b/src/guides/v2.4/install-gde/install/cli/install-cli-uninstall-langpk.md
index 117bd934b1d..d7ccf48473c 100644
--- a/src/guides/v2.4/install-gde/install/cli/install-cli-uninstall-langpk.md
+++ b/src/guides/v2.4/install-gde/install/cli/install-cli-uninstall-langpk.md
@@ -4,8 +4,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/language-packages.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/language-packages.html
+status: migrated
---
## Overview of uninstalling language packages {#instgde-cli-uninst-lgpk-over}
diff --git a/src/guides/v2.4/install-gde/install/cli/install-cli-uninstall-mods.md b/src/guides/v2.4/install-gde/install/cli/install-cli-uninstall-mods.md
index 2a1aaa32b14..fa3620e1b72 100644
--- a/src/guides/v2.4/install-gde/install/cli/install-cli-uninstall-mods.md
+++ b/src/guides/v2.4/install-gde/install/cli/install-cli-uninstall-mods.md
@@ -4,8 +4,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/uninstall-modules.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/uninstall-modules.html
+status: migrated
---
## Prerequisites {#instgde-cli-uninst-prereq}
diff --git a/src/guides/v2.4/install-gde/install/cli/install-cli-uninstall.md b/src/guides/v2.4/install-gde/install/cli/install-cli-uninstall.md
index 33139cb48be..7f329a32f6c 100644
--- a/src/guides/v2.4/install-gde/install/cli/install-cli-uninstall.md
+++ b/src/guides/v2.4/install-gde/install/cli/install-cli-uninstall.md
@@ -4,8 +4,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/uninstall.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/uninstall.html
+status: migrated
---
## First steps {#instgde-cli-before}
diff --git a/src/guides/v2.4/install-gde/install/cli/install-cli.md b/src/guides/v2.4/install-gde/install/cli/install-cli.md
index 8df4516101b..e99987823fe 100644
--- a/src/guides/v2.4/install-gde/install/cli/install-cli.md
+++ b/src/guides/v2.4/install-gde/install/cli/install-cli.md
@@ -14,8 +14,8 @@ redirect_from:
- /guides/v2.4/install-gde/install/web/install-web_5-create-admin.html
- /guides/v2.4/install-gde/install/web/install-web_6-install.html
- /guides/v2.4/install-gde/install/cli/install-cli-install.html
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/advanced.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/advanced.html
+status: migrated
---
{:.bs-callout-tip}
diff --git a/src/guides/v2.4/install-gde/install/get-help.md b/src/guides/v2.4/install-gde/install/get-help.md
index 607484ff568..78e27d1ab34 100644
--- a/src/guides/v2.4/install-gde/install/get-help.md
+++ b/src/guides/v2.4/install-gde/install/get-help.md
@@ -8,8 +8,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/advanced.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/advanced.html
+status: migrated
---
{% include install/get-help.md %}
diff --git a/src/guides/v2.4/install-gde/install/post-install-config.md b/src/guides/v2.4/install-gde/install/post-install-config.md
index 5e7b6d5e88b..fe75a2559d2 100644
--- a/src/guides/v2.4/install-gde/install/post-install-config.md
+++ b/src/guides/v2.4/install-gde/install/post-install-config.md
@@ -4,8 +4,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/next-steps/configuration.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/next-steps/configuration.html
+status: migrated
---
Now that you've finished installing the Magento application, you need to configure it. This topic provides some recommended configuration settings for Magento; the list is not complete so watch this space.
diff --git a/src/guides/v2.4/install-gde/install/post-install-umask.md b/src/guides/v2.4/install-gde/install/post-install-umask.md
index 12a2e7451cc..2e1b82a18bb 100644
--- a/src/guides/v2.4/install-gde/install/post-install-umask.md
+++ b/src/guides/v2.4/install-gde/install/post-install-umask.md
@@ -8,8 +8,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/next-steps/set-umask.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/next-steps/set-umask.html
+status: migrated
---
## Optionally set `magento_umask` {#mage-owner-umask}
diff --git a/src/guides/v2.4/install-gde/install/prepare-install.md b/src/guides/v2.4/install-gde/install/prepare-install.md
index d4aef14115d..ed8084ea94c 100644
--- a/src/guides/v2.4/install-gde/install/prepare-install.md
+++ b/src/guides/v2.4/install-gde/install/prepare-install.md
@@ -4,8 +4,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://developer.adobe.com/commerce/contributor/guides/install/update-dependencies/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/contributor/guides/install/update-dependencies/
+status: migrated
---
## Introduction to Magento installation dependencies {#install-update-depend}
diff --git a/src/guides/v2.4/install-gde/install/sample-data-after-clone.md b/src/guides/v2.4/install-gde/install/sample-data-after-clone.md
index b1c5066a683..c2750b88c84 100644
--- a/src/guides/v2.4/install-gde/install/sample-data-after-clone.md
+++ b/src/guides/v2.4/install-gde/install/sample-data-after-clone.md
@@ -9,8 +9,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/next-steps/sample-data/git-repositories.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/next-steps/sample-data/git-repositories.html
+status: migrated
---
{% include install/sampledata/sample-data-clone-24.md %}
diff --git a/src/guides/v2.4/install-gde/install/sample-data-after-composer.md b/src/guides/v2.4/install-gde/install/sample-data-after-composer.md
index 7807a14e857..13330fd97cd 100644
--- a/src/guides/v2.4/install-gde/install/sample-data-after-composer.md
+++ b/src/guides/v2.4/install-gde/install/sample-data-after-composer.md
@@ -8,8 +8,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/next-steps/sample-data/composer-packages.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/next-steps/sample-data/composer-packages.html
+status: migrated
---
{% include install/sampledata/sample-data-composer.md %}
diff --git a/src/guides/v2.4/install-gde/install/sample-data-after-magento.md b/src/guides/v2.4/install-gde/install/sample-data-after-magento.md
index 9a7e7c97106..63eecda4286 100644
--- a/src/guides/v2.4/install-gde/install/sample-data-after-magento.md
+++ b/src/guides/v2.4/install-gde/install/sample-data-after-magento.md
@@ -8,8 +8,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/next-steps/sample-data/overview.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/next-steps/sample-data/overview.html
+status: migrated
---
The following topics discuss how to install optional sample data after you have already installed the Magento software. There is one additional step compared to pre-installation, which is to update the Magento [database schema](https://glossary.magento.com/database-schema) and data.
diff --git a/src/guides/v2.4/install-gde/install/sample-data-before-clone.md b/src/guides/v2.4/install-gde/install/sample-data-before-clone.md
index 5aefcffdc28..c1f973c3342 100644
--- a/src/guides/v2.4/install-gde/install/sample-data-before-clone.md
+++ b/src/guides/v2.4/install-gde/install/sample-data-before-clone.md
@@ -9,8 +9,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/next-steps/sample-data/git-repositories.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/next-steps/sample-data/git-repositories.html
+status: migrated
---
{% include install/sampledata/sample-data-clone-24.md %}
diff --git a/src/guides/v2.4/install-gde/install/sample-data-before-composer.md b/src/guides/v2.4/install-gde/install/sample-data-before-composer.md
index 77310a63685..edaf2950df9 100644
--- a/src/guides/v2.4/install-gde/install/sample-data-before-composer.md
+++ b/src/guides/v2.4/install-gde/install/sample-data-before-composer.md
@@ -8,8 +8,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/next-steps/sample-data/composer-packages.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/next-steps/sample-data/composer-packages.html
+status: migrated
---
{% include install/sampledata/sample-data-composer.md %}
diff --git a/src/guides/v2.4/install-gde/install/sample-data-other-cmds.md b/src/guides/v2.4/install-gde/install/sample-data-other-cmds.md
index 0d4d7a30f6e..793440e8b53 100644
--- a/src/guides/v2.4/install-gde/install/sample-data-other-cmds.md
+++ b/src/guides/v2.4/install-gde/install/sample-data-other-cmds.md
@@ -8,8 +8,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/next-steps/sample-data/remove-or-update.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/next-steps/sample-data/remove-or-update.html
+status: migrated
---
{% include install/sampledata/sample-data-other-cmds.md %}
diff --git a/src/guides/v2.4/install-gde/install/sample-data.md b/src/guides/v2.4/install-gde/install/sample-data.md
index 62e22503767..f9aad17e6dd 100644
--- a/src/guides/v2.4/install-gde/install/sample-data.md
+++ b/src/guides/v2.4/install-gde/install/sample-data.md
@@ -8,8 +8,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/next-steps/sample-data/overview.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/next-steps/sample-data/overview.html
+status: migrated
---
{% include install/sampledata/sample-data-intro.md %}
diff --git a/src/guides/v2.4/install-gde/install/verify.md b/src/guides/v2.4/install-gde/install/verify.md
index 250d5bf84bb..56622e5b762 100644
--- a/src/guides/v2.4/install-gde/install/verify.md
+++ b/src/guides/v2.4/install-gde/install/verify.md
@@ -8,8 +8,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/next-steps/verify.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/next-steps/verify.html
+status: migrated
---
## Verify the storefront (with optional sample data) {#instgde-verify-front-sample}
diff --git a/src/guides/v2.4/install-gde/prereq/apache.md b/src/guides/v2.4/install-gde/prereq/apache.md
index 5131d34dfb5..38c6f0c3b5e 100644
--- a/src/guides/v2.4/install-gde/prereq/apache.md
+++ b/src/guides/v2.4/install-gde/prereq/apache.md
@@ -4,8 +4,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/prerequisites/web-server/apache.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/prerequisites/web-server/apache.html
+status: migrated
---
## Apache versions supported {#apache-support}
diff --git a/src/guides/v2.4/install-gde/prereq/connect-auth.md b/src/guides/v2.4/install-gde/prereq/connect-auth.md
index 48a04e6bc0d..cd67fd042f4 100644
--- a/src/guides/v2.4/install-gde/prereq/connect-auth.md
+++ b/src/guides/v2.4/install-gde/prereq/connect-auth.md
@@ -5,8 +5,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/prerequisites/authentication-keys.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/prerequisites/authentication-keys.html
+status: migrated
---
{% include install/auth-tokens-get.md %}
diff --git a/src/guides/v2.4/install-gde/prereq/dev_install.md b/src/guides/v2.4/install-gde/prereq/dev_install.md
index cf917b17eea..046b67816c7 100644
--- a/src/guides/v2.4/install-gde/prereq/dev_install.md
+++ b/src/guides/v2.4/install-gde/prereq/dev_install.md
@@ -4,8 +4,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://developer.adobe.com/commerce/contributor/guides/install/clone-repository/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/contributor/guides/install/clone-repository/
+status: migrated
---
You can clone the latest code from the [Magento GitHub repository][gh-repo], and use code from a release branch or a development branch.
diff --git a/src/guides/v2.4/install-gde/prereq/elasticsearch.md b/src/guides/v2.4/install-gde/prereq/elasticsearch.md
index e0f8b599b7e..e1ceaa5f240 100644
--- a/src/guides/v2.4/install-gde/prereq/elasticsearch.md
+++ b/src/guides/v2.4/install-gde/prereq/elasticsearch.md
@@ -5,8 +5,8 @@ functional_areas:
- Search
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/prerequisites/search-engine/overview.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/prerequisites/search-engine/overview.html
+status: migrated
---
As of {{ site.data.var.ee }} and {{ site.data.var.ce }} 2.4, all installations must be configured to use [Elasticsearch][] or [OpenSearch][] as the [catalog](https://glossary.magento.com/catalog) search solution.
diff --git a/src/guides/v2.4/install-gde/prereq/es-aws.md b/src/guides/v2.4/install-gde/prereq/es-aws.md
index 2067440c887..a9b0a3e7312 100644
--- a/src/guides/v2.4/install-gde/prereq/es-aws.md
+++ b/src/guides/v2.4/install-gde/prereq/es-aws.md
@@ -5,8 +5,8 @@ functional_areas:
- Search
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/prerequisites/search-engine/aws-opensearch.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/prerequisites/search-engine/aws-opensearch.html
+status: migrated
---
{{ site.data.var.ee }} and {{ site.data.var.ce }} 2.4.3 supports using Amazon OpenSearch Service clusters. This service is the successor to Amazon Elasticsearch Service. This topic describes how to configure Commerce to use AWS OpenSearch, and how to migrate data from a local Elasticsearch or OpenSearch instance to an AWS OpenSearch cluster.
diff --git a/src/guides/v2.4/install-gde/prereq/es-config-apache.md b/src/guides/v2.4/install-gde/prereq/es-config-apache.md
index 8286322f614..4e642b8e6cf 100644
--- a/src/guides/v2.4/install-gde/prereq/es-config-apache.md
+++ b/src/guides/v2.4/install-gde/prereq/es-config-apache.md
@@ -7,8 +7,8 @@ functional_areas:
- Search
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/prerequisites/search-engine/configure-apache.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/prerequisites/search-engine/configure-apache.html
+status: migrated
---
{% include config/es-webserver-overview.md %}
diff --git a/src/guides/v2.4/install-gde/prereq/es-config-nginx.md b/src/guides/v2.4/install-gde/prereq/es-config-nginx.md
index 89a50b240d5..4a4e036edc8 100644
--- a/src/guides/v2.4/install-gde/prereq/es-config-nginx.md
+++ b/src/guides/v2.4/install-gde/prereq/es-config-nginx.md
@@ -7,8 +7,8 @@ functional_areas:
- Search
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/prerequisites/search-engine/configure-nginx.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/prerequisites/search-engine/configure-nginx.html
+status: migrated
---
{% include config/es-webserver-overview.md %}
diff --git a/src/guides/v2.4/install-gde/prereq/file-sys-perms-over.md b/src/guides/v2.4/install-gde/prereq/file-sys-perms-over.md
index 46d69d1ca8e..ecb468a8f45 100644
--- a/src/guides/v2.4/install-gde/prereq/file-sys-perms-over.md
+++ b/src/guides/v2.4/install-gde/prereq/file-sys-perms-over.md
@@ -4,8 +4,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/prerequisites/file-system/overview.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/prerequisites/file-system/overview.html
+status: migrated
---
It is important to secure your Magento installation in a development environment to help prevent issues related to unauthorized people or processes accessing—and potentially harming—your system. Use the following file system ownership and permissions guidelines to protect your installation.
diff --git a/src/guides/v2.4/install-gde/prereq/file-system-perms.md b/src/guides/v2.4/install-gde/prereq/file-system-perms.md
index 7a8e31bd624..3329c61f0d7 100644
--- a/src/guides/v2.4/install-gde/prereq/file-system-perms.md
+++ b/src/guides/v2.4/install-gde/prereq/file-system-perms.md
@@ -4,8 +4,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/prerequisites/file-system/configure-permissions.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/prerequisites/file-system/configure-permissions.html
+status: migrated
---
{% include install/file-system-perms-before.md %}
diff --git a/src/guides/v2.4/install-gde/prereq/install-rabbitmq.md b/src/guides/v2.4/install-gde/prereq/install-rabbitmq.md
index 3ae9b2407ec..355c1c1dfff 100644
--- a/src/guides/v2.4/install-gde/prereq/install-rabbitmq.md
+++ b/src/guides/v2.4/install-gde/prereq/install-rabbitmq.md
@@ -4,8 +4,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/prerequisites/rabbitmq.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/prerequisites/rabbitmq.html
+status: migrated
---
## RabbitMQ Overview {#overview}
diff --git a/src/guides/v2.4/install-gde/prereq/mysql.md b/src/guides/v2.4/install-gde/prereq/mysql.md
index f7fcd34960c..5e02d9241f4 100644
--- a/src/guides/v2.4/install-gde/prereq/mysql.md
+++ b/src/guides/v2.4/install-gde/prereq/mysql.md
@@ -1,7 +1,7 @@
---
title: MySQL
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/prerequisites/database-server/mysql.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/prerequisites/database-server/mysql.html
+status: migrated
---
## General guidelines {#instgde-prereq-mysql-intro}
diff --git a/src/guides/v2.4/install-gde/prereq/mysql_remote.md b/src/guides/v2.4/install-gde/prereq/mysql_remote.md
index 65c9b8a2eea..007daeefdfc 100644
--- a/src/guides/v2.4/install-gde/prereq/mysql_remote.md
+++ b/src/guides/v2.4/install-gde/prereq/mysql_remote.md
@@ -4,8 +4,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/prerequisites/database-server/mysql-remote.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/prerequisites/database-server/mysql-remote.html
+status: migrated
---
There are times when you will want to host the database on a separate server, rather than running the database server and the web server on the same machine.
diff --git a/src/guides/v2.4/install-gde/prereq/nginx.md b/src/guides/v2.4/install-gde/prereq/nginx.md
index 488c03787be..ae3f516aa61 100644
--- a/src/guides/v2.4/install-gde/prereq/nginx.md
+++ b/src/guides/v2.4/install-gde/prereq/nginx.md
@@ -4,8 +4,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/prerequisites/web-server/nginx.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/prerequisites/web-server/nginx.html
+status: migrated
---
Magento supports nginx 1.18 (or the [latest mainline version](https://nginx.org/en/linux_packages.html#mainline)). You must also install the latest version of `php-fpm`.
diff --git a/src/guides/v2.4/install-gde/prereq/optional.md b/src/guides/v2.4/install-gde/prereq/optional.md
index b7e9604c88a..6eca3593ffd 100644
--- a/src/guides/v2.4/install-gde/prereq/optional.md
+++ b/src/guides/v2.4/install-gde/prereq/optional.md
@@ -6,8 +6,8 @@ functional_areas:
- Setup
redirect_from:
- guides/v2.3/install-gde/trouble/php/tshoot_phpini.html
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/prerequisites/optional-software.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/prerequisites/optional-software.html
+status: migrated
---
## Magento optional software {#install-optional-intro}
diff --git a/src/guides/v2.4/install-gde/prereq/php-settings.md b/src/guides/v2.4/install-gde/prereq/php-settings.md
index 8187acd568f..185f0e24fef 100644
--- a/src/guides/v2.4/install-gde/prereq/php-settings.md
+++ b/src/guides/v2.4/install-gde/prereq/php-settings.md
@@ -4,8 +4,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/prerequisites/php-settings.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/prerequisites/php-settings.html
+status: migrated
---
This topic discusses how to set required [PHP](https://glossary.magento.com/php) options.
diff --git a/src/guides/v2.4/install-gde/prereq/prereq-overview.md b/src/guides/v2.4/install-gde/prereq/prereq-overview.md
index f700daea5f6..810e78b13e4 100644
--- a/src/guides/v2.4/install-gde/prereq/prereq-overview.md
+++ b/src/guides/v2.4/install-gde/prereq/prereq-overview.md
@@ -4,8 +4,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/prerequisites/overview.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/prerequisites/overview.html
+status: migrated
---
## Before you begin {#instgde-prereq-overview}
diff --git a/src/guides/v2.4/install-gde/prereq/security.md b/src/guides/v2.4/install-gde/prereq/security.md
index 11c12c308c6..7c9d776e4f1 100644
--- a/src/guides/v2.4/install-gde/prereq/security.md
+++ b/src/guides/v2.4/install-gde/prereq/security.md
@@ -7,8 +7,8 @@ functional_areas:
- Install
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/prerequisites/security.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/prerequisites/security.html
+status: migrated
---
## SELinux {#install-prereq-selinux}
diff --git a/src/guides/v2.4/install-gde/system-requirements.md b/src/guides/v2.4/install-gde/system-requirements.md
index c74c72f2f3c..4545ec0bd85 100644
--- a/src/guides/v2.4/install-gde/system-requirements.md
+++ b/src/guides/v2.4/install-gde/system-requirements.md
@@ -8,8 +8,8 @@ redirect_from:
- /guides/v2.4/install-gde/system-requirements-tech.html
- /guides/v2.4/architecture/tech-stack.html
- /system-requirements.html
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/system-requirements.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/system-requirements.html
+status: migrated
---
This table shows versions of third-party software dependencies that Adobe has tested with specific {{ site.data.var.ee }} and {{ site.data.var.ce }} releases. Adobe only supports the combination of system requirements described in the following table.
diff --git a/src/guides/v2.4/install-gde/tutorials/change-docroot-to-pub.md b/src/guides/v2.4/install-gde/tutorials/change-docroot-to-pub.md
index 072f2b362bb..e6a3f271e47 100644
--- a/src/guides/v2.4/install-gde/tutorials/change-docroot-to-pub.md
+++ b/src/guides/v2.4/install-gde/tutorials/change-docroot-to-pub.md
@@ -1,7 +1,7 @@
---
title: Modify docroot to improve security
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/docroot.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/docroot.html
+status: migrated
---
In a standard installation with an Apache web server, Magento is installed to the default web root: `/var/www/html/magento2`.
diff --git a/src/guides/v2.4/inventory/architecture.md b/src/guides/v2.4/inventory/architecture.md
deleted file mode 120000
index a226065aa12..00000000000
--- a/src/guides/v2.4/inventory/architecture.md
+++ /dev/null
@@ -1 +0,0 @@
-../../v2.3/inventory/architecture.md
\ No newline at end of file
diff --git a/src/guides/v2.4/inventory/architecture.md b/src/guides/v2.4/inventory/architecture.md
new file mode 100644
index 00000000000..af564b3915f
--- /dev/null
+++ b/src/guides/v2.4/inventory/architecture.md
@@ -0,0 +1,75 @@
+---
+group: inventory
+title: Inventory management architecture
+redirect_to: https://developer.adobe.com/commerce/php/architecture/modules/inventory-management/
+status: migrated
+---
+
+Magento 2 is a highly modular system that allows 3rd-party developers to extend and customize the system on many levels. As a result, a developer can replace or add any component (module) without affecting the rest of the system.
+
+Module interchangeability was one of the main reasons behind introducing [Service Layer]({{ page.baseurl }}/architecture/archi_perspectives/service_layer.html) in Magento 2. By using service contracts and providing extensions over them, 3rd-party developers can:
+
+* Enhance out-of-the-box business logic
+* Replace a module without breaking the system or other extensions relying on these contracts
+
+In Magento 2, a set of interfaces in a module's `/Api` directory typically define the service contracts, including the APIs and their implementations. A module interface expresses the elements (entity interfaces and services to manipulate them) that the module requires. These elements defined in the interface represent a gateway for communication between modules. The implementation contains the working business logic that corresponds to the elements declared in the interface.
+
+By placing service contracts (APIs), implementations, and UI code in the same module, Magento combines different architectural layers of the system in the scope of one component. Unfortunately, this means that a developer who wants to tweak a module's UI would be changing the same module as another developer who would like to substitute the implementation for predefined business logic. Even modules that the developer expects to be used in headless Magento installations (those that don't use the Admin at all) must contain UI code.
+
+## Inventory management service layer
+
+Implementing a good modular architecture means maintaining a loose coupling between components of the system, reducing dependencies on components that are not needed for a particular deployment. To allow modules to be swapped out, we have designed the Inventory Management modules to follow the [single responsibility principle](https://en.wikipedia.org/wiki/Single_responsibility_principle) (SRP). Each module has responsibility over a single part of the functionality, and all of its services are narrowly aligned with that responsibility.
+
+As a result of applying SRP to module responsibilities (while taking into account the multi-layered architecture of Magento), Inventory Management is comprised of independent modules responsible for:
+
+* Service contract APIs
+* Implementation of the business logic for APIs
+* Admin UI
+* Frontend UI
+
+The Admin and frontend UIs can be separated, because it's possible to have two different technology stacks. The Admin UI uses UI components, while the frontend UI can use the [PWA](https://developer.adobe.com/commerce/pwa-studio/) studio stack, consisting of technology such as webpack, React, Redux, and GraphQL.
+
+Now, instead of creating one module that covers a specialized business domain, we create up to four modules, each one responsible for a dedicated layer of the system to provide high granularity for customizations. For example, in the standard Magento architecture, the `InventorySales` module would have contained all the APIs, business logic, and UI definitions. Now, these responsibilities are defined in the `InventorySales`, `InventorySalesApi`, `InventorySalesAdminUI`, and `InventorySalesFrontendUI` modules.
+
+This approach implies additional code limitations in the modules:
+
+* All modules should depend on the API module. Implementations can be swapped in `di.xml` files.
+* API modules should contain web API tests. These tests cover API endpoints agnostically to the implementation details. Example: `InventoryApi\Tests\Api\*`
+* Only UI modules should contain MFTF tests, because these tests cover the interaction between the user and the UI. Example: `InventoryCatalogAdminUi\Test\Mftf\*`.
+
+## Module dependencies
+
+The list of Inventory Management dependencies varies, depending on whether the merchant has installed a headless version of Magento. These merchants have integrated Magento with external Enterprise Resource Planning (ERP) software, and they often consider the ERP software to be the "source of truth" for processes like order processing and inventory tracking. The ERP provides its own UI for managing information and processes. Attempting to use the Magento UI to manage the same things would be excessive and would lead to sophisticated bi-directional synchronization of all changed data.
+
+### Dependencies in a standard installation
+
+For non-headless installations, Inventory Management has dependencies on the following modules:
+
+* Backend
+* BundleProduct
+* Catalog
+* CatalogInventory (legacy)
+* ConfigurableProduct
+* Directory
+* EAV
+* GroupedProduct
+* ImportExport
+* Reports
+* Sales
+* Shipping
+* Store
+* UI
+
+### Dependencies in a headless installation
+
+In headless installations, Inventory Management is dependent on the following modules:
+
+* BundleProduct
+* Catalog
+* CatalogInventory (legacy)
+* ConfigurableProduct
+* EAV
+* GroupedProduct
+* ImportExport
+* Sales
+* Store
diff --git a/src/guides/v2.4/inventory/index.md b/src/guides/v2.4/inventory/index.md
index 915f4427fab..f38144cb64a 100644
--- a/src/guides/v2.4/inventory/index.md
+++ b/src/guides/v2.4/inventory/index.md
@@ -2,8 +2,8 @@
group: inventory
title: Inventory Management overview
landing-page: Inventory
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/inventory/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/inventory/
+status: migrated
---
{{site.data.var.ce}} and {{site.data.var.ee}} v2.3 include new and expanded features and APIs for {{site.data.var.im}}. {{site.data.var.im}} replaces all core APIs in the Open Source `CatalogInventory` module and the `ScalableInventory` module in Commerce. It also provides additional APIs to extend and add functionality.
diff --git a/src/guides/v2.4/inventory/inventory-api-reference.md b/src/guides/v2.4/inventory/inventory-api-reference.md
index 3f8b864c810..0e557332d35 100644
--- a/src/guides/v2.4/inventory/inventory-api-reference.md
+++ b/src/guides/v2.4/inventory/inventory-api-reference.md
@@ -1,6 +1,8 @@
---
group: inventory
title: Inventory API reference
+redirect_to: https://developer.adobe.com/commerce/php/development/components/web-api/inventory-management/
+status: migrated
---
{% assign tool = 'magento-cloud' %}
diff --git a/src/guides/v2.4/reference/cli/magento-commerce.md b/src/guides/v2.4/reference/cli/magento-commerce.md
index f88b56b8db8..aa4901a77d8 100644
--- a/src/guides/v2.4/reference/cli/magento-commerce.md
+++ b/src/guides/v2.4/reference/cli/magento-commerce.md
@@ -5,8 +5,8 @@ functional_areas:
- Configuration
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/reference/commerce-on-premises.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/reference/commerce-on-premises.html
+status: migrated
---
{% assign tool = 'bin/magento' %}
diff --git a/src/guides/v2.4/reference/cli/magento.md b/src/guides/v2.4/reference/cli/magento.md
index 60d69ba26ab..20e13235d71 100644
--- a/src/guides/v2.4/reference/cli/magento.md
+++ b/src/guides/v2.4/reference/cli/magento.md
@@ -5,8 +5,8 @@ functional_areas:
- Configuration
- System
- Setup
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/reference/magento-open-source.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/reference/magento-open-source.html
+status: migrated
---
{% assign tool = 'bin/magento' %}
diff --git a/src/guides/v2.4/reference/mftf/backward-incompatible-changes.md b/src/guides/v2.4/reference/mftf/backward-incompatible-changes.md
index deffde7ac2b..2eae7d41ac1 100644
--- a/src/guides/v2.4/reference/mftf/backward-incompatible-changes.md
+++ b/src/guides/v2.4/reference/mftf/backward-incompatible-changes.md
@@ -3,6 +3,8 @@ title: Backward incompatible changes in functional tests
group: mftf
functional_areas:
- Test
+redirect_to: https://developer.adobe.com/commerce/testing/functional-testing-framework/backward-incompatible-changes/
+status: migrated
---
This reference describes important changes introduced to functional tests in the Magento codebase after the 2.3.0 release. This is in compliance with the [Magento MFTF test versioning and backward compatibility policy][].
diff --git a/src/guides/v2.4/release-notes/2-4-2-p2.md b/src/guides/v2.4/release-notes/2-4-2-p2.md
index 9fff70dc977..8b88204241a 100644
--- a/src/guides/v2.4/release-notes/2-4-2-p2.md
+++ b/src/guides/v2.4/release-notes/2-4-2-p2.md
@@ -1,6 +1,8 @@
---
group: release-notes
title: Adobe Commerce 2.4.2-p2 Release Notes
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/release/notes/security-patches/2-4-2-p2.html
+status: migrated
---
{{ site.data.var.ee }} 2.4.2-p2 is a security release that provides 18 security fixes that enhance your Magento 2.4.2 deployment. Merchants can now install time-sensitive security fixes without applying the hundreds of functional fixes and enhancements that a full quarterly release provides. Patch 2.4.2-p2 provides fixes for vulnerabilities that have been identified in our previous quarterly release, {{ site.data.var.ee }} 2.4.2 and {{ site.data.var.ce }} 2.4.2.
diff --git a/src/guides/v2.4/release-notes/2-4-3-p1.md b/src/guides/v2.4/release-notes/2-4-3-p1.md
index 1814d6aba6b..141cff6c842 100644
--- a/src/guides/v2.4/release-notes/2-4-3-p1.md
+++ b/src/guides/v2.4/release-notes/2-4-3-p1.md
@@ -1,6 +1,8 @@
---
group: release-notes
title: Adobe Commerce 2.4.3-p1 Release Notes
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/release/notes/security-patches/2-4-3-p1.html
+status: migrated
---
{{ site.data.var.ee }} 2.4.3-p1 is a security release that provides seven security fixes that enhance your {{ site.data.var.ee }} 2.4.3 or {{ site.data.var.ce }} 2.4.3 deployment. It provides fixes for vulnerabilities that have been identified in the previous release ({{ site.data.var.ee }} 2.4.3 and {{ site.data.var.ce }} 2.4.3).
diff --git a/src/guides/v2.4/release-notes/2-4-3-p2.md b/src/guides/v2.4/release-notes/2-4-3-p2.md
index 84a49fc7459..255a9a6c02d 100644
--- a/src/guides/v2.4/release-notes/2-4-3-p2.md
+++ b/src/guides/v2.4/release-notes/2-4-3-p2.md
@@ -1,6 +1,8 @@
---
group: release-notes
title: Adobe Commerce 2.4.3-p2 Release Notes
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/release/notes/security-patches/2-4-3-p2.html
+status: migrated
---
{{ site.data.var.ee }} 2.4.3-p2 is a security release that provides two security fixes that enhance your {{ site.data.var.ee }} 2.4.3 or {{ site.data.var.ce }} 2.4.3 deployment. It provides fixes for vulnerabilities that have been identified in the previous release ({{ site.data.var.ee }} 2.4.3 and {{ site.data.var.ce }} 2.4.3).
diff --git a/src/guides/v2.4/release-notes/2-4-3-p3.md b/src/guides/v2.4/release-notes/2-4-3-p3.md
index e10f2184434..92405a307c6 100644
--- a/src/guides/v2.4/release-notes/2-4-3-p3.md
+++ b/src/guides/v2.4/release-notes/2-4-3-p3.md
@@ -1,6 +1,8 @@
---
group: release-notes
title: Adobe Commerce 2.4.3-p3 Release Notes
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/release/notes/security-patches/2-4-3-p3.html
+status: migrated
---
{{ site.data.var.ee }} 2.4.3-p3 is a security release that provides 17 security fixes that enhance your {{ site.data.var.ee }} 2.4.3 or {{ site.data.var.ce }} 2.4.3 deployment. It provides fixes for vulnerabilities that have been identified in the previous release ({{ site.data.var.ee }} 2.4.3 and {{ site.data.var.ce }} 2.4.3).
diff --git a/src/guides/v2.4/release-notes/2-4-4-p1.md b/src/guides/v2.4/release-notes/2-4-4-p1.md
index 5e16570019a..a8dcf3d7e9b 100644
--- a/src/guides/v2.4/release-notes/2-4-4-p1.md
+++ b/src/guides/v2.4/release-notes/2-4-4-p1.md
@@ -1,6 +1,8 @@
---
group: release-notes
title: Adobe Commerce 2.4.4-p1 Release Notes
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/release/notes/security-patches/2-4-4-p1.html
+status: migrated
---
{{ site.data.var.ee }} 2.4.4-p1 is a security release that provides 17 security fixes that enhance your {{ site.data.var.ee }} 2.4.4 or {{ site.data.var.ce }} 2.4.4 deployment. It provides fixes for vulnerabilities that have been identified in the previous release ({{ site.data.var.ee }} 2.4.4 and {{ site.data.var.ce }} 2.4.4).
diff --git a/src/guides/v2.4/release-notes/2-4-4-p2.md b/src/guides/v2.4/release-notes/2-4-4-p2.md
new file mode 100644
index 00000000000..3846e061205
--- /dev/null
+++ b/src/guides/v2.4/release-notes/2-4-4-p2.md
@@ -0,0 +1,29 @@
+---
+group: release-notes
+title: Adobe Commerce 2.4.4-p2 Release Notes
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/release/notes/security-patches/2-4-4-p2.html
+status: migrated
+---
+
+{{ site.data.var.ee }} 2.4.4-p2 is a security release that provides five security fixes that enhance your {{ site.data.var.ee }} 2.4.4 or {{ site.data.var.ce }} 2.4.4 deployment. It provides fixes for vulnerabilities that have been identified in the previous release ({{ site.data.var.ee }} 2.4.4 and {{ site.data.var.ce }} 2.4.4).
+
+{:.bs-callout-info}
+Releases may contain backward-incompatible changes (BIC). To review minor backward-incompatible changes, see [BIC reference]({{page.baseurl}}/release-notes/backward-incompatible-changes/reference.html). (Major backward-incompatible issues are described in [BIC highlights]({{page.baseurl}}/release-notes/backward-incompatible-changes/index.html). 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](https://support.magento.com/hc/en-us/articles/7707818131597-Apply-a-patch-to-continue-offering-DHL-as-shipping-carrier?_ga=2.201689433.994140970.1661546561-1218319047.1534347481) Knowledge Base article for information about downloading and installing the patch.
+
+## What's in this release?
+
+This security patch includes five security bug fixes. One fix included the creation of a new configuration setting. The **Require email confirmation if email has been changed** configuration setting lets administrators require email confirmation when an admin user changes their email address.
+
+See [Adobe Security Bulletin](https://helpx.adobe.com/security/products/magento/apsb22-48.html).
+
+## Installation and upgrade instructions
+
+For instructions on downloading and applying security patches (including patch 2.4.4-p2), see [Quick start install]({{site.baseurl}}/guides/v2.4/install-gde/composer.html).
+
+## More information?
+
+For general information about security patches, see [Introducing the New Security Patch Release](https://community.magento.com/t5/Magento-DevBlog/Introducing-the-New-Security-Patch-Release/ba-p/141287).
diff --git a/src/guides/v2.4/release-notes/2-4-5-p1.md b/src/guides/v2.4/release-notes/2-4-5-p1.md
new file mode 100644
index 00000000000..42c672ce451
--- /dev/null
+++ b/src/guides/v2.4/release-notes/2-4-5-p1.md
@@ -0,0 +1,25 @@
+---
+group: release-notes
+title: Adobe Commerce 2.4.5-p1 Release Notes
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/release/notes/security-patches/2-4-5-p1.html
+status: migrated
+---
+
+{{ site.data.var.ee }} 2.4.5-p1 is a security release that provides five security fixes that enhance your {{ site.data.var.ee }} 2.4.5 or {{ site.data.var.ce }} 2.4.5 deployment. It provides fixes for vulnerabilities that have been identified in the previous release ({{ site.data.var.ee }} 2.4.5 and {{ site.data.var.ce }} 2.4.5).
+
+{:.bs-callout-info}
+Releases may contain backward-incompatible changes (BIC). To review minor backward-incompatible changes, see [BIC reference]({{page.baseurl}}/release-notes/backward-incompatible-changes/reference.html). (Major backward-incompatible issues are described in [BIC highlights]({{page.baseurl}}/release-notes/backward-incompatible-changes/index.html). Not all releases introduce major BICs.)
+
+## What's in this release?
+
+This security patch includes five security bug fixes. One fix included the creation of a new configuration setting. The **Require email confirmation if email has been changed** configuration setting lets administrators require email confirmation when an admin user changes their email address.
+
+See [Adobe Security Bulletin](https://helpx.adobe.com/security/products/magento/apsb22-48.html).
+
+## Installation and upgrade instructions
+
+For instructions on downloading and applying security patches (including patch 2.4.5-p1), see [Quick start install]({{site.baseurl}}/guides/v2.4/install-gde/composer.html).
+
+## More information?
+
+For general information about security patches, see [Introducing the New Security Patch Release](https://community.magento.com/t5/Magento-DevBlog/Introducing-the-New-Security-Patch-Release/ba-p/141287).
diff --git a/src/guides/v2.4/release-notes/b2b-release-notes.md b/src/guides/v2.4/release-notes/b2b-release-notes.md
index 845a7abca93..dc3a7d69fc4 100644
--- a/src/guides/v2.4/release-notes/b2b-release-notes.md
+++ b/src/guides/v2.4/release-notes/b2b-release-notes.md
@@ -1,8 +1,8 @@
---
group: release-notes
title: Commerce B2B Release Notes
-migrated_to: https://experienceleague.adobe.com/docs/commerce-admin/b2b/release-notes.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-admin/b2b/release-notes.html
+status: migrated
---
The release notes for the B2B extension captures additions and bug fixes that {{ site.data.var.ee }} has added during a release cycle.
diff --git a/src/guides/v2.4/release-notes/backward-incompatible-changes/index.md b/src/guides/v2.4/release-notes/backward-incompatible-changes/index.md
index 11b7fe8fd62..318716b43f3 100644
--- a/src/guides/v2.4/release-notes/backward-incompatible-changes/index.md
+++ b/src/guides/v2.4/release-notes/backward-incompatible-changes/index.md
@@ -1,6 +1,8 @@
---
group: release-notes
title: Magento 2.4 backward incompatible changes
+redirect_to: https://developer.adobe.com/commerce/php/development/backward-incompatible-changes/highlights/
+status: migrated
---
This page highlights backward incompatible changes between releases that have a major impact and require detailed explanation and special instructions to ensure third-party modules continue working with Magento. High-level reference information for all backward incompatible changes in each release are documented in the [Backward incompatible changes reference]({{page.baseurl}}/release-notes/backward-incompatible-changes/reference.html) topic.
diff --git a/src/guides/v2.4/release-notes/backward-incompatible-changes/reference.md b/src/guides/v2.4/release-notes/backward-incompatible-changes/reference.md
index 2ce9a3a173d..7df96eb0ac7 100644
--- a/src/guides/v2.4/release-notes/backward-incompatible-changes/reference.md
+++ b/src/guides/v2.4/release-notes/backward-incompatible-changes/reference.md
@@ -1,6 +1,8 @@
---
group: release-notes
title: Backward incompatible changes reference
+redirect_to: https://developer.adobe.com/commerce/php/development/backward-incompatible-changes/reference/
+status: migrated
---
Use this page to review high-level reference information for all backward incompatible changes in each release. Backward incompatible changes that have a major impact and require detailed explanation and special instructions are documented in the [Backward incompatible changes highlights]({{page.baseurl}}/release-notes/backward-incompatible-changes/index.html) topic.
diff --git a/src/guides/v2.4/release-notes/bk-release-notes.md b/src/guides/v2.4/release-notes/bk-release-notes.md
index 9c189ecdfe8..31014ee878e 100644
--- a/src/guides/v2.4/release-notes/bk-release-notes.md
+++ b/src/guides/v2.4/release-notes/bk-release-notes.md
@@ -2,13 +2,17 @@
group: release-notes
title: 2.4 Release Information
redirect_from: magento-release-information.html
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/release/notes/overview.html
+status: migrated
---
## {{site.data.var.ee}} and {{site.data.var.ce}} 2.4.x release notes
+* [{{site.data.var.ee}} 2.4.5-p1 Release Notes]({{page.baseurl}}/release-notes/2-4-5-p1.html)
* [{{site.data.var.ce}} 2.4.5 Release Notes]({{page.baseurl}}/release-notes/open-source-2-4-5.html)
* [{{site.data.var.ee}} 2.4.5 Release Notes]({{page.baseurl}}/release-notes/commerce-2-4-5.html)
+* [{{site.data.var.ee}} 2.4.4-p2 Release Notes]({{page.baseurl}}/release-notes/2-4-4-p2.html)
* [{{site.data.var.ee}} 2.4.4-p1 Release Notes]({{page.baseurl}}/release-notes/2-4-4-p1.html)
* [{{site.data.var.ce}} 2.4.4 Release Notes]({{page.baseurl}}/release-notes/open-source-2-4-4.html)
* [{{site.data.var.ee}} 2.4.4 Release Notes]({{page.baseurl}}/release-notes/commerce-2-4-4.html)
diff --git a/src/guides/v2.4/release-notes/commerce-2-4-1.md b/src/guides/v2.4/release-notes/commerce-2-4-1.md
index d8753d0fa8b..baeeaac25f2 100644
--- a/src/guides/v2.4/release-notes/commerce-2-4-1.md
+++ b/src/guides/v2.4/release-notes/commerce-2-4-1.md
@@ -1,6 +1,8 @@
---
group: release-notes
title: Adobe Commerce 2.4.1 Release Notes
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/release/notes/adobe-commerce/2-4-1.html
+status: migrated
---
{{site.data.var.ee}} 2.4.1 introduces enhancements to performance and security plus significant additions to the B2B feature set. Security enhancements include support for the `SameSite` attribute for cookies and the addition of CAPTCHA protection for payment-related and order-related API endpoints and the Place Order storefront page. B2B improvements focus on the order approval process, B2B shipping methods, expanded logging of Admin actions, and enhanced security on storefront.
@@ -173,7 +175,7 @@ B2B merchants can now control shipping methods that are offered to each Company.
#### New Admin features
* B2B merchants can create orders from the Admin on behalf of customers using Payment on Account as the payment method.
-* Merchants can now directly view all quotes associated with a user from the customer’s detail page.
+* Merchants can now directly view all quotes associated with a user from the customer's detail page.
* Merchants can now filter the Customers Now Online grid by Company.
* Admins can now filter customers in the Admin by Sales Rep.
@@ -434,7 +436,7 @@ We have fixed hundreds of issues in the Magento 2.4.1 core code.
-* The **Delete** button on the **Add to Shopping Cart by SKU** section of a customer’s **Manage Shopping Cart** page now works as expected when multiple rows are selected.
+* The **Delete** button on the **Add to Shopping Cart by SKU** section of a customer's **Manage Shopping Cart** page now works as expected when multiple rows are selected.
@@ -442,7 +444,7 @@ We have fixed hundreds of issues in the Magento 2.4.1 core code.
-* A customer’s shipping address is now selected by default at checkout when the address is located in the country identified on the Allow Countries list and that list includes only that country. Previously, Magento did not select the address as default and displayed this error message: `Please specify a regionId in shipping address`.
+* A customer's shipping address is now selected by default at checkout when the address is located in the country identified on the Allow Countries list and that list includes only that country. Previously, Magento did not select the address as default and displayed this error message: `Please specify a regionId in shipping address`.
@@ -486,7 +488,7 @@ We have fixed hundreds of issues in the Magento 2.4.1 core code.
-* The success message that Magento displays when a shopper adds a product to their cart from the customer account sidebar now contains a link to the shopper’s shopping cart. _Fix submitted by Ajith in pull request [27977](https://github.com/magento/magento2/pull/27977)_. [GitHub-29097](https://github.com/magento/magento2/issues/29097)
+* The success message that Magento displays when a shopper adds a product to their cart from the customer account sidebar now contains a link to the shopper's shopping cart. _Fix submitted by Ajith in pull request [27977](https://github.com/magento/magento2/pull/27977)_. [GitHub-29097](https://github.com/magento/magento2/issues/29097)
@@ -512,7 +514,7 @@ We have fixed hundreds of issues in the Magento 2.4.1 core code.
-* Magento now removes disabled products from a shopper’s cart before checkout. Previously, when a shopper added a product to their cart that was disabled before checkout completed, Magento removed the disabled product from the cart, but the product remained in the quote, and the shopper could not check out. [GitHub-26680](https://github.com/magento/magento2/issues/26680)
+* Magento now removes disabled products from a shopper's cart before checkout. Previously, when a shopper added a product to their cart that was disabled before checkout completed, Magento removed the disabled product from the cart, but the product remained in the quote, and the shopper could not check out. [GitHub-26680](https://github.com/magento/magento2/issues/26680)
@@ -520,7 +522,7 @@ We have fixed hundreds of issues in the Magento 2.4.1 core code.
-* Shoppers can now open a product’s detail page by clicking on the product name in the compare products sidebar. _Fix submitted by Eduard Chitoraga in pull request [27451](https://github.com/magento/magento2/pull/27451)_. [GitHub-21101](https://github.com/magento/magento2/issues/21101)
+* Shoppers can now open a product's detail page by clicking on the product name in the compare products sidebar. _Fix submitted by Eduard Chitoraga in pull request [27451](https://github.com/magento/magento2/pull/27451)_. [GitHub-21101](https://github.com/magento/magento2/issues/21101)
@@ -640,11 +642,11 @@ We have fixed hundreds of issues in the Magento 2.4.1 core code.
-* Magento no longer throws a validation error when you use POST `/V1/products` to a configurable product with an `int` value of 0. Previously, Magento threw this error: `Product with id "%1" does not contain required attribute “%2”.”` _Fix submitted by Vadim Malesh in pull request [29001](https://github.com/magento/magento2/pull/29001)_. [GitHub-13210](https://github.com/magento/magento2/issues/13210)
+* Magento no longer throws a validation error when you use POST `/V1/products` to a configurable product with an `int` value of 0. Previously, Magento threw this error: `Product with id "%1" does not contain required attribute "%2"."` _Fix submitted by Vadim Malesh in pull request [29001](https://github.com/magento/magento2/pull/29001)_. [GitHub-13210](https://github.com/magento/magento2/issues/13210)
-* The configuration options attribute of a parent product are no longer assigned to a new configurable product’s `size` attribute. _Fix submitted by Abel Truong in pull request [27339](https://github.com/magento/magento2/pull/27339)_. [GitHub-26449](https://github.com/magento/magento2/issues/26449)
+* The configuration options attribute of a parent product are no longer assigned to a new configurable product's `size` attribute. _Fix submitted by Abel Truong in pull request [27339](https://github.com/magento/magento2/pull/27339)_. [GitHub-26449](https://github.com/magento/magento2/issues/26449)
### Cookies
@@ -782,7 +784,7 @@ We have fixed hundreds of issues in the Magento 2.4.1 core code.
-* A product’s `stock_item` data is updated and downloadable product links and samples are preserved as expected when you use a REST PUT call to update `stock_item` values. Previously, after the product update, the product no longer contained links to download content. _Fix submitted by Vadim Malesh in pull request [28799](https://github.com/magento/magento2/pull/28799)_. [GitHub-21811](https://github.com/magento/magento2/issues/21811)
+* A product's `stock_item` data is updated and downloadable product links and samples are preserved as expected when you use a REST PUT call to update `stock_item` values. Previously, after the product update, the product no longer contained links to download content. _Fix submitted by Vadim Malesh in pull request [28799](https://github.com/magento/magento2/pull/28799)_. [GitHub-21811](https://github.com/magento/magento2/issues/21811)
@@ -814,7 +816,7 @@ We have fixed hundreds of issues in the Magento 2.4.1 core code.
-* You can now create an email template that sends email with `Content-Type: "text/plain”`. Previously, Magento ignored the content type specified in the template. _Fix submitted by twoonesixdigital in pull request [26474](https://github.com/magento/magento2/pull/26474)_. [GitHub-26471](https://github.com/magento/magento2/issues/26471)
+* You can now create an email template that sends email with `Content-Type: "text/plain"`. Previously, Magento ignored the content type specified in the template. _Fix submitted by twoonesixdigital in pull request [26474](https://github.com/magento/magento2/pull/26474)_. [GitHub-26471](https://github.com/magento/magento2/issues/26471)
@@ -962,7 +964,7 @@ We have fixed hundreds of issues in the Magento 2.4.1 core code.
-* Magento now adds an admin user’s ACL role ID to the product category tree cache ID. This will limit the category trees that an admin with limited scope can see as expected. _Fix submitted by quangdo-aligent in pull request [27429](https://github.com/magento/magento2/pull/27429)_. [GitHub-28306](https://github.com/magento/magento2/issues/28306)
+* Magento now adds an admin user's ACL role ID to the product category tree cache ID. This will limit the category trees that an admin with limited scope can see as expected. _Fix submitted by quangdo-aligent in pull request [27429](https://github.com/magento/magento2/pull/27429)_. [GitHub-28306](https://github.com/magento/magento2/issues/28306)
### Gift cards
@@ -1475,7 +1477,7 @@ We have fixed hundreds of issues in the Magento 2.4.1 core code.
-* Elasticsearch results now include the correct values for each store view’s attribute options. If a Dropdown or Multiple Select attribute has a different option value in the non-default store view than in the default store view, Elasticsearch now indexes that value or returns the product with that value in the results. Previously, Elasticsearch did not index that value or return the product with that value in the results.
+* Elasticsearch results now include the correct values for each store view's attribute options. If a Dropdown or Multiple Select attribute has a different option value in the non-default store view than in the default store view, Elasticsearch now indexes that value or returns the product with that value in the results. Previously, Elasticsearch did not index that value or return the product with that value in the results.
@@ -1525,7 +1527,7 @@ We have fixed hundreds of issues in the Magento 2.4.1 core code.
-* The **Set Product as New** attribute label now appears as expected on a product’s detail and scheduled update pages.
+* The **Set Product as New** attribute label now appears as expected on a product's detail and scheduled update pages.
@@ -1537,7 +1539,7 @@ We have fixed hundreds of issues in the Magento 2.4.1 core code.
-* You can now use POST `/V1/products/special-price` to update a product’s special price without specifying a `price_to` parameter value. Previously, attempts to set the price update without the `price_to` parameter specified were unsuccessful.
+* You can now use POST `/V1/products/special-price` to update a product's special price without specifying a `price_to` parameter value. Previously, attempts to set the price update without the `price_to` parameter specified were unsuccessful.
### Store
@@ -1578,7 +1580,7 @@ We have fixed hundreds of issues in the Magento 2.4.1 core code.
-* Magento no longer displays a fixed product tax attribute on the storefront for a product after a merchant has unassigned it from the product’s attribute set.
+* Magento no longer displays a fixed product tax attribute on the storefront for a product after a merchant has unassigned it from the product's attribute set.
### Test
@@ -1686,7 +1688,7 @@ We have fixed hundreds of issues in the Magento 2.4.1 core code.
-* Magento now correctly displays the calendar icon used for selecting a customer’s date of birth on the Conditions tab of **Customers** > **Segments** > **Add Segment**.
+* Magento now correctly displays the calendar icon used for selecting a customer's date of birth on the Conditions tab of **Customers** > **Segments** > **Add Segment**.
@@ -1890,7 +1892,7 @@ We have fixed hundreds of issues in the Magento 2.4.1 core code.
-* Added a test for deleting items from a customer’s wish list as an Admin user. _Fix submitted by Dmitry Tsymbal in pull request [28632](https://github.com/magento/magento2/pull/28632)_. [GitHub-28721](https://github.com/magento/magento2/issues/28721)
+* Added a test for deleting items from a customer's wish list as an Admin user. _Fix submitted by Dmitry Tsymbal in pull request [28632](https://github.com/magento/magento2/pull/28632)_. [GitHub-28721](https://github.com/magento/magento2/issues/28721)
diff --git a/src/guides/v2.4/release-notes/commerce-2-4-2.md b/src/guides/v2.4/release-notes/commerce-2-4-2.md
index acb39626a89..6953071db3f 100644
--- a/src/guides/v2.4/release-notes/commerce-2-4-2.md
+++ b/src/guides/v2.4/release-notes/commerce-2-4-2.md
@@ -1,6 +1,8 @@
---
group: release-notes
title: Adobe Commerce 2.4.2 Release Notes
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/release/notes/adobe-commerce/2-4-2.html
+status: migrated
---
{{site.data.var.ee}} 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. B2B improvements focus on support for online payments for purchase orders. Elasticsearch 7.9.x and Redis 6.x are now supported.
@@ -375,7 +377,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* 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.
+* 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.
@@ -439,7 +441,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* Magento now correctly updates a cart’s item subtotal when a shopper clicks **Update Shopping Cart** while checking out with multiple addresses. [GitHub-30408](https://github.com/magento/magento2/issues/30408)
+* Magento now correctly updates a cart's item subtotal when a shopper clicks **Update Shopping Cart** while checking out with multiple addresses. [GitHub-30408](https://github.com/magento/magento2/issues/30408)
@@ -481,7 +483,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* Problems with product sort order on the storefront have been resolved. Previously, when Magento 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.
+* Problems with product sort order on the storefront have been resolved. Previously, when Magento 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.
@@ -533,7 +535,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* 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](https://github.com/magento/magento2/issues/26432)
+* 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](https://github.com/magento/magento2/issues/26432)
@@ -553,7 +555,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* 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](https://github.com/magento/magento2/issues/26432)
+* 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](https://github.com/magento/magento2/issues/26432)
@@ -607,7 +609,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* Corrected the pluralization of “item” in the mini cart and checkout order summary. [GitHub-29920](https://github.com/magento/magento2/issues/29920)
+* Corrected the pluralization of "item" in the mini cart and checkout order summary. [GitHub-29920](https://github.com/magento/magento2/issues/29920)
@@ -691,7 +693,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* A virtual product no longer changes type when its status is changed from enabled to disabled (or vice versa). Previously, Magento changed a product’s type from virtual to simple when its status changed.
+* A virtual product no longer changes type when its status is changed from enabled to disabled (or vice versa). Previously, Magento changed a product's type from virtual to simple when its status changed.
@@ -809,7 +811,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* 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, Magento 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)”}`
+* 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, Magento 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
@@ -819,7 +821,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
* 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`.
+* Resolved issues with Composer upgrades that were the result of the dotdigital module's dependency on `magento/module-authorization`.
### Downloadable
@@ -877,7 +879,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* Images on a store’s home page are now rendered successfully. Previously, the page source HTML was corrupted because the three consecutive slashes in the image’s base64 code was misinterpreted as a comment.
+* Images on a store's home page are now rendered successfully. Previously, the page source HTML was corrupted because the three consecutive slashes in the image's base64 code was misinterpreted as a comment.
@@ -899,7 +901,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* You can now configure a native session handler that differs from the handler that is defined in `php.ini`. Previously, `SessionManager` did not set the memcache as `save_handler`, but instead used the file’s `session_handler`. Magento threw this error: `main.CRITICAL: Warning: SessionHandler::read(): open(127.0.0.1:11211/sess_0imeeaqmnvemdg4e3h57tat0ik, O_RDWR) failed: No such file or directory (2) in../vendor/magento/framework/Session/SaveHandler/Native.php on line 22 {"exception":"[object] (Exception(code: 0): Warning: SessionHandler::read(): open(127.0.0.1:11211/sess_0imeeaqmnvemdg4e3h57tat0ik, O_RDWR) failed: No such file or directory (2) in ../vendor/magento/framework/Session/SaveHandler/Native.php on line 22 at ../vendor/magento/framework/App/ErrorHandler.php:61)”}`. [GitHub-24717](https://github.com/magento/magento2/issues/24717)
+* You can now configure a native session handler that differs from the handler that is defined in `php.ini`. Previously, `SessionManager` did not set the memcache as `save_handler`, but instead used the file's `session_handler`. Magento threw this error: `main.CRITICAL: Warning: SessionHandler::read(): open(127.0.0.1:11211/sess_0imeeaqmnvemdg4e3h57tat0ik, O_RDWR) failed: No such file or directory (2) in../vendor/magento/framework/Session/SaveHandler/Native.php on line 22 {"exception":"[object] (Exception(code: 0): Warning: SessionHandler::read(): open(127.0.0.1:11211/sess_0imeeaqmnvemdg4e3h57tat0ik, O_RDWR) failed: No such file or directory (2) in ../vendor/magento/framework/Session/SaveHandler/Native.php on line 22 at ../vendor/magento/framework/App/ErrorHandler.php:61)"}`. [GitHub-24717](https://github.com/magento/magento2/issues/24717)
@@ -1107,7 +1109,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* Added missing `order_data` array to `EmailSender` classes. This brings these classes into alignment with Magento’s recommendation to use scalar variables instead of objects within the email templates. [GitHub-29604](https://github.com/magento/magento2/issues/29604)
+* Added missing `order_data` array to `EmailSender` classes. This brings these classes into alignment with Magento's recommendation to use scalar variables instead of objects within the email templates. [GitHub-29604](https://github.com/magento/magento2/issues/29604)
### Google Tag Manager
@@ -1245,7 +1247,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* Images on a store’s home page are now rendered successfully. Previously, the page source HTML was corrupted because the three consecutive slashes in the image’s base64 code were misinterpreted as a comment.
+* Images on a store's home page are now rendered successfully. Previously, the page source HTML was corrupted because the three consecutive slashes in the image's base64 code were misinterpreted as a comment.
@@ -1271,7 +1273,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* Customer address `region_id` is no longer assigned a `NULL` value when you import customer addresses using a CSV file (`entity type = "customer address"` and `import behavior = "add/update”`) from which certain field values have been deleted.
+* Customer address `region_id` is no longer assigned a `NULL` value when you import customer addresses using a CSV file (`entity type = "customer address"` and `import behavior = "add/update"`) from which certain field values have been deleted.
@@ -1649,7 +1651,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* Magento now completes Payflow Pro payments successfully when the shopper’s name contains accented letters. Previously, payment did not complete, and Magento logged this error: `report.CRITICAL: String to be escaped was not valid UTF-8 or could not be converted`.
+* Magento now completes Payflow Pro payments successfully when the shopper's name contains accented letters. Previously, payment did not complete, and Magento logged this error: `report.CRITICAL: String to be escaped was not valid UTF-8 or could not be converted`.
@@ -1663,7 +1665,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* Magento no longer creates duplicate orders when an order is placed with PayPal Express. Previously, when a shopper tried to pay for an order with PayPal Express but PayPal returned an error, Magento still created the order. This resulted in duplicate orders on the merchant’s site. [GitHub-13952](https://github.com/magento/magento2/issues/13952)
+* Magento no longer creates duplicate orders when an order is placed with PayPal Express. Previously, when a shopper tried to pay for an order with PayPal Express but PayPal returned an error, Magento still created the order. This resulted in duplicate orders on the merchant's site. [GitHub-13952](https://github.com/magento/magento2/issues/13952)
@@ -1743,7 +1745,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* Magento no longer displays the contents of a customer’s cart after the customers session expires. Previously, Magento displayed this error when a guest customer tried to check out when persistent shopping cart was enabled: `No such entity with cartid = 0`.
+* Magento no longer displays the contents of a customer's cart after the customers session expires. Previously, Magento displayed this error when a guest customer tried to check out when persistent shopping cart was enabled: `No such entity with cartid = 0`.
### Pricing
@@ -2011,7 +2013,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* The `rest/V1/products/special-price` API can now be used to schedule product special prices for multiple stores. Previously, Magento threw an error when a merchant scheduled a price update for multiple stores for same `from` and `to` time when a roll back is available at the new schedule’s start time.
+* The `rest/V1/products/special-price` API can now be used to schedule product special prices for multiple stores. Previously, Magento threw an error when a merchant scheduled a price update for multiple stores for same `from` and `to` time when a roll back is available at the new schedule's start time.
### Store
@@ -2021,7 +2023,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* Magento now creates correct URLs for categories and products after a store view’s top-level URL key is changed. Previously, when a store view’s category tree contained modified `url_keys`, if a category key did not change but the category parents’ key did, then the original code would used the category’s default store view when creating URLs. [GitHub-28633](https://github.com/magento/magento2/issues/28633)
+* Magento now creates correct URLs for categories and products after a store view's top-level URL key is changed. Previously, when a store view's category tree contained modified `url_keys`, if a category key did not change but the category parents' key did, then the original code would used the category's default store view when creating URLs. [GitHub-28633](https://github.com/magento/magento2/issues/28633)
### Target rules
@@ -2217,7 +2219,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* Magento now preserves an attribute’s value when you move the attribute from one group to another.
+* Magento now preserves an attribute's value when you move the attribute from one group to another.
@@ -2245,7 +2247,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* The WAI-ARIA attribute `aria-atomic="true”` has been added to the error container tag. [GitHub-29560](https://github.com/magento/magento2/issues/29560)
+* The WAI-ARIA attribute `aria-atomic="true"` has been added to the error container tag. [GitHub-29560](https://github.com/magento/magento2/issues/29560)
@@ -2287,7 +2289,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* You can now use POST `V1/invoice/:invoiceId/refund` to refund an invoice that has a zero quantity of products and zero shipping charges (for example, `{“items": [{"qty": 0, "orderItemId": 6, "extensionAttributes": {}}], "appendComment": false, "notify": true, "isOnline": true, "arguments": {"adjustment_negative": 0.0, "adjustment_positive": 0.99, "shipping_amount": 0}}.` ) Previously, Magento threw this error: `You can't create a creditmemo without products`. [GitHub-23069](https://github.com/magento/magento2/issues/23069)
+* You can now use POST `V1/invoice/:invoiceId/refund` to refund an invoice that has a zero quantity of products and zero shipping charges (for example, `{"items": [{"qty": 0, "orderItemId": 6, "extensionAttributes": {}}], "appendComment": false, "notify": true, "isOnline": true, "arguments": {"adjustment_negative": 0.0, "adjustment_positive": 0.99, "shipping_amount": 0}}.` ) Previously, Magento threw this error: `You can't create a creditmemo without products`. [GitHub-23069](https://github.com/magento/magento2/issues/23069)
@@ -2352,7 +2354,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
cd magento_root/pub/shop01
```
-1. Create symlinks for the store’s parent directories in the newly created directory:
+1. Create symlinks for the store's parent directories in the newly created directory:
```bash
ln -s ../media media
@@ -2396,7 +2398,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
}
```
-1. Configure your Apache server to point to the new subdirectory. Deployment configurations can vary widely. Here’s an example server configuration:
+1. Configure your Apache server to point to the new subdirectory. Deployment configurations can vary widely. Here's an example server configuration:
```xml
diff --git a/src/guides/v2.4/release-notes/commerce-2-4-3.md b/src/guides/v2.4/release-notes/commerce-2-4-3.md
index 894e8b0615f..4dec351a6e2 100644
--- a/src/guides/v2.4/release-notes/commerce-2-4-3.md
+++ b/src/guides/v2.4/release-notes/commerce-2-4-3.md
@@ -1,6 +1,8 @@
---
group: release-notes
title: Adobe Commerce 2.4.3 Release Notes
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/release/notes/adobe-commerce/2-4-3.html
+status: migrated
---
{{ site.data.var.ee }} 2.4.3 introduces enhancements to performance and security plus significant platform improvements. Security enhancements include expansion of reCAPTCHA coverage and inclusion of built-in rate limiting. Core composer dependencies and third-party libraries have been upgraded to the latest versions that are compatible with PHP 8.x.
@@ -286,7 +288,7 @@ We have fixed hundreds of issues in the Magento 2.4.3 core code.
-* A bundle item’s price can now be set to 0.00. Previously, when you returned to the edit page after setting the price to 0.00, the price returned to its default value. [GitHub-32383](https://github.com/magento/magento2/issues/32383)
+* A bundle item's price can now be set to 0.00. Previously, when you returned to the edit page after setting the price to 0.00, the price returned to its default value. [GitHub-32383](https://github.com/magento/magento2/issues/32383)
@@ -298,7 +300,7 @@ We have fixed hundreds of issues in the Magento 2.4.3 core code.
-* An administrator can now change the value for a bundle product’s `Shipment Type` attribute after it has been moved to a different attribute group. Previously, this attribute was always saved with a `Together` value if it were moved to an attribute group other than the default group in the attribute set.
+* An administrator can now change the value for a bundle product's `Shipment Type` attribute after it has been moved to a different attribute group. Previously, this attribute was always saved with a `Together` value if it were moved to an attribute group other than the default group in the attribute set.
@@ -322,7 +324,7 @@ We have fixed hundreds of issues in the Magento 2.4.3 core code.
-* Merchants can now assign a unique price for a bundle product on each store view of a multistore deployment. Website-specific prices are saved in the `catalog_product_bundle_selection_price` table. Previously, Magento did not base a bundle product’s price on website scope even when **Stores** > **Configuration** > **Catalog** > **Catalog** > **Price** > **Catalog Price Scope** was set to `Website`. No website-specific prices were saved in `catalog_product_bundle_selection_price`. [GitHub-12584](https://github.com/magento/magento2/issues/12584)
+* Merchants can now assign a unique price for a bundle product on each store view of a multistore deployment. Website-specific prices are saved in the `catalog_product_bundle_selection_price` table. Previously, Magento did not base a bundle product's price on website scope even when **Stores** > **Configuration** > **Catalog** > **Catalog** > **Price** > **Catalog Price Scope** was set to `Website`. No website-specific prices were saved in `catalog_product_bundle_selection_price`. [GitHub-12584](https://github.com/magento/magento2/issues/12584)
@@ -350,7 +352,7 @@ We have fixed hundreds of issues in the Magento 2.4.3 core code.
-* CAPTCHA now correctly validates data provided by a shopper, and CAPTCHA fields are now displayed as expected after a shopper’s multiple unsuccessful attempts to check out with PayPal Payflow Pro.
+* CAPTCHA now correctly validates data provided by a shopper, and CAPTCHA fields are now displayed as expected after a shopper's multiple unsuccessful attempts to check out with PayPal Payflow Pro.
@@ -620,7 +622,7 @@ We have fixed hundreds of issues in the Magento 2.4.3 core code.
-* Magento no longer duplicates product thumbnails in a product’s image gallery when you click on a product’s configurable options.
+* Magento no longer duplicates product thumbnails in a product's image gallery when you click on a product's configurable options.
@@ -652,7 +654,7 @@ We have fixed hundreds of issues in the Magento 2.4.3 core code.
-* `cron` jobs now complete as expected and no longer throw this serialization error: `[Magento\Framework\DB\Adapter\DeadlockException]SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when trying to get lock; try restarting transaction, query was: DELETE FROM cron_schedule WHERE (status = 'missed') AND (job_code in ('indexer_reindex_all_invalid', 'indexer_update_all_views', 'indexer_clean_all_changelogs')) AND (created_at < '2018-09-28 18:32:28’)`. [GitHub-18409](https://github.com/magento/magento2/issues/18409)
+* `cron` jobs now complete as expected and no longer throw this serialization error: `[Magento\Framework\DB\Adapter\DeadlockException]SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when trying to get lock; try restarting transaction, query was: DELETE FROM cron_schedule WHERE (status = 'missed') AND (job_code in ('indexer_reindex_all_invalid', 'indexer_update_all_views', 'indexer_clean_all_changelogs')) AND (created_at < '2018-09-28 18:32:28')`. [GitHub-18409](https://github.com/magento/magento2/issues/18409)
@@ -1064,7 +1066,7 @@ We have fixed hundreds of issues in the Magento 2.4.3 core code.
-* The `applyRewardPointsToCart` mutation now updates a cart’s grand total to accurately reflect the value of the reward points deducted. [GitHub-486](https://github.com/magento/partners-magento2ee/issues/486)
+* The `applyRewardPointsToCart` mutation now updates a cart's grand total to accurately reflect the value of the reward points deducted. [GitHub-486](https://github.com/magento/partners-magento2ee/issues/486)
@@ -1072,7 +1074,7 @@ We have fixed hundreds of issues in the Magento 2.4.3 core code.
-* Merchants can now use the GraphQL `setShippingAddressesOnCart` method to set billing and shipping addresses for a shopper’s cart when guest checkout is disabled.
+* Merchants can now use the GraphQL `setShippingAddressesOnCart` method to set billing and shipping addresses for a shopper's cart when guest checkout is disabled.
@@ -1120,7 +1122,7 @@ We have fixed hundreds of issues in the Magento 2.4.3 core code.
-* The `products` query no longer exposes a product’s special price when the special price period is set for a future date. [GitHub-30210](https://github.com/magento/magento2/issues/30210), [GitHub-29631](https://github.com/magento/magento2/issues/29631)
+* The `products` query no longer exposes a product's special price when the special price period is set for a future date. [GitHub-30210](https://github.com/magento/magento2/issues/30210), [GitHub-29631](https://github.com/magento/magento2/issues/29631)
@@ -1164,7 +1166,7 @@ We have fixed hundreds of issues in the Magento 2.4.3 core code.
-* Administrators can now successfully change the `name` of a bundle product’s `bundle_values` from the Admin. Previously, Magento displayed the product as out-of-stock on the storefront after you changed the name from the Admin. Products were also merged with the same SKU into a single bundle-option section.
+* Administrators can now successfully change the `name` of a bundle product's `bundle_values` from the Admin. Previously, Magento displayed the product as out-of-stock on the storefront after you changed the name from the Admin. Products were also merged with the same SKU into a single bundle-option section.
@@ -1240,7 +1242,7 @@ We have fixed hundreds of issues in the Magento 2.4.3 core code.
-* Magento no longer throws an `Invalid header value detected` error on the Contact us form when a shopper enters an email address that contains French diacritic marks (such as "é", “è”). Magento now converts UTF-8 letters in the user name to ASCII encoding. Previously, UTF-8 letters were not converted to ASCII encoding in the unique section of the email address.
+* Magento no longer throws an `Invalid header value detected` error on the Contact us form when a shopper enters an email address that contains French diacritic marks (such as "é", "è"). Magento now converts UTF-8 letters in the user name to ASCII encoding. Previously, UTF-8 letters were not converted to ASCII encoding in the unique section of the email address.
@@ -1529,7 +1531,7 @@ Repetitive actions have been replaced with action groups in these tests:
-* The payment methods list is now updated as expected when a guest shopper changes an order’s shipping address to a different country during checkout. Previously, changing billing address did not trigger an update of the possible payment methods.
+* The payment methods list is now updated as expected when a guest shopper changes an order's shipping address to a different country during checkout. Previously, changing billing address did not trigger an update of the possible payment methods.
#### PayPal
@@ -1573,7 +1575,7 @@ Repetitive actions have been replaced with action groups in these tests:
-* Scheduled price updates are now applied to products already in a shopper’s cart. [GitHub-356](https://github.com/magento/partners-magento2ee/issues/356)
+* Scheduled price updates are now applied to products already in a shopper's cart. [GitHub-356](https://github.com/magento/partners-magento2ee/issues/356)
@@ -2001,7 +2003,7 @@ Repetitive actions have been replaced with action groups in these tests:
-* Order emails sent from the Admin now use the store locale not the locale that is associated with the administrator’s account. [GitHub-26521](https://github.com/magento/magento2/issues/26521)
+* Order emails sent from the Admin now use the store locale not the locale that is associated with the administrator's account. [GitHub-26521](https://github.com/magento/magento2/issues/26521)
### UI
@@ -2123,7 +2125,7 @@ Repetitive actions have been replaced with action groups in these tests:
-* Magento now uses the correct custom email template when generating email for new administrators. Previously, Magento used the old default template, which omitted the administrator’s first and last names.
+* Magento now uses the correct custom email template when generating email for new administrators. Previously, Magento used the old default template, which omitted the administrator's first and last names.
@@ -2175,7 +2177,7 @@ Repetitive actions have been replaced with action groups in these tests:
-* An administrator can now delete all of a widget’s layout updates. Previously, when a widget had multiple layout updates, an administrator could delete only the first.
+* An administrator can now delete all of a widget's layout updates. Previously, when a widget had multiple layout updates, an administrator could delete only the first.
@@ -2189,7 +2191,7 @@ Repetitive actions have been replaced with action groups in these tests:
-* Magento no longer resets a configurable product’s configuration settings when you click the **Edit item** button for the product from a wish list. [GitHub-32119](https://github.com/magento/magento2/issues/32119)
+* Magento no longer resets a configurable product's configuration settings when you click the **Edit item** button for the product from a wish list. [GitHub-32119](https://github.com/magento/magento2/issues/32119)
diff --git a/src/guides/v2.4/release-notes/commerce-2-4-4.md b/src/guides/v2.4/release-notes/commerce-2-4-4.md
index ac4ed96d199..3728483b8ca 100644
--- a/src/guides/v2.4/release-notes/commerce-2-4-4.md
+++ b/src/guides/v2.4/release-notes/commerce-2-4-4.md
@@ -1,6 +1,8 @@
---
group: release-notes
title: Adobe Commerce 2.4.4 Release Notes
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/release/notes/adobe-commerce/2-4-4.html
+status: migrated
---
{{ site.data.var.ee }} 2.4.4 introduces support for PHP 8.1. All project libraries and dependencies have been updated for compatibility with PHP 8.1. Core Composer dependencies and third-party libraries have also been upgraded to the latest versions that are compatible with PHP 8.1. This release also provides support for OpenSearch 1.2.
@@ -198,7 +200,7 @@ PWA Studio v.12.3.0 is compatible with {{ site.data.var.ee }} 2.4.4. It includes
* The Venmo payment option is now supported.
-* Pay Later has been added as an option for shoppers based on the shopper's location, not the merchant’s location.
+* Pay Later has been added as an option for shoppers based on the shopper's location, not the merchant's location.
* Merchants can now set the shopper country when testing the shopper experience in their country of choice. Previously, tests were limited to testing only for the country in which the merchant is located. This change is valid in sandbox mode only.
@@ -238,7 +240,7 @@ We are fixing hundreds of issues in the {{ site.data.var.ee }} 2.4.4 core code.
-* Data patches can no longer ignore a table’s unique constraints and insert duplicate values into a MySQL database table. Previously, patches could insert duplicate values, which corrupted the database.
+* Data patches can no longer ignore a table's unique constraints and insert duplicate values into a MySQL database table. Previously, patches could insert duplicate values, which corrupted the database.
@@ -338,7 +340,7 @@ We are fixing hundreds of issues in the {{ site.data.var.ee }} 2.4.4 core code.
-* Shoppers can now add a bundle product with Fixed Product Tax and two options to their shopping cart. Previously, {{ site.data.var.ee }} did not add the product and displayed this error: `We can’t add this item to your shopping cart right now`.
+* Shoppers can now add a bundle product with Fixed Product Tax and two options to their shopping cart. Previously, {{ site.data.var.ee }} did not add the product and displayed this error: `We can't add this item to your shopping cart right now`.
@@ -442,7 +444,7 @@ We are fixing hundreds of issues in the {{ site.data.var.ee }} 2.4.4 core code.
-* {{ site.data.var.ee }} no longer throws this error when a shopper adds a billing address that is missing a street field: `Uncaught TypeError: Unable to process binding "text: function(){return currentBillingAddress().street.join(', ') }”`. [GitHub-33826](https://github.com/magento/magento2/issues/33826)
+* {{ site.data.var.ee }} no longer throws this error when a shopper adds a billing address that is missing a street field: `Uncaught TypeError: Unable to process binding "text: function(){return currentBillingAddress().street.join(', ') }"`. [GitHub-33826](https://github.com/magento/magento2/issues/33826)
@@ -450,7 +452,7 @@ We are fixing hundreds of issues in the {{ site.data.var.ee }} 2.4.4 core code.
-* Checkout no longer fails at the payment stage when the billing address is missing street field values or the street field value is not an array. Previously, checkout failed with this error: `Uncaught TypeError: Unable to process binding "text: function(){return currentBillingAddress().street.join(', ') }”`. [GitHub-33826](https://github.com/magento/magento2/issues/33826)
+* Checkout no longer fails at the payment stage when the billing address is missing street field values or the street field value is not an array. Previously, checkout failed with this error: `Uncaught TypeError: Unable to process binding "text: function(){return currentBillingAddress().street.join(', ') }"`. [GitHub-33826](https://github.com/magento/magento2/issues/33826)
@@ -656,7 +658,7 @@ We are fixing hundreds of issues in the {{ site.data.var.ee }} 2.4.4 core code.
-* Order emails now contain data localized using the shopper’s locale as expected. Previously, order emails used the Admin locale.
+* Order emails now contain data localized using the shopper's locale as expected. Previously, order emails used the Admin locale.
@@ -942,7 +944,7 @@ We are fixing hundreds of issues in the {{ site.data.var.ee }} 2.4.4 core code.
-* {{ site.data.var.ee }} now converts the timestamp in the export filename to the user’s timezone after a scheduled export. Previously, these values were not converted, and {{ site.data.var.ee }} displayed the UTC timestamp.
+* {{ site.data.var.ee }} now converts the timestamp in the export filename to the user's timezone after a scheduled export. Previously, these values were not converted, and {{ site.data.var.ee }} displayed the UTC timestamp.
@@ -1511,7 +1513,7 @@ Repetitive actions have been replaced with action groups in these tests:
-* Shipment email now includes the tracking number for the current shipment only. Previously, when an order included several shipments, each shipment’s email included the tracking numbers from all shipments related to the order.
+* Shipment email now includes the tracking number for the current shipment only. Previously, when an order included several shipments, each shipment's email included the tracking numbers from all shipments related to the order.
@@ -1597,7 +1599,7 @@ Repetitive actions have been replaced with action groups in these tests:
-* Merchants can now test the shopper experience of the country in which the shopper is located, rather than the merchant’s location.
+* Merchants can now test the shopper experience of the country in which the shopper is located, rather than the merchant's location.
@@ -1905,7 +1907,7 @@ The following unit tests have been refactored to use `PHPUnit` instead of `Aspec
Dotdigital is a customer engagement platform that helps digital marketers and developers deliver communications across the customer journey. We harness the power of customer data, powering engagement, conversion, and loyalty for brands as they grow and scale. Customers love our easy-to-use platform that connects first party data across the systems, surfacing powerful insights and automating predictive cross-channel messages.
-Dotdigital’s 350+ employees serve mid-market and enterprise companies around the world and across industries. We aspire to inspire responsible marketing and are committed to sustainability, privacy, and security. Dotdigital is proud to be the world’s first carbon-neutral marketing automation platform, certified for ISO 14001, ISO 27701, and ISO 27001.
+Dotdigital's 350+ employees serve mid-market and enterprise companies around the world and across industries. We aspire to inspire responsible marketing and are committed to sustainability, privacy, and security. Dotdigital is proud to be the world's first carbon-neutral marketing automation platform, certified for ISO 14001, ISO 27701, and ISO 27001.
See [Dotdigital — Marketing Automation](https://marketplace.magento.com/dotdigital-dotdigital-magento2-os-package.html) for purchase and download information.
diff --git a/src/guides/v2.4/release-notes/commerce-2-4-5.md b/src/guides/v2.4/release-notes/commerce-2-4-5.md
index 72f746c1446..4205f964971 100644
--- a/src/guides/v2.4/release-notes/commerce-2-4-5.md
+++ b/src/guides/v2.4/release-notes/commerce-2-4-5.md
@@ -1,6 +1,8 @@
---
group: release-notes
title: Adobe Commerce 2.4.5 Release Notes
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/release/notes/adobe-commerce/2-4-5.html
+status: migrated
---
{{ site.data.var.ee }} introduces improvements to platform quality, payment methods, GraphQL caching performance, and accessibility. It includes updates to integrated Google modules and the Upgrade Compatibility Tool and introduces Live Search B2B support.
@@ -151,7 +153,7 @@ Adobe Commerce merchants who have an Adobe ID and want a streamlined login to Ad
### Branding and style changes
-The Admin has been updated to align with Adobe’s brand strategy. Changes affect headers, footers, data grid color updates, and navigation elements.
+The Admin has been updated to align with Adobe's brand strategy. Changes affect headers, footers, data grid color updates, and navigation elements.
### B2B
@@ -281,7 +283,7 @@ We have fixed hundreds of issues in the {{ site.data.var.ee }} 2.4.5 core code.
-* Screen readers announce the word “Venia” only once when navigating to Venia headers and footers. Previously, the same word was announced twice consecutively.
+* Screen readers announce the word "Venia" only once when navigating to Venia headers and footers. Previously, the same word was announced twice consecutively.
@@ -461,7 +463,7 @@ We have fixed hundreds of issues in the {{ site.data.var.ee }} 2.4.5 core code.
-* Administrators can now change configurable product options in a shopper’s cart from the Admin slide panel. Previously, the slide panel did not work correctly.
+* Administrators can now change configurable product options in a shopper's cart from the Admin slide panel. Previously, the slide panel did not work correctly.
@@ -535,7 +537,7 @@ We have fixed hundreds of issues in the {{ site.data.var.ee }} 2.4.5 core code.
-* {{ site.data.var.ee }} now correctly displays a configurable product’s stock status, available configurations, and displayed price when the availability of one of the configurable product’s child product is changed by a scheduled update. Previously, when a configurable product had two children and the availability of one child product was disabled with a scheduled update, the parent product’s stock status was incorrectly displayed as **Out of Stock** when the update was active, After the update completed, the displayed price and the availability of its configurations was miscalculated.
+* {{ site.data.var.ee }} now correctly displays a configurable product's stock status, available configurations, and displayed price when the availability of one of the configurable product's child product is changed by a scheduled update. Previously, when a configurable product had two children and the availability of one child product was disabled with a scheduled update, the parent product's stock status was incorrectly displayed as **Out of Stock** when the update was active, After the update completed, the displayed price and the availability of its configurations was miscalculated.
* You can now re-order configurable products with optional custom options. Previously, re-order attempts failed, and meant displayed this error: `Some of the selected options are not currently available`. [GitHub-35409](https://github.com/magento/magento2/issues/35409)
@@ -685,7 +687,7 @@ We have fixed hundreds of issues in the {{ site.data.var.ee }} 2.4.5 core code.
-* You can now create a customer account on an iOS device with the inclined apostrophe (’) in the first, middle, or last name. Previously, only the straight apostrophe was allowed, and using iOS 11+ default inclined apostrophe resulted in a `Name is not valid!` error.
+* You can now create a customer account on an iOS device with the inclined apostrophe (') in the first, middle, or last name. Previously, only the straight apostrophe was allowed, and using iOS 11+ default inclined apostrophe resulted in a `Name is not valid!` error.
@@ -1052,7 +1054,7 @@ Repetitive actions have been replaced with action groups in these tests:
-* Redis cache management has been improved by the addition of TTL (expiration date) for configurable products’ associated product data caches. Previously, these caches were not evicted due to missing TTL values if Redis key eviction policy was configured to a volatile eviction policy.
+* Redis cache management has been improved by the addition of TTL (expiration date) for configurable products' associated product data caches. Previously, these caches were not evicted due to missing TTL values if Redis key eviction policy was configured to a volatile eviction policy.
@@ -1324,7 +1326,7 @@ Repetitive actions have been replaced with action groups in these tests:
-* Administrators can now set the current user’s expiration date higher than 2038 and save the user successfully. Previously, the user whose expiration date was changed could not log back in after logging out.
+* Administrators can now set the current user's expiration date higher than 2038 and save the user successfully. Previously, the user whose expiration date was changed could not log back in after logging out.
diff --git a/src/guides/v2.4/release-notes/open-source-2-4-1.md b/src/guides/v2.4/release-notes/open-source-2-4-1.md
index e4523b2df55..0ef8fae9589 100644
--- a/src/guides/v2.4/release-notes/open-source-2-4-1.md
+++ b/src/guides/v2.4/release-notes/open-source-2-4-1.md
@@ -1,6 +1,8 @@
---
group: release-notes
title: Magento Open Source 2.4.1 Release Notes
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/release/notes/magento-open-source/2-4-1.html
+status: migrated
---
{{site.data.var.ce}} 2.4.1 introduces enhancements to performance and security. Security enhancements include support for the `SameSite` attribute for cookies and the addition of CAPTCHA protection for payment-related and order-related API endpoints and the Place Order storefront page.
@@ -337,7 +339,7 @@ _Fix submitted by Michał Derlatka in pull request [29256](https://github.com/ma
-* The **Delete** button on the **Add to Shopping Cart by SKU** section of a customer’s **Manage Shopping Cart** page now works as expected when multiple rows are selected.
+* The **Delete** button on the **Add to Shopping Cart by SKU** section of a customer's **Manage Shopping Cart** page now works as expected when multiple rows are selected.
@@ -345,7 +347,7 @@ _Fix submitted by Michał Derlatka in pull request [29256](https://github.com/ma
-* A customer’s shipping address is now selected by default at checkout when the address is located in the country identified on the Allow Countries list and that list includes only that country. Previously, Magento did not select the address as default and displayed this error message: `Please specify a regionId in shipping address`.
+* A customer's shipping address is now selected by default at checkout when the address is located in the country identified on the Allow Countries list and that list includes only that country. Previously, Magento did not select the address as default and displayed this error message: `Please specify a regionId in shipping address`.
@@ -389,7 +391,7 @@ _Fix submitted by Michał Derlatka in pull request [29256](https://github.com/ma
-* The success message that Magento displays when a shopper adds a product to their cart from the customer account sidebar now contains a link to the shopper’s shopping cart. _Fix submitted by Ajith in pull request [27977](https://github.com/magento/magento2/pull/27977)_. [GitHub-29097](https://github.com/magento/magento2/issues/29097)
+* The success message that Magento displays when a shopper adds a product to their cart from the customer account sidebar now contains a link to the shopper's shopping cart. _Fix submitted by Ajith in pull request [27977](https://github.com/magento/magento2/pull/27977)_. [GitHub-29097](https://github.com/magento/magento2/issues/29097)
@@ -415,7 +417,7 @@ _Fix submitted by Michał Derlatka in pull request [29256](https://github.com/ma
-* Magento now removes disabled products from a shopper’s cart before checkout. Previously, when a shopper added a product to their cart that was disabled before checkout completed, Magento removed the disabled product from the cart, but the product remained in the quote, and the shopper could not check out. [GitHub-26680](https://github.com/magento/magento2/issues/26680)
+* Magento now removes disabled products from a shopper's cart before checkout. Previously, when a shopper added a product to their cart that was disabled before checkout completed, Magento removed the disabled product from the cart, but the product remained in the quote, and the shopper could not check out. [GitHub-26680](https://github.com/magento/magento2/issues/26680)
@@ -423,7 +425,7 @@ _Fix submitted by Michał Derlatka in pull request [29256](https://github.com/ma
-* Shoppers can now open a product’s detail page by clicking on the product name in the compare products sidebar. _Fix submitted by Eduard Chitoraga in pull request [27451](https://github.com/magento/magento2/pull/27451)_. [GitHub-21101](https://github.com/magento/magento2/issues/21101)
+* Shoppers can now open a product's detail page by clicking on the product name in the compare products sidebar. _Fix submitted by Eduard Chitoraga in pull request [27451](https://github.com/magento/magento2/pull/27451)_. [GitHub-21101](https://github.com/magento/magento2/issues/21101)
@@ -533,11 +535,11 @@ _Fix submitted by Michał Derlatka in pull request [29256](https://github.com/ma
-* Magento no longer throws a validation error when you use POST `/V1/products` to a configurable product with an `int` value of 0. Previously, Magento threw this error: `Product with id "%1" does not contain required attribute “%2”.”` _Fix submitted by Vadim Malesh in pull request [29001](https://github.com/magento/magento2/pull/29001)_. [GitHub-13210](https://github.com/magento/magento2/issues/13210)
+* Magento no longer throws a validation error when you use POST `/V1/products` to a configurable product with an `int` value of 0. Previously, Magento threw this error: `Product with id "%1" does not contain required attribute "%2"."` _Fix submitted by Vadim Malesh in pull request [29001](https://github.com/magento/magento2/pull/29001)_. [GitHub-13210](https://github.com/magento/magento2/issues/13210)
-* The configuration options attribute of a parent product are no longer assigned to a new configurable product’s `size` attribute. _Fix submitted by Abel Truong in pull request [27339](https://github.com/magento/magento2/pull/27339)_. [GitHub-26449](https://github.com/magento/magento2/issues/26449)
+* The configuration options attribute of a parent product are no longer assigned to a new configurable product's `size` attribute. _Fix submitted by Abel Truong in pull request [27339](https://github.com/magento/magento2/pull/27339)_. [GitHub-26449](https://github.com/magento/magento2/issues/26449)
### Cookies
@@ -655,7 +657,7 @@ _Fix submitted by Michał Derlatka in pull request [29256](https://github.com/ma
-* A product’s `stock_item` data is updated and downloadable product links and samples are preserved as expected when you use a REST PUT call to update `stock_item` values. Previously, after the product update, the product no longer contained links to download content. _Fix submitted by Vadim Malesh in pull request [28799](https://github.com/magento/magento2/pull/28799)_. [GitHub-21811](https://github.com/magento/magento2/issues/21811)
+* A product's `stock_item` data is updated and downloadable product links and samples are preserved as expected when you use a REST PUT call to update `stock_item` values. Previously, after the product update, the product no longer contained links to download content. _Fix submitted by Vadim Malesh in pull request [28799](https://github.com/magento/magento2/pull/28799)_. [GitHub-21811](https://github.com/magento/magento2/issues/21811)
@@ -697,7 +699,7 @@ _Fix submitted by Michał Derlatka in pull request [29256](https://github.com/ma
-* You can now create an email template that sends email with `Content-Type: "text/plain”`. Previously, Magento ignored the content type specified in the template. _Fix submitted by twoonesixdigital in pull request [26474](https://github.com/magento/magento2/pull/26474)_. [GitHub-26471](https://github.com/magento/magento2/issues/26471)
+* You can now create an email template that sends email with `Content-Type: "text/plain"`. Previously, Magento ignored the content type specified in the template. _Fix submitted by twoonesixdigital in pull request [26474](https://github.com/magento/magento2/pull/26474)_. [GitHub-26471](https://github.com/magento/magento2/issues/26471)
### Frameworks
@@ -821,7 +823,7 @@ _Fix submitted by Michał Derlatka in pull request [29256](https://github.com/ma
-* Magento now adds an admin user’s ACL role ID to the product category tree cache ID. This will limit the category trees that an admin with limited scope can see as expected. _Fix submitted by quangdo-aligent in pull request [27429](https://github.com/magento/magento2/pull/27429)_. [GitHub-28306](https://github.com/magento/magento2/issues/28306)
+* Magento now adds an admin user's ACL role ID to the product category tree cache ID. This will limit the category trees that an admin with limited scope can see as expected. _Fix submitted by quangdo-aligent in pull request [27429](https://github.com/magento/magento2/pull/27429)_. [GitHub-28306](https://github.com/magento/magento2/issues/28306)
### GraphQL
@@ -1282,7 +1284,7 @@ _Fix submitted by Michał Derlatka in pull request [29256](https://github.com/ma
-* Elasticsearch results now include the correct values for each store view’s attribute options. If a `Dropdown` or `Multiple Select` attribute has a different option value in the non-default store view than in the default store view, Elasticsearch now indexes that value or returns the product with that value in the results. Previously, Elasticsearch did not index that value or return the product with that value in the results.
+* Elasticsearch results now include the correct values for each store view's attribute options. If a `Dropdown` or `Multiple Select` attribute has a different option value in the non-default store view than in the default store view, Elasticsearch now indexes that value or returns the product with that value in the results. Previously, Elasticsearch did not index that value or return the product with that value in the results.
@@ -1354,7 +1356,7 @@ _Fix submitted by Michał Derlatka in pull request [29256](https://github.com/ma
-* Magento no longer displays a fixed product tax attribute on the storefront for a product after a merchant has unassigned it from the product’s attribute set.
+* Magento no longer displays a fixed product tax attribute on the storefront for a product after a merchant has unassigned it from the product's attribute set.
### Test
@@ -1466,7 +1468,7 @@ _Fix submitted by Michał Derlatka in pull request [29256](https://github.com/ma
-* Magento now correctly displays the calendar icon used for selecting a customer’s date of birth on the Conditions tab of **Customers** > **Segments** > **Add Segment**.
+* Magento now correctly displays the calendar icon used for selecting a customer's date of birth on the Conditions tab of **Customers** > **Segments** > **Add Segment**.
@@ -1632,7 +1634,7 @@ _Fix submitted by Michał Derlatka in pull request [29256](https://github.com/ma
-* Added a test for deleting items from a customer’s wish list as an Admin user. _Fix submitted by Dmitry Tsymbal in pull request [28632](https://github.com/magento/magento2/pull/28632)_. [GitHub-28721](https://github.com/magento/magento2/issues/28721)
+* Added a test for deleting items from a customer's wish list as an Admin user. _Fix submitted by Dmitry Tsymbal in pull request [28632](https://github.com/magento/magento2/pull/28632)_. [GitHub-28721](https://github.com/magento/magento2/issues/28721)
diff --git a/src/guides/v2.4/release-notes/open-source-2-4-2.md b/src/guides/v2.4/release-notes/open-source-2-4-2.md
index 9d29f70188b..7281bdb02dc 100644
--- a/src/guides/v2.4/release-notes/open-source-2-4-2.md
+++ b/src/guides/v2.4/release-notes/open-source-2-4-2.md
@@ -1,6 +1,8 @@
---
group: release-notes
title: Magento Open Source 2.4.2 Release Notes
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/release/notes/magento-open-source/2-4-2.html
+status: migrated
---
{{site.data.var.ce}} 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.
@@ -286,7 +288,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* 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.
+* 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.
@@ -338,7 +340,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* Magento now correctly updates a cart’s item subtotal when a shopper clicks **Update Shopping Cart** while checking out with multiple addresses. [GitHub-30408](https://github.com/magento/magento2/issues/30408)
+* Magento now correctly updates a cart's item subtotal when a shopper clicks **Update Shopping Cart** while checking out with multiple addresses. [GitHub-30408](https://github.com/magento/magento2/issues/30408)
@@ -380,7 +382,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* Problems with product sort order on the storefront have been resolved. Previously, when Magento 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.
+* Problems with product sort order on the storefront have been resolved. Previously, when Magento 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.
@@ -428,7 +430,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* 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](https://github.com/magento/magento2/issues/26432)
+* 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](https://github.com/magento/magento2/issues/26432)
@@ -448,7 +450,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* 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](https://github.com/magento/magento2/issues/26432)
+* 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](https://github.com/magento/magento2/issues/26432)
@@ -501,7 +503,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* Corrected the pluralization of “item” in the mini cart and checkout order summary. [GitHub-29920](https://github.com/magento/magento2/issues/29920)
+* Corrected the pluralization of "item" in the mini cart and checkout order summary. [GitHub-29920](https://github.com/magento/magento2/issues/29920)
@@ -585,7 +587,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* A virtual product no longer changes type when its status is changed from enabled to disabled (or vice versa). Previously, Magento changed a product’s type from virtual to simple when its status changed.
+* A virtual product no longer changes type when its status is changed from enabled to disabled (or vice versa). Previously, Magento changed a product's type from virtual to simple when its status changed.
@@ -691,7 +693,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* 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, Magento 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)”}`
+* 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, Magento 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
@@ -701,7 +703,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
* 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`.
+* Resolved issues with Composer upgrades that were the result of the dotdigital module's dependency on `magento/module-authorization`.
### Downloadable
@@ -749,7 +751,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* Images on a store’s home page are now rendered successfully. Previously, the page source HTML was corrupted because the three consecutive slashes in the image’s base64 code was misinterpreted as a comment.
+* Images on a store's home page are now rendered successfully. Previously, the page source HTML was corrupted because the three consecutive slashes in the image's base64 code was misinterpreted as a comment.
@@ -771,7 +773,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* You can now configure a native session handler that differs from the handler that is defined in `php.ini`. Previously, `SessionManager` did not set the memcache as `save_handler`, but instead used the file’s `session_handler`. Magento threw this error: `main.CRITICAL: Warning: SessionHandler::read(): open(127.0.0.1:11211/sess_0imeeaqmnvemdg4e3h57tat0ik, O_RDWR) failed: No such file or directory (2) in../vendor/magento/framework/Session/SaveHandler/Native.php on line 22 {"exception":"[object] (Exception(code: 0): Warning: SessionHandler::read(): open(127.0.0.1:11211/sess_0imeeaqmnvemdg4e3h57tat0ik, O_RDWR) failed: No such file or directory (2) in ../vendor/magento/framework/Session/SaveHandler/Native.php on line 22 at ../vendor/magento/framework/App/ErrorHandler.php:61)”}`. [GitHub-24717](https://github.com/magento/magento2/issues/24717)
+* You can now configure a native session handler that differs from the handler that is defined in `php.ini`. Previously, `SessionManager` did not set the memcache as `save_handler`, but instead used the file's `session_handler`. Magento threw this error: `main.CRITICAL: Warning: SessionHandler::read(): open(127.0.0.1:11211/sess_0imeeaqmnvemdg4e3h57tat0ik, O_RDWR) failed: No such file or directory (2) in../vendor/magento/framework/Session/SaveHandler/Native.php on line 22 {"exception":"[object] (Exception(code: 0): Warning: SessionHandler::read(): open(127.0.0.1:11211/sess_0imeeaqmnvemdg4e3h57tat0ik, O_RDWR) failed: No such file or directory (2) in ../vendor/magento/framework/Session/SaveHandler/Native.php on line 22 at ../vendor/magento/framework/App/ErrorHandler.php:61)"}`. [GitHub-24717](https://github.com/magento/magento2/issues/24717)
@@ -889,7 +891,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* Added missing `order_data` array to `EmailSender` classes. This brings these classes into alignment with Magento’s recommendation to use scalar variables instead of objects within the email templates. [GitHub-29604](https://github.com/magento/magento2/issues/29604)
+* Added missing `order_data` array to `EmailSender` classes. This brings these classes into alignment with Magento's recommendation to use scalar variables instead of objects within the email templates. [GitHub-29604](https://github.com/magento/magento2/issues/29604)
### GraphQL
@@ -1113,7 +1115,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* Images on a store’s home page are now rendered successfully. Previously, the page source HTML was corrupted because the three consecutive slashes in the image’s base64 code were misinterpreted as a comment.
+* Images on a store's home page are now rendered successfully. Previously, the page source HTML was corrupted because the three consecutive slashes in the image's base64 code were misinterpreted as a comment.
@@ -1135,7 +1137,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* Customer address `region_id` is no longer assigned a `NULL` value when you import customer addresses using a CSV file (`entity type = "customer address"` and `import behavior = "add/update”`) from which certain field values have been deleted.
+* Customer address `region_id` is no longer assigned a `NULL` value when you import customer addresses using a CSV file (`entity type = "customer address"` and `import behavior = "add/update"`) from which certain field values have been deleted.
@@ -1497,7 +1499,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* Magento now completes Payflow Pro payments successfully when the shopper’s name contains accented letters. Previously, payment did not complete, and Magento logged this error: `report.CRITICAL: String to be escaped was not valid UTF-8 or could not be converted`.
+* Magento now completes Payflow Pro payments successfully when the shopper's name contains accented letters. Previously, payment did not complete, and Magento logged this error: `report.CRITICAL: String to be escaped was not valid UTF-8 or could not be converted`.
#### PayPal
@@ -1507,7 +1509,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* Magento no longer creates duplicate orders when an order is placed with PayPal Express. Previously, when a shopper tried to pay for an order with PayPal Express but PayPal returned an error, Magento still created the order. This resulted in duplicate orders on the merchant’s site. [GitHub-13952](https://github.com/magento/magento2/issues/13952)
+* Magento no longer creates duplicate orders when an order is placed with PayPal Express. Previously, when a shopper tried to pay for an order with PayPal Express but PayPal returned an error, Magento still created the order. This resulted in duplicate orders on the merchant's site. [GitHub-13952](https://github.com/magento/magento2/issues/13952)
@@ -1587,7 +1589,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* Magento no longer displays the contents of a customer’s cart after the customers session expires. Previously, Magento displayed this error when a guest customer tried to check out when persistent shopping cart was enabled: `No such entity with cartid = 0`.
+* Magento no longer displays the contents of a customer's cart after the customers session expires. Previously, Magento displayed this error when a guest customer tried to check out when persistent shopping cart was enabled: `No such entity with cartid = 0`.
### Pricing
@@ -1799,7 +1801,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* Magento now creates correct URLs for categories and products after a store view’s top-level URL key is changed. Previously, when a store view’s category tree contained modified `url_keys`, if a category key did not change but the category parents’ key did, then the original code would used the category’s default store view when creating URLs. [GitHub-28633](https://github.com/magento/magento2/issues/28633)
+* Magento now creates correct URLs for categories and products after a store view's top-level URL key is changed. Previously, when a store view's category tree contained modified `url_keys`, if a category key did not change but the category parents' key did, then the original code would used the category's default store view when creating URLs. [GitHub-28633](https://github.com/magento/magento2/issues/28633)
### Target rules
@@ -1983,7 +1985,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* Magento now preserves an attribute’s value when you move the attribute from one group to another.
+* Magento now preserves an attribute's value when you move the attribute from one group to another.
@@ -2003,7 +2005,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* The WAI-ARIA attribute `aria-atomic="true”` has been added to the error container tag. [GitHub-29560](https://github.com/magento/magento2/issues/29560)
+* The WAI-ARIA attribute `aria-atomic="true"` has been added to the error container tag. [GitHub-29560](https://github.com/magento/magento2/issues/29560)
@@ -2049,7 +2051,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
-* You can now use POST `V1/invoice/:invoiceId/refund` to refund an invoice that has a zero quantity of products and zero shipping charges (for example, `{“items": [{"qty": 0, "orderItemId": 6, "extensionAttributes": {}}], "appendComment": false, "notify": true, "isOnline": true, "arguments": {"adjustment_negative": 0.0, "adjustment_positive": 0.99, "shipping_amount": 0}}.` ) Previously, Magento threw this error: `You can't create a creditmemo without products`. [GitHub-23069](https://github.com/magento/magento2/issues/23069)
+* You can now use POST `V1/invoice/:invoiceId/refund` to refund an invoice that has a zero quantity of products and zero shipping charges (for example, `{"items": [{"qty": 0, "orderItemId": 6, "extensionAttributes": {}}], "appendComment": false, "notify": true, "isOnline": true, "arguments": {"adjustment_negative": 0.0, "adjustment_positive": 0.99, "shipping_amount": 0}}.` ) Previously, Magento threw this error: `You can't create a creditmemo without products`. [GitHub-23069](https://github.com/magento/magento2/issues/23069)
@@ -2110,7 +2112,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
cd magento_root/pub/shop01
```
-1. Create symlinks for the store’s parent directories in the newly created directory:
+1. Create symlinks for the store's parent directories in the newly created directory:
```bash
ln -s ../media media
@@ -2154,7 +2156,7 @@ We have fixed hundreds of issues in the Magento 2.4.2 core code.
}
```
-1. Configure your Apache server to point to the new subdirectory. Deployment configurations can vary widely. Here’s an example server configuration:
+1. Configure your Apache server to point to the new subdirectory. Deployment configurations can vary widely. Here's an example server configuration:
```xml
diff --git a/src/guides/v2.4/release-notes/open-source-2-4-3.md b/src/guides/v2.4/release-notes/open-source-2-4-3.md
index 93a28da74b2..c12d91e4fe7 100644
--- a/src/guides/v2.4/release-notes/open-source-2-4-3.md
+++ b/src/guides/v2.4/release-notes/open-source-2-4-3.md
@@ -1,6 +1,8 @@
---
group: release-notes
title: Magento Open Source 2.4.3 Release Notes
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/release/notes/magento-open-source/2-4-3.html
+status: migrated
---
{{ site.data.var.ce }} 2.4.3 introduces enhancements to performance and security plus significant platform improvements. Security enhancements include expansion of reCAPTCHA coverage and inclusion of built-in rate limiting. Core composer dependencies and third-party libraries have been upgraded to the latest versions that are compatible with PHP 8.x. Page Builder is now available as a bundled extension in {{site.data.var.ce}}. It is now the default content editing tool for {{site.data.var.ee}} and {{site.data.var.ce}}.
@@ -230,7 +232,7 @@ We have fixed hundreds of issues in the Magento 2.4.3 core code.
-* A bundle item’s price can now be set to 0.00. Previously, when you returned to the edit page after setting the price to 0.00, the price returned to its default value. [GitHub-32383](https://github.com/magento/magento2/issues/32383)
+* A bundle item's price can now be set to 0.00. Previously, when you returned to the edit page after setting the price to 0.00, the price returned to its default value. [GitHub-32383](https://github.com/magento/magento2/issues/32383)
@@ -242,7 +244,7 @@ We have fixed hundreds of issues in the Magento 2.4.3 core code.
-* An administrator can now change the value for a bundle product’s `Shipment Type` attribute after it has been moved to a different attribute group. Previously, this attribute was always saved with a `Together` value if it were moved to an attribute group other than the default group in the attribute set.
+* An administrator can now change the value for a bundle product's `Shipment Type` attribute after it has been moved to a different attribute group. Previously, this attribute was always saved with a `Together` value if it were moved to an attribute group other than the default group in the attribute set.
@@ -266,7 +268,7 @@ We have fixed hundreds of issues in the Magento 2.4.3 core code.
-* Merchants can now assign a unique price for a bundle product on each store view of a multistore deployment. Website-specific prices are saved in the `catalog_product_bundle_selection_price` table. Previously, Magento did not base a bundle product’s price on website scope even when **Stores** > **Configuration** > **Catalog** > **Catalog** > **Price** > **Catalog Price Scope** was set to `Website`. No website-specific prices were saved in `catalog_product_bundle_selection_price`. [GitHub-12584](https://github.com/magento/magento2/issues/12584)
+* Merchants can now assign a unique price for a bundle product on each store view of a multistore deployment. Website-specific prices are saved in the `catalog_product_bundle_selection_price` table. Previously, Magento did not base a bundle product's price on website scope even when **Stores** > **Configuration** > **Catalog** > **Catalog** > **Price** > **Catalog Price Scope** was set to `Website`. No website-specific prices were saved in `catalog_product_bundle_selection_price`. [GitHub-12584](https://github.com/magento/magento2/issues/12584)
@@ -286,7 +288,7 @@ We have fixed hundreds of issues in the Magento 2.4.3 core code.
-* CAPTCHA now correctly validates data provided by a shopper, and CAPTCHA fields are now displayed as expected after a shopper’s multiple unsuccessful attempts to check out with PayPal Payflow Pro.
+* CAPTCHA now correctly validates data provided by a shopper, and CAPTCHA fields are now displayed as expected after a shopper's multiple unsuccessful attempts to check out with PayPal Payflow Pro.
@@ -528,7 +530,7 @@ We have fixed hundreds of issues in the Magento 2.4.3 core code.
-* Magento no longer duplicates product thumbnails in a product’s image gallery when you click on a product’s configurable options.
+* Magento no longer duplicates product thumbnails in a product's image gallery when you click on a product's configurable options.
@@ -560,7 +562,7 @@ We have fixed hundreds of issues in the Magento 2.4.3 core code.
-* `cron` jobs now complete as expected and no longer throw this serialization error: `[Magento\Framework\DB\Adapter\DeadlockException]SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when trying to get lock; try restarting transaction, query was: DELETE FROM cron_schedule WHERE (status = 'missed') AND (job_code in ('indexer_reindex_all_invalid', 'indexer_update_all_views', 'indexer_clean_all_changelogs')) AND (created_at < '2018-09-28 18:32:28’)`. [GitHub-18409](https://github.com/magento/magento2/issues/18409)
+* `cron` jobs now complete as expected and no longer throw this serialization error: `[Magento\Framework\DB\Adapter\DeadlockException]SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when trying to get lock; try restarting transaction, query was: DELETE FROM cron_schedule WHERE (status = 'missed') AND (job_code in ('indexer_reindex_all_invalid', 'indexer_update_all_views', 'indexer_clean_all_changelogs')) AND (created_at < '2018-09-28 18:32:28')`. [GitHub-18409](https://github.com/magento/magento2/issues/18409)
@@ -844,7 +846,7 @@ We have fixed hundreds of issues in the Magento 2.4.3 core code.
-* The `applyRewardPointsToCart` mutation now updates a cart’s grand total to accurately reflect the value of the reward points deducted. [GitHub-486](https://github.com/magento/partners-magento2ee/issues/486)
+* The `applyRewardPointsToCart` mutation now updates a cart's grand total to accurately reflect the value of the reward points deducted. [GitHub-486](https://github.com/magento/partners-magento2ee/issues/486)
@@ -852,7 +854,7 @@ We have fixed hundreds of issues in the Magento 2.4.3 core code.
-* Merchants can now use the GraphQL `setShippingAddressesOnCart` method to set billing and shipping addresses for a shopper’s cart when guest checkout is disabled.
+* Merchants can now use the GraphQL `setShippingAddressesOnCart` method to set billing and shipping addresses for a shopper's cart when guest checkout is disabled.
@@ -900,7 +902,7 @@ We have fixed hundreds of issues in the Magento 2.4.3 core code.
-* The `products` query no longer exposes a product’s special price when the special price period is set for a future date. [GitHub-30210](https://github.com/magento/magento2/issues/30210), [GitHub-29631](https://github.com/magento/magento2/issues/29631)
+* The `products` query no longer exposes a product's special price when the special price period is set for a future date. [GitHub-30210](https://github.com/magento/magento2/issues/30210), [GitHub-29631](https://github.com/magento/magento2/issues/29631)
@@ -944,7 +946,7 @@ We have fixed hundreds of issues in the Magento 2.4.3 core code.
-* Administrators can now successfully change the `name` of a bundle product’s `bundle_values` from the Admin. Previously, Magento displayed the product as out-of-stock on the storefront after you changed the name from the Admin. Products were also merged with the same SKU into a single bundle-option section.
+* Administrators can now successfully change the `name` of a bundle product's `bundle_values` from the Admin. Previously, Magento displayed the product as out-of-stock on the storefront after you changed the name from the Admin. Products were also merged with the same SKU into a single bundle-option section.
@@ -1020,7 +1022,7 @@ We have fixed hundreds of issues in the Magento 2.4.3 core code.
-* Magento no longer throws an `Invalid header value detected` error on the Contact us form when a shopper enters an email address that contains French diacritic marks (such as "é", “è”). Magento now converts UTF-8 letters in the user name to ASCII encoding. Previously, UTF-8 letters were not converted to ASCII encoding in the unique section of the email address.
+* Magento no longer throws an `Invalid header value detected` error on the Contact us form when a shopper enters an email address that contains French diacritic marks (such as "é", "è"). Magento now converts UTF-8 letters in the user name to ASCII encoding. Previously, UTF-8 letters were not converted to ASCII encoding in the unique section of the email address.
@@ -1310,7 +1312,7 @@ Repetitive actions have been replaced with action groups in these tests:
-* The payment methods list is now updated as expected when a guest shopper changes an order’s shipping address to a different country during checkout. Previously, changing billing address did not trigger an update of the possible payment methods.
+* The payment methods list is now updated as expected when a guest shopper changes an order's shipping address to a different country during checkout. Previously, changing billing address did not trigger an update of the possible payment methods.
#### PayPal
@@ -1354,7 +1356,7 @@ Repetitive actions have been replaced with action groups in these tests:
-* Scheduled price updates are now applied to products already in a shopper’s cart. [GitHub-356](https://github.com/magento/partners-magento2ee/issues/356)
+* Scheduled price updates are now applied to products already in a shopper's cart. [GitHub-356](https://github.com/magento/partners-magento2ee/issues/356)
@@ -1698,7 +1700,7 @@ Repetitive actions have been replaced with action groups in these tests:
-* Order emails sent from the Admin now use the store locale not the locale that is associated with the administrator’s account.
+* Order emails sent from the Admin now use the store locale not the locale that is associated with the administrator's account.
### UI
@@ -1816,7 +1818,7 @@ Repetitive actions have been replaced with action groups in these tests:
-* Magento now uses the correct custom email template when generating email for new Admin users. Previously, Magento used the old default template, which omitted the administrator’s first and last names.
+* Magento now uses the correct custom email template when generating email for new Admin users. Previously, Magento used the old default template, which omitted the administrator's first and last names.
@@ -1852,7 +1854,7 @@ Repetitive actions have been replaced with action groups in these tests:
-* An administrator can now delete all of a widget’s layout updates. Previously, when a widget had multiple layout updates, an administrator could delete only the first.
+* An administrator can now delete all of a widget's layout updates. Previously, when a widget had multiple layout updates, an administrator could delete only the first.
@@ -1862,7 +1864,7 @@ Repetitive actions have been replaced with action groups in these tests:
-* Magento no longer resets a configurable product’s configuration settings when you click the **Edit item** button for the product from a wish list. [GitHub-32119](https://github.com/magento/magento2/issues/32119)
+* Magento no longer resets a configurable product's configuration settings when you click the **Edit item** button for the product from a wish list. [GitHub-32119](https://github.com/magento/magento2/issues/32119)
diff --git a/src/guides/v2.4/release-notes/open-source-2-4-4.md b/src/guides/v2.4/release-notes/open-source-2-4-4.md
index 3be8f29cd87..99f57f3f441 100644
--- a/src/guides/v2.4/release-notes/open-source-2-4-4.md
+++ b/src/guides/v2.4/release-notes/open-source-2-4-4.md
@@ -1,6 +1,8 @@
---
group: release-notes
title: Magento Open Source 2.4.4 Release Notes
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/release/notes/magento-open-source/2-4-4.html
+status: migrated
---
{{ site.data.var.ce }} 2.4.4 introduces support for PHP 8.1. All project libraries and dependencies have been updated for compatibility with PHP 8.1. Core Composer dependencies and third-party libraries have also been upgraded to the latest versions that are compatible with PHP 8.1. This release also provides support for OpenSearch 1.2.
@@ -148,7 +150,7 @@ With the exception of [Braintree](https://docs.magento.com/user-guide/payment/br
* The Venmo payment option is now supported.
-* Pay Later has been added as an option for shoppers based on the shopper's location, not the merchant’s location.
+* Pay Later has been added as an option for shoppers based on the shopper's location, not the merchant's location.
* Merchants can now set the shopper country when testing the shopper experience in their country of choice. Previously, tests were limited to testing only for the country in which the merchant is located. This change is valid in sandbox mode only.
@@ -174,7 +176,7 @@ We are fixing hundreds of issues in the {{ site.data.var.ce }} 2.4.4 core code.
-* Data patches can no longer ignore a table’s unique constraints and insert duplicate values into a MySQL database table. Previously, patches could insert duplicate values, which corrupted the database.
+* Data patches can no longer ignore a table's unique constraints and insert duplicate values into a MySQL database table. Previously, patches could insert duplicate values, which corrupted the database.
@@ -268,7 +270,7 @@ We are fixing hundreds of issues in the {{ site.data.var.ce }} 2.4.4 core code.
-* Shoppers can now add a bundle product with Fixed Product Tax and two options to their shopping cart. Previously, {{ site.data.var.ce }} did not add the product and displayed this error: `We can’t add this item to your shopping cart right now`.
+* Shoppers can now add a bundle product with Fixed Product Tax and two options to their shopping cart. Previously, {{ site.data.var.ce }} did not add the product and displayed this error: `We can't add this item to your shopping cart right now`.
@@ -372,7 +374,7 @@ We are fixing hundreds of issues in the {{ site.data.var.ce }} 2.4.4 core code.
-* {{ site.data.var.ce }} no longer throws this error when a shopper adds a billing address that is missing a street field: `Uncaught TypeError: Unable to process binding "text: function(){return currentBillingAddress().street.join(', ') }”`. [GitHub-33826](https://github.com/magento/magento2/issues/33826)
+* {{ site.data.var.ce }} no longer throws this error when a shopper adds a billing address that is missing a street field: `Uncaught TypeError: Unable to process binding "text: function(){return currentBillingAddress().street.join(', ') }"`. [GitHub-33826](https://github.com/magento/magento2/issues/33826)
@@ -380,7 +382,7 @@ We are fixing hundreds of issues in the {{ site.data.var.ce }} 2.4.4 core code.
-* Checkout no longer fails at the payment stage when the billing address is missing street field values or the street field value is not an array. Previously, checkout failed with this error: `Uncaught TypeError: Unable to process binding "text: function(){return currentBillingAddress().street.join(', ') }”`. [GitHub-33826](https://github.com/magento/magento2/issues/33826)
+* Checkout no longer fails at the payment stage when the billing address is missing street field values or the street field value is not an array. Previously, checkout failed with this error: `Uncaught TypeError: Unable to process binding "text: function(){return currentBillingAddress().street.join(', ') }"`. [GitHub-33826](https://github.com/magento/magento2/issues/33826)
@@ -576,7 +578,7 @@ We are fixing hundreds of issues in the {{ site.data.var.ce }} 2.4.4 core code.
-* Order emails now contain data localized using the shopper’s locale as expected. Previously, order emails used the Admin locale.
+* Order emails now contain data localized using the shopper's locale as expected. Previously, order emails used the Admin locale.
@@ -828,7 +830,7 @@ We are fixing hundreds of issues in the {{ site.data.var.ce }} 2.4.4 core code.
-* {{ site.data.var.ce }} now converts the timestamp in the export filename to the user’s timezone after a scheduled export. Previously, these values were not converted, and {{ site.data.var.ce }} displayed the UTC timestamp.
+* {{ site.data.var.ce }} now converts the timestamp in the export filename to the user's timezone after a scheduled export. Previously, these values were not converted, and {{ site.data.var.ce }} displayed the UTC timestamp.
@@ -1345,7 +1347,7 @@ Repetitive actions have been replaced with action groups in these tests:
-* Shipment email now includes the tracking number for the current shipment only. Previously, when an order included several shipments, each shipment’s email included the tracking numbers from all shipments related to the order.
+* Shipment email now includes the tracking number for the current shipment only. Previously, when an order included several shipments, each shipment's email included the tracking numbers from all shipments related to the order.
@@ -1407,7 +1409,7 @@ Repetitive actions have been replaced with action groups in these tests:
-* Merchants can now test the shopper experience of the country in which the shopper is located, rather than the merchant’s location.
+* Merchants can now test the shopper experience of the country in which the shopper is located, rather than the merchant's location.
* Functional tests have been stabilized for PHP 8.x compatibility. [GitHub-34327](https://github.com/magento/magento2/issues/34327), [GitHub-34188](https://github.com/magento/magento2/issues/34188)
@@ -1689,7 +1691,7 @@ The following unit tests have been refactored to use `PHPUnit` instead of `Aspec
Dotdigital is a customer engagement platform that helps digital marketers and developers deliver communications across the customer journey. We harness the power of customer data, powering engagement, conversion, and loyalty for brands as they grow and scale. Customers love our easy-to-use platform that connects first party data across the systems, surfacing powerful insights and automating predictive cross-channel messages.
-Dotdigital’s 350+ employees serve mid-market and enterprise companies around the world and across industries. We aspire to inspire responsible marketing and are committed to sustainability, privacy, and security. Dotdigital is proud to be the world’s first carbon-neutral marketing automation platform, certified for ISO 14001, ISO 27701, and ISO 27001.
+Dotdigital's 350+ employees serve mid-market and enterprise companies around the world and across industries. We aspire to inspire responsible marketing and are committed to sustainability, privacy, and security. Dotdigital is proud to be the world's first carbon-neutral marketing automation platform, certified for ISO 14001, ISO 27701, and ISO 27001.
See [Dotdigital — Marketing Automation](https://marketplace.magento.com/dotdigital-dotdigital-magento2-os-package.html) for purchase and download information.
diff --git a/src/guides/v2.4/release-notes/open-source-2-4-5.md b/src/guides/v2.4/release-notes/open-source-2-4-5.md
index 59470ce59f0..1d12237b602 100644
--- a/src/guides/v2.4/release-notes/open-source-2-4-5.md
+++ b/src/guides/v2.4/release-notes/open-source-2-4-5.md
@@ -1,6 +1,8 @@
---
group: release-notes
title: Magento Open Source 2.4.5 Release Notes
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/release/notes/magento-open-source/2-4-5.html
+status: migrated
---
{{ site.data.var.ce }} introduces improvements to platform quality, payment methods, GraphQL caching performance, and accessibility. It includes updates to integrated Google modules.
@@ -226,7 +228,7 @@ We have fixed hundreds of issues in the {{ site.data.var.ce }} 2.4.5 core code.
-* Screen readers announce the word “Venia” only once when navigating to Venia headers and footers. Previously, the same word was announced twice consecutively.
+* Screen readers announce the word "Venia" only once when navigating to Venia headers and footers. Previously, the same word was announced twice consecutively.
@@ -390,7 +392,7 @@ We have fixed hundreds of issues in the {{ site.data.var.ce }} 2.4.5 core code.
-* Administrators can now change configurable product options in a shopper’s cart from the Admin slide panel. Previously, the slide panel did not work correctly.
+* Administrators can now change configurable product options in a shopper's cart from the Admin slide panel. Previously, the slide panel did not work correctly.
@@ -586,7 +588,7 @@ We have fixed hundreds of issues in the {{ site.data.var.ce }} 2.4.5 core code.
-* You can now create a customer account on an iOS device with the inclined apostrophe (’) in the first, middle, or last name. Previously, only the straight apostrophe was allowed, and using iOS 11+ default inclined apostrophe resulted in a `Name is not valid!` error.
+* You can now create a customer account on an iOS device with the inclined apostrophe (') in the first, middle, or last name. Previously, only the straight apostrophe was allowed, and using iOS 11+ default inclined apostrophe resulted in a `Name is not valid!` error.
@@ -930,7 +932,7 @@ Repetitive actions have been replaced with action groups in these tests:
-* Redis cache management has been improved by the addition of TTL (expiration date) for configurable products’ associated product data caches. Previously, these caches were not evicted due to missing TTL values if Redis key eviction policy was configured to a volatile eviction policy.
+* Redis cache management has been improved by the addition of TTL (expiration date) for configurable products' associated product data caches. Previously, these caches were not evicted due to missing TTL values if Redis key eviction policy was configured to a volatile eviction policy.
@@ -1122,7 +1124,7 @@ Repetitive actions have been replaced with action groups in these tests:
-* Administrators can now set the current user’s expiration date higher than 2038 and save the user successfully. Previously, the user whose expiration date was changed could not log back in after logging out.
+* Administrators can now set the current user's expiration date higher than 2038 and save the user successfully. Previously, the user whose expiration date was changed could not log back in after logging out.
diff --git a/src/guides/v2.4/release-notes/packages-cloud.md b/src/guides/v2.4/release-notes/packages-cloud.md
index 5da0023ab40..3e4ee9892b1 100644
--- a/src/guides/v2.4/release-notes/packages-cloud.md
+++ b/src/guides/v2.4/release-notes/packages-cloud.md
@@ -1,6 +1,8 @@
---
group: release-notes
title: Cloud packages for Adobe Commerce
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/release/packages/cloud.html
+status: migrated
---
+* **PayPal JavaScript SDK upgrade**. We've migrated the PayPal Express Checkout integration to the latest PayPal JavaScript SDK, an SDK that automatically collects and passes needed risk parameters to PayPal. The behavior of the PayPal Express Checkout payment method remains unchanged. However, upgrading this SDK to the latest version let merchants access the latest features and security enhancements.
* **Deprecation and removal of the Web Set Up Wizard**. You must use the command line to install or upgrade Magento 2.4.0. See [Install Magento]({{ page.baseurl }}/install-gde/install/cli/install-cli.html).
@@ -128,7 +130,7 @@ This release contains enhancements to core quality, which improve the quality of
* Decrease in the size of network data transfers between Redis and Magento
- * Reduction in Redis’ consumption of CPU cycles by improving the adapter’s ability to automatically determine what needs to be loaded
+ * Reduction in Redis' consumption of CPU cycles by improving the adapter's ability to automatically determine what needs to be loaded
* Reduction in race conditions on Redis write operations
@@ -261,7 +263,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* You can now successfully remove a website along with the website’s scope-specific configuration settings in `app/etc/config.php` as expected. Previously, when you tried to remove the website, the operation failed, and Magento displayed this error: `The website with code xxx that was requested wasn't found. Verify the website and try again`. Additionally, Magento displayed this error on the storefront: `Config files have changed. Run app:config:import or setup:upgrade command to synchronize configuration`. [GitHub-24061](https://github.com/magento/magento2/issues/24061)
+* You can now successfully remove a website along with the website's scope-specific configuration settings in `app/etc/config.php` as expected. Previously, when you tried to remove the website, the operation failed, and Magento displayed this error: `The website with code xxx that was requested wasn't found. Verify the website and try again`. Additionally, Magento displayed this error on the storefront: `Config files have changed. Run app:config:import or setup:upgrade command to synchronize configuration`. [GitHub-24061](https://github.com/magento/magento2/issues/24061)
@@ -294,7 +296,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Problems with LESS compilation in Magento’s Luma theme when using an alternative LESS compiler than the one that ships with Magento by default have been resolved. _Fix submitted by Pieter Hoste in pull request [24003](https://github.com/magento/magento2/pull/24003)_. [GitHub-23619](https://github.com/magento/magento2/issues/23619)
+* Problems with LESS compilation in Magento's Luma theme when using an alternative LESS compiler than the one that ships with Magento by default have been resolved. _Fix submitted by Pieter Hoste in pull request [24003](https://github.com/magento/magento2/pull/24003)_. [GitHub-23619](https://github.com/magento/magento2/issues/23619)
@@ -330,7 +332,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Magento no longer saves a preview of an Adobe Stock image when you move the cursor to the window’s left vertical scroll bar after clicking **Save Preview** but not confirming the save operation. _Fix submitted by Serhiy Zhovnir in pull request [27399](https://github.com/magento/magento2/pull/27399)_. [GitHub-1002](https://github.com/magento/adobe-stock-integration/issues/1002)
+* Magento no longer saves a preview of an Adobe Stock image when you move the cursor to the window's left vertical scroll bar after clicking **Save Preview** but not confirming the save operation. _Fix submitted by Serhiy Zhovnir in pull request [27399](https://github.com/magento/magento2/pull/27399)_. [GitHub-1002](https://github.com/magento/adobe-stock-integration/issues/1002)
### Analytics
@@ -368,7 +370,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Administrators can no longer manually enter a tax class in the Admin for a bundle product when the bundle product’s **Tax Class** and **Dynamic Price** settings are disabled for the default store view. Previously, when an administrator unchecked the **Use Default Value** option next to **Tax Class**, Magento enabled the option, permitting an administrator to enter another value and save the product.
+* Administrators can no longer manually enter a tax class in the Admin for a bundle product when the bundle product's **Tax Class** and **Dynamic Price** settings are disabled for the default store view. Previously, when an administrator unchecked the **Use Default Value** option next to **Tax Class**, Magento enabled the option, permitting an administrator to enter another value and save the product.
@@ -408,7 +410,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Magento now displays an informative message when a product in the mini cart becomes out-of-stock before checkout. Once you’ve removed the out-of-stock item, Magento displays the **Proceed to Checkout** button. Previously, Magento did not display this button.
+* Magento now displays an informative message when a product in the mini cart becomes out-of-stock before checkout. Once you've removed the out-of-stock item, Magento displays the **Proceed to Checkout** button. Previously, Magento did not display this button.
@@ -432,7 +434,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Changing the billing street no longer changes a customer’s shipping address when a single address has been selected for both billing and shipping address. _Fix submitted by Yurii Tvardyi in pull request [26279](https://github.com/magento/magento2/pull/26279)_. [GitHub-26276](https://github.com/magento/magento2/issues/26276)
+* Changing the billing street no longer changes a customer's shipping address when a single address has been selected for both billing and shipping address. _Fix submitted by Yurii Tvardyi in pull request [26279](https://github.com/magento/magento2/pull/26279)_. [GitHub-26276](https://github.com/magento/magento2/issues/26276)
@@ -458,13 +460,13 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Changing the billing street no longer changes a customer’s shipping address when a single address has been selected for both the billing and shipping addresses. _Fix submitted by Yurii Tvardyi in pull request [26279](https://github.com/magento/magento2/pull/26279)_. [GitHub-26276](https://github.com/magento/magento2/issues/26276)
+* Changing the billing street no longer changes a customer's shipping address when a single address has been selected for both the billing and shipping addresses. _Fix submitted by Yurii Tvardyi in pull request [26279](https://github.com/magento/magento2/pull/26279)_. [GitHub-26276](https://github.com/magento/magento2/issues/26276)
### Catalog
-* Magento now disables the ability of a restricted administrator to change a product’s quantity attribute and disables advanced inventory as expected. Previously, only the visual display of the quantity attribute was affected, and Magento changed the quantity value in the database after the product was saved.
+* Magento now disables the ability of a restricted administrator to change a product's quantity attribute and disables advanced inventory as expected. Previously, only the visual display of the quantity attribute was affected, and Magento changed the quantity value in the database after the product was saved.
@@ -488,7 +490,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* The product compare feature now works as expected. It now displays only products in the current user’s compare list.
+* The product compare feature now works as expected. It now displays only products in the current user's compare list.
@@ -540,7 +542,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* The sample description that is provided for a newly product’s description and title no longer contains double quotation marks. _Fix submitted by Nathan Morgan in pull request [25655](https://github.com/magento/magento2/pull/25655)_. [GitHub-25654](https://github.com/magento/magento2/issues/25654)
+* The sample description that is provided for a newly product's description and title no longer contains double quotation marks. _Fix submitted by Nathan Morgan in pull request [25655](https://github.com/magento/magento2/pull/25655)_. [GitHub-25654](https://github.com/magento/magento2/issues/25654)
@@ -556,7 +558,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Saving a new (duplicated) product no longer results in the duplication of the product’s images hundreds of times. _Fix submitted by Jeroen in pull request [25875](https://github.com/magento/magento2/pull/25875)_. [GitHub-9466](https://github.com/magento/magento2/issues/9466)
+* Saving a new (duplicated) product no longer results in the duplication of the product's images hundreds of times. _Fix submitted by Jeroen in pull request [25875](https://github.com/magento/magento2/pull/25875)_. [GitHub-9466](https://github.com/magento/magento2/issues/9466)
@@ -572,7 +574,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* You can now use the Actions dropdown menu from the Products grid to specify whether a product has weight when you update multiple products’s attributes from the Admin. _Fix submitted by Bartomiej Szubert in pull request [26075](https://github.com/magento/magento2/pull/26075)_. [GitHub-6310](https://github.com/magento/magento2/issues/6310)
+* You can now use the Actions dropdown menu from the Products grid to specify whether a product has weight when you update multiple products's attributes from the Admin. _Fix submitted by Bartomiej Szubert in pull request [26075](https://github.com/magento/magento2/pull/26075)_. [GitHub-6310](https://github.com/magento/magento2/issues/6310)
@@ -622,7 +624,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* New CMS pages are now added as expected to a website’s store page hierarchy.
+* New CMS pages are now added as expected to a website's store page hierarchy.
@@ -726,7 +728,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Magento now displays a product’s special price as expected when you select a discounted option of a configurable product. Previously, `class="normal-price"` was not changed to `class="special-price"` when a discounted option was selected. _Fix submitted by Ravi Chandra in pull request [26170](https://github.com/magento/magento2/pull/26170)_. [GitHub-24972](https://github.com/magento/magento2/issues/24972)
+* Magento now displays a product's special price as expected when you select a discounted option of a configurable product. Previously, `class="normal-price"` was not changed to `class="special-price"` when a discounted option was selected. _Fix submitted by Ravi Chandra in pull request [26170](https://github.com/magento/magento2/pull/26170)_. [GitHub-24972](https://github.com/magento/magento2/issues/24972)
### Cookies
@@ -808,7 +810,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Magento now displays only the products that the customer has placed in their cart when the cart is viewed from the Admin. Previously, a customer’s shopping cart displayed all the products in the catalog when viewed from the Admin. _Fix submitted by Ravinder in pull request [26489](https://github.com/magento/magento2/pull/26489)_. [GitHub-26437](https://github.com/magento/magento2/issues/26437)
+* Magento now displays only the products that the customer has placed in their cart when the cart is viewed from the Admin. Previously, a customer's shopping cart displayed all the products in the catalog when viewed from the Admin. _Fix submitted by Ravinder in pull request [26489](https://github.com/magento/magento2/pull/26489)_. [GitHub-26437](https://github.com/magento/magento2/issues/26437)
@@ -834,7 +836,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* We’ve improved the performance of editing and saving customer segments that contain large numbers of customers (more than three million). Previously, when you created or edited a customer segment that contained many customers, Magento threw a 500 error.
+* We've improved the performance of editing and saving customer segments that contain large numbers of customers (more than three million). Previously, when you created or edited a customer segment that contained many customers, Magento threw a 500 error.
### Directory
@@ -888,7 +890,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
### Frameworks
-* Dependencies on Zend Framework have been migrated to the [Laminas project](https://getlaminas.org/about/foundation) to reflect the transitioning of Zend Framework to the Linux Foundation’s Laminas Project. Zend Framework has been deprecated. _Fix submitted by Ihor Sviziev in pull request [26436](https://github.com/magento/magento2/pull/26436)_. [GitHub-26335](https://github.com/magento/magento2/issues/26335)
+* Dependencies on Zend Framework have been migrated to the [Laminas project](https://getlaminas.org/about/foundation) to reflect the transitioning of Zend Framework to the Linux Foundation's Laminas Project. Zend Framework has been deprecated. _Fix submitted by Ihor Sviziev in pull request [26436](https://github.com/magento/magento2/pull/26436)_. [GitHub-26335](https://github.com/magento/magento2/issues/26335)
@@ -904,7 +906,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* The Update Attribute action now correctly updates the timestamp of a product’s `updated_at column` from `catalog_product_entity` when you update the product from the Admin edit product page.
+* The Update Attribute action now correctly updates the timestamp of a product's `updated_at column` from `catalog_product_entity` when you update the product from the Admin edit product page.
@@ -916,7 +918,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* We’ve improved the performance of the `Magento\Framework\App\DeploymentConfig\Reader::load` function. Previously, when a request was made to Magento, this function was called repetitively, which resulted in `config.php` and `env.php config` files being loaded each time the method was called.
+* We've improved the performance of the `Magento\Framework\App\DeploymentConfig\Reader::load` function. Previously, when a request was made to Magento, this function was called repetitively, which resulted in `config.php` and `env.php config` files being loaded each time the method was called.
@@ -924,7 +926,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Non-cacheable blocks added to the default layout in reference instructions for non-existent (undeclared) components on the page no longer affect page caching. Adding non-cacheable blocks to default layout handlers renders all Magento pages non-cacheable. This results from the layout generation process: During layout generation, Magento collects all available layout handles for a particular page and merges instructions from them into the page’s final layout structure. The default layout handle is used as a basic handle for every page. As a result, layout updates that are declared for the default handler appear on every Magento page. [GitHub-9041](https://github.com/magento/magento2/issues/9041)
+* Non-cacheable blocks added to the default layout in reference instructions for non-existent (undeclared) components on the page no longer affect page caching. Adding non-cacheable blocks to default layout handlers renders all Magento pages non-cacheable. This results from the layout generation process: During layout generation, Magento collects all available layout handles for a particular page and merges instructions from them into the page's final layout structure. The default layout handle is used as a basic handle for every page. As a result, layout updates that are declared for the default handler appear on every Magento page. [GitHub-9041](https://github.com/magento/magento2/issues/9041)
@@ -970,7 +972,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* A store’s Admin URL no longer redirects to the storefront URL when these two URLs differ.
+* A store's Admin URL no longer redirects to the storefront URL when these two URLs differ.
@@ -1066,7 +1068,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Magento now implements PHP7.x’s [throwable interface](https://www.php.net/manual/en/class.throwable.php) to enable the catching of all errors that might potentially expose sensitive information such as passwords. _Fix submitted by miszyman in pull request [25250](https://github.com/magento/magento2/pull/25250)_. [GitHub-23350](https://github.com/magento/magento2/issues/23350)
+* Magento now implements PHP7.x's [throwable interface](https://www.php.net/manual/en/class.throwable.php) to enable the catching of all errors that might potentially expose sensitive information such as passwords. _Fix submitted by miszyman in pull request [25250](https://github.com/magento/magento2/pull/25250)_. [GitHub-23350](https://github.com/magento/magento2/issues/23350)
@@ -1086,7 +1088,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* We’ve added the `@api` PHP annotation to `AbstractExtensibleModel`, the `@deprecated` PHP annotation to `AbstractExtensibleObject`, and `@see` to `AbstractExtensibleModel`. _Fix submitted by Alexander Taranovsky in pull request [22011](https://github.com/magento/magento2/pull/22011)_. [GitHub-22010](https://github.com/magento/magento2/issues/22010)
+* We've added the `@api` PHP annotation to `AbstractExtensibleModel`, the `@deprecated` PHP annotation to `AbstractExtensibleObject`, and `@see` to `AbstractExtensibleModel`. _Fix submitted by Alexander Taranovsky in pull request [22011](https://github.com/magento/magento2/pull/22011)_. [GitHub-22010](https://github.com/magento/magento2/issues/22010)
### Gift cards
@@ -1110,7 +1112,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Magento now correctly calculates the cost of gift wrapping based on the number of products for which you’ve ordered gift wrap. Previously, Magento included the cost of gift wrap for one product only in the order.
+* Magento now correctly calculates the cost of gift wrapping based on the number of products for which you've ordered gift wrap. Previously, Magento included the cost of gift wrap for one product only in the order.
### Google Tag Manager
@@ -1150,7 +1152,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* You can now add a child product of a grouped product to your cart when one of the grouped product’s other child products is out-of-stock. Previously, when one child product was out-of-stock, you could not add any other child products to the cart.
+* You can now add a child product of a grouped product to your cart when one of the grouped product's other child products is out-of-stock. Previously, when one child product was out-of-stock, you could not add any other child products to the cart.
### Images
@@ -1164,7 +1166,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* You can now successfully save an image to a category from the Admin. Previously, after you saved the image, part of the URL was missing, and you couldn’t re-open the image.
+* You can now successfully save an image to a category from the Admin. Previously, after you saved the image, part of the URL was missing, and you couldn't re-open the image.
@@ -1206,7 +1208,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Customizable options are now imported as expected when `row_id` is not equal to a product's `entity_id`. Previously, Magento did not import customizable options when `row_id` was not equal to a product’s `entity_id`, which resulted in certain products not being imported.
+* Customizable options are now imported as expected when `row_id` is not equal to a product's `entity_id`. Previously, Magento did not import customizable options when `row_id` was not equal to a product's `entity_id`, which resulted in certain products not being imported.
@@ -1226,7 +1228,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Magento now successfully imports all custom options for a configurable product’s child products when `store_view_code` is specified. This works whether you choose to import configurable products individually or collectively. Previously, Magento did not successfully import all custom options when the import file contained more than one item and `store_view_code` was specified.
+* Magento now successfully imports all custom options for a configurable product's child products when `store_view_code` is specified. This works whether you choose to import configurable products individually or collectively. Previously, Magento did not successfully import all custom options when the import file contained more than one item and `store_view_code` was specified.
@@ -1378,7 +1380,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Clicking **Enter** after naming a new folder in the Media Gallery now saves all changes you’ve made. Previously, clicking **Enter** instead of using the mouse to select **OK** resulted in all changes being lost. _Fix submitted by Sergiy Vasiutynskyi in pull request [27029](https://github.com/magento/magento2/pull/27029)_. [GitHub-26847](https://github.com/magento/magento2/issues/26847)
+* Clicking **Enter** after naming a new folder in the Media Gallery now saves all changes you've made. Previously, clicking **Enter** instead of using the mouse to select **OK** resulted in all changes being lost. _Fix submitted by Sergiy Vasiutynskyi in pull request [27029](https://github.com/magento/magento2/pull/27029)_. [GitHub-26847](https://github.com/magento/magento2/issues/26847)
@@ -1428,7 +1430,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* You can now successfully complete an order and return to the merchant’s home page when **Website Payments Pro Hosted Solution** is configured. Previously, when you clicked **Return to merchant**, Magento threw this error: `Invalid Form Key. Please refresh the page`.
+* You can now successfully complete an order and return to the merchant's home page when **Website Payments Pro Hosted Solution** is configured. Previously, when you clicked **Return to merchant**, Magento threw this error: `Invalid Form Key. Please refresh the page`.
@@ -1440,7 +1442,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* You can now remove additional information from the `quote_payment column additional_information` table after you’ve saved a quote. Previously, you could not remove this information after saving the quote because the `unsAdditionalInformation` method in `\Magento\Payment\Model\Info` did not initialize data properly. _Fix submitted by Marco Oliveira in pull request [26084](https://github.com/magento/magento2/pull/26084)_. [GitHub-26083](https://github.com/magento/magento2/issues/26083)
+* You can now remove additional information from the `quote_payment column additional_information` table after you've saved a quote. Previously, you could not remove this information after saving the quote because the `unsAdditionalInformation` method in `\Magento\Payment\Model\Info` did not initialize data properly. _Fix submitted by Marco Oliveira in pull request [26084](https://github.com/magento/magento2/pull/26084)_. [GitHub-26083](https://github.com/magento/magento2/issues/26083)
@@ -1458,7 +1460,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Magento no longer changes an order’s status to `Processing` in the Payment Review section of the checkout workflow when a payment with PayPal fails.
+* Magento no longer changes an order's status to `Processing` in the Payment Review section of the checkout workflow when a payment with PayPal fails.
@@ -1482,11 +1484,11 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Magento now successfully processes orders placed with PayPal Express Checkout where the order’s shipping address specifies a country region that the customer has manually entered into the text field rather than selected from the drop-down menu on the Shipping page. Previously, Magento displayed this error on the order review page: `Error 500: NOTICE: PHP message: PHP Fatal error: Uncaught Error: Call to a member function getId() on null in httpdocs/vendor/magento/module-paypal/Model/Api/Nvp.php:1527`. [GitHub-26698](https://github.com/magento/magento2/issues/26698)
+* Magento now successfully processes orders placed with PayPal Express Checkout where the order's shipping address specifies a country region that the customer has manually entered into the text field rather than selected from the drop-down menu on the Shipping page. Previously, Magento displayed this error on the order review page: `Error 500: NOTICE: PHP message: PHP Fatal error: Uncaught Error: Call to a member function getId() on null in httpdocs/vendor/magento/module-paypal/Model/Api/Nvp.php:1527`. [GitHub-26698](https://github.com/magento/magento2/issues/26698)
-* The PayPal Pro payment method now works as expected in the Chrome 80 browser. This payment method previously invoked a Magento callback endpoint that needed access to the customer’s session — access that the new default Chrome SameSite cookie functionality does not permit. [GitHub-26840](https://github.com/magento/magento2/issues/26840)
+* The PayPal Pro payment method now works as expected in the Chrome 80 browser. This payment method previously invoked a Magento callback endpoint that needed access to the customer's session — access that the new default Chrome SameSite cookie functionality does not permit. [GitHub-26840](https://github.com/magento/magento2/issues/26840)
@@ -1522,11 +1524,11 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Magento now saves and displays the correct price for tiered products even after you’ve edited products multiple times. Previously, Magento did not save the last edits made to product price. _Fix submitted by Ravi Chandra in pull request [26162](https://github.com/magento/magento2/pull/26162)_. [GitHub-25195](https://github.com/magento/magento2/issues/25195)
+* Magento now saves and displays the correct price for tiered products even after you've edited products multiple times. Previously, Magento did not save the last edits made to product price. _Fix submitted by Ravi Chandra in pull request [26162](https://github.com/magento/magento2/pull/26162)_. [GitHub-25195](https://github.com/magento/magento2/issues/25195)
-* Both fixed and discount save percentage are now correctly applied on an order’s final price. Previously, Magento displayed an incorrect tier price (both fixed & discount) save percentage on the product detail page. _Fix submitted by Sathish Subramanian in pull request [26584](https://github.com/magento/magento2/pull/26584)_. [GitHub-26583](https://github.com/magento/magento2/issues/26583)
+* Both fixed and discount save percentage are now correctly applied on an order's final price. Previously, Magento displayed an incorrect tier price (both fixed & discount) save percentage on the product detail page. _Fix submitted by Sathish Subramanian in pull request [26584](https://github.com/magento/magento2/pull/26584)_. [GitHub-26583](https://github.com/magento/magento2/issues/26583)
### Product alert
@@ -1536,7 +1538,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Product stock alert unsubscribe now works when a user’s session has expired. Previously, when you clicked on the **Click here to stop alerts for this product** link, Magento displayed a 404 error.
+* Product stock alert unsubscribe now works when a user's session has expired. Previously, when you clicked on the **Click here to stop alerts for this product** link, Magento displayed a 404 error.
@@ -1612,7 +1614,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Magento now honors a customer’s default shipping address. Previously, Magento did not honor the default billing and default shipping addresses according to the settings, and the **Same As Billing Address** setting was not enabled automatically.
+* Magento now honors a customer's default shipping address. Previously, Magento did not honor the default billing and default shipping addresses according to the settings, and the **Same As Billing Address** setting was not enabled automatically.
@@ -1632,7 +1634,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* You can now successfully add a product to the cart from the Admin when the stock quantity is 1. Previously, Magento didn’t add the product to the cart and displayed this message: `The requested qty is not available`. _Fix submitted by Serhii Petrychenko in pull request [26650](https://github.com/magento/magento2/pull/26650)._ [GitHub-25675](https://github.com/magento/magento2/issues/25675)
+* You can now successfully add a product to the cart from the Admin when the stock quantity is 1. Previously, Magento didn't add the product to the cart and displayed this message: `The requested qty is not available`. _Fix submitted by Serhii Petrychenko in pull request [26650](https://github.com/magento/magento2/pull/26650)._ [GitHub-25675](https://github.com/magento/magento2/issues/25675)
@@ -1948,7 +1950,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* We’ve resolved a bug in `JsFooterPlugin.php` that affected the display of dynamic blocks. Previously, Magento displayed this error when you directly accessed `/banner/ajax/load/url`: `Uncaught TypeError: strpos() expects parameter 1 to be string, null given in`.
+* We've resolved a bug in `JsFooterPlugin.php` that affected the display of dynamic blocks. Previously, Magento displayed this error when you directly accessed `/banner/ajax/load/url`: `Uncaught TypeError: strpos() expects parameter 1 to be string, null given in`.
@@ -2084,7 +2086,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* You can now update the value of a downloadable product’s sample and link title by enabling the **Use default** checkbox. _Fix submitted by Abel Truong in pull request [27295](https://github.com/magento/magento2/pull/27295)_. [GitHub-27169](https://github.com/magento/magento2/issues/27169)
+* You can now update the value of a downloadable product's sample and link title by enabling the **Use default** checkbox. _Fix submitted by Abel Truong in pull request [27295](https://github.com/magento/magento2/pull/27295)_. [GitHub-27169](https://github.com/magento/magento2/issues/27169)
@@ -2112,15 +2114,15 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Customers who change language on a CMS page can now successfully navigate to the store view they’ve selected. Previously, Magento displayed a 404 error.
+* Customers who change language on a CMS page can now successfully navigate to the store view they've selected. Previously, Magento displayed a 404 error.
-* URL rewrite generation for product URLs for which you’ve enabled category path inclusion now works as expected. Previously, in deployments with multiple store views, Magento sometimes generated incorrect URL rewrites by using the default value of the category url path instead of the storeview-specific URL path. _Fix submitted by Pieter Hoste in pull request [26784](https://github.com/magento/magento2/pull/26784)_. [GitHub-25124](https://github.com/magento/magento2/issues/25124), [GitHub-11616](https://github.com/magento/magento2/issues/11616)
+* URL rewrite generation for product URLs for which you've enabled category path inclusion now works as expected. Previously, in deployments with multiple store views, Magento sometimes generated incorrect URL rewrites by using the default value of the category url path instead of the storeview-specific URL path. _Fix submitted by Pieter Hoste in pull request [26784](https://github.com/magento/magento2/pull/26784)_. [GitHub-25124](https://github.com/magento/magento2/issues/25124), [GitHub-11616](https://github.com/magento/magento2/issues/11616)
-* We’ve added a check to prevent URL redirects if the request path is the same as the target path. _Fix submitted by Bartomiej Szubert in pull request [26902](https://github.com/magento/magento2/pull/26902)_. [GitHub-20309](https://github.com/magento/magento2/issues/20309)
+* We've added a check to prevent URL redirects if the request path is the same as the target path. _Fix submitted by Bartomiej Szubert in pull request [26902](https://github.com/magento/magento2/pull/26902)_. [GitHub-20309](https://github.com/magento/magento2/issues/20309)
@@ -2192,7 +2194,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* We’ve improved the error message that is displayed when a customer tries to share their wishlist with more email addresses than is permitted. _Fix submitted by divyajyothi5321 in pull request [26066](https://github.com/magento/magento2/pull/26066)_. [GitHub-26064](https://github.com/magento/magento2/issues/26064)
+* We've improved the error message that is displayed when a customer tries to share their wishlist with more email addresses than is permitted. _Fix submitted by divyajyothi5321 in pull request [26066](https://github.com/magento/magento2/pull/26066)_. [GitHub-26064](https://github.com/magento/magento2/issues/26064)
@@ -2230,11 +2232,11 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
**Issue**: Administrators cannot add a configurable product by SKU to a quote. When an administrator clicks on the **Add to Quote** button, the Quote Edit page remained in a loading state, and the administrator could not save their changes. **Workaround**: There is no workaround for B2B Quote editing. However, you can still order products by selecting the products from the products list instead of adding them by SKU. See B2B Admin cannot add a configurable product to a quote](https://support.magento.com/hc/en-us/articles/360046801971) Knowledge Base article.
-**Issue**: Merchants can’t create a new order from the Admin because the **Add Products By SKU** and **Add Products** buttons are missing from the order creation page when JavaScript bundling is enabled. **Workaround**: Disable the JavaScript bundling for your Magento deployment.
+**Issue**: Merchants can't create a new order from the Admin because the **Add Products By SKU** and **Add Products** buttons are missing from the order creation page when JavaScript bundling is enabled. **Workaround**: Disable the JavaScript bundling for your Magento deployment.
**Issue**: Magento throws a `404 not found` error when a customer tries to remove reward points when checking out an order being shipped to multiple addresses.
-**Issue**: Editing a configurable product from a customer’s wishlist results in the following unexpected behavior: An unexpected field appears on the Configure Product page, and the Configure Product page does not disappear after you click **OK**. Magento also displays this message: `Please load Wish List item`. **Workaround**: Reload the Configure Product page.
+**Issue**: Editing a configurable product from a customer's wishlist results in the following unexpected behavior: An unexpected field appears on the Configure Product page, and the Configure Product page does not disappear after you click **OK**. Magento also displays this message: `Please load Wish List item`. **Workaround**: Reload the Configure Product page.
**Issue**: Customers cannot change the number of orders displayed per page when the Orders list spans multiple pages. Currently, Magento displays this message when you navigate to the last page of orders and try to change the number of orders displayed per page: `You have placed no orders`. See [Orders display error](https://support.magento.com/hc/en-us/articles/360046802271) Knowledge Base article. **Workaround**: Re-opening the My Orders page will result in the display of the Orders list.
@@ -2260,7 +2262,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
* **Issue**: Magento displays an error when an administrator tries to access the Braintree Settlement Report page (**Admin** > **Reports** ). Currently, Magento displays this message: `An error has happened during application run. See exception log for details`. See [Braintree Settlement Report fails to load](https://support.magento.com/hc/en-us/articles/360046798251) Knowledge Base article. The **BUNDLE-2683_SettlementReport.patch** hotfix for this issue is now available from [Releases](https://magento.com/tech-resources/download).
-* **Issue**: Merchants can’t create partial invoices for orders in deployments where Venmo is enabled and the **Enable Vault for Card Payments** setting is disabled. Currently, Magento displays this error: `The "vault_capture" command doesn't exist. Verify the command and try again`.
+* **Issue**: Merchants can't create partial invoices for orders in deployments where Venmo is enabled and the **Enable Vault for Card Payments** setting is disabled. Currently, Magento displays this error: `The "vault_capture" command doesn't exist. Verify the command and try again`.
* **Issue**: Magento displays two identical PayPal methods in the Payment Method drop-down list that is available when creating a new cart price rule.
@@ -2278,7 +2280,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
### Vertex
-* **Issue**: Magento displays an **Address verification** button on the shipping section of the checkout workflow even when address validation is disabled. The address validator doesn’t re-check the updated address and continues to display a message that indicates that the address is invalid when a customer enters a correct address after first entering an incorrect address even when address validation is enabled. **Workaround**: Disable Vertex address validation.
+* **Issue**: Magento displays an **Address verification** button on the shipping section of the checkout workflow even when address validation is disabled. The address validator doesn't re-check the updated address and continues to display a message that indicates that the address is invalid when a customer enters a correct address after first entering an incorrect address even when address validation is enabled. **Workaround**: Disable Vertex address validation.
## Community contributions
diff --git a/src/guides/v2.4/release-notes/release-notes-2-4-0-open-source.md b/src/guides/v2.4/release-notes/release-notes-2-4-0-open-source.md
index ab7c231922b..74d846057bc 100644
--- a/src/guides/v2.4/release-notes/release-notes-2-4-0-open-source.md
+++ b/src/guides/v2.4/release-notes/release-notes-2-4-0-open-source.md
@@ -1,6 +1,8 @@
---
group: release-notes
title: Magento Open Source 2.4.0 Release Notes
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/release/notes/magento-open-source/2-4-0.html
+status: migrated
---
{{site.data.var.ce}} 2.4.0 introduces support for PHP 7.4, Elasticsearch 7.6.x, and MySQL 8.0. Substantial security changes include the enablement of two-factor authentication in the Admin by default.
@@ -90,7 +92,7 @@ The following platform upgrades help enhance website security and performance. S
* **MariaDB 10.4 support**. Support for MySQL 8.0 provides the opportunity for merchants to deploy MariaDB 10.4 with Magento. Although merchants can still use MariaDB 10.2 with Magento 2.4.0, we recommend upgrading to MariaDB 10.4 for improved performance and reliability. MariaDB 10.0 and 10.1 are no longer supported (as a result of removing support for MySQL 5.6 in this release).
-* **Migration of dependencies on Zend Framework to the [Laminas project](https://getlaminas.org/about/foundation)** to reflect the transitioning of Zend Framework to the Linux Foundation’s Laminas Project. Zend Framework has been deprecated. See the [Migration of Zend Framework to the Laminas Project](https://community.magento.com/t5/Magento-DevBlog/Migration-of-Zend-Framework-to-the-Laminas-Project/ba-p/443251) DevBlog post.
+* **Migration of dependencies on Zend Framework to the [Laminas project](https://getlaminas.org/about/foundation)** to reflect the transitioning of Zend Framework to the Linux Foundation's Laminas Project. Zend Framework has been deprecated. See the [Migration of Zend Framework to the Laminas Project](https://community.magento.com/t5/Magento-DevBlog/Migration-of-Zend-Framework-to-the-Laminas-Project/ba-p/443251) DevBlog post.
* **Decomposition of Magento Controllers** allows extension developers to implement ActionInterface directly without "layer supertype" classes. See the [Decomposition of Magento Controllers](https://community.magento.com/t5/Magento-DevBlog/Decomposition-of-Magento-Controllers/ba-p/430883) DevBlog post. _Enhancement started by Vinai Kopp in pull request [16268](https://github.com/magento/magento2/pull/16268) and finalized by Lukasz Bajsarowicz in pull request [26778](https://github.com/magento/magento2/pull/26778)_. [GitHub-9582](https://github.com/magento/magento2/issues/9582)
@@ -108,7 +110,7 @@ This release contains enhancements to core quality, which improve the quality of
* **Support for partial-word search for Elasticsearch (new default search engine)**. Elasticsearch now supports the use of partial words in search terms for product names and SKUs when using quick search. This capability was supported by the MySQL search engine, which has been deprecated and replaced by Elasticsearch in this release.
-* **PayPal JavaScript SDK upgrade**. We’ve migrated the PayPal Express Checkout integration to the latest PayPal JavaScript SDK, an SDK that automatically collects and passes needed risk parameters to PayPal. The behavior of the PayPal Express Checkout payment method remains unchanged. However, upgrading this SDK to the latest version let merchants access the latest features and security enhancements.
+* **PayPal JavaScript SDK upgrade**. We've migrated the PayPal Express Checkout integration to the latest PayPal JavaScript SDK, an SDK that automatically collects and passes needed risk parameters to PayPal. The behavior of the PayPal Express Checkout payment method remains unchanged. However, upgrading this SDK to the latest version let merchants access the latest features and security enhancements.
* **Deprecation and removal of the Web Set Up Wizard**. You must use the command line to install or upgrade Magento 2.4.0. See [Install Magento]({{ page.baseurl }}/install-gde/install/cli/install-cli.html).
@@ -129,7 +131,7 @@ This release contains enhancements to core quality, which improve the quality of
* Decrease in the size of network data transfers between Redis and Magento
- * Reduction in Redis’ consumption of CPU cycles by improving the adapter’s ability to automatically determine what needs to be loaded
+ * Reduction in Redis' consumption of CPU cycles by improving the adapter's ability to automatically determine what needs to be loaded
* Reduction in race conditions on Redis write operations
@@ -231,7 +233,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* You can now successfully remove a website along with the website’s scope-specific configuration settings in `app/etc/config.php` as expected. Previously, when you tried to remove the website, the operation failed, and Magento displayed this error: `The website with code xxx that was requested wasn't found. Verify the website and try again`. Additionally, Magento displayed this error on the storefront: `Config files have changed. Run app:config:import or setup:upgrade command to synchronize configuration`. [GitHub-24061](https://github.com/magento/magento2/issues/24061)
+* You can now successfully remove a website along with the website's scope-specific configuration settings in `app/etc/config.php` as expected. Previously, when you tried to remove the website, the operation failed, and Magento displayed this error: `The website with code xxx that was requested wasn't found. Verify the website and try again`. Additionally, Magento displayed this error on the storefront: `Config files have changed. Run app:config:import or setup:upgrade command to synchronize configuration`. [GitHub-24061](https://github.com/magento/magento2/issues/24061)
@@ -264,7 +266,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Problems with LESS compilation in Magento’s Luma theme when using an alternative LESS compiler than the one that ships with Magento by default have been resolved. _Fix submitted by Pieter Hoste in pull request [24003](https://github.com/magento/magento2/pull/24003)_. [GitHub-23619](https://github.com/magento/magento2/issues/23619)
+* Problems with LESS compilation in Magento's Luma theme when using an alternative LESS compiler than the one that ships with Magento by default have been resolved. _Fix submitted by Pieter Hoste in pull request [24003](https://github.com/magento/magento2/pull/24003)_. [GitHub-23619](https://github.com/magento/magento2/issues/23619)
@@ -294,7 +296,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Magento no longer saves a preview of an Adobe Stock image when you move the cursor to the window’s left vertical scroll bar after clicking **Save Preview** but not confirming the save operation. _Fix submitted by Serhiy Zhovnir in pull request [27399](https://github.com/magento/magento2/pull/27399)_. [GitHub-1002](https://github.com/magento/adobe-stock-integration/issues/1002)
+* Magento no longer saves a preview of an Adobe Stock image when you move the cursor to the window's left vertical scroll bar after clicking **Save Preview** but not confirming the save operation. _Fix submitted by Serhiy Zhovnir in pull request [27399](https://github.com/magento/magento2/pull/27399)_. [GitHub-1002](https://github.com/magento/adobe-stock-integration/issues/1002)
### Backend
@@ -322,7 +324,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Administrators can no longer manually enter a tax class in the Admin for a bundle product when the bundle product’s **Tax Class** and **Dynamic Price** settings are disabled for the default store view. Previously, when an administrator unchecked the **Use Default Value** option next to **Tax Class**, Magento enabled the option, permitting an administrator to enter another value and save the product.
+* Administrators can no longer manually enter a tax class in the Admin for a bundle product when the bundle product's **Tax Class** and **Dynamic Price** settings are disabled for the default store view. Previously, when an administrator unchecked the **Use Default Value** option next to **Tax Class**, Magento enabled the option, permitting an administrator to enter another value and save the product.
@@ -362,7 +364,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Magento now displays an informative message when a product in the mini cart becomes out-of-stock before checkout. Once you’ve removed the out-of-stock item, Magento displays the **Proceed to Checkout** button. Previously, Magento did not display this button.
+* Magento now displays an informative message when a product in the mini cart becomes out-of-stock before checkout. Once you've removed the out-of-stock item, Magento displays the **Proceed to Checkout** button. Previously, Magento did not display this button.
@@ -386,7 +388,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Changing the billing street no longer changes a customer’s shipping address when a single address has been selected for both billing and shipping address. _Fix submitted by Yurii Tvardyi in pull request [26279](https://github.com/magento/magento2/pull/26279)_. [GitHub-26276](https://github.com/magento/magento2/issues/26276)
+* Changing the billing street no longer changes a customer's shipping address when a single address has been selected for both billing and shipping address. _Fix submitted by Yurii Tvardyi in pull request [26279](https://github.com/magento/magento2/pull/26279)_. [GitHub-26276](https://github.com/magento/magento2/issues/26276)
@@ -412,7 +414,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Changing the billing street no longer changes a customer’s shipping address when a single address has been selected for both the billing and shipping addresses. _Fix submitted by Yurii Tvardyi in pull request [26279](https://github.com/magento/magento2/pull/26279)_. [GitHub-26276](https://github.com/magento/magento2/issues/26276)
+* Changing the billing street no longer changes a customer's shipping address when a single address has been selected for both the billing and shipping addresses. _Fix submitted by Yurii Tvardyi in pull request [26279](https://github.com/magento/magento2/pull/26279)_. [GitHub-26276](https://github.com/magento/magento2/issues/26276)
### Catalog
@@ -438,7 +440,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* The product compare feature now works as expected. It now displays only products in the current user’s compare list.
+* The product compare feature now works as expected. It now displays only products in the current user's compare list.
@@ -486,7 +488,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* The sample description that is provided for a newly product’s description and title no longer contains double quotation marks. _Fix submitted by Nathan Morgan in pull request [25655](https://github.com/magento/magento2/pull/25655)_. [GitHub-25654](https://github.com/magento/magento2/issues/25654)
+* The sample description that is provided for a newly product's description and title no longer contains double quotation marks. _Fix submitted by Nathan Morgan in pull request [25655](https://github.com/magento/magento2/pull/25655)_. [GitHub-25654](https://github.com/magento/magento2/issues/25654)
@@ -502,7 +504,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Saving a new (duplicated) product no longer results in the duplication of the product’s images hundreds of times. _Fix submitted by Jeroen in pull request [25875](https://github.com/magento/magento2/pull/25875)_. [GitHub-9466](https://github.com/magento/magento2/issues/9466)
+* Saving a new (duplicated) product no longer results in the duplication of the product's images hundreds of times. _Fix submitted by Jeroen in pull request [25875](https://github.com/magento/magento2/pull/25875)_. [GitHub-9466](https://github.com/magento/magento2/issues/9466)
@@ -518,7 +520,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* You can now use the Actions dropdown menu from the Products grid to specify whether a product has weight when you update multiple products’ attributes from the Admin. _Fix submitted by Bartomiej Szubert in pull request [26075](https://github.com/magento/magento2/pull/26075)_. [GitHub-6310](https://github.com/magento/magento2/issues/6310)
+* You can now use the Actions dropdown menu from the Products grid to specify whether a product has weight when you update multiple products' attributes from the Admin. _Fix submitted by Bartomiej Szubert in pull request [26075](https://github.com/magento/magento2/pull/26075)_. [GitHub-6310](https://github.com/magento/magento2/issues/6310)
@@ -620,7 +622,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* New CMS pages are now added as expected to a website’s store page hierarchy.
+* New CMS pages are now added as expected to a website's store page hierarchy.
@@ -662,7 +664,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Magento now displays a product’s special price as expected when you select a discounted option of a configurable product. Previously, `class="normal-price"` was not changed to `class="special-price"` when a discounted option was selected. _Fix submitted by Ravi Chandra in pull request [26170](https://github.com/magento/magento2/pull/26170)_. [GitHub-24972](https://github.com/magento/magento2/issues/24972)
+* Magento now displays a product's special price as expected when you select a discounted option of a configurable product. Previously, `class="normal-price"` was not changed to `class="special-price"` when a discounted option was selected. _Fix submitted by Ravi Chandra in pull request [26170](https://github.com/magento/magento2/pull/26170)_. [GitHub-24972](https://github.com/magento/magento2/issues/24972)
### Cookies
@@ -724,7 +726,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Magento now displays only the products that the customer has placed in their cart when the cart is viewed from the Admin. Previously, a customer’s shopping cart displayed all the products in the catalog when viewed from the Admin. _Fix submitted by Ravinder in pull request [26489](https://github.com/magento/magento2/pull/26489)_. [GitHub-26437](https://github.com/magento/magento2/issues/26437)
+* Magento now displays only the products that the customer has placed in their cart when the cart is viewed from the Admin. Previously, a customer's shopping cart displayed all the products in the catalog when viewed from the Admin. _Fix submitted by Ravinder in pull request [26489](https://github.com/magento/magento2/pull/26489)_. [GitHub-26437](https://github.com/magento/magento2/issues/26437)
@@ -792,7 +794,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Magento now displays only the products that the customer has placed in their cart when the cart is viewed from the Admin. Previously, a customer’s shopping cart displayed all the products in the catalog when viewed from the Admin. _Fix submitted by Ravinder in pull request [26489](https://github.com/magento/magento2/pull/26489)_. [GitHub-26437](https://github.com/magento/magento2/issues/26437)
+* Magento now displays only the products that the customer has placed in their cart when the cart is viewed from the Admin. Previously, a customer's shopping cart displayed all the products in the catalog when viewed from the Admin. _Fix submitted by Ravinder in pull request [26489](https://github.com/magento/magento2/pull/26489)_. [GitHub-26437](https://github.com/magento/magento2/issues/26437)
@@ -844,7 +846,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
### Frameworks
-* Dependencies on Zend Framework have been migrated to the [Laminas project](https://getlaminas.org/about/foundation) to reflect the transitioning of Zend Framework to the Linux Foundation’s Laminas Project. Zend Framework has been deprecated. _Fix submitted by Ihor Sviziev in pull request [26436](https://github.com/magento/magento2/pull/26436)_. [GitHub-26335](https://github.com/magento/magento2/issues/26335)
+* Dependencies on Zend Framework have been migrated to the [Laminas project](https://getlaminas.org/about/foundation) to reflect the transitioning of Zend Framework to the Linux Foundation's Laminas Project. Zend Framework has been deprecated. _Fix submitted by Ihor Sviziev in pull request [26436](https://github.com/magento/magento2/pull/26436)_. [GitHub-26335](https://github.com/magento/magento2/issues/26335)
@@ -860,7 +862,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* The Update Attribute action now correctly updates the timestamp of a product’s `updated_at column` from `catalog_product_entity` when you update the product from the Admin edit product page.
+* The Update Attribute action now correctly updates the timestamp of a product's `updated_at column` from `catalog_product_entity` when you update the product from the Admin edit product page.
@@ -872,7 +874,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* We’ve improved the performance of the `Magento\Framework\App\DeploymentConfig\Reader::load` function. Previously, when a request was made to Magento, this function was called repetitively, which resulted in `config.php` and `env.php config` files being loaded each time the method was called.
+* We've improved the performance of the `Magento\Framework\App\DeploymentConfig\Reader::load` function. Previously, when a request was made to Magento, this function was called repetitively, which resulted in `config.php` and `env.php config` files being loaded each time the method was called.
@@ -880,7 +882,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Non-cacheable blocks added to the default layout in reference instructions for non-existent (undeclared) components on the page no longer affect page caching. Adding non-cacheable blocks to default layout handlers renders all Magento pages non-cacheable. This results from the layout generation process: During layout generation, Magento collects all available layout handles for a particular page and merges instructions from them into the page’s final layout structure. The default layout handle is used as a basic handle for every page. As a result, layout updates that are declared for the default handler appear on every Magento page. [GitHub-9041](https://github.com/magento/magento2/issues/9041)
+* Non-cacheable blocks added to the default layout in reference instructions for non-existent (undeclared) components on the page no longer affect page caching. Adding non-cacheable blocks to default layout handlers renders all Magento pages non-cacheable. This results from the layout generation process: During layout generation, Magento collects all available layout handles for a particular page and merges instructions from them into the page's final layout structure. The default layout handle is used as a basic handle for every page. As a result, layout updates that are declared for the default handler appear on every Magento page. [GitHub-9041](https://github.com/magento/magento2/issues/9041)
@@ -926,7 +928,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* A store’s Admin URL no longer redirects to the storefront URL when these two URLs differ.
+* A store's Admin URL no longer redirects to the storefront URL when these two URLs differ.
@@ -1018,7 +1020,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Magento now implements PHP7.x’s [throwable interface](https://www.php.net/manual/en/class.throwable.php) to enable the catching of all errors that might potentially expose sensitive information such as passwords. _Fix submitted by miszyman in pull request [25250](https://github.com/magento/magento2/pull/25250)_. [GitHub-23350](https://github.com/magento/magento2/issues/23350)
+* Magento now implements PHP7.x's [throwable interface](https://www.php.net/manual/en/class.throwable.php) to enable the catching of all errors that might potentially expose sensitive information such as passwords. _Fix submitted by miszyman in pull request [25250](https://github.com/magento/magento2/pull/25250)_. [GitHub-23350](https://github.com/magento/magento2/issues/23350)
@@ -1038,7 +1040,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* We’ve added the `@api` PHP annotation to `AbstractExtensibleModel`, the `@deprecated` PHP annotation to `AbstractExtensibleObject`, and `@see` to `AbstractExtensibleModel`. _Fix submitted by Alexander Taranovsky in pull request [22011](https://github.com/magento/magento2/pull/22011)_. [GitHub-22010](https://github.com/magento/magento2/issues/22010)
+* We've added the `@api` PHP annotation to `AbstractExtensibleModel`, the `@deprecated` PHP annotation to `AbstractExtensibleObject`, and `@see` to `AbstractExtensibleModel`. _Fix submitted by Alexander Taranovsky in pull request [22011](https://github.com/magento/magento2/pull/22011)_. [GitHub-22010](https://github.com/magento/magento2/issues/22010)
### GraphQL
@@ -1068,7 +1070,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* You can now add a child product of a grouped product to your cart when one of the grouped product’s other child products is out-of-stock. Previously, when one child product was out-of-stock, you could not add any other child products to the cart.
+* You can now add a child product of a grouped product to your cart when one of the grouped product's other child products is out-of-stock. Previously, when one child product was out-of-stock, you could not add any other child products to the cart.
### Images
@@ -1082,7 +1084,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* You can now successfully save an image to a category from the Admin. Previously, after you saved the image, part of the URL was missing, and you couldn’t re-open the image.
+* You can now successfully save an image to a category from the Admin. Previously, after you saved the image, part of the URL was missing, and you couldn't re-open the image.
@@ -1120,7 +1122,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Customizable options are now imported as expected when `row_id` is not equal to a product's `entity_id`. Previously, Magento did not import customizable options when `row_id` was not equal to a product’s `entity_id`, which resulted in certain products not being imported.
+* Customizable options are now imported as expected when `row_id` is not equal to a product's `entity_id`. Previously, Magento did not import customizable options when `row_id` was not equal to a product's `entity_id`, which resulted in certain products not being imported.
@@ -1140,7 +1142,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Magento now successfully imports all custom options for a configurable product’s child products when `store_view_code` is specified. This works whether you choose to import configurable products individually or collectively. Previously, Magento did not successfully import all custom options when the import file contained more than one item and `store_view_code` was specified.
+* Magento now successfully imports all custom options for a configurable product's child products when `store_view_code` is specified. This works whether you choose to import configurable products individually or collectively. Previously, Magento did not successfully import all custom options when the import file contained more than one item and `store_view_code` was specified.
@@ -1270,7 +1272,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Clicking **Enter** after naming a new folder in the Media Gallery now saves all changes you’ve made. Previously, clicking **Enter** instead of using the mouse to select **OK** resulted in all changes being lost. _Fix submitted by Sergiy Vasiutynskyi in pull request [27029](https://github.com/magento/magento2/pull/27029)_. [GitHub-26847](https://github.com/magento/magento2/issues/26847)
+* Clicking **Enter** after naming a new folder in the Media Gallery now saves all changes you've made. Previously, clicking **Enter** instead of using the mouse to select **OK** resulted in all changes being lost. _Fix submitted by Sergiy Vasiutynskyi in pull request [27029](https://github.com/magento/magento2/pull/27029)_. [GitHub-26847](https://github.com/magento/magento2/issues/26847)
@@ -1314,7 +1316,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* You can now successfully complete an order and return to the merchant’s home page when **Website Payments Pro Hosted Solution** is configured. Previously, when you clicked **Return to merchant**, Magento threw this error: `Invalid Form Key. Please refresh the page`.
+* You can now successfully complete an order and return to the merchant's home page when **Website Payments Pro Hosted Solution** is configured. Previously, when you clicked **Return to merchant**, Magento threw this error: `Invalid Form Key. Please refresh the page`.
@@ -1326,7 +1328,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* You can now remove additional information from the `quote_payment column additional_information` table after you’ve saved a quote. Previously, you could not remove this information after saving the quote because the `unsAdditionalInformation` method in `\Magento\Payment\Model\Info` did not initialize data properly. _Fix submitted by Marco Oliveira in pull request [26084](https://github.com/magento/magento2/pull/26084)_. [GitHub-26083](https://github.com/magento/magento2/issues/26083)
+* You can now remove additional information from the `quote_payment column additional_information` table after you've saved a quote. Previously, you could not remove this information after saving the quote because the `unsAdditionalInformation` method in `\Magento\Payment\Model\Info` did not initialize data properly. _Fix submitted by Marco Oliveira in pull request [26084](https://github.com/magento/magento2/pull/26084)_. [GitHub-26083](https://github.com/magento/magento2/issues/26083)
@@ -1344,7 +1346,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Magento no longer changes an order’s status to `Processing` in the Payment Review section of the checkout workflow when a payment with PayPal fails.
+* Magento no longer changes an order's status to `Processing` in the Payment Review section of the checkout workflow when a payment with PayPal fails.
@@ -1368,11 +1370,11 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Magento now successfully processes orders placed with PayPal Express Checkout where the order’s shipping address specifies a country region that the customer has manually entered into the text field rather than selected from the drop-down menu on the Shipping page. Previously, Magento displayed this error on the order review page: `Error 500: NOTICE: PHP message: PHP Fatal error: Uncaught Error: Call to a member function getId() on null in httpdocs/vendor/magento/module-paypal/Model/Api/Nvp.php:1527`. [GitHub-26698](https://github.com/magento/magento2/issues/26698)
+* Magento now successfully processes orders placed with PayPal Express Checkout where the order's shipping address specifies a country region that the customer has manually entered into the text field rather than selected from the drop-down menu on the Shipping page. Previously, Magento displayed this error on the order review page: `Error 500: NOTICE: PHP message: PHP Fatal error: Uncaught Error: Call to a member function getId() on null in httpdocs/vendor/magento/module-paypal/Model/Api/Nvp.php:1527`. [GitHub-26698](https://github.com/magento/magento2/issues/26698)
-* The PayPal Pro payment method now works as expected in the Chrome 80 browser. This payment method previously invoked a Magento callback endpoint that needed access to the customer’s session — access that the new default Chrome SameSite cookie functionality does not permit. [GitHub-26840](https://github.com/magento/magento2/issues/26840)
+* The PayPal Pro payment method now works as expected in the Chrome 80 browser. This payment method previously invoked a Magento callback endpoint that needed access to the customer's session — access that the new default Chrome SameSite cookie functionality does not permit. [GitHub-26840](https://github.com/magento/magento2/issues/26840)
@@ -1408,11 +1410,11 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Magento now saves and displays the correct price for tiered products even after you’ve edited products multiple times. Previously, Magento did not save the last edits made to product price. _Fix submitted by Ravi Chandra in pull request [26162](https://github.com/magento/magento2/pull/26162)_. [GitHub-25195](https://github.com/magento/magento2/issues/25195)
+* Magento now saves and displays the correct price for tiered products even after you've edited products multiple times. Previously, Magento did not save the last edits made to product price. _Fix submitted by Ravi Chandra in pull request [26162](https://github.com/magento/magento2/pull/26162)_. [GitHub-25195](https://github.com/magento/magento2/issues/25195)
-* Both fixed and discount save percentage are now correctly applied on an order’s final price. Previously, Magento displayed an incorrect tier price (both fixed & discount) save percentage on the product detail page. _Fix submitted by Sathish Subramanian in pull request [26584](https://github.com/magento/magento2/pull/26584)_. [GitHub-26583](https://github.com/magento/magento2/issues/26583)
+* Both fixed and discount save percentage are now correctly applied on an order's final price. Previously, Magento displayed an incorrect tier price (both fixed & discount) save percentage on the product detail page. _Fix submitted by Sathish Subramanian in pull request [26584](https://github.com/magento/magento2/pull/26584)_. [GitHub-26583](https://github.com/magento/magento2/issues/26583)
@@ -1420,7 +1422,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Product stock alert unsubscribe now works when a user’s session has expired. Previously, when you clicked on the **Click here to stop alerts for this product** link, Magento displayed a 404 error.
+* Product stock alert unsubscribe now works when a user's session has expired. Previously, when you clicked on the **Click here to stop alerts for this product** link, Magento displayed a 404 error.
@@ -1472,7 +1474,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Magento now honors a customer’s default shipping address. Previously, Magento did not honor the default billing and default shipping addresses according to the settings, and the **Same As Billing Address** setting was not enabled automatically.
+* Magento now honors a customer's default shipping address. Previously, Magento did not honor the default billing and default shipping addresses according to the settings, and the **Same As Billing Address** setting was not enabled automatically.
@@ -1492,7 +1494,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* You can now successfully add a product to the cart from the Admin when the stock quantity is 1. Previously, Magento didn’t add the product to the cart and displayed this message: `The requested qty is not available`. _Fix submitted by Serhii Petrychenko in pull request [26650](https://github.com/magento/magento2/pull/26650)._ [GitHub-25675](https://github.com/magento/magento2/issues/25675)
+* You can now successfully add a product to the cart from the Admin when the stock quantity is 1. Previously, Magento didn't add the product to the cart and displayed this message: `The requested qty is not available`. _Fix submitted by Serhii Petrychenko in pull request [26650](https://github.com/magento/magento2/pull/26650)._ [GitHub-25675](https://github.com/magento/magento2/issues/25675)
@@ -1790,7 +1792,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* We’ve resolved a bug in `JsFooterPlugin.php` that affected the display of dynamic blocks. Previously, Magento displayed this error when you directly accessed `/banner/ajax/load/url`: `Uncaught TypeError: strpos() expects parameter 1 to be string, null given in`.
+* We've resolved a bug in `JsFooterPlugin.php` that affected the display of dynamic blocks. Previously, Magento displayed this error when you directly accessed `/banner/ajax/load/url`: `Uncaught TypeError: strpos() expects parameter 1 to be string, null given in`.
@@ -1922,7 +1924,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* You can now update the value of a downloadable product’s sample and link title by enabling the **Use default** checkbox. _Fix submitted by Abel Truong in pull request [27295](https://github.com/magento/magento2/pull/27295)_. [GitHub-27169](https://github.com/magento/magento2/issues/27169)
+* You can now update the value of a downloadable product's sample and link title by enabling the **Use default** checkbox. _Fix submitted by Abel Truong in pull request [27295](https://github.com/magento/magento2/pull/27295)_. [GitHub-27169](https://github.com/magento/magento2/issues/27169)
@@ -1950,15 +1952,15 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* Customers who change language on a CMS page can now successfully navigate to the store view they’ve selected. Previously, Magento displayed a 404 error.
+* Customers who change language on a CMS page can now successfully navigate to the store view they've selected. Previously, Magento displayed a 404 error.
-* URL rewrite generation for product URLs for which you’ve enabled category path inclusion now works as expected. Previously, in deployments with multiple store views, Magento sometimes generated incorrect URL rewrites by using the default value of the category url path instead of the storeview-specific URL path. _Fix submitted by Pieter Hoste in pull request [26784](https://github.com/magento/magento2/pull/26784)_. [GitHub-25124](https://github.com/magento/magento2/issues/25124), [GitHub-11616](https://github.com/magento/magento2/issues/11616)
+* URL rewrite generation for product URLs for which you've enabled category path inclusion now works as expected. Previously, in deployments with multiple store views, Magento sometimes generated incorrect URL rewrites by using the default value of the category url path instead of the storeview-specific URL path. _Fix submitted by Pieter Hoste in pull request [26784](https://github.com/magento/magento2/pull/26784)_. [GitHub-25124](https://github.com/magento/magento2/issues/25124), [GitHub-11616](https://github.com/magento/magento2/issues/11616)
-* We’ve added a check to prevent URL redirects if the request path is the same as the target path. _Fix submitted by Bartomiej Szubert in pull request [26902](https://github.com/magento/magento2/pull/26902)_. [GitHub-20309](https://github.com/magento/magento2/issues/20309)
+* We've added a check to prevent URL redirects if the request path is the same as the target path. _Fix submitted by Bartomiej Szubert in pull request [26902](https://github.com/magento/magento2/pull/26902)_. [GitHub-20309](https://github.com/magento/magento2/issues/20309)
@@ -2016,7 +2018,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
-* We’ve improved the error message that is displayed when a customer tries to share their wishlist with more email addresses than is permitted. _Fix submitted by divyajyothi5321 in pull request [26066](https://github.com/magento/magento2/pull/26066)_. [GitHub-26064](https://github.com/magento/magento2/issues/26064)
+* We've improved the error message that is displayed when a customer tries to share their wishlist with more email addresses than is permitted. _Fix submitted by divyajyothi5321 in pull request [26066](https://github.com/magento/magento2/pull/26066)_. [GitHub-26064](https://github.com/magento/magento2/issues/26064)
@@ -2050,11 +2052,11 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
**Issue**: The **Add selections to my cart** button on the bottom of the shopping cart does not work. **Workaround**: Use the **Add selections to my cart** button on the top of the page. See [Add selections to my cart button does not work](https://support.magento.com/hc/en-us/articles/360045838312) Knowledge Base article.
-**Issue**: Merchants can’t create a new order from the Admin because the **Add Products By SKU** and **Add Products** buttons are missing from the order creation page when JavaScript bundling is enabled. **Workaround**: Disable the JavaScript bundling for your Magento deployment.
+**Issue**: Merchants can't create a new order from the Admin because the **Add Products By SKU** and **Add Products** buttons are missing from the order creation page when JavaScript bundling is enabled. **Workaround**: Disable the JavaScript bundling for your Magento deployment.
**Issue**: Magento throws a `404 not found` error when a customer tries to remove reward points when checking out an order being shipped to multiple addresses.
-**Issue**: Editing a configurable product from a customer’s wishlist results in the following unexpected behavior: An unexpected field appears on the Configure Product page, and the Configure Product page does not disappear after you click **OK**. Magento also displays this message: `Please load Wish List item`. **Workaround**: Reload the Configure Product page.
+**Issue**: Editing a configurable product from a customer's wishlist results in the following unexpected behavior: An unexpected field appears on the Configure Product page, and the Configure Product page does not disappear after you click **OK**. Magento also displays this message: `Please load Wish List item`. **Workaround**: Reload the Configure Product page.
**Issue**: Customers cannot change the number of orders displayed per page when the Orders list spans multiple pages. Currently, Magento displays this message when you navigate to the last page of orders and try to change the number of orders displayed per page: `You have placed no orders`. See [Orders display error](https://support.magento.com/hc/en-us/articles/360046802271) Knowledge Base article. **Workaround**: Re-opening the My Orders page will result in the display of the Orders list.
@@ -2074,7 +2076,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
* **Issue**: Magento displays an error when an administrator tries to access the Braintree Settlement Report page (**Admin** > **Reports** ). Currently, Magento displays this message: `An error has happened during application run. See exception log for details`. See [Braintree Settlement Report fails to load](https://support.magento.com/hc/en-us/articles/360046798251) Knowledge Base article. The **BUNDLE-2683_SettlementReport.patch** hotfix for this issue is now available from [Releases](https://magento.com/tech-resources/download).
-* **Issue**: Merchants can’t create partial invoices for orders in deployments where Venmo is enabled and the **Enable Vault for Card Payments** setting is disabled. Currently, Magento displays this error: `The "vault_capture" command doesn't exist. Verify the command and try again`.
+* **Issue**: Merchants can't create partial invoices for orders in deployments where Venmo is enabled and the **Enable Vault for Card Payments** setting is disabled. Currently, Magento displays this error: `The "vault_capture" command doesn't exist. Verify the command and try again`.
* **Issue**: Magento displays two identical PayPal methods in the Payment Method drop-down list that is available when creating a new cart price rule.
@@ -2088,7 +2090,7 @@ We have fixed hundreds of issues in the Magento 2.4.0 core code.
### Vertex
-* **Issue**: Magento displays an **Address verification** button on the shipping section of the checkout workflow even when address validation is disabled. The address validator doesn’t re-check the updated address and continues to display a message that indicates that the address is invalid when a customer enters a correct address after first entering an incorrect address even when address validation is enabled. **Workaround**: Disable Vertex address validation.
+* **Issue**: Magento displays an **Address verification** button on the shipping section of the checkout workflow even when address validation is disabled. The address validator doesn't re-check the updated address and continues to display a message that indicates that the address is invalid when a customer enters a correct address after first entering an incorrect address even when address validation is enabled. **Workaround**: Disable Vertex address validation.
## Community contributions
diff --git a/src/guides/v2.4/rest/anonymous-api-security.md b/src/guides/v2.4/rest/anonymous-api-security.md
index ea0e85a75ca..8d7544886ce 100644
--- a/src/guides/v2.4/rest/anonymous-api-security.md
+++ b/src/guides/v2.4/rest/anonymous-api-security.md
@@ -1,8 +1,8 @@
---
group: rest-api
title: Restricting access to anonymous web APIs
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/use-rest/anonymous-api-security/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/use-rest/anonymous-api-security/
+status: migrated
---
Magento 2 allows some web APIs to be accessed by unauthenticated (anonymous) users. Many of these APIs allow a customer to have a robust shopping experience on the [website](https://glossary.magento.com/website) without having to log in.
diff --git a/src/guides/v2.4/rest/asynchronous-web-endpoints.md b/src/guides/v2.4/rest/asynchronous-web-endpoints.md
index 06f9a8c2973..6c298007ed1 100644
--- a/src/guides/v2.4/rest/asynchronous-web-endpoints.md
+++ b/src/guides/v2.4/rest/asynchronous-web-endpoints.md
@@ -5,8 +5,8 @@ contributor_name: comwrap GmbH
contributor_link: https://www.comwrap.com/en.html
functional_areas:
- Integration
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/use-rest/asynchronous-web-endpoints/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/use-rest/asynchronous-web-endpoints/
+status: migrated
---
An asynchronous web endpoint intercepts messages to a Web API and writes them to the message queue. Each time the system accepts such an API request, it generates a UUID identifier. Magento includes this UUID when it adds the message to the queue. Then, a consumer reads the messages from the queue and executes them one-by-one.
diff --git a/src/guides/v2.4/rest/bk-rest.md b/src/guides/v2.4/rest/bk-rest.md
index 0334dc1896d..2cb75a7b91c 100644
--- a/src/guides/v2.4/rest/bk-rest.md
+++ b/src/guides/v2.4/rest/bk-rest.md
@@ -1,8 +1,8 @@
---
group: rest-api
title: REST API Overview
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/
+status: migrated
functional_areas:
- Integration
---
@@ -17,7 +17,7 @@ You can also create a dynamic REST API documentation set on your server with liv
Magento uses [Swagger][] to display REST APIs for all installed products and allows you to try out the APIs.
For more information, see [Generate local REST API reference](generate-local.html).
-[REST API documentation]: https://magento.redoc.ly
+[REST API documentation]: https://developer.adobe.com/commerce/webapi/rest/quick-reference/
[ReDoc]: https://github.com/Rebilly/ReDoc
[Open-API specification]: https://github.com/OAI/OpenAPI-Specification
[Swagger]: https://swagger.io/
diff --git a/src/guides/v2.4/rest/bulk-endpoints.md b/src/guides/v2.4/rest/bulk-endpoints.md
index 414e2af0b6c..2b7c83926d9 100644
--- a/src/guides/v2.4/rest/bulk-endpoints.md
+++ b/src/guides/v2.4/rest/bulk-endpoints.md
@@ -5,8 +5,8 @@ contributor_name: comwrap GmbH
contributor_link: https://www.comwrap.com/en.html
functional_areas:
- Integration
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/use-rest/bulk-endpoints/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/use-rest/bulk-endpoints/
+status: migrated
---
Bulk API endpoints differ from other REST endpoints in that they combine multiple calls of the same type into an array and execute them as a single request. The endpoint handler splits the array into individual entities and writes them as separate messages to the message queue.
diff --git a/src/guides/v2.4/rest/generate-local.md b/src/guides/v2.4/rest/generate-local.md
index 47b3741663a..a6b2abffe10 100644
--- a/src/guides/v2.4/rest/generate-local.md
+++ b/src/guides/v2.4/rest/generate-local.md
@@ -1,8 +1,8 @@
---
group: rest-api
title: Generate a local REST reference
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/quick-reference/generate-local/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/quick-reference/generate-local/
+status: migrated
functional_areas:
- Integration
---
diff --git a/src/guides/v2.4/rest/modules/catalog-pricing.md b/src/guides/v2.4/rest/modules/catalog-pricing.md
index c0218404205..b8639d79aec 100644
--- a/src/guides/v2.4/rest/modules/catalog-pricing.md
+++ b/src/guides/v2.4/rest/modules/catalog-pricing.md
@@ -1,8 +1,8 @@
---
group: rest-api
title: Manage prices for multiple products
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/modules/catalog/catalog-pricing/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/modules/catalog/catalog-pricing/
+status: migrated
functional_areas:
- Integration
---
diff --git a/src/guides/v2.4/rest/modules/catalog.md b/src/guides/v2.4/rest/modules/catalog.md
index 8f1d787d324..426aeeeae77 100644
--- a/src/guides/v2.4/rest/modules/catalog.md
+++ b/src/guides/v2.4/rest/modules/catalog.md
@@ -1,8 +1,8 @@
---
group: rest-api
title: Catalog module
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/modules/catalog/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/modules/catalog/
+status: migrated
functional_areas:
- Integration
- Catalog
diff --git a/src/guides/v2.4/rest/modules/inventory/bulk-inventory.md b/src/guides/v2.4/rest/modules/inventory/bulk-inventory.md
index 52c877e2025..5dda42e4449 100644
--- a/src/guides/v2.4/rest/modules/inventory/bulk-inventory.md
+++ b/src/guides/v2.4/rest/modules/inventory/bulk-inventory.md
@@ -1,8 +1,8 @@
---
group: rest-api
title: Inventory mass actions
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/inventory/bulk-inventory/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/inventory/bulk-inventory/
+status: migrated
---
Magento provides several endpoints that allow Multi Source merchants to make quick updates across multiple products. This is helpful for transferring inventory between sources and removing a source without editing each product individually.
diff --git a/src/guides/v2.4/rest/modules/inventory/check-salable-quantity.md b/src/guides/v2.4/rest/modules/inventory/check-salable-quantity.md
index 949f4f71fbf..b41dd21e764 100644
--- a/src/guides/v2.4/rest/modules/inventory/check-salable-quantity.md
+++ b/src/guides/v2.4/rest/modules/inventory/check-salable-quantity.md
@@ -1,8 +1,8 @@
---
group: rest-api
title: Check salable quantities
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/inventory/check-salable-quantity/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/inventory/check-salable-quantity/
+status: migrated
---
Magento provides several endpoints that allow you to check whether a product from a specified stock is salable and the available quantity.
diff --git a/src/guides/v2.4/rest/modules/inventory/in-store-pickup.md b/src/guides/v2.4/rest/modules/inventory/in-store-pickup.md
index 37c3e35f0e4..c5199d4a398 100644
--- a/src/guides/v2.4/rest/modules/inventory/in-store-pickup.md
+++ b/src/guides/v2.4/rest/modules/inventory/in-store-pickup.md
@@ -1,8 +1,8 @@
---
group: rest-api
title: In-Store Pickup
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/inventory/in-store-pickup/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/inventory/in-store-pickup/
+status: migrated
contributor_name: Oleksandr Kravchuk
contributor_link: https://github.com/swnsma
---
diff --git a/src/guides/v2.4/rest/modules/inventory/link-stocks-sources.md b/src/guides/v2.4/rest/modules/inventory/link-stocks-sources.md
index 38893b1112c..b3e5494d892 100644
--- a/src/guides/v2.4/rest/modules/inventory/link-stocks-sources.md
+++ b/src/guides/v2.4/rest/modules/inventory/link-stocks-sources.md
@@ -1,8 +1,8 @@
---
group: rest-api
title: Link and unlink stocks and sources
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/inventory/link-stocks-sources/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/inventory/link-stocks-sources/
+status: migrated
---
In Admin, you can assign (link) sources to a stock when you create the stock. In REST, creating a stock and assigning sources to it are separate steps.
diff --git a/src/guides/v2.4/rest/modules/inventory/manage-low-quantity.md b/src/guides/v2.4/rest/modules/inventory/manage-low-quantity.md
index b47cdb59094..58cfcbc7a7a 100644
--- a/src/guides/v2.4/rest/modules/inventory/manage-low-quantity.md
+++ b/src/guides/v2.4/rest/modules/inventory/manage-low-quantity.md
@@ -1,8 +1,8 @@
---
group: rest-api
title: Manage low-quantity notifications
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/inventory/manage-low-quantity/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/inventory/manage-low-quantity/
+status: migrated
---
Low stock notification alert the merchant that the salable quantity of a stock has reached a critical threshold. The Admin allows the merchant to configure low-quantity notifications from several locations:
diff --git a/src/guides/v2.4/rest/modules/inventory/manage-source-items.md b/src/guides/v2.4/rest/modules/inventory/manage-source-items.md
index 9245e211933..5bba2ec38a2 100644
--- a/src/guides/v2.4/rest/modules/inventory/manage-source-items.md
+++ b/src/guides/v2.4/rest/modules/inventory/manage-source-items.md
@@ -1,8 +1,8 @@
---
group: rest-api
title: Manage source items
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/inventory/manage-source-items/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/inventory/manage-source-items/
+status: migrated
---
If Magento is configured to manage inventory, Magento assigns all existing products to the default source. Currently, Magento also assigns newly-created products to the default source. Single Source merchants do not need to manage source items, but Multi Source merchants may need to move products from the default source to a custom source, or move products from one custom source to another.
diff --git a/src/guides/v2.4/rest/modules/inventory/manage-source-selection.md b/src/guides/v2.4/rest/modules/inventory/manage-source-selection.md
index d70b45a87ef..3ee64e19a3d 100644
--- a/src/guides/v2.4/rest/modules/inventory/manage-source-selection.md
+++ b/src/guides/v2.4/rest/modules/inventory/manage-source-selection.md
@@ -1,8 +1,8 @@
---
group: rest-api
title: Manage source selection algorithms
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/inventory/manage-source-selection/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/inventory/manage-source-selection/
+status: migrated
---
Inventory Management uses the Source Selection Algorithm (SSA) to track the salable quantities of product inventory across all sources and make recommendations for partial and full shipments.
diff --git a/src/guides/v2.4/rest/modules/inventory/manage-sources.md b/src/guides/v2.4/rest/modules/inventory/manage-sources.md
index 22fcc913f4d..838a7d2ccec 100644
--- a/src/guides/v2.4/rest/modules/inventory/manage-sources.md
+++ b/src/guides/v2.4/rest/modules/inventory/manage-sources.md
@@ -1,8 +1,8 @@
---
group: rest-api
title: Manage sources
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/inventory/manage-sources/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/inventory/manage-sources/
+status: migrated
---
Sources represent locations storing and shipping available product stock. Any location with available stock and capable of order fulfillment can be added as a source. These locations can include warehouses, brick-and-mortar stores, distribution centers, and drop shippers.
diff --git a/src/guides/v2.4/rest/modules/inventory/manage-stocks.md b/src/guides/v2.4/rest/modules/inventory/manage-stocks.md
index 4c67001e04a..ee60364de95 100644
--- a/src/guides/v2.4/rest/modules/inventory/manage-stocks.md
+++ b/src/guides/v2.4/rest/modules/inventory/manage-stocks.md
@@ -1,8 +1,8 @@
---
group: rest-api
title: Manage stocks
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/inventory/manage-stocks/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/inventory/manage-stocks/
+status: migrated
---
Stocks map your sources to sales channels, providing a direct link to salable quantities and inventories.
diff --git a/src/guides/v2.4/rest/modules/sales/refunds.md b/src/guides/v2.4/rest/modules/sales/refunds.md
index 6e9c61b8f8a..ec82f3c850b 100644
--- a/src/guides/v2.4/rest/modules/sales/refunds.md
+++ b/src/guides/v2.4/rest/modules/sales/refunds.md
@@ -1,8 +1,8 @@
---
group: rest-api
title: Refunds
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/modules/sales/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/modules/sales/
+status: migrated
functional_areas:
- Integration
diff --git a/src/guides/v2.4/rest/notes.md b/src/guides/v2.4/rest/notes.md
index 9c7f50fdbf3..dc80a07f42f 100644
--- a/src/guides/v2.4/rest/notes.md
+++ b/src/guides/v2.4/rest/notes.md
@@ -1,8 +1,8 @@
---
group: rest-api
title: REST usage notes
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/use-rest/notes/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/use-rest/notes/
+status: migrated
functional_areas:
- Integration
---
diff --git a/src/guides/v2.4/rest/operation-status-endpoints.md b/src/guides/v2.4/rest/operation-status-endpoints.md
index b058f6077a4..86a6849f2b5 100644
--- a/src/guides/v2.4/rest/operation-status-endpoints.md
+++ b/src/guides/v2.4/rest/operation-status-endpoints.md
@@ -1,8 +1,8 @@
---
group: rest-api
title: Bulk operation status endpoints
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/use-rest/operation-status-endpoints/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/use-rest/operation-status-endpoints/
+status: migrated
contributor_name: comwrap GmbH
contributor_link: https://www.comwrap.com/
functional_areas:
diff --git a/src/guides/v2.4/rest/operation-status-search.md b/src/guides/v2.4/rest/operation-status-search.md
index 6dda8f84599..9973092db00 100644
--- a/src/guides/v2.4/rest/operation-status-search.md
+++ b/src/guides/v2.4/rest/operation-status-search.md
@@ -1,8 +1,8 @@
---
group: rest-api
title: Search for the status of a bulk operation
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/use-rest/operation-status-search
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/use-rest/operation-status-search
+status: migrated
contributor_name: comwrap GmbH
contributor_link: https://www.comwrap.com
functional_areas:
diff --git a/src/guides/v2.4/rest/performing-searches.md b/src/guides/v2.4/rest/performing-searches.md
index 70f6bddaa75..03684d0b253 100644
--- a/src/guides/v2.4/rest/performing-searches.md
+++ b/src/guides/v2.4/rest/performing-searches.md
@@ -1,8 +1,8 @@
---
group: rest-api
title: Search using REST endpoints
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/use-rest/performing-searches/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/use-rest/performing-searches/
+status: migrated
---
POST, PUT, and DELETE requests to the REST Web [API](https://glossary.magento.com/api) require the service method parameters to be in the body of the request. For example, to create a Customer, you would specify a JSON array (or [XML](https://glossary.magento.com/xml) structure) in the body of the message.
diff --git a/src/guides/v2.4/rest/protected-endpoints.md b/src/guides/v2.4/rest/protected-endpoints.md
index f38924afcab..fa0fc646892 100644
--- a/src/guides/v2.4/rest/protected-endpoints.md
+++ b/src/guides/v2.4/rest/protected-endpoints.md
@@ -1,8 +1,8 @@
---
group: rest-api
title: Protected endpoints
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/use-rest/protected-endpoints/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/use-rest/protected-endpoints/
+status: migrated
functional_areas:
- Integration
---
diff --git a/src/guides/v2.4/rest/retrieve-filtered-responses.md b/src/guides/v2.4/rest/retrieve-filtered-responses.md
index 3fea1a41ba9..80ec0a36e72 100644
--- a/src/guides/v2.4/rest/retrieve-filtered-responses.md
+++ b/src/guides/v2.4/rest/retrieve-filtered-responses.md
@@ -1,8 +1,8 @@
---
group: rest-api
title: Retrieve filtered responses for REST endpoints
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/use-rest/retrieve-filtered-responses/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/use-rest/retrieve-filtered-responses/
+status: migrated
---
Some REST calls return dozens or even hundreds of parameters, and parsing through all this data can be unwieldy. In addition, mobile app developers might find the bandwidth needed to process a request to be excessive. To resolve these problems, Magento provides a query parameter-based syntax for REST requests that return partial responses.
diff --git a/src/guides/v2.4/rest/search-endpoint.md b/src/guides/v2.4/rest/search-endpoint.md
index 41215d166ab..c409ec9df7e 100644
--- a/src/guides/v2.4/rest/search-endpoint.md
+++ b/src/guides/v2.4/rest/search-endpoint.md
@@ -1,8 +1,8 @@
---
group: rest-api
title: Search for products with the /search endpoint
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/use-rest/search-endpoint/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/use-rest/search-endpoint/
+status: migrated
contributor_name: comwrap GmbH
contributor_link: https://www.comwrap.com/
---
diff --git a/src/guides/v2.4/rest/tutorials/bulk-configurable-product/config-product-intro.md b/src/guides/v2.4/rest/tutorials/bulk-configurable-product/config-product-intro.md
index 503008aad6f..db09fce65fd 100644
--- a/src/guides/v2.4/rest/tutorials/bulk-configurable-product/config-product-intro.md
+++ b/src/guides/v2.4/rest/tutorials/bulk-configurable-product/config-product-intro.md
@@ -12,8 +12,8 @@ functional_areas:
- Integration
contributor_name: comwrap GmbH
contributor_link: https://www.comwrap.com/en.html
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/bulk-configurable-product/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/bulk-configurable-product/
+status: migrated
---
A system integrator can use Magento REST bulk APIs to perform actions on a large scale; such as, creating multiple customers and products, changing prices across an inventory, and assigning large groups of products to a specific warehouse, all within a single call.
diff --git a/src/guides/v2.4/rest/tutorials/bulk-configurable-product/create-configurable-simple-products.md b/src/guides/v2.4/rest/tutorials/bulk-configurable-product/create-configurable-simple-products.md
index 24b40ce8900..9d458482ac7 100644
--- a/src/guides/v2.4/rest/tutorials/bulk-configurable-product/create-configurable-simple-products.md
+++ b/src/guides/v2.4/rest/tutorials/bulk-configurable-product/create-configurable-simple-products.md
@@ -13,8 +13,8 @@ functional_areas:
- Integration
contributor_name: comwrap GmbH
contributor_link: https://www.comwrap.com/en.html
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/bulk-configurable-product/create-configurable-simple-products/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/bulk-configurable-product/create-configurable-simple-products/
+status: migrated
---
By providing configurable and simple product information, you can use the bulk API to create all necessary products with a single call.
diff --git a/src/guides/v2.4/rest/tutorials/bulk-configurable-product/create-personalization-option.md b/src/guides/v2.4/rest/tutorials/bulk-configurable-product/create-personalization-option.md
index a81ba03db37..3dfc3775c4e 100644
--- a/src/guides/v2.4/rest/tutorials/bulk-configurable-product/create-personalization-option.md
+++ b/src/guides/v2.4/rest/tutorials/bulk-configurable-product/create-personalization-option.md
@@ -13,8 +13,8 @@ functional_areas:
- Integration
contributor_name: comwrap GmbH
contributor_link: https://www.comwrap.com/en.html
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/bulk-configurable-product/create-personalization-option/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/bulk-configurable-product/create-personalization-option/
+status: migrated
---
Let's add a text box to the product page that allows the customer to add his name (up to 15 characters) to the back of the shirt.
diff --git a/src/guides/v2.4/rest/tutorials/bulk-configurable-product/define-config-product-options.md b/src/guides/v2.4/rest/tutorials/bulk-configurable-product/define-config-product-options.md
index 94624ab75f8..8af07be7332 100644
--- a/src/guides/v2.4/rest/tutorials/bulk-configurable-product/define-config-product-options.md
+++ b/src/guides/v2.4/rest/tutorials/bulk-configurable-product/define-config-product-options.md
@@ -13,8 +13,8 @@ functional_areas:
- Integration
contributor_name: comwrap GmbH
contributor_link: https://www.comwrap.com/en.html
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/bulk-configurable-product/define-config-product-options/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/bulk-configurable-product/define-config-product-options/
+status: migrated
---
Now that we've created all the Champ Tee products, we need to assign `size` as the configurable attribute and link the simple products to the configurable product.
diff --git a/src/guides/v2.4/rest/tutorials/bulk-configurable-product/plan-product.md b/src/guides/v2.4/rest/tutorials/bulk-configurable-product/plan-product.md
index 0a5778a4076..51f20dff12c 100644
--- a/src/guides/v2.4/rest/tutorials/bulk-configurable-product/plan-product.md
+++ b/src/guides/v2.4/rest/tutorials/bulk-configurable-product/plan-product.md
@@ -13,8 +13,8 @@ functional_areas:
- Integration
contributor_name: comwrap GmbH
contributor_link: https://www.comwrap.com/en.html
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/bulk-configurable-product/plan-product/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/bulk-configurable-product/plan-product/
+status: migrated
---
To create a configurable product programmatically, you'll need to know the following:
diff --git a/src/guides/v2.4/rest/tutorials/bundle-product/bundle-product-intro.md b/src/guides/v2.4/rest/tutorials/bundle-product/bundle-product-intro.md
index 566634c6b78..ed6b3dab442 100644
--- a/src/guides/v2.4/rest/tutorials/bundle-product/bundle-product-intro.md
+++ b/src/guides/v2.4/rest/tutorials/bundle-product/bundle-product-intro.md
@@ -2,8 +2,8 @@
layout: tutorial
group: rest-api
title: Create a bundle product tutorial
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/bundle-product/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/bundle-product/
+status: migrated
contributor_name: Goivvy LLC
contributor_link: https://www.goivvy.com/magento-optimization-service
---
diff --git a/src/guides/v2.4/rest/tutorials/bundle-product/create-bundle-product.md b/src/guides/v2.4/rest/tutorials/bundle-product/create-bundle-product.md
index d9ab1f1dcaf..2fdf68fb0f0 100644
--- a/src/guides/v2.4/rest/tutorials/bundle-product/create-bundle-product.md
+++ b/src/guides/v2.4/rest/tutorials/bundle-product/create-bundle-product.md
@@ -2,8 +2,8 @@
layout: tutorial
group: rest-api
title: Step 3. Create the bundle product
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/bundle-product/create-bundle-product/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/bundle-product/create-bundle-product/
+status: migrated
contributor_name: Goivvy LLC
contributor_link: https://www.goivvy.com/magento-optimization-service
---
diff --git a/src/guides/v2.4/rest/tutorials/bundle-product/create-simple-products.md b/src/guides/v2.4/rest/tutorials/bundle-product/create-simple-products.md
index 47dfffa6b34..b6c8bff5ca6 100644
--- a/src/guides/v2.4/rest/tutorials/bundle-product/create-simple-products.md
+++ b/src/guides/v2.4/rest/tutorials/bundle-product/create-simple-products.md
@@ -2,8 +2,8 @@
layout: tutorial
group: rest-api
title: Step 2. Create the simple products
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/bundle-product/create-simple-products/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/bundle-product/create-simple-products/
+status: migrated
contributor_name: Goivvy LLC
contributor_link: https://www.goivvy.com/magento-optimization-service
---
diff --git a/src/guides/v2.4/rest/tutorials/bundle-product/plan-product.md b/src/guides/v2.4/rest/tutorials/bundle-product/plan-product.md
index cebb6d7faf8..d368cc01ac3 100644
--- a/src/guides/v2.4/rest/tutorials/bundle-product/plan-product.md
+++ b/src/guides/v2.4/rest/tutorials/bundle-product/plan-product.md
@@ -2,8 +2,8 @@
layout: tutorial
group: rest-api
title: Step 1. Plan the product
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/bundle-product/plan-product/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/bundle-product/plan-product/
+status: migrated
contributor_name: Goivvy LLC
contributor_link: https://www.goivvy.com/magento-optimization-service
---
diff --git a/src/guides/v2.4/rest/tutorials/configurable-product/config-product-intro.md b/src/guides/v2.4/rest/tutorials/configurable-product/config-product-intro.md
index 69e3d8a8516..ef7a79d3648 100644
--- a/src/guides/v2.4/rest/tutorials/configurable-product/config-product-intro.md
+++ b/src/guides/v2.4/rest/tutorials/configurable-product/config-product-intro.md
@@ -2,8 +2,8 @@
layout: tutorial
group: rest-api
title: Create a configurable product tutorial
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/configurable-product/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/configurable-product/
+status: migrated
menu_title: Initial tasks
menu_order: 0
level3_subgroup: configurable-product-tutorial
diff --git a/src/guides/v2.4/rest/tutorials/configurable-product/create-configurable-product.md b/src/guides/v2.4/rest/tutorials/configurable-product/create-configurable-product.md
index c692e234806..4d8fe31203e 100644
--- a/src/guides/v2.4/rest/tutorials/configurable-product/create-configurable-product.md
+++ b/src/guides/v2.4/rest/tutorials/configurable-product/create-configurable-product.md
@@ -2,8 +2,8 @@
layout: tutorial
group: rest-api
title: Step 2. Create the configurable product
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/configurable-product/create-configurable-product/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/configurable-product/create-configurable-product/
+status: migrated
subtitle: Create a configurable product tutorial
menu_title: Step 2. Create the configurable product
menu_order: 20
diff --git a/src/guides/v2.4/rest/tutorials/configurable-product/create-personalization-option.md b/src/guides/v2.4/rest/tutorials/configurable-product/create-personalization-option.md
index 27be40fe7d3..ce86e015031 100644
--- a/src/guides/v2.4/rest/tutorials/configurable-product/create-personalization-option.md
+++ b/src/guides/v2.4/rest/tutorials/configurable-product/create-personalization-option.md
@@ -2,8 +2,8 @@
layout: tutorial
group: rest-api
title: Step 5. Create the personalization option
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/configurable-product/create-personalization-option/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/configurable-product/create-personalization-option/
+status: migrated
subtitle: Create a configurable product tutorial
menu_title: Step 5. Create the personalization option
menu_order: 50
diff --git a/src/guides/v2.4/rest/tutorials/configurable-product/create-simple-products.md b/src/guides/v2.4/rest/tutorials/configurable-product/create-simple-products.md
index 20086fcdbaf..ae0b21fffb4 100644
--- a/src/guides/v2.4/rest/tutorials/configurable-product/create-simple-products.md
+++ b/src/guides/v2.4/rest/tutorials/configurable-product/create-simple-products.md
@@ -2,8 +2,8 @@
layout: tutorial
group: rest-api
title: Step 3. Create the simple products
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/configurable-product/create-simple-products/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/configurable-product/create-simple-products/
+status: migrated
subtitle: Create a configurable product tutorial
menu_title: Step 3. Create the simple products
menu_order: 30
diff --git a/src/guides/v2.4/rest/tutorials/configurable-product/define-config-product-options.md b/src/guides/v2.4/rest/tutorials/configurable-product/define-config-product-options.md
index 9b70b9ebda5..03ff3ec9e06 100644
--- a/src/guides/v2.4/rest/tutorials/configurable-product/define-config-product-options.md
+++ b/src/guides/v2.4/rest/tutorials/configurable-product/define-config-product-options.md
@@ -2,8 +2,8 @@
layout: tutorial
group: rest-api
title: Step 4. Define configurable product options
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/configurable-product/define-config-product-options/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/configurable-product/define-config-product-options/
+status: migrated
subtitle: Create a configurable product tutorial
menu_title: Step 4. Define configurable product options
menu_order: 40
diff --git a/src/guides/v2.4/rest/tutorials/configurable-product/plan-product.md b/src/guides/v2.4/rest/tutorials/configurable-product/plan-product.md
index ca43d432e45..3a6eb1a0da5 100644
--- a/src/guides/v2.4/rest/tutorials/configurable-product/plan-product.md
+++ b/src/guides/v2.4/rest/tutorials/configurable-product/plan-product.md
@@ -2,8 +2,8 @@
layout: tutorial
group: rest-api
title: Step 1. Plan the product
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/configurable-product/plan-product/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/configurable-product/plan-product/
+status: migrated
subtitle: Create a configurable product tutorial
menu_title: Step 1. Plan the product
menu_order: 10
diff --git a/src/guides/v2.4/rest/tutorials/grouped-product/create-and-manage-grouped-products.md b/src/guides/v2.4/rest/tutorials/grouped-product/create-and-manage-grouped-products.md
index 34a623c76fc..2adc969b906 100644
--- a/src/guides/v2.4/rest/tutorials/grouped-product/create-and-manage-grouped-products.md
+++ b/src/guides/v2.4/rest/tutorials/grouped-product/create-and-manage-grouped-products.md
@@ -1,8 +1,8 @@
---
group: rest-api
title: Create and manage grouped products tutorial
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/grouped-product/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/grouped-product/
+status: migrated
functional_areas:
- Integration
---
diff --git a/src/guides/v2.4/rest/tutorials/index.md b/src/guides/v2.4/rest/tutorials/index.md
index 7226d18bfdb..2bed9b845bb 100644
--- a/src/guides/v2.4/rest/tutorials/index.md
+++ b/src/guides/v2.4/rest/tutorials/index.md
@@ -1,8 +1,8 @@
---
group: rest-api
title: REST tutorials
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/
+status: migrated
functional_areas:
- Integration
- Orders
@@ -33,7 +33,7 @@ Before you begin any tutorial, make sure you know the basics about {{site.data.v
* Know how to construct a REST call in Magento. See [Construct a request](https://developer.adobe.com/commerce/webapi/get-started/gs-web-api-request) for details.
-* Find the Magento REST API documentation. You can view the [static REST API documentation on devdocs](https://magento.redoc.ly/) or [generate a local API reference](https://developer.adobe.com/commerce/webapi/rest/quick-reference/generate-local).
+* Find the Magento REST API documentation. You can view the [static REST API documentation](https://developer.adobe.com/commerce/webapi/rest/quick-reference/) or [generate a local API reference](https://developer.adobe.com/commerce/webapi/rest/quick-reference/generate-local).
* Find the Magento Merchant documentation. Refer to [Getting Started with {{site.data.var.ce}}]({{ site.user_guide_url }}/getting-started.html) for information about the Luma store that is created when you install Magento with the sample data.
diff --git a/src/guides/v2.4/rest/tutorials/inventory/assign-source-to-stock.md b/src/guides/v2.4/rest/tutorials/inventory/assign-source-to-stock.md
index 4d5e0d3b803..204ffeed9fb 100644
--- a/src/guides/v2.4/rest/tutorials/inventory/assign-source-to-stock.md
+++ b/src/guides/v2.4/rest/tutorials/inventory/assign-source-to-stock.md
@@ -2,8 +2,8 @@
layout: tutorial
group: rest-api
title: Step 4. Link stocks and sources
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/inventory/assign-source-to-stock/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/inventory/assign-source-to-stock/
+status: migrated
subtitle: Order processing with Inventory Management
menu_title: Step 4. Link stocks and sources
menu_order: 40
diff --git a/src/guides/v2.4/rest/tutorials/inventory/bulk-transfer-products.md b/src/guides/v2.4/rest/tutorials/inventory/bulk-transfer-products.md
index 40812c17dda..c3725dbabad 100644
--- a/src/guides/v2.4/rest/tutorials/inventory/bulk-transfer-products.md
+++ b/src/guides/v2.4/rest/tutorials/inventory/bulk-transfer-products.md
@@ -2,8 +2,8 @@
layout: tutorial
group: rest-api
title: Step 13. Bulk transfer products
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/inventory/bulk-transfer-products/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/inventory/bulk-transfer-products/
+status: migrated
subtitle: Order processing with Inventory Management
menu_title: Step 13. Bulk transfer products
menu_order: 130
diff --git a/src/guides/v2.4/rest/tutorials/inventory/configure-environment.md b/src/guides/v2.4/rest/tutorials/inventory/configure-environment.md
index 6cefb6407f1..d803724f9d0 100644
--- a/src/guides/v2.4/rest/tutorials/inventory/configure-environment.md
+++ b/src/guides/v2.4/rest/tutorials/inventory/configure-environment.md
@@ -2,8 +2,8 @@
layout: tutorial
group: rest-api
title: Step 1. Configure your environment
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/inventory/configure-environment/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/inventory/configure-environment/
+status: migrated
subtitle: Order processing with Inventory Management
menu_title: Step 1. Configure your environment
menu_order: 10
diff --git a/src/guides/v2.4/rest/tutorials/inventory/create-cart-add-products.md b/src/guides/v2.4/rest/tutorials/inventory/create-cart-add-products.md
index 86c81c2946a..1e150c7a815 100644
--- a/src/guides/v2.4/rest/tutorials/inventory/create-cart-add-products.md
+++ b/src/guides/v2.4/rest/tutorials/inventory/create-cart-add-products.md
@@ -2,8 +2,8 @@
layout: tutorial
group: rest-api
title: Step 7. Create a cart and add products to it
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/inventory/create-cart-add-products/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/inventory/create-cart-add-products/
+status: migrated
subtitle: Order processing with Inventory Management
menu_title: Step 7. Create a cart and add products to it
menu_order: 70
diff --git a/src/guides/v2.4/rest/tutorials/inventory/create-customer.md b/src/guides/v2.4/rest/tutorials/inventory/create-customer.md
index da7030b6380..f4c2aaa9b1b 100644
--- a/src/guides/v2.4/rest/tutorials/inventory/create-customer.md
+++ b/src/guides/v2.4/rest/tutorials/inventory/create-customer.md
@@ -2,8 +2,8 @@
layout: tutorial
group: rest-api
title: Step 6. Create a customer and generate a customer token
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/inventory/create-customer/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/inventory/create-customer/
+status: migrated
subtitle: Order processing with Inventory Management
menu_title: Step 6. Create a customer and generate a customer token
menu_order: 60
diff --git a/src/guides/v2.4/rest/tutorials/inventory/create-invoice.md b/src/guides/v2.4/rest/tutorials/inventory/create-invoice.md
index f8e6b9eb3b8..de89d8dc70d 100644
--- a/src/guides/v2.4/rest/tutorials/inventory/create-invoice.md
+++ b/src/guides/v2.4/rest/tutorials/inventory/create-invoice.md
@@ -2,8 +2,8 @@
layout: tutorial
group: rest-api
title: Step 10. Create an invoice
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/inventory/create-invoice/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/inventory/create-invoice/
+status: migrated
subtitle: Order processing with Inventory Management
menu_title: Step 10. Create an invoice
menu_order: 100
diff --git a/src/guides/v2.4/rest/tutorials/inventory/create-order.md b/src/guides/v2.4/rest/tutorials/inventory/create-order.md
index b6b86cb4c24..cdf91e3a044 100644
--- a/src/guides/v2.4/rest/tutorials/inventory/create-order.md
+++ b/src/guides/v2.4/rest/tutorials/inventory/create-order.md
@@ -2,8 +2,8 @@
layout: tutorial
group: rest-api
title: Step 9. Create an order
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/inventory/create-order/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/inventory/create-order/
+status: migrated
subtitle: Order processing with Inventory Management
menu_title: Step 9. Create an order
menu_order: 90
diff --git a/src/guides/v2.4/rest/tutorials/inventory/create-shipment.md b/src/guides/v2.4/rest/tutorials/inventory/create-shipment.md
index 31977f6bc94..043ef96a5f4 100644
--- a/src/guides/v2.4/rest/tutorials/inventory/create-shipment.md
+++ b/src/guides/v2.4/rest/tutorials/inventory/create-shipment.md
@@ -2,8 +2,8 @@
layout: tutorial
group: rest-api
title: Step 12. Create a shipment
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/inventory/create-shipment/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/inventory/create-shipment/
+status: migrated
menu_title: Step 12. Create a shipment
subtitle: Order processing with Inventory Management
menu_order: 120
diff --git a/src/guides/v2.4/rest/tutorials/inventory/create-sources.md b/src/guides/v2.4/rest/tutorials/inventory/create-sources.md
index 4dc9c4c23bd..161bf95dc8e 100644
--- a/src/guides/v2.4/rest/tutorials/inventory/create-sources.md
+++ b/src/guides/v2.4/rest/tutorials/inventory/create-sources.md
@@ -2,8 +2,8 @@
layout: tutorial
group: rest-api
title: Step 2. Create sources
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/inventory/create-sources/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/inventory/create-sources/
+status: migrated
subtitle: Order processing with Inventory Management
menu_title: Step 2. Create sources
menu_order: 20
diff --git a/src/guides/v2.4/rest/tutorials/inventory/create-stock.md b/src/guides/v2.4/rest/tutorials/inventory/create-stock.md
index 4cd78263726..7d92b6267d5 100644
--- a/src/guides/v2.4/rest/tutorials/inventory/create-stock.md
+++ b/src/guides/v2.4/rest/tutorials/inventory/create-stock.md
@@ -2,8 +2,8 @@
layout: tutorial
group: rest-api
title: Step 3. Create stocks
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/inventory/create-stock/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/inventory/create-stock/
+status: migrated
subtitle: Order processing with Inventory Management
menu_title: Step 3. Create stocks
menu_order: 30
diff --git a/src/guides/v2.4/rest/tutorials/inventory/in-store-pickup.md b/src/guides/v2.4/rest/tutorials/inventory/in-store-pickup.md
index cd7bfc1d2d3..02088e80e03 100644
--- a/src/guides/v2.4/rest/tutorials/inventory/in-store-pickup.md
+++ b/src/guides/v2.4/rest/tutorials/inventory/in-store-pickup.md
@@ -2,8 +2,8 @@
layout: tutorial
group: rest-api
title: Step 14. Create an order for in-store pickup (optional)
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/inventory/in-store-pickup/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/inventory/in-store-pickup/
+status: migrated
subtitle: Order processing with Inventory Management
menu_title: Step 14. Bulk transfer products
menu_order: 140
diff --git a/src/guides/v2.4/rest/tutorials/inventory/index.md b/src/guides/v2.4/rest/tutorials/inventory/index.md
index 7d7a871f446..45bbe82d3f6 100644
--- a/src/guides/v2.4/rest/tutorials/inventory/index.md
+++ b/src/guides/v2.4/rest/tutorials/inventory/index.md
@@ -2,8 +2,8 @@
layout: tutorial
group: rest-api
title: Order Processing with Inventory Management
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/inventory/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/inventory/
+status: migrated
menu_title: Initial tasks
menu_order: 0
level3_subgroup: msi-tutorial
@@ -34,4 +34,4 @@ This **14-step tutorial** generally takes **1 hour**.
### Other resources
-* Magento uses [Swagger](https://swagger.io) to provide REST API documentation on local instances of Magento. See [Generate a local API reference](https://developer.adobe.com/commerce/webapi/rest/quick-reference/generate-local) for more information. You can view the [static REST API documentation](https://magento.redoc.ly/), which displays reference information using ReDoc.
+* Magento uses [Swagger](https://swagger.io) to provide REST API documentation on local instances of Magento. See [Generate a local API reference](https://developer.adobe.com/commerce/webapi/rest/quick-reference/generate-local) for more information. You can view the [static REST API documentation](https://developer.adobe.com/commerce/webapi/rest/quick-reference/), which displays reference information using ReDoc.
diff --git a/src/guides/v2.4/rest/tutorials/inventory/prepare-for-checkout.md b/src/guides/v2.4/rest/tutorials/inventory/prepare-for-checkout.md
index 10ae3e49e7b..f45cf1586e4 100644
--- a/src/guides/v2.4/rest/tutorials/inventory/prepare-for-checkout.md
+++ b/src/guides/v2.4/rest/tutorials/inventory/prepare-for-checkout.md
@@ -2,8 +2,8 @@
layout: tutorial
group: rest-api
title: Step 8. Prepare for checkout
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/inventory/prepare-for-checkout/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/inventory/prepare-for-checkout/
+status: migrated
subtitle: Order processing with Inventory Management
menu_title: Step 8. Prepare for checkout
menu_order: 80
diff --git a/src/guides/v2.4/rest/tutorials/inventory/reassign-products-to-another-source.md b/src/guides/v2.4/rest/tutorials/inventory/reassign-products-to-another-source.md
index 7d3b3af32a2..4d1adea9880 100644
--- a/src/guides/v2.4/rest/tutorials/inventory/reassign-products-to-another-source.md
+++ b/src/guides/v2.4/rest/tutorials/inventory/reassign-products-to-another-source.md
@@ -2,8 +2,8 @@
layout: tutorial
group: rest-api
title: Step 5. Reassign products to custom sources
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/inventory/reassign-products-to-another-source/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/inventory/reassign-products-to-another-source/
+status: migrated
subtitle: Order processing with Inventory Management
menu_title: Step 5. Reassign products to custom sources
menu_order: 50
diff --git a/src/guides/v2.4/rest/tutorials/inventory/run-ssa.md b/src/guides/v2.4/rest/tutorials/inventory/run-ssa.md
index 271eba6fed3..1e19d5d1de8 100644
--- a/src/guides/v2.4/rest/tutorials/inventory/run-ssa.md
+++ b/src/guides/v2.4/rest/tutorials/inventory/run-ssa.md
@@ -2,8 +2,8 @@
layout: tutorial
group: rest-api
title: Step 11. Run the Source Selection Algorithms
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/inventory/run-ssa/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/inventory/run-ssa/
+status: migrated
subtitle: Order processing with Inventory Management
menu_title: Step 11. Run the Source Selection Algorithms
menu_order: 110
diff --git a/src/guides/v2.4/rest/tutorials/orders/order-add-items.md b/src/guides/v2.4/rest/tutorials/orders/order-add-items.md
index d5520bc783c..4d71d3510ec 100644
--- a/src/guides/v2.4/rest/tutorials/orders/order-add-items.md
+++ b/src/guides/v2.4/rest/tutorials/orders/order-add-items.md
@@ -2,8 +2,8 @@
layout: tutorial
group: rest-api
title: Step 5. Add items to the cart
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/orders/order-add-items/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/orders/order-add-items/
+status: migrated
subtitle: Order processing tutorial
return_to:
title: REST tutorials
diff --git a/src/guides/v2.4/rest/tutorials/orders/order-admin-token.md b/src/guides/v2.4/rest/tutorials/orders/order-admin-token.md
index 77be57283e2..2384c1cdf0e 100644
--- a/src/guides/v2.4/rest/tutorials/orders/order-admin-token.md
+++ b/src/guides/v2.4/rest/tutorials/orders/order-admin-token.md
@@ -2,8 +2,8 @@
layout: tutorial
group: rest-api
title: Step 2. Get the admin token
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/orders/order-admin-token/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/orders/order-admin-token/
+status: migrated
subtitle: Order processing tutorial
return_to:
title: REST tutorials
diff --git a/src/guides/v2.4/rest/tutorials/orders/order-config-store.md b/src/guides/v2.4/rest/tutorials/orders/order-config-store.md
index 5a8700c6070..975636bedc9 100644
--- a/src/guides/v2.4/rest/tutorials/orders/order-config-store.md
+++ b/src/guides/v2.4/rest/tutorials/orders/order-config-store.md
@@ -2,8 +2,8 @@
layout: tutorial
group: rest-api
title: Step 1. Configure the store
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/orders/order-config-store/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/orders/order-config-store/
+status: migrated
subtitle: Order processing tutorial
return_to:
title: REST tutorials
diff --git a/src/guides/v2.4/rest/tutorials/orders/order-create-customer.md b/src/guides/v2.4/rest/tutorials/orders/order-create-customer.md
index a64b4a80f55..99431238f71 100644
--- a/src/guides/v2.4/rest/tutorials/orders/order-create-customer.md
+++ b/src/guides/v2.4/rest/tutorials/orders/order-create-customer.md
@@ -2,8 +2,8 @@
layout: tutorial
group: rest-api
title: Step 3. Create a customer
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/orders/order-create-customer/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/orders/order-create-customer/
+status: migrated
subtitle: Order processing tutorial
return_to:
title: REST tutorials
diff --git a/src/guides/v2.4/rest/tutorials/orders/order-create-invoice.md b/src/guides/v2.4/rest/tutorials/orders/order-create-invoice.md
index 82f5aa547b5..c680c537008 100644
--- a/src/guides/v2.4/rest/tutorials/orders/order-create-invoice.md
+++ b/src/guides/v2.4/rest/tutorials/orders/order-create-invoice.md
@@ -2,8 +2,8 @@
layout: tutorial
group: rest-api
title: Step 8. Create an invoice
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/orders/order-create-invoice/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/orders/order-create-invoice/
+status: migrated
subtitle: Order processing tutorial
return_to:
title: REST tutorials
diff --git a/src/guides/v2.4/rest/tutorials/orders/order-create-order.md b/src/guides/v2.4/rest/tutorials/orders/order-create-order.md
index f2299f13f51..b98ceef7865 100644
--- a/src/guides/v2.4/rest/tutorials/orders/order-create-order.md
+++ b/src/guides/v2.4/rest/tutorials/orders/order-create-order.md
@@ -2,8 +2,8 @@
layout: tutorial
group: rest-api
title: Step 7. Create an order
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/orders/order-create-order/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/orders/order-create-order/
+status: migrated
subtitle: Order processing tutorial
return_to:
title: REST tutorials
diff --git a/src/guides/v2.4/rest/tutorials/orders/order-create-quote.md b/src/guides/v2.4/rest/tutorials/orders/order-create-quote.md
index 225b43afab9..33d58cd2f28 100644
--- a/src/guides/v2.4/rest/tutorials/orders/order-create-quote.md
+++ b/src/guides/v2.4/rest/tutorials/orders/order-create-quote.md
@@ -2,8 +2,8 @@
layout: tutorial
group: rest-api
title: Step 4. Create a quote
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/orders/order-create-quote/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/orders/order-create-quote/
+status: migrated
subtitle: Order processing tutorial
return_to:
title: REST tutorials
diff --git a/src/guides/v2.4/rest/tutorials/orders/order-create-shipment.md b/src/guides/v2.4/rest/tutorials/orders/order-create-shipment.md
index 2aa755af0a9..06909c70dac 100644
--- a/src/guides/v2.4/rest/tutorials/orders/order-create-shipment.md
+++ b/src/guides/v2.4/rest/tutorials/orders/order-create-shipment.md
@@ -2,8 +2,8 @@
layout: tutorial
group: rest-api
title: Step 9. Create a shipment
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/orders/order-create-shipment/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/orders/order-create-shipment/
+status: migrated
subtitle: Order processing tutorial
return_to:
title: REST tutorials
diff --git a/src/guides/v2.4/rest/tutorials/orders/order-intro.md b/src/guides/v2.4/rest/tutorials/orders/order-intro.md
index 0a5bed63941..3641073644e 100644
--- a/src/guides/v2.4/rest/tutorials/orders/order-intro.md
+++ b/src/guides/v2.4/rest/tutorials/orders/order-intro.md
@@ -2,8 +2,8 @@
layout: tutorial
group: rest-api
title: Order processing tutorial
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/orders/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/orders/
+status: migrated
menu_title: Initial tasks
return_to:
title: REST tutorials
@@ -34,7 +34,7 @@ Complete the following prerequisites:
* Know how to construct a REST call in Magento. See [Construct a request](https://developer.adobe.com/commerce/webapi/get-started/gs-web-api-request) for details.
-* Find the Magento REST API documentation. You can view the [static REST API documentation on devdocs](https://magento.redoc.ly/) or [generate a local API reference](https://developer.adobe.com/commerce/webapi/rest/quick-reference/generate-local).
+* Find the Magento REST API documentation. You can view the [static REST API documentation](https://developer.adobe.com/commerce/webapi/rest/quick-reference/) or [generate a local API reference](https://developer.adobe.com/commerce/webapi/rest/quick-reference/generate-local).
* Find the Magento Merchant documentation. Refer to [Getting Started with {{site.data.var.ce}} 2.1]({{ site.user_guide_url }}/getting-started.html) for information about the Luma store that is created when you install Magento with the sample data.
diff --git a/src/guides/v2.4/rest/tutorials/orders/order-issue-refund.md b/src/guides/v2.4/rest/tutorials/orders/order-issue-refund.md
index 59b35d3d67a..2f3eb41cb9a 100644
--- a/src/guides/v2.4/rest/tutorials/orders/order-issue-refund.md
+++ b/src/guides/v2.4/rest/tutorials/orders/order-issue-refund.md
@@ -2,8 +2,8 @@
layout: tutorial
group: rest-api
title: Step 10. Issue a partial refund
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/orders/order-issue-refund/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/orders/order-issue-refund/
+status: migrated
subtitle: Order processing tutorial
return_to:
title: REST tutorials
@@ -86,4 +86,4 @@ Related topics
* [Getting Started with Magento Web APIs](https://developer.adobe.com/commerce/webapi/get-started/)
* [Create a configurable product Tutorial](https://developer.adobe.com/commerce/webapi/rest/tutorials/configurable-product/)
* [REST API Reference Overview](https://developer.adobe.com/commerce/webapi/rest/)
-* [REST API documentation](https://magento.redoc.ly/)
+* [REST API documentation](https://developer.adobe.com/commerce/webapi/rest/quick-reference/)
diff --git a/src/guides/v2.4/rest/tutorials/orders/order-prepare-checkout.md b/src/guides/v2.4/rest/tutorials/orders/order-prepare-checkout.md
index fed294fe0b3..93656b301b7 100644
--- a/src/guides/v2.4/rest/tutorials/orders/order-prepare-checkout.md
+++ b/src/guides/v2.4/rest/tutorials/orders/order-prepare-checkout.md
@@ -3,8 +3,8 @@ layout: tutorial
group: rest-api
subgroup:
title: Step 6. Prepare for checkout
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/orders/order-prepare-checkout/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/orders/order-prepare-checkout/
+status: migrated
subtitle: Order Processing tutorial
return_to:
title: REST tutorials
diff --git a/src/guides/v2.4/rest/tutorials/prerequisite-tasks/create-admin-token.md b/src/guides/v2.4/rest/tutorials/prerequisite-tasks/create-admin-token.md
index 22e387cd895..0acfa137014 100644
--- a/src/guides/v2.4/rest/tutorials/prerequisite-tasks/create-admin-token.md
+++ b/src/guides/v2.4/rest/tutorials/prerequisite-tasks/create-admin-token.md
@@ -1,8 +1,8 @@
---
group: rest-api
title: Generate the admin token
-migrated_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/prerequisite-tasks/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/webapi/rest/tutorials/prerequisite-tasks/
+status: migrated
functional_areas:
- Integration
- Orders
diff --git a/src/guides/v2.4/search.md b/src/guides/v2.4/search.md
deleted file mode 120000
index 04c3c9cb14b..00000000000
--- a/src/guides/v2.4/search.md
+++ /dev/null
@@ -1 +0,0 @@
-../v2.3/search.md
\ No newline at end of file
diff --git a/src/guides/v2.4/security/google-recaptcha.md b/src/guides/v2.4/security/google-recaptcha.md
index fd5293278c7..aef77e71d18 100644
--- a/src/guides/v2.4/security/google-recaptcha.md
+++ b/src/guides/v2.4/security/google-recaptcha.md
@@ -3,6 +3,8 @@ group: configuration-guide
title: Google reCAPTCHA
functional_areas:
- Configuration
+redirect_to: https://experienceleague.adobe.com/docs/commerce-admin/systems/security/captcha/security-google-recaptcha.html
+status: migrated
---
Google reCAPTCHA provides a greater level of security for both the storefront and Admin UI than is available with standard CAPTCHA, and gives you the ability to:
diff --git a/src/guides/v2.4/security/security-txt.md b/src/guides/v2.4/security/security-txt.md
index f18b5f4c119..d9833a2d5ce 100644
--- a/src/guides/v2.4/security/security-txt.md
+++ b/src/guides/v2.4/security/security-txt.md
@@ -5,8 +5,8 @@ contributor_name: Kalpesh Mehta from Corra
contributor_link: https://partners.magento.com/portal/details/partner/id/70/
functional_areas:
- Configuration
-migrated_to: https://experienceleague.adobe.com/docs/commerce-operations/configuration-guide/security/security-txt.html
-layout: migrated
+redirect_to: https://experienceleague.adobe.com/docs/commerce-operations/configuration-guide/security/security-txt.html
+status: migrated
---
When security vulnerabilities are discovered by researchers, proper reporting channels are often lacking. As a result, some vulnerabilities are not reported. The purpose of the `security.txt` [file format](https://tools.ietf.org/html/draft-foudil-securitytxt-09) is to give security researchers the information they need to report their findings.
diff --git a/src/guides/v2.4/security/two-factor-authentication.md b/src/guides/v2.4/security/two-factor-authentication.md
index 7172d2ab9c6..2d8d3fd45f8 100644
--- a/src/guides/v2.4/security/two-factor-authentication.md
+++ b/src/guides/v2.4/security/two-factor-authentication.md
@@ -3,6 +3,8 @@ group: configuration-guide
title: Two-Factor Authentication
functional_areas:
- Configuration
+redirect_to: https://developer.adobe.com/commerce/testing/functional-testing-framework/two-factor-authentication/
+status: migrated
---
Magento Two-Factor Authentication (2FA) improves security by requiring two-step authentication to access the Magento _Admin_ UI from all devices. The extension supports multiple authenticators including Google Authenticator, Authy, Duo, and U2F keys. 2FA applies to Magento _Admin_ users only. It is not available for storefront customer accounts.
@@ -58,7 +60,7 @@ The 2FA provider for Magento Headless can be selected with the `config:set` comm
Two-Factor Authentication is implemented for Magento Web APIs with the following changes:
-- `AdminTokenServiceInterface::createAdminAccessToken()` throws an exception when the _Admin_ user doesn’t have personal 2FA configured, and also indicates that the confirmation email has been sent.
+- `AdminTokenServiceInterface::createAdminAccessToken()` throws an exception when the _Admin_ user doesn't have personal 2FA configured, and also indicates that the confirmation email has been sent.
- `AdminTokenServiceInterface::createAdminAccessToken()` throws an exception that indicates which provider is configured for the user and suggests a provider-specific login endpoint.
- 2FA provider-specific endpoints allow each _Admin_ user to configure a personal 2FA and provides tokens for username, password, and OTP (2FA code).
diff --git a/src/guides/v2.4/soap/bk-soap.md b/src/guides/v2.4/soap/bk-soap.md
deleted file mode 120000
index da000e53d67..00000000000
--- a/src/guides/v2.4/soap/bk-soap.md
+++ /dev/null
@@ -1 +0,0 @@
-../../v2.3/soap/bk-soap.md
\ No newline at end of file
diff --git a/src/guides/v2.4/soap/bk-soap.md b/src/guides/v2.4/soap/bk-soap.md
new file mode 100644
index 00000000000..5db89a8e240
--- /dev/null
+++ b/src/guides/v2.4/soap/bk-soap.md
@@ -0,0 +1,23 @@
+---
+group: soap
+title: SOAP Reference
+redirect_to: https://developer.adobe.com/commerce/webapi/get-started/soap-web-api-calls/
+status: migrated
+functional_areas:
+ - Integration
+---
+## Soap WSDL Endpoint Format
+
+`http:///soap/?wsdl&services=`
+
+The value of `store_code` can be one of the following:
+
+* `default`
+* The assigned store code
+* `all`. This value only applies to the [CMS](https://glossary.magento.com/cms) and Product modules. If this value is specified, the [API](https://glossary.magento.com/api) call affects all the merchant's stores.
+
+## List of Service Names per Module
+
+The entire list can be retrieved here: `http:///soap/default?wsdl_list=1`
+
+{% include webapi/services23.md%}
diff --git a/src/guides/v2.4/test/integration/annotations.md b/src/guides/v2.4/test/integration/annotations.md
index b3a34ae5a5e..5fdb0605dc4 100644
--- a/src/guides/v2.4/test/integration/annotations.md
+++ b/src/guides/v2.4/test/integration/annotations.md
@@ -1,8 +1,8 @@
---
group: testing
title: Using DocBlock Annotations
-migrated_to: https://developer.adobe.com/commerce/testing/guide/integration/annotations/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/testing/guide/integration/annotations/
+status: migrated
---
DocBlock annotations help to declare context in your code. In addition to built-in [PHPUnit annotations][]
diff --git a/src/guides/v2.4/test/integration/annotations/depends.md b/src/guides/v2.4/test/integration/annotations/depends.md
index 7b0909218f5..305b129030b 100644
--- a/src/guides/v2.4/test/integration/annotations/depends.md
+++ b/src/guides/v2.4/test/integration/annotations/depends.md
@@ -1,8 +1,8 @@
---
group: testing
title: Depends Annotation
-migrated_to: https://developer.adobe.com/commerce/testing/guide/integration/annotations/magento-depends/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/testing/guide/integration/annotations/magento-depends/
+status: migrated
---
The `@depends` annotation helps you to define some dependencies between methods.
diff --git a/src/guides/v2.4/test/integration/annotations/magento-app-area.md b/src/guides/v2.4/test/integration/annotations/magento-app-area.md
index a789c04bff5..11cf35d6ca3 100644
--- a/src/guides/v2.4/test/integration/annotations/magento-app-area.md
+++ b/src/guides/v2.4/test/integration/annotations/magento-app-area.md
@@ -1,8 +1,8 @@
---
group: testing
title: Application Area Annotation in the Integration Testing Framework
-migrated_to: https://developer.adobe.com/commerce/testing/guide/integration/annotations/magento-app-area/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/testing/guide/integration/annotations/magento-app-area/
+status: migrated
---
Configure a test environment in scope of the particular [application area][] with the `@magentoAppArea` annotation.
diff --git a/src/guides/v2.4/test/integration/annotations/magento-app-isolation.md b/src/guides/v2.4/test/integration/annotations/magento-app-isolation.md
index cea1e90441e..5ff55fe61b3 100644
--- a/src/guides/v2.4/test/integration/annotations/magento-app-isolation.md
+++ b/src/guides/v2.4/test/integration/annotations/magento-app-isolation.md
@@ -1,8 +1,8 @@
---
group: testing
title: Application isolation annotation
-migrated_to: https://developer.adobe.com/commerce/testing/guide/integration/annotations/magento-app-isolation/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/testing/guide/integration/annotations/magento-app-isolation/
+status: migrated
---
An application state can be changed during test execution.
diff --git a/src/guides/v2.4/test/integration/annotations/magento-cache.md b/src/guides/v2.4/test/integration/annotations/magento-cache.md
index 8c42a24c195..aac57c7fe09 100644
--- a/src/guides/v2.4/test/integration/annotations/magento-cache.md
+++ b/src/guides/v2.4/test/integration/annotations/magento-cache.md
@@ -1,8 +1,8 @@
---
group: testing
title: Cache Annotation
-migrated_to: https://developer.adobe.com/commerce/testing/guide/integration/annotations/magento-cache/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/testing/guide/integration/annotations/magento-cache/
+status: migrated
---
Enable or disable a [cache type][] using the `@magentoCache` annotation.
diff --git a/src/guides/v2.4/test/integration/annotations/magento-components-dir.md b/src/guides/v2.4/test/integration/annotations/magento-components-dir.md
index a4771e1f421..20e4db56c55 100644
--- a/src/guides/v2.4/test/integration/annotations/magento-components-dir.md
+++ b/src/guides/v2.4/test/integration/annotations/magento-components-dir.md
@@ -1,8 +1,8 @@
---
group: testing
title: Component registration annotation
-migrated_to: https://developer.adobe.com/commerce/testing/guide/integration/annotations/magento-components-dir/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/testing/guide/integration/annotations/magento-components-dir/
+status: migrated
---
When your test design requires to register fixture components and unregister them after the test execution, use the `@magentoComponentsDir` annotation.
diff --git a/src/guides/v2.4/test/integration/annotations/magento-config-fixture.md b/src/guides/v2.4/test/integration/annotations/magento-config-fixture.md
index 44f6f3f835b..58aaebb0a6e 100644
--- a/src/guides/v2.4/test/integration/annotations/magento-config-fixture.md
+++ b/src/guides/v2.4/test/integration/annotations/magento-config-fixture.md
@@ -1,8 +1,8 @@
---
group: testing
title: Configuration fixture annotation
-migrated_to: https://developer.adobe.com/commerce/testing/guide/integration/annotations/magento-config-fixture/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/testing/guide/integration/annotations/magento-config-fixture/
+status: migrated
---
To set Magento configuration values for individual tests and revert them after the test execution, use the `@magentoConfigFixture` annotation.
diff --git a/src/guides/v2.4/test/integration/annotations/magento-data-fixture.md b/src/guides/v2.4/test/integration/annotations/magento-data-fixture.md
index 8e3abb75615..8933712f6d2 100644
--- a/src/guides/v2.4/test/integration/annotations/magento-data-fixture.md
+++ b/src/guides/v2.4/test/integration/annotations/magento-data-fixture.md
@@ -1,8 +1,8 @@
---
group: testing
title: Data fixture annotation
-migrated_to: https://developer.adobe.com/commerce/testing/guide/integration/annotations/magento-data-fixture/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/testing/guide/integration/annotations/magento-data-fixture/
+status: migrated
---
A data fixture is a PHP script that sets data you want to reuse in your test.
diff --git a/src/guides/v2.4/test/integration/annotations/magento-db-isolation.md b/src/guides/v2.4/test/integration/annotations/magento-db-isolation.md
index 99270b8dd7e..0bf59edb7b4 100644
--- a/src/guides/v2.4/test/integration/annotations/magento-db-isolation.md
+++ b/src/guides/v2.4/test/integration/annotations/magento-db-isolation.md
@@ -1,8 +1,8 @@
---
group: testing
title: Database isolation annotation
-migrated_to: https://developer.adobe.com/commerce/testing/guide/integration/annotations/magento-db-isolation/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/testing/guide/integration/annotations/magento-db-isolation/
+status: migrated
---
To isolate database changes between tests, the Integration testing framework (ITF) implements the `@magentoDbIsolation` annotation.
diff --git a/src/guides/v2.4/test/integration/attributes.md b/src/guides/v2.4/test/integration/attributes.md
index 5b30534fe68..8fda4809c43 100644
--- a/src/guides/v2.4/test/integration/attributes.md
+++ b/src/guides/v2.4/test/integration/attributes.md
@@ -1,8 +1,8 @@
---
group: testing
title: Using PHP built-in attributes
-migrated_to: https://developer.adobe.com/commerce/testing/guide/integration/attributes/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/testing/guide/integration/attributes/
+status: migrated
---
[PHP built-in attributes][] help to declare context in your code. Attributes can be used alone or together with Annotations to help to declare context in your code.
diff --git a/src/guides/v2.4/test/integration/attributes/magento-app-area.md b/src/guides/v2.4/test/integration/attributes/magento-app-area.md
index 515b9e280d8..5946f45398a 100644
--- a/src/guides/v2.4/test/integration/attributes/magento-app-area.md
+++ b/src/guides/v2.4/test/integration/attributes/magento-app-area.md
@@ -1,8 +1,8 @@
---
group: testing
title: Application Area attribute
-migrated_to: https://developer.adobe.com/commerce/testing/guide/integration/attributes/app-area/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/testing/guide/integration/attributes/app-area/
+status: migrated
---
Configure a test environment in scope of the particular [application area][] with the `AppArea` annotation.
diff --git a/src/guides/v2.4/test/integration/attributes/magento-app-isolation.md b/src/guides/v2.4/test/integration/attributes/magento-app-isolation.md
index f21857c08b9..bcee09beb8e 100644
--- a/src/guides/v2.4/test/integration/attributes/magento-app-isolation.md
+++ b/src/guides/v2.4/test/integration/attributes/magento-app-isolation.md
@@ -1,8 +1,8 @@
---
group: testing
title: Application isolation attribute
-migrated_to: https://developer.adobe.com/commerce/testing/guide/integration/attributes/app-isolation/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/testing/guide/integration/attributes/app-isolation/
+status: migrated
---
An application state can be changed during test execution.
diff --git a/src/guides/v2.4/test/integration/attributes/magento-cache.md b/src/guides/v2.4/test/integration/attributes/magento-cache.md
index 60b11a5f34e..7f976f16fbf 100644
--- a/src/guides/v2.4/test/integration/attributes/magento-cache.md
+++ b/src/guides/v2.4/test/integration/attributes/magento-cache.md
@@ -1,8 +1,8 @@
---
group: testing
title: Cache attribute
-migrated_to: https://developer.adobe.com/commerce/testing/guide/integration/attributes/cache/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/testing/guide/integration/attributes/cache/
+status: migrated
---
Enable or disable a [cache type][] using the `Cache` attribute.
diff --git a/src/guides/v2.4/test/integration/attributes/magento-components-dir.md b/src/guides/v2.4/test/integration/attributes/magento-components-dir.md
index 5b2c662f33e..41716e84bcd 100644
--- a/src/guides/v2.4/test/integration/attributes/magento-components-dir.md
+++ b/src/guides/v2.4/test/integration/attributes/magento-components-dir.md
@@ -1,8 +1,8 @@
---
group: testing
title: Component registration attribute
-migrated_to: https://developer.adobe.com/commerce/testing/guide/integration/attributes/components-dir/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/testing/guide/integration/attributes/components-dir/
+status: migrated
---
When your test design requires you to register fixture components and unregister them after the test execution, use the `ComponentsDir` attribute.
diff --git a/src/guides/v2.4/test/integration/attributes/magento-config-fixture.md b/src/guides/v2.4/test/integration/attributes/magento-config-fixture.md
index 36c22f0b458..e65c78bf482 100644
--- a/src/guides/v2.4/test/integration/attributes/magento-config-fixture.md
+++ b/src/guides/v2.4/test/integration/attributes/magento-config-fixture.md
@@ -1,8 +1,8 @@
---
group: testing
title: Configuration fixture attribute
-migrated_to: https://developer.adobe.com/commerce/testing/guide/integration/attributes/config-fixture/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/testing/guide/integration/attributes/config-fixture/
+status: migrated
---
To set configuration values for individual tests and revert them after the test execution, use the `Config` attribute.
diff --git a/src/guides/v2.4/test/integration/attributes/magento-data-fixture-before-transaction.md b/src/guides/v2.4/test/integration/attributes/magento-data-fixture-before-transaction.md
index ffbe9b94132..40f75acf958 100644
--- a/src/guides/v2.4/test/integration/attributes/magento-data-fixture-before-transaction.md
+++ b/src/guides/v2.4/test/integration/attributes/magento-data-fixture-before-transaction.md
@@ -1,8 +1,8 @@
---
group: testing
title: Data fixture before transaction attribute
-migrated_to: https://developer.adobe.com/commerce/testing/guide/integration/attributes/data-fixture-before-transaction/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/testing/guide/integration/attributes/data-fixture-before-transaction/
+status: migrated
---
## Overview
diff --git a/src/guides/v2.4/test/integration/attributes/magento-data-fixture.md b/src/guides/v2.4/test/integration/attributes/magento-data-fixture.md
index 508b1895738..21b512a56be 100644
--- a/src/guides/v2.4/test/integration/attributes/magento-data-fixture.md
+++ b/src/guides/v2.4/test/integration/attributes/magento-data-fixture.md
@@ -4,8 +4,8 @@ title: Data fixture attribute
redirect_from:
- /guides/v2.4/test/integration/annotations/magento-data-fixture-data-provider.html
- /guides/v2.4/test/integration/parameterized_data_fixture.html
-migrated_to: https://developer.adobe.com/commerce/testing/guide/integration/attributes/data-fixture/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/testing/guide/integration/attributes/data-fixture/
+status: migrated
---
## Overview
diff --git a/src/guides/v2.4/test/integration/attributes/magento-db-isolation.md b/src/guides/v2.4/test/integration/attributes/magento-db-isolation.md
index 05abec01ccf..b2d007e362e 100644
--- a/src/guides/v2.4/test/integration/attributes/magento-db-isolation.md
+++ b/src/guides/v2.4/test/integration/attributes/magento-db-isolation.md
@@ -1,8 +1,8 @@
---
group: testing
title: Database isolation attribute
-migrated_to: https://developer.adobe.com/commerce/testing/guide/integration/attributes/db-isolation/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/testing/guide/integration/attributes/db-isolation/
+status: migrated
---
To isolate database changes between tests, the Integration testing framework (ITF) implements the `DbIsolation` attribute.
diff --git a/src/guides/v2.4/test/integration/attributes/magento-indexer-dimension-mode.md b/src/guides/v2.4/test/integration/attributes/magento-indexer-dimension-mode.md
index 1066384d931..f347e056f7c 100644
--- a/src/guides/v2.4/test/integration/attributes/magento-indexer-dimension-mode.md
+++ b/src/guides/v2.4/test/integration/attributes/magento-indexer-dimension-mode.md
@@ -1,8 +1,8 @@
---
group: testing
title: Indexer dimension mode
-migrated_to: https://developer.adobe.com/commerce/testing/guide/integration/attributes/indexer-dimension-mode/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/testing/guide/integration/attributes/indexer-dimension-mode/
+status: migrated
---
## Overview
diff --git a/src/guides/v2.4/test/integration/integration_test_execution.md b/src/guides/v2.4/test/integration/integration_test_execution.md
index 66cacc7f941..efd89674375 100644
--- a/src/guides/v2.4/test/integration/integration_test_execution.md
+++ b/src/guides/v2.4/test/integration/integration_test_execution.md
@@ -6,8 +6,8 @@ contributor_link: https://vinaikopp.com/
functional_areas:
- Testing
- test
-migrated_to: https://developer.adobe.com/commerce/testing/guide/integration/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/testing/guide/integration/
+status: migrated
---
Integration tests require the Magento runtime environment, so they need a little preparation before they can be executed.
diff --git a/src/guides/v2.4/test/js/jasmine.md b/src/guides/v2.4/test/js/jasmine.md
index 91db47235f9..dc5fe847220 100644
--- a/src/guides/v2.4/test/js/jasmine.md
+++ b/src/guides/v2.4/test/js/jasmine.md
@@ -4,8 +4,8 @@ title: JavaScript unit testing with Jasmine
functional_areas:
- Testing
- test
-migrated_to: https://developer.adobe.com/commerce/testing/guide/js/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/testing/guide/js/
+status: migrated
---
Magento uses a custom [Grunt] task named `spec` to run Jasmine tests. The task collects the tests from `dev/tests/js/jasmine/tests` and can be run for all tests, a theme, or a single test.
diff --git a/src/guides/v2.4/test/static/static-analysis.md b/src/guides/v2.4/test/static/static-analysis.md
index 86d7c66a623..310c07e973a 100644
--- a/src/guides/v2.4/test/static/static-analysis.md
+++ b/src/guides/v2.4/test/static/static-analysis.md
@@ -4,8 +4,8 @@ title: Setting up static analysis
functional_areas:
- Testing
- test
-migrated_to: https://developer.adobe.com/commerce/testing/guide/static/analysis/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/testing/guide/static/analysis/
+status: migrated
---
## Introduction
diff --git a/src/guides/v2.4/test/static/static_test_execution.md b/src/guides/v2.4/test/static/static_test_execution.md
index 4b272f897bd..377b0552850 100644
--- a/src/guides/v2.4/test/static/static_test_execution.md
+++ b/src/guides/v2.4/test/static/static_test_execution.md
@@ -4,8 +4,8 @@ title: Running Static Tests
functional_areas:
- Testing
- test
-migrated_to: https://developer.adobe.com/commerce/testing/guide/static/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/testing/guide/static/
+status: migrated
---
Executing Magento 2 static tests is straightforward. They can be executed in several ways.
diff --git a/src/guides/v2.4/test/svc/semver_test_execution.md b/src/guides/v2.4/test/svc/semver_test_execution.md
index b80af0c0fd6..7a6e4865cc7 100644
--- a/src/guides/v2.4/test/svc/semver_test_execution.md
+++ b/src/guides/v2.4/test/svc/semver_test_execution.md
@@ -4,8 +4,8 @@ title: Running Semantic Version Checker
functional_areas:
- Testing
- test
-migrated_to: https://developer.adobe.com/commerce/testing/guide/svc/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/testing/guide/svc/
+status: migrated
---
Executing the Magento 2 Semantic Version Checker is a simple process, but it requires an external tool.
diff --git a/src/guides/v2.4/test/testing.md b/src/guides/v2.4/test/testing.md
index 5a004c65f43..943729ad0d5 100644
--- a/src/guides/v2.4/test/testing.md
+++ b/src/guides/v2.4/test/testing.md
@@ -2,8 +2,8 @@
group: testing
title: Application Testing Guide
landing-page: Application Testing Guide
-migrated_to: https://developer.adobe.com/commerce/testing/guide/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/testing/guide/
+status: migrated
---
Magento actively leverages various testing strategies to ensure product and code quality.
diff --git a/src/guides/v2.4/test/unit/annotations/data-provider.md b/src/guides/v2.4/test/unit/annotations/data-provider.md
index 08bd8210339..61b127258f4 100644
--- a/src/guides/v2.4/test/unit/annotations/data-provider.md
+++ b/src/guides/v2.4/test/unit/annotations/data-provider.md
@@ -1,8 +1,8 @@
---
group: testing
title: Data Provider Annotation
-migrated_to: https://developer.adobe.com/commerce/testing/guide/unit/annotations/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/testing/guide/unit/annotations/
+status: migrated
---
A Data Provider allows you to define the test once and run it multiple times with different inputs, for checking multiple use cases.
diff --git a/src/guides/v2.4/test/unit/unit_test_execution.md b/src/guides/v2.4/test/unit/unit_test_execution.md
index 04da87cc14d..a4d46609412 100644
--- a/src/guides/v2.4/test/unit/unit_test_execution.md
+++ b/src/guides/v2.4/test/unit/unit_test_execution.md
@@ -6,8 +6,8 @@ contributor_link: https://vinaikopp.com/
functional_areas:
- Testing
- test
-migrated_to: https://developer.adobe.com/commerce/testing/guide/unit/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/testing/guide/unit/
+status: migrated
---
Executing the Magento 2 unit tests is straight forward.
diff --git a/src/guides/v2.4/test/unit/unit_test_execution_cli.md b/src/guides/v2.4/test/unit/unit_test_execution_cli.md
index d430b6ca10b..c8243c1d256 100644
--- a/src/guides/v2.4/test/unit/unit_test_execution_cli.md
+++ b/src/guides/v2.4/test/unit/unit_test_execution_cli.md
@@ -6,8 +6,8 @@ contributor_link: https://vinaikopp.com/
functional_areas:
- Testing
- test
-migrated_to: https://developer.adobe.com/commerce/testing/guide/unit/command-line/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/testing/guide/unit/command-line/
+status: migrated
---
### Running all unit tests
diff --git a/src/guides/v2.4/test/unit/unit_test_execution_phpstorm.md b/src/guides/v2.4/test/unit/unit_test_execution_phpstorm.md
index ca4c01ff3c7..d5ca0f7739c 100644
--- a/src/guides/v2.4/test/unit/unit_test_execution_phpstorm.md
+++ b/src/guides/v2.4/test/unit/unit_test_execution_phpstorm.md
@@ -6,8 +6,8 @@ contributor_link: https://vinaikopp.com/
functional_areas:
- Testing
- test
-migrated_to: https://developer.adobe.com/commerce/testing/guide/unit/phpstorm/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/testing/guide/unit/phpstorm/
+status: migrated
---
Running tests in PhpStorm requires following steps to setup the system.
diff --git a/src/guides/v2.4/test/unit/writing_testable_code.md b/src/guides/v2.4/test/unit/writing_testable_code.md
index 399fc6d572f..73078914a82 100644
--- a/src/guides/v2.4/test/unit/writing_testable_code.md
+++ b/src/guides/v2.4/test/unit/writing_testable_code.md
@@ -6,8 +6,8 @@ contributor_link: https://vinaikopp.com/
functional_areas:
- Testing
- test
-migrated_to: https://developer.adobe.com/commerce/testing/guide/unit/writing-testable-code/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/testing/guide/unit/writing-testable-code/
+status: migrated
---
This topic does not aim to be a replacement for existing documentation about testing, but rather tries to highlight some thoughts on the subject. Although the truth of anything depends somewhat on the context, this topic attempts to provide information that is applicable in *most* situations.
diff --git a/src/guides/v2.4/ui_comp_guide/best-practices/semantic_config.md b/src/guides/v2.4/ui_comp_guide/best-practices/semantic_config.md
index 56d81943c40..516a06e02ac 100644
--- a/src/guides/v2.4/ui_comp_guide/best-practices/semantic_config.md
+++ b/src/guides/v2.4/ui_comp_guide/best-practices/semantic_config.md
@@ -1,8 +1,8 @@
---
group: ui-components-guide
title: Using the new structure in UI components XML configuration
-migrated_to: https://developer.adobe.com/commerce/frontend-core/ui-components/concepts/semantic-configuration/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/frontend-core/ui-components/concepts/semantic-configuration/
+status: migrated
---
Magento 2.2.0 introduces a new structure for [UI components XML configuration]({{ page.baseurl }}/ui_comp_guide/concepts/ui_comp_xmldeclaration_concept.html), aimed at improving configuration semantics.
diff --git a/src/guides/v2.4/ui_comp_guide/bk-ui_comps.md b/src/guides/v2.4/ui_comp_guide/bk-ui_comps.md
index f557ab3fd9c..c32575d7f39 100644
--- a/src/guides/v2.4/ui_comp_guide/bk-ui_comps.md
+++ b/src/guides/v2.4/ui_comp_guide/bk-ui_comps.md
@@ -3,8 +3,8 @@ group: ui-components-guide
title: Overview of UI components
redirect_from:
- /guides/v2.3/ui-components/ui-listing-grid.html
-migrated_to: https://developer.adobe.com/commerce/frontend-core/ui-components/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/frontend-core/ui-components/
+status: migrated
---
## Overview of UI components
diff --git a/src/guides/v2.4/ui_comp_guide/components/basic-attributes.md b/src/guides/v2.4/ui_comp_guide/components/basic-attributes.md
index 12576b1f792..9d9d51b2717 100644
--- a/src/guides/v2.4/ui_comp_guide/components/basic-attributes.md
+++ b/src/guides/v2.4/ui_comp_guide/components/basic-attributes.md
@@ -1,8 +1,8 @@
---
group: ui-components-guide
title: Basic attributes
-migrated_to: https://developer.adobe.com/commerce/frontend-core/ui-components/concepts/basic-attributes/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/frontend-core/ui-components/concepts/basic-attributes/
+status: migrated
---
## Overview
diff --git a/src/guides/v2.4/ui_comp_guide/components/image-uploader/index.md b/src/guides/v2.4/ui_comp_guide/components/image-uploader/index.md
index 28fccd8dc56..7876b681a12 100644
--- a/src/guides/v2.4/ui_comp_guide/components/image-uploader/index.md
+++ b/src/guides/v2.4/ui_comp_guide/components/image-uploader/index.md
@@ -1,8 +1,8 @@
---
group: ui-components-guide
title: ImageUploader component
-migrated_to: https://developer.adobe.com/commerce/frontend-core/ui-components/components/image-uploader/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/frontend-core/ui-components/components/image-uploader/
+status: migrated
---
The ImageUploader UI component gives users the ability to upload images to the Magento Media Gallery.
diff --git a/src/guides/v2.4/ui_comp_guide/components/ui-actiondelete.md b/src/guides/v2.4/ui_comp_guide/components/ui-actiondelete.md
index 72f6b1e2854..3967afd3454 100644
--- a/src/guides/v2.4/ui_comp_guide/components/ui-actiondelete.md
+++ b/src/guides/v2.4/ui_comp_guide/components/ui-actiondelete.md
@@ -1,8 +1,8 @@
---
group: ui-components-guide
title: ActionDelete component
-migrated_to: https://developer.adobe.com/commerce/frontend-core/ui-components/components/action-delete/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/frontend-core/ui-components/components/action-delete/
+status: migrated
---
## Overview
diff --git a/src/guides/v2.4/ui_comp_guide/components/ui-actionscolumn.md b/src/guides/v2.4/ui_comp_guide/components/ui-actionscolumn.md
index 9fcafc03669..88213a24daa 100644
--- a/src/guides/v2.4/ui_comp_guide/components/ui-actionscolumn.md
+++ b/src/guides/v2.4/ui_comp_guide/components/ui-actionscolumn.md
@@ -1,8 +1,8 @@
---
group: ui-components-guide
title: ActionsColumn component
-migrated_to: https://developer.adobe.com/commerce/frontend-core/ui-components/components/actions-column/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/frontend-core/ui-components/components/actions-column/
+status: migrated
---
The ActionsColumns component implements a table's column responsible for displaying and performing a list of record-related actions.
diff --git a/src/guides/v2.4/ui_comp_guide/components/ui-bookmarks.md b/src/guides/v2.4/ui_comp_guide/components/ui-bookmarks.md
index 8e94aacc80e..1123bccf1ed 100644
--- a/src/guides/v2.4/ui_comp_guide/components/ui-bookmarks.md
+++ b/src/guides/v2.4/ui_comp_guide/components/ui-bookmarks.md
@@ -1,8 +1,8 @@
---
group: ui-components-guide
title: Bookmarks component
-migrated_to: https://developer.adobe.com/commerce/frontend-core/ui-components/components/bookmarks/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/frontend-core/ui-components/components/bookmarks/
+status: migrated
---
The Bookmarks component stores active and changed state of a grid implemented using [Listing]({{ page.baseurl }}/ui_comp_guide/components/ui-listing-grid.html). It includes the state of filters, columns position, applied sorting, pagination, and so on.
diff --git a/src/guides/v2.4/ui_comp_guide/components/ui-button.md b/src/guides/v2.4/ui_comp_guide/components/ui-button.md
index 1493d7992d9..2eabe2c8568 100644
--- a/src/guides/v2.4/ui_comp_guide/components/ui-button.md
+++ b/src/guides/v2.4/ui_comp_guide/components/ui-button.md
@@ -1,8 +1,8 @@
---
group: ui-components-guide
title: Button component
-migrated_to: https://developer.adobe.com/commerce/frontend-core/ui-components/components/button/
-layout: migrated
+redirect_to: https://developer.adobe.com/commerce/frontend-core/ui-components/components/button/
+status: migrated
---
The Button component allows user to perform a list of predefined actions by clicking on the corresponding button. Its default display mode is the [HTML](https://glossary.magento.com/html) `