Merge branch 'master' into update_errors

Author: danidelcar

src/_data/toc/live-search.yml

@@ -4,10 +4,6 @@ pages:
   url: /live-search/overview.html
   versionless: true
 
-- label: Install Live Search
-  url: /live-search/install.html
-  versionless: true
-
 - label: Storefront Popover
   url: /live-search/storefront-popover.html
   versionless: true
@@ -45,7 +41,3 @@ pages:
 - label: Events
   url: /live-search/events.html
   versionless: true
-
-- label: Release Notes
-  url: /live-search/release-notes.html
-  versionless: true

src/_data/whats-new.yml

@@ -4,8 +4,72 @@ description: This page contains recent changes that we think you'd like to know
   We exclude from this list proofreading, spelling checks, and all minor updates.
 link: "/whats-new.html"
 thread: "/whatsnew-feed.xml"
-updated: Mon Nov 29 15:40:15 2021
+updated: Mon Dec 6 15:38:46 2021
 entries:
+- description: Added instructions to manage [_Outgoing emails_  configuration](https://devdocs.magento.com/cloud/project/project-webint-basic.html) for Adobe
+    Commerce on cloud Staging and Production environments using the Magento Cloud
+    CLI command `magento-cloud environment:info`.
+  versions: 2.x
+  type: Technical
+  date: December 1, 2021
+  link: https://github.com/magento-commerce/devdocs/pull/2668
+  merge_commit: abb2648eaf97973f7bc2f4bd449069a2d43f860b
+  contributor: meker12
+  membership: true
+  labels:
+  - 2.x
+  - Technical
+- description: Added [Payment Services](https://devdocs.magento.com/payment-services/index.html)
+    topics with the latest information of the new marketplace extension.
+  versions: 2.4.x
+  type: Major Update
+  date: November 30, 2021
+  link: https://github.com/magento-commerce/devdocs/pull/2555
+  merge_commit: cacf3206b238119950bd247d7c99e4513c3ef64d
+  contributor: shrielenee
+  membership: true
+  labels:
+  - Major Update
+  - 2.4.x
+- description: Added new topics about [buying](https://devdocs.magento.com/marketplace/sellers/subscriptions/buying-subscriptions.html)
+    and [selling](https://devdocs.magento.com/marketplace/sellers/subscriptions/selling-subscriptions.html)
+    subscription-based extensions.
+  versions: 2.x
+  type: New Topic
+  date: November 30, 2021
+  link: https://github.com/magento/devdocs/pull/9266
+  merge_commit: 15e085d7855e3f6b31d38dc71a9a831743641531
+  contributor: igorin
+  membership: true
+  labels:
+  - 2.x
+  - Internal Dev
+  - New Topic
+  - 'Progress: done'
+- description: Published [release notes](https://devdocs.magento.com/quality-patches/release-notes.html)
+    for the 1.1.7 Quality Patches Tool (QPT) package release.
+  versions: 2.x
+  type: Major Update
+  date: November 29, 2021
+  link: https://github.com/magento-commerce/devdocs/pull/2670
+  merge_commit: fab5665a3fc37f662a3ce6565e4c5eda0dc54da0
+  contributor: agorbivskyi
+  membership: true
+  labels:
+  - 2.x
+  - Major Update
+- description: Restored the original Adobe Commerce [lifecycle policy](https://devdocs.magento.com/release/lifecycle-policy.html)
+    page and added a new end of software support table.
+  versions: 2.x
+  type: New Topic
+  date: November 29, 2021
+  link: https://github.com/magento-commerce/devdocs/pull/2658
+  merge_commit: b1d4477825c7358b8069d3cef6c68ae49106881b
+  contributor: jeff-matthews
+  membership: true
+  labels:
+  - 2.x
+  - New Topic
 - description: Added the 'Reindexing in parallel mode` section to the [Manage the
     indexers](https://devdocs.magento.com/guides/v2.4/config-guide/cli/config-cli-subcommands-index.html)
     topic.

src/_includes/config/redis-verify.md

@@ -50,6 +50,10 @@ If you use Redis for page caching, you'll see output similar to the following:
 ... more ...
 ```
 
+### Inspecting compressed data
+
+To inspect compressed Session data and Page Cache, the [Redis Desktop Manager](https://flathub.org/apps/details/dev.rdm.RDM) supports the automatic decompression of Magento 2 Session and Page cache and displays PHP session data in a human-readable form.
+
 ### Redis ping command
 
 Enter the following command:

src/cloud/cdn/configure-fastly.md

@@ -150,11 +150,11 @@ When domain validation completes, Adobe provisions the Let's Encrypt TLS/SSL cer
 
 During the initial Fastly setup process, you can use the following URLs to configure and test Fastly caching in Staging and Production environments:
 
--  Pro projects:
+-  For Pro Staging and Production:
    -  `mcprod.<your-domain>.com`
    -  `mcstaging.<your-domain>.com`
 
--  Starter projects:
+-  For Starter Production only:
    -  `mcprod.<your-domain>.com`
 
 {:.bs-callout-info}

src/cloud/project/project-multi-sites.md

@@ -11,7 +11,7 @@ functional_areas:
 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).
 
 {:.bs-callout-warning}
-Be aware that catalog data expands as you increase the number of websites and stores. Depending on your project architecture, the additional stores can lead to a longer indexing process and slower response times for non-cached catalog pages. Adobe recommends that you monitor site performance closely.
+Catalog data expands as you increase the number of websites and stores. Depending on your project architecture, the additional stores can lead to a longer indexing process and slower response times for non-cached catalog pages. Adobe recommends that you monitor site performance closely.
 
 The process to set up multiple stores depends on whether you choose to use unique or shared domains.
 
@@ -36,15 +36,17 @@ To add a store view to the site base URL, you do not have to create multiple dir
 
 ## Add New Domains
 
-The process to add a new domain depends on the type of Cloud account:
+Custom domains can be added to Pro Staging and any Production environment; they cannot be added to Integration environments.
 
--  For Pro
+The process to add a domain depends on the type of Cloud account:
 
-   You must open a Support ticket to request new domains to be added to the cluster.
+-  For Pro Staging and Production
 
--  For Starter
+   Add the new domain to Fastly, see [Manage domains][], or open a support ticket to request assistance. In addition, you must open a Support ticket to request new domains to be added to a cluster.
 
-   You can add the new domain to Fastly for Production, or you can create a support ticket to request assistance. You must add the new domain to the **Domains** tab in the Program UI: `https://<zone>.magento.cloud/projects/<project-ID>/edit`
+-  For Starter Production only
+
+   Add the new domain to Fastly, see [Manage domains][], or open a support ticket to request assistance. In addition, you must add the new domain to the **Domains** tab in the Project Web Interface: `https://<zone>.magento.cloud/projects/<project-ID>/edit`
 
 ## Configure local installation
 
@@ -337,3 +339,4 @@ Adobe recommends fully testing in the Staging environment before pushing to the
 
 [addstorecode]: {{ site.baseurl }}/guides/v2.4/config-guide/multi-site/ms_websites.html#multi-storecode-baseurl
 [config-multiweb]: {{ site.baseurl }}/guides/v2.4/config-guide/multi-site/ms_over.html
+[Manage domains]: {{ site.baseurl }}cloud/cdn/configure-fastly-customize-cache.html#manage-domains

src/cloud/project/project-upgrade.md

@@ -22,9 +22,6 @@ Review the [{{site.data.var.ece}} service versions][version compatibility matrix
 -  Upgrade third-party extensions to the latest supported version.
 -  Update the `.gitignore` file.
 
-{:.bs-callout-info}
-If you upgrade the PHP version, you must also submit a Support ticket to update the New Relic service.
-
 ### Configuration management
 
 Older versions of {{site.data.var.ee}}, such as 2.1.4 or later to 2.2.x or later, used a `config.local.php` file for Configuration Management. {{site.data.var.ee}} version 2.2.0 and later use the `config.php` file, which works exactly like the `config.local.php` file, but it has different configuration settings that include a list of your enabled modules and additional configuration options.

src/cloud/project/project-webint-basic.md

@@ -1,10 +1,6 @@
 ---
 group: cloud-guide
-subgroup: 100_project
 title: Configure your project
-menu_title: Configure your project
-menu_order: 5
-menu_node:
 functional_areas:
   - Cloud
   - Configuration
@@ -30,7 +26,7 @@ The Project Web Interface provides several ways to access your project and envir
 To access projects and environments through the Project Web Interface:
 
 1. [Log in to your project](https://account.magento.com/customer/account/login/).
-1. Click **Access Project** for a list of URLs and SSH.
+1. Click **Access Site** for a list of URLs for web access and the command for SSH access.
 
    ![Access your project by URL or SSH]({{ site.baseurl }}/common/images/cloud/cloud_project-access.png){:width="600px"}
 

src/cloud/project/project-webint-snap.md

@@ -5,7 +5,9 @@ functional_areas:
   - Cloud
 ---
 
-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. You cannot snapshot Pro Staging or Production environments.
+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.
+
+The Pro Staging and Production environments receive regular backups for disaster recovery purposes by default, see [Pro Backup & Disaster Recovery]({{ site.baseurl }}/cloud/architecture/pro-architecture.html#backup-and-disaster-recovery). However, these backups are not publicly accessible because they are stored in a separate system. You can open a ticket to request a backup with a specific date, time, and timezone. Then we can extract it from the external system and provide it to you.
 
 A _snapshot_ is a complete backup of an environment that includes all persistent data from all running services (for example, your MySQL database, Redis, and so on) and any files stored on the mounted volumes. Because an environment deploys as a read-only file system, restoring a snapshot is very fast.
 

src/cloud/project/services-mysql.md

@@ -8,13 +8,13 @@ redirect_from:
   - /cloud/project/project-conf-files_services-mysql.html  
 ---
 
-The `mysql` service provides persistent data storage based on [MariaDB](https://mariadb.com/) versions 10.2-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.
+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.
 
 {% include install/maria-db.md %}
 
 {:.bs-callout-warning}
 Be careful when upgrading MariaDB from version 10.1 to 10.2.
-MariaDB 10.1 is the last version that support XtraDB as the storage engine. Version 10.2 uses InnoDB for the storage engine. Once you upgrade from 10.1 to 10.2, you cannot rollback the change. {{site.data.var.ee}} supports both storage engines; however, you must check extensions and other systems used by your project to make sure they are compatible with MariaDB 10.2. Read about this [backwards incompatible change](https://mariadb.com/kb/en/upgrading-from-mariadb-101-to-mariadb-102/#incompatible-changes-between-101-and-102).
+MariaDB 10.1 is the last version that supports XtraDB as the storage engine. Version 10.2 uses InnoDB for the storage engine. Once you upgrade from 10.1 to 10.2, you cannot rollback the change. {{site.data.var.ee}} supports both storage engines; however, you must check extensions and other systems used by your project to make sure they are compatible with MariaDB 10.2. Read about this [backwards incompatible change](https://mariadb.com/kb/en/upgrading-from-mariadb-101-to-mariadb-102/#incompatible-changes-between-101-and-102).
 
 {% include cloud/service-config-integration-starter.md %}
 
@@ -50,12 +50,12 @@ MariaDB 10.1 is the last version that support XtraDB as the storage engine. Vers
 
 ## Set up multiple database users
 
-Optionally, you can set up multiple databases as well as multiple users with different permissions.
+Optionally, you can set up multiple databases and multiple users with different permissions.
 
-An _endpoint_ is a set of credentials (or users) with specific privileges. By default, there is one endpoint named `mysql` that has administrator access to all defined databases. To set up multiple database users, you must define multiple endpoints in the services.yaml file and declare the relationships in the .magento.app.yaml file.
+An _endpoint_ is a set of credentials (or users) with specific privileges. By default, there is one endpoint named `mysql` that has administrator access to all defined databases. To set up multiple database users, you must define multiple endpoints in the services.yaml file and declare the relationships in the `.magento.app.yaml` file. For Pro Staging and Production environments, submit a Support ticket to request the additional user.
 
 {:.bs-callout-warning}
-You cannot use multiple _databases_ with {{site.data.var.ee}} at this time, but you **can** create multiple endpoints to restrict access to the `main` database.
+You cannot use multiple _databases_ with {{site.data.var.ee}}, but you **can** create multiple endpoints to restrict access to the `main` database.
 
 Use a nested array to define the endpoints for specific user access. Each endpoint can designate access to one or more schemas (databases) and different levels of permission on each.
 
@@ -87,13 +87,13 @@ mysql:
                     main: rw
 ```
 
-In the preceding example, the `admin` endpoint provides admin-level access to the `main` database, the `reporter` endpoint provides read-only access, and the `importer` endpoint provides read-write access. This means that:
+In the preceding example, the `admin` endpoint provides admin-level access to the `main` database, the `reporter` endpoint provides read-only access, and the `importer` endpoint provides read-write access, which means:
 
 -  The `admin` user has full control of the database.
 -  The `reporter` user has SELECT privileges only.
 -  The `importer` user has SELECT, INSERT, UPDATE, and DELETE privileges.
 
-You must add the endpoints defined in the above example to the `relationships` property of the `.magento.app.yaml` file. For example:
+Add the endpoints defined in the above example to the `relationships` property of the `.magento.app.yaml` file. For example:
 
 ```yaml
 relationships:
@@ -103,13 +103,17 @@ relationships:
 ```
 
 {:.bs-callout-info}
-If you configure one MySQL user, you cannot use the [`DEFINER`](http://dev.mysql.com/doc/refman/5.6/en/show-grants.html) access control mechanism for stored procedures and views.
+If you configure one MySQL user, you cannot use the [`DEFINER`](https://dev.mysql.com/doc/refman/5.6/en/show-grants.html) access control mechanism for stored procedures and views.
 
 ## Connect to the database
 
-Accessing the MariaDB database directly requires you to use a SSH to log in to the remote server, and connect to the database.
+Accessing the MariaDB database directly requires you to use a SSH to log in to the remote Cloud environment, and connect to the database.
 
-1. Log in to the remote server using SSH.
+1. Use SSH to log in to the remote environment.
+
+   ```bash
+   magento-cloud ssh
+   ```
 
 1. Retrieve the MySQL login credentials from the `database` and `type` properties in the [$MAGENTO_CLOUD_RELATIONSHIPS]({{ site.baseurl }}/cloud/project/magento-app-properties.html#relationships) variable.
 
@@ -147,7 +151,7 @@ Accessing the MariaDB database directly requires you to use a SSH to log in to t
    ],
    ```
 
-1. Connect to the database:
+1. Connect to the database.
 
    -  For Starter, use the following command:
 
@@ -161,13 +165,16 @@ Accessing the MariaDB database directly requires you to use a SSH to log in to t
       mysql -h <hostname> -P <number> -u <username> -p'<password>'
       ```
 
+{:.bs-callout-tip}
+You can use the `magento-cloud db:sql` command to connect to the remote database and run SQL commands.
+
 ## Connect to secondary database
 
-In some cases, you might need to connect to the secondary database, for example to improve database performance or resolve database locking issues. If this configuration is required, use `"port" : 3304` to establish the connection. See the [{{ site.data.var.ece }} database best practice](https://support.magento.com/hc/en-us/articles/360049045351) article in the _{{site.data.var.ee}} Help Center_.
+Sometimes, you have to connect to the secondary database to improve database performance or resolve database locking issues. If this configuration is required, use `"port" : 3304` to establish the connection. See the [{{ site.data.var.ece }} database best practice](https://support.magento.com/hc/en-us/articles/360049045351) article in the _{{site.data.var.ee}} Help Center_.
 
 ## Troubleshooting
 
-See the following {{site.data.var.ee}} Support articles for help troubleshooting MySQL problems:
+See the following {{site.data.var.ee}} Support articles for help with troubleshooting MySQL problems:
 
 -  [Checking slow queries and processes MySQL](https://support.magento.com/hc/en-us/articles/360030903091-Checking-slow-queries-and-processes-MySQL-)
 -  [Create database dump on Cloud](https://support.magento.com/hc/en-us/articles/360003254334-Create-database-dump-on-Cloud)