From 9c74955215330d651f994d76d1d1e5d5f2d4ff2a Mon Sep 17 00:00:00 2001 From: Dima Shevtsov Date: Mon, 27 Aug 2018 20:05:07 -0500 Subject: [PATCH] Fixed target="_blank" in links --- Rakefile | 2 +- _includes/cache/page-cache-overview.md | 2 +- _includes/install/auth-tokens-get.md | 6 +- _includes/install/composer-overview.md | 2 +- .../m1x/ce18-ee113/ce1.8_release-notes.html | 2 +- .../m1x/ce18-ee113/ee1.13_release-notes.html | 4 +- .../m1x/ce19-ee114/ce1.9_release-notes.html | 2 +- .../m1x/ce19-ee114/ee1.14_release-notes.html | 2 +- guides/v2.0/cloud/access-acct/fastly.md | 22 ++--- .../cloud/access-acct/first-time-setup.md | 8 +- .../first-time-setup_import-first-steps.md | 2 +- .../first-time-setup_import-prepare.md | 8 +- .../architecture/pro-architecture-legacy.md | 2 +- .../starter-develop-deploy-workflow.md | 6 +- .../cloud/before/before-setup-env-2_clone.md | 6 +- .../before/before-workspace-cloud-account.md | 2 +- .../configure/cloud-vcl-custom-snippets.md | 22 ++--- guides/v2.0/cloud/howtos/how-to.md | 2 +- .../cloud/live/stage-prod-migrate-prereq.md | 2 +- guides/v2.0/cloud/live/stage-prod-migrate.md | 6 +- .../v2.0/cloud/onboarding/onboarding-tasks.md | 10 +-- .../cloud/project/bitbucket-integration.md | 6 +- guides/v2.0/cloud/project/new-relic.md | 14 ++-- .../project/project-conf-files_magento-app.md | 84 +++++++++---------- .../project-conf-files_services-elastic.md | 8 +- .../project-conf-files_services-rabbit.md | 2 +- .../project-conf-files_services-redis.md | 2 +- guides/v2.0/cloud/project/project-start.md | 2 +- .../cloud/project/project-webint-basic.md | 2 +- guides/v2.0/cloud/project/projects.md | 2 +- .../release-notes/CloudReleaseNotes2.1.2.md | 2 +- .../cloud/requirements/cloud-requirements.md | 8 +- guides/v2.0/cloud/trouble/trouble_fastly.md | 8 +- .../v2.0/comp-mgr/prereq/prereq_auth-token.md | 2 +- .../config-guide/bootstrap/mage-profiler.md | 6 +- .../config-guide/bootstrap/magento-modes.md | 2 +- .../cli/config-cli-subcommands-compiler.md | 4 +- .../cli/config-cli-subcommands-i18n.md | 8 +- .../cli/config-cli-subcommands-perf-data.md | 2 +- .../cli/config-cli-subcommands-spt-util.md | 2 +- .../cli/config-cli-subcommands-static-view.md | 2 +- .../cli/config-cli-subcommands-urn.md | 2 +- .../cli/config-cli-subcommands.md | 2 +- guides/v2.0/config-guide/secy/secy-cron.md | 12 +-- .../varnish/config-varnish-magento.md | 6 +- guides/v2.0/contributor-guide/contributing.md | 14 ++-- .../build/composer-integration.md | 12 +-- .../extension-dev-guide/cache/page-caching.md | 2 +- .../cache/page-caching/private-content.md | 22 ++--- .../cache/page-caching/public-content.md | 8 +- .../cache/partial-caching.md | 2 +- guides/v2.0/get-started/create-integration.md | 2 +- .../v2.0/install-gde/basics/basics_docroot.md | 4 +- guides/v2.0/install-gde/prereq/dev_install.md | 12 +-- .../install-gde/prereq/install-rabbitmq.md | 16 ++-- guides/v2.0/install-gde/prereq/mysql.md | 22 ++--- guides/v2.0/install-gde/prereq/nginx.md | 2 +- guides/v2.0/install-gde/prereq/php-centos.md | 12 +-- guides/v2.0/install-gde/prereq/php-ubuntu.md | 8 +- .../tutorials/change-docroot-to-pub.md | 4 +- .../migration/migration-tool-internal-spec.md | 4 +- .../migration/migration-troubleshooting.md | 2 +- guides/v2.0/mtf/mtf_entities/mtf_block.md | 16 ++-- guides/v2.1/cloud/access-acct/fastly.md | 36 ++++---- .../cloud/access-acct/first-time-setup.md | 8 +- .../first-time-setup_import-first-steps.md | 2 +- .../first-time-setup_import-prepare.md | 8 +- .../architecture/pro-architecture-legacy.md | 2 +- .../starter-develop-deploy-workflow.md | 6 +- .../cloud/before/before-setup-env-2_clone.md | 6 +- .../before/before-workspace-cloud-account.md | 2 +- guides/v2.1/cloud/cdn/cloud-fastly.md | 8 +- .../cloud/cdn/fastly-image-optimization.md | 6 +- .../configure/cloud-vcl-custom-snippets.md | 22 ++--- .../cloud/configure/configuration-overview.md | 2 +- guides/v2.1/cloud/env/setup-notifications.md | 2 +- guides/v2.1/cloud/env/variables-build.md | 4 +- guides/v2.1/cloud/env/variables-deploy.md | 4 +- guides/v2.1/cloud/howtos/how-to.md | 2 +- .../integrations/bitbucket-integration.md | 4 +- .../cloud/integrations/github-integration.md | 2 +- guides/v2.1/cloud/live/go-live-checklist.md | 2 +- guides/v2.1/cloud/live/sens-data-initial.md | 2 +- .../cloud/live/stage-prod-migrate-prereq.md | 2 +- guides/v2.1/cloud/live/stage-prod-migrate.md | 2 +- .../v2.1/cloud/onboarding/onboarding-tasks.md | 10 +-- guides/v2.1/cloud/project/new-relic.md | 2 +- .../project/project-conf-files_magento-app.md | 82 +++++++++--------- .../project-conf-files_services-elastic.md | 8 +- .../project-conf-files_services-rabbit.md | 2 +- .../project-conf-files_services-redis.md | 2 +- guides/v2.1/cloud/project/project-start.md | 2 +- .../cloud/project/project-webint-basic.md | 2 +- guides/v2.1/cloud/project/projects.md | 2 +- guides/v2.1/cloud/project/sendgrid.md | 4 +- guides/v2.1/cloud/reference/cloud-composer.md | 2 +- .../v2.1/cloud/reference/discover-deploy.md | 2 +- guides/v2.1/cloud/reference/docker-config.md | 12 +-- .../v2.1/cloud/reference/git-integration.md | 16 ++-- .../release-notes/CloudReleaseNotes2.1.2.md | 2 +- .../v2.1/cloud/release-notes/cloud-tools.md | 6 +- .../cloud/requirements/cloud-requirements.md | 6 +- guides/v2.1/cloud/trouble/robots-sitemap.md | 2 +- guides/v2.1/cloud/trouble/trouble_fastly.md | 8 +- guides/v2.1/comp-mgr/install-extensions.md | 4 +- .../v2.1/comp-mgr/prereq/prereq_auth-token.md | 2 +- .../comp-mgr/trouble/cman/tshoot_backup.md | 10 +-- .../comp-mgr/upgrader/ce-ee-upgrade-start.md | 4 +- .../v2.1/config-guide/bootstrap/mage-dirs.md | 2 +- .../config-guide/bootstrap/mage-profiler.md | 6 +- .../bootstrap/magento-bootstrap.md | 18 ++-- .../bootstrap/magento-how-to-set.md | 10 +-- .../v2.1/config-guide/cache/cache-options.md | 4 +- guides/v2.1/config-guide/cache/cache-types.md | 6 +- guides/v2.1/config-guide/secy/secy-cron.md | 12 +-- guides/v2.1/contributor-guide/contributing.md | 16 ++-- .../contributor-guide/devdocs-maintainers.md | 2 +- guides/v2.1/contributor-guide/maintainers.md | 4 +- .../bk-ext-best-practices.md | 2 +- .../build/composer-integration.md | 12 +-- .../extension-dev-guide/cache/page-caching.md | 2 +- .../cache/page-caching/private-content.md | 22 ++--- .../cache/page-caching/public-content.md | 8 +- .../cache/partial-caching.md | 2 +- guides/v2.1/get-started/create-integration.md | 2 +- .../v2.1/install-gde/basics/basics_docroot.md | 4 +- guides/v2.1/install-gde/composer.md | 2 +- .../install/cli/install-cli-install.md | 6 +- guides/v2.1/install-gde/prereq/apache.md | 12 +-- guides/v2.1/install-gde/prereq/dev_install.md | 4 +- .../install-gde/prereq/install-rabbitmq.md | 10 +-- guides/v2.1/install-gde/prereq/mysql.md | 22 ++--- guides/v2.1/install-gde/prereq/nginx.md | 2 +- guides/v2.1/install-gde/prereq/optional.md | 16 ++-- guides/v2.1/install-gde/prereq/php-centos.md | 12 +-- .../v2.1/install-gde/prereq/php-settings.md | 12 +-- guides/v2.1/install-gde/prereq/php-ubuntu.md | 6 +- .../install-gde/prereq/prereq-overview.md | 2 +- .../install-gde/system-requirements-tech.md | 40 ++++----- .../tutorials/change-docroot-to-pub.md | 4 +- .../migration/migration-tool-internal-spec.md | 4 +- .../migration/migration-troubleshooting.md | 2 +- guides/v2.1/mtf/mtf_entities/mtf_block.md | 16 ++-- .../accessibilityGuideline.md | 20 ++--- .../starter-develop-deploy-workflow.md | 6 +- .../cloud/configure/configuration-overview.md | 2 +- guides/v2.2/cloud/env/variables-build.md | 4 +- guides/v2.2/cloud/env/variables-deploy.md | 4 +- guides/v2.2/cloud/live/sens-data-initial.md | 2 +- .../project/project-conf-files_magento-app.md | 82 +++++++++--------- .../project-conf-files_services-elastic.md | 8 +- guides/v2.2/cloud/project/project-start.md | 2 +- guides/v2.2/cloud/project/project-upgrade.md | 2 +- guides/v2.2/cloud/reference/cloud-composer.md | 4 +- .../v2.2/cloud/reference/discover-deploy.md | 2 +- .../release-notes/CloudReleaseNotes2.2.md | 4 +- .../v2.2/cloud/release-notes/cloud-tools.md | 6 +- .../cloud/requirements/cloud-requirements.md | 8 +- guides/v2.2/cloud/trouble/robots-sitemap.md | 2 +- .../comp-mgr/upgrader/ce-ee-upgrade-start.md | 2 +- .../cli/config-cli-subcommands-perf-data.md | 2 +- .../templates/template-sample.md | 2 +- .../frontend-dev-guide/themes/theme-create.md | 8 +- guides/v2.2/get-started/create-integration.md | 2 +- guides/v2.2/install-gde/prereq/mysql.md | 22 ++--- guides/v2.2/install-gde/prereq/nginx.md | 2 +- guides/v2.2/install-gde/prereq/php-centos.md | 12 +-- guides/v2.2/install-gde/prereq/php-ubuntu.md | 6 +- .../install-gde/prereq/prereq-overview.md | 2 +- .../install-gde/system-requirements-tech.md | 56 ++++++------- .../2.3/test/actions.md | 2 +- .../migration/migration-troubleshooting.md | 2 +- guides/v2.3/architecture/tech-stack.md | 2 +- .../cli/config-cli-subcommands-perf-data.md | 2 +- .../config-guide/elasticsearch/es-overview.md | 8 +- .../message-queues/config-mq.md | 6 +- .../message-queues/queue-migration.md | 4 +- .../templates/template-sample.md | 2 +- .../frontend-dev-guide/themes/theme-create.md | 8 +- guides/v2.3/get-started/create-integration.md | 2 +- guides/v2.3/install-gde/prereq/apache.md | 12 +-- .../install-gde/prereq/install-rabbitmq.md | 10 +-- guides/v2.3/install-gde/prereq/mysql.md | 22 ++--- guides/v2.3/install-gde/prereq/nginx.md | 2 +- guides/v2.3/install-gde/prereq/optional.md | 14 ++-- .../install-gde/prereq/php-centos-ubuntu.md | 14 ++-- .../v2.3/install-gde/prereq/php-settings.md | 8 +- .../install-gde/system-requirements-tech.md | 48 +++++------ .../ui_comp_guide/components/ui-wysiwyg.md | 4 +- 189 files changed, 776 insertions(+), 776 deletions(-) diff --git a/Rakefile b/Rakefile index 76165ebd37e..9cb3c75a5e6 100644 --- a/Rakefile +++ b/Rakefile @@ -39,7 +39,7 @@ end desc "Build the entire web site" task build: %w[clean] do print 'Building the site with Jekyll: $ '.magenta - jekyll 'build' + jekyll 'build --verbose' puts 'Built!'.green end diff --git a/_includes/cache/page-cache-overview.md b/_includes/cache/page-cache-overview.md index efd184922bb..049efb9fd1b 100644 --- a/_includes/cache/page-cache-overview.md +++ b/_includes/cache/page-cache-overview.md @@ -23,7 +23,7 @@ To create an uncacheable page, mark any block on that page as uncacheable in the Examples of uncacheable pages include the compare products, cart, {% glossarytooltip 278c3ce0-cd4c-4ffc-a098-695d94d73bde %}checkout{% endglossarytooltip %} pages, and so on. -[Example]({{ site.mage2000url }}app/code/Magento/Paypal/view/frontend/layout/paypal_payflow_returnurl.xml){:target="_blank"} +[Example]({{ site.mage2000url }}app/code/Magento/Paypal/view/frontend/layout/paypal_payflow_returnurl.xml){:target="_blank"}
Do not configure content pages (i.e., catalog, product, and CMS pages) to be uncacheable. Doing so has an adverse affect on performance. diff --git a/_includes/install/auth-tokens-get.md b/_includes/install/auth-tokens-get.md index 153c6966545..1b7ce83891c 100644 --- a/_includes/install/auth-tokens-get.md +++ b/_includes/install/auth-tokens-get.md @@ -2,7 +2,7 @@ The `repo.magento.com` repository is where Magento 2 and third-party Composer pa To create authentication keys: -1. Log in to the [Magento Marketplace](https://marketplace.magento.com){:target="_blank"}. If you don't have an account, click **Register**. +1. Log in to the [Magento Marketplace](https://marketplace.magento.com){:target="_blank"}. If you don't have an account, click **Register**. 2. Click your account name in the top-right of the page and select **My Profile**. 3. Click **Access Keys** in the Marketplace tab. @@ -20,9 +20,9 @@ You can also disable or delete authentication keys. For example, you can disable * To enable a previously disabled key: Click **Enable**. * To delete keys: Click **Delete**. -You cannot delete or disable keys you created by signing in to your [magento.com account](https://www.magentocommerce.com/products/customer/account/login){:target="_blank"}. To manage those keys: +You cannot delete or disable keys you created by signing in to your [magento.com account](https://www.magentocommerce.com/products/customer/account/login){:target="_blank"}. To manage those keys: -1. Log in to your [magento.com account](https://www.magentocommerce.com/products/customer/account/login){:target="_blank"}. +1. Log in to your [magento.com account](https://www.magentocommerce.com/products/customer/account/login){:target="_blank"}. 2. Click **My Account** at the top of the page. 3. Click **Account Settings** > **Downloads Access Token**. diff --git a/_includes/install/composer-overview.md b/_includes/install/composer-overview.md index 5066b32f62f..698d1c79abf 100644 --- a/_includes/install/composer-overview.md +++ b/_includes/install/composer-overview.md @@ -1,4 +1,4 @@ -We use [Composer](https://getcomposer.org/){:target="\_blank"} to manage Magento components and their dependencies. Using Composer to get the Magento software {% glossarytooltip 7490850a-0654-4ce1-83ff-d88c1d7d07fa %}metapackage{% endglossarytooltip %} provides the following advantages: +We use [Composer](https://getcomposer.org/){:target="_blank"} to manage Magento components and their dependencies. Using Composer to get the Magento software {% glossarytooltip 7490850a-0654-4ce1-83ff-d88c1d7d07fa %}metapackage{% endglossarytooltip %} provides the following advantages: - Reuse third-party libraries without bundling them with source code - Reduce extension conflicts and compatibility issues by using a component-based architecture with robust dependency management diff --git a/guides/m1x/ce18-ee113/ce1.8_release-notes.html b/guides/m1x/ce18-ee113/ce1.8_release-notes.html index aadf37d9c57..0fb39bfb6ab 100644 --- a/guides/m1x/ce18-ee113/ce1.8_release-notes.html +++ b/guides/m1x/ce18-ee113/ce1.8_release-notes.html @@ -78,7 +78,7 @@

Discover Card Validation Patch Available

PHP 5.4 Patch Available

You can use PHP 5.4 with Magento CE versions 1.6.0.0–1.8.1.0.

To get the patch, see Getting the PHP 5.4 patch for Magento Enterprise Edition (EE) and Community Edition (CE).

-

For more information about PHP 5.4, see the PHP migration page and the PHP changelog.

+

For more information about PHP 5.4, see the PHP migration page and the PHP changelog.

How to Get Patches For Magento CE

This section discusses how to get patches referenced in these Release Notes.

diff --git a/guides/m1x/ce18-ee113/ee1.13_release-notes.html b/guides/m1x/ce18-ee113/ee1.13_release-notes.html index 3abb3064579..e10f90f471d 100644 --- a/guides/m1x/ce18-ee113/ee1.13_release-notes.html +++ b/guides/m1x/ce18-ee113/ee1.13_release-notes.html @@ -80,7 +80,7 @@

Discover Card Validation Patch Available

PHP 5.4 Patch Available

You can use PHP 5.4 with Magento EE versions 11.0.0.0–1.13.1.0.

To get the patch, see Getting the PHP 5.4 patch for Magento Enterprise Edition (EE) and Community Edition (CE).

-

For more information about PHP 5.4, see the PHP migration page and the PHP changelog.

+

For more information about PHP 5.4, see the PHP migration page and the PHP changelog.

How to get Patches for Magento EE

This section discusses how to get patches referenced in these Release Notes. Magento has other patches available from the EE support portal and the partner portal; you can use the following instructions to install any of those patches as well.

@@ -583,7 +583,7 @@

For More Information about SEO

Known Issue in EE 1.13.0.2

diff --git a/guides/m1x/ce19-ee114/ce1.9_release-notes.html b/guides/m1x/ce19-ee114/ce1.9_release-notes.html index 2930a4aa4e3..457cf2fe744 100644 --- a/guides/m1x/ce19-ee114/ce1.9_release-notes.html +++ b/guides/m1x/ce19-ee114/ce1.9_release-notes.html @@ -551,7 +551,7 @@

Highlights

  • Cross-border trade: (Also referred to as pricing consistency.) We support European Union (EU) merchants operating across regions and geographies who want to show their customers a single price. Pricing is clean and uncluttered regardless of tax structures and rates that vary from country to country.
    To enable cross-border trade in the Admin Panel, click System > Configuration > SALES > Tax > Calculation Settings, option Enable Cross Border Trade.
    • -
  • Supports PHP 5.4. For more information, see the PHP changelog.
    • +
  • Supports PHP 5.4. For more information, see the PHP changelog.
  • The Zend Framework has been upgraded to version 1.12.3
  • Checkout improvements:
    • You can capture up to 18% more sales by providing customers access to financing using the Bill Me Later service at no additional cost to you.
      • diff --git a/guides/m1x/ce19-ee114/ee1.14_release-notes.html b/guides/m1x/ce19-ee114/ee1.14_release-notes.html index 67bfd1a4f1e..7e60c9d6ef7 100644 --- a/guides/m1x/ce19-ee114/ee1.14_release-notes.html +++ b/guides/m1x/ce19-ee114/ee1.14_release-notes.html @@ -600,7 +600,7 @@

      Highlights

      Note: If you're using the Solr search engine with Commerce versions 1.13.1 or earlier, you must perform an additional step during upgrade due to the fact that the Solr schema changes in Commerce 1.14. You must copy two files to your Solr server—schema.xml and solrconfig.xml. For details, see the section on upgrading Solr in the Magento upgrade guide.
    • Cross-border trade: (Also referred to as pricing consistency.) We support European Union (EU) merchants operating across regions and geographies who want to show their customers a single price. Pricing is clean and uncluttered regardless of tax structures and rates that vary from country to country.
      To enable cross-border trade in the Admin Panel, click System > Configuration > SALES > Tax > Calculation Settings, option Enable Cross Border Trade.
      • -
    • Supports PHP 5.4. For more information, see the PHP changelog.
      • +
    • Supports PHP 5.4. For more information, see the PHP changelog.
    • The Zend Framework has been upgraded to version 1.12.3
    • Checkout improvements:
      • You can capture up to 18% more sales by providing customers access to financing using the Bill Me Later service at no additional cost to you.
        • diff --git a/guides/v2.0/cloud/access-acct/fastly.md b/guides/v2.0/cloud/access-acct/fastly.md index 1018623640d..32da2c8af2b 100644 --- a/guides/v2.0/cloud/access-acct/fastly.md +++ b/guides/v2.0/cloud/access-acct/fastly.md @@ -110,11 +110,11 @@ Complete the following configuration steps in Staging and Production environment 4. For **Caching Application**, uncheck the **Use system value** checkbox and select **Fastly CDN** from the drop-down list. ![Choose Fastly]({{ site.baseurl }}/common/images/cloud-fastly_enable-admin.png){:width="550px"} -5. Expand **Fastly Configuration**. You can then [choose caching options](https://github.com/fastly/fastly-magento2/blob/master/Documentation/CONFIGURATION.md#configure-the-module){:target="\_blank"}. +5. Expand **Fastly Configuration**. You can then [choose caching options](https://github.com/fastly/fastly-magento2/blob/master/Documentation/CONFIGURATION.md#configure-the-module){:target="_blank"}. 6. When you're done, click **Save Config** at the top of the page. 7. Clear the cache according to the notification. After you have cleared the cache, navigate back to **Stores** > **Configuration** > **Advanced** > **System** > **Fastly Configuration** and continue your configurations. -Configure the following features and enable additional [configuration options](https://github.com/fastly/fastly-magento2/blob/master/Documentation/CONFIGURATION.md#further-configuration-options){:target="\_blank"}: +Configure the following features and enable additional [configuration options](https://github.com/fastly/fastly-magento2/blob/master/Documentation/CONFIGURATION.md#further-configuration-options){:target="_blank"}: * [Upload Fastly VCL snippets](#upload-vcl-snippets) * [Configure backends and Origin shielding](#backend) @@ -129,7 +129,7 @@ Configure the following features and enable additional [configuration options](h You don't have to create or code VCL snippets. We provide a default set of snippets for Fastly. You only need to click **Upload VCL to Fastly** to finish this step. -The installed Fastly module includes the following default [VCL snippets](https://github.com/fastly/fastly-magento2/tree/master/etc/vcl_snippets){:target="\blank"} that drive the integration with Fastly. These VCL snippets are not available until you upload them. When you click Upload, you push a set of these default VCL snippets to Fastly for your specific Service ID and extension. +The installed Fastly module includes the following default [VCL snippets](https://github.com/fastly/fastly-magento2/tree/master/etc/vcl_snippets){:target="_blank"} that drive the integration with Fastly. These VCL snippets are not available until you upload them. When you click Upload, you push a set of these default VCL snippets to Fastly for your specific Service ID and extension. For VCL snippet developers, these default snippets are prepended with `magentomodule_` with a priority of 50. You should not use this prepended name for your own snippets. For full details, see our guide to create and add [custom VCL snippets](#custom-vcl). @@ -147,7 +147,7 @@ To use snippets, you must upload the Fastly VCL using the Magento Admin as follo With this uploaded, you can create and upload custom VCL snippets with advanced settings and options. You use APIs to add these VCL snippets, further adding them in your site code depending on the actions. -For more information, see [Fastly VCL documentation](https://docs.fastly.com/guides/vcl/guide-to-vcl){:target="\_blank"} and [Fastly VCL snippets](https://docs.fastly.com/guides/vcl-snippets/about-vcl-snippets){:target="\_blank"}. +For more information, see [Fastly VCL documentation](https://docs.fastly.com/guides/vcl/guide-to-vcl){:target="_blank"} and [Fastly VCL snippets](https://docs.fastly.com/guides/vcl-snippets/about-vcl-snippets){:target="_blank"}. ## Configure backends and Origin shielding {#backend} @@ -171,7 +171,7 @@ You can add multiple backends. Repeat these instructions to create multiple back 6. Click **Upload** to save. The settings are communicated to Fastly. 7. In the Magento Admin, click **Save Config**. -For more information from Fastly, see the Magento 2 [Backend settings guide](https://github.com/fastly/fastly-magento2/blob/21b61c8189971275589219d418332798efc7db41/Documentation/Guides/BACKEND-SETTINGS.md){:target="\_blank"}. +For more information from Fastly, see the Magento 2 [Backend settings guide](https://github.com/fastly/fastly-magento2/blob/21b61c8189971275589219d418332798efc7db41/Documentation/Guides/BACKEND-SETTINGS.md){:target="_blank"}. ## Configure purge options {#purge} @@ -193,7 +193,7 @@ To configure Fastly purge options: 3. Click **Save Config** at the top of the page. 4. After the page reloads, click **Upload VCL to Fastly** in the *Fastly Configuration* section. -For more information, see [Fastly's configuration options](https://github.com/fastly/fastly-magento2/blob/21b61c8189971275589219d418332798efc7db41/Documentation/CONFIGURATION.md#further-configuration-options){:target="\_blank"}. +For more information, see [Fastly's configuration options](https://github.com/fastly/fastly-magento2/blob/21b61c8189971275589219d418332798efc7db41/Documentation/CONFIGURATION.md#further-configuration-options){:target="_blank"}. ## Create a custom error/maintenance page {#fastly-errpg} @@ -208,7 +208,7 @@ To create a custom error/maintenance page: 3. In the provided field, enter your HTML code. The HTML you enter can be a maximum of 65,535 bytes in length.
        - Avoid using images on your site in the event Fastly is not available. To use images, refer to [Data URIs on the css-tricks site](https://css-tricks.com/data-uris/){:target="\_blank"}. + Avoid using images on your site in the event Fastly is not available. To use images, refer to [Data URIs on the css-tricks site](https://css-tricks.com/data-uris/){:target="_blank"}.
        4. When you're done, click **Upload** to send your updates to Fastly. 5. Click **Save Config** at the top of the page. @@ -235,13 +235,13 @@ The Fastly module includes GeoIP handling to automatically redirect visitors or 1. In the **Fastly Configuration** section, expand **Advanced**. 2. Scroll down and select **Yes** to **Enable GeoIP**. Additional configuration options display. 3. For GeoIP Action, select if the visitor is automatically redirected with **Redirect** or provided a list of stores to select from with **Dialog**. -4. For **Country Mapping**, click **Add** to enter a two-letter country code to map with a specific Magento store from a list. For a list of country codes, see [this site](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2){:target="\_blank"}. +4. For **Country Mapping**, click **Add** to enter a two-letter country code to map with a specific Magento store from a list. For a list of country codes, see [this site](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2){:target="_blank"}. ![Add GeoIP country maps]({{ site.baseurl }}/common/images/cloud_fastly-geo-code.png) 5. Click **Save Config** at the top of the page. 6. After page reload, click *Upload VCL to Fastly* in the *Fastly Configuration* section. -Fastly also provides a series of [geolocation-related VCL features](https://docs.fastly.com/guides/vcl/geolocation-related-vcl-features){:target="\_blank"} for customized geolocation coding. +Fastly also provides a series of [geolocation-related VCL features](https://docs.fastly.com/guides/vcl/geolocation-related-vcl-features){:target="_blank"} for customized geolocation coding. ## Configure DNS for Fastly {#fastly-dns} @@ -275,11 +275,11 @@ Refer to [Go live checklist]({{ page.baseurl }}/cloud/live/go-live-checklist.htm If you use TLS with Fastly enabled in your environment, you must provide your DNS provider with a TXT record from Fastly. We provide a Domain Validated SSL certificate with Subject Alternative Name enabled, issued by GLobalSign. When entering your [Support ticket]({{ page.baseurl }}/cloud/trouble/trouble.html) for [DNS information](#fastly-dns) and going live, let us know you are using TLS, provide your domain names, and request the TXT record. You can then send this record to your DNS provider. The domain validation process is executed by Fastly. -For details on this TXT record, see Fastly's [DNS TXT record validation](https://docs.fastly.com/guides/securing-communications/domain-validation-for-tls-certificates#dns-text-record-verification){:target="\_blank"}. +For details on this TXT record, see Fastly's [DNS TXT record validation](https://docs.fastly.com/guides/securing-communications/domain-validation-for-tls-certificates#dns-text-record-verification){:target="_blank"}. ## Upgrade Fastly {#upgrade} -Fastly updates the Magento module to resolve issues, increase performance, and provide new features. You can check the [Magento Marketplace](https://marketplace.magento.com/fastly-magento2.html){:target="\_blank"} and [GitHub](https://github.com/fastly/fastly-magento2/releases){:target="\_blank"} for updates on the latest releases. +Fastly updates the Magento module to resolve issues, increase performance, and provide new features. You can check the [Magento Marketplace](https://marketplace.magento.com/fastly-magento2.html){:target="_blank"} and [GitHub](https://github.com/fastly/fastly-magento2/releases){:target="_blank"} for updates on the latest releases. When you upgrade Fastly, you get the upgraded subset of default VCL snippets. When you finish upgrading, you must [upload upgraded default VCL snippets to Fastly](#upload-vcl-snippets): diff --git a/guides/v2.0/cloud/access-acct/first-time-setup.md b/guides/v2.0/cloud/access-acct/first-time-setup.md index d8362db8040..15fccd6bc4c 100644 --- a/guides/v2.0/cloud/access-acct/first-time-setup.md +++ b/guides/v2.0/cloud/access-acct/first-time-setup.md @@ -30,10 +30,10 @@ After you receive an invitation, you can complete tasks to create your local, pu We highly recommend having experience with the following technologies and methodologies: * Magento [technology stack]({{ page.baseurl }}/architecture/tech-stack.html) -* [Git](https://git-scm.com/){:target="\_blank"} for repository and code management, [branching methodologies](https://git-scm.com/book/en/v2/Git-Branching-Branching-Workflows){:target="\_blank"}, and working with Magento Git code -* [GitHub](https://github.com/){:target="\_blank"} for managing your code and accessing Magento repos -* [Fastly](https://www.fastly.com/){:target="\_blank"} for CDN and caching, used in Staging and Production -* [Galera Cluster](http://galeracluster.com/){:target="\_blank"} for databases, used in Staging and Production (with triple redundancy failover in Production) +* [Git](https://git-scm.com/){:target="_blank"} for repository and code management, [branching methodologies](https://git-scm.com/book/en/v2/Git-Branching-Branching-Workflows){:target="_blank"}, and working with Magento Git code +* [GitHub](https://github.com/){:target="_blank"} for managing your code and accessing Magento repos +* [Fastly](https://www.fastly.com/){:target="_blank"} for CDN and caching, used in Staging and Production +* [Galera Cluster](http://galeracluster.com/){:target="_blank"} for databases, used in Staging and Production (with triple redundancy failover in Production) ## Gather credentials {#credentials} diff --git a/guides/v2.0/cloud/access-acct/first-time-setup_import-first-steps.md b/guides/v2.0/cloud/access-acct/first-time-setup_import-first-steps.md index 42f5d00543b..5d2ad8c7aa4 100644 --- a/guides/v2.0/cloud/access-acct/first-time-setup_import-first-steps.md +++ b/guides/v2.0/cloud/access-acct/first-time-setup_import-first-steps.md @@ -92,7 +92,7 @@ The complete workflow for importing existing code includes the following steps: ## Create a new {{site.data.var.ece}} project {#cloud-import-proj} -1. Access your account. Open the email you received from Magento Cloud (accounts@magento.cloud) and click the _Access your project now_ link. Or you can log in to [your Magento Commerce account](https://accounts.magento.cloud){:target="\_blank"}. +1. Access your account. Open the email you received from Magento Cloud (accounts@magento.cloud) and click the _Access your project now_ link. Or you can log in to [your Magento Commerce account](https://accounts.magento.cloud){:target="_blank"}. 1. Click the _This project has no code yet_ link next to the project name. diff --git a/guides/v2.0/cloud/access-acct/first-time-setup_import-prepare.md b/guides/v2.0/cloud/access-acct/first-time-setup_import-prepare.md index 5d016103773..25af15ec9e2 100644 --- a/guides/v2.0/cloud/access-acct/first-time-setup_import-prepare.md +++ b/guides/v2.0/cloud/access-acct/first-time-setup_import-prepare.md @@ -37,7 +37,7 @@ To import {{site.data.var.ee}} code to a {{site.data.var.ece}} project, you need You need to add these files to your {{site.data.var.ee}} code: -1. Go to the [{{site.data.var.ece}} GitHub](https://github.com/magento/magento-cloud){:target="\_blank"}. +1. Go to the [{{site.data.var.ece}} GitHub](https://github.com/magento/magento-cloud){:target="_blank"}. 2. Select the branch corresponding to the {{site.data.var.ee}} version you currently have. The following figure shows an example of selecting the `2.1.4` branch. @@ -59,7 +59,7 @@ You need to add these files to your {{site.data.var.ee}} code: For example, to create `/.magento.app.yaml` from the 2.1.4 branch: - 1. In the {{site.data.var.ece}} GitHub, click [**.magento.app.yaml**](https://github.com/magento/magento-cloud/blob/2.1.4/.magento.app.yaml){:target="\_blank"}. + 1. In the {{site.data.var.ece}} GitHub, click [**.magento.app.yaml**](https://github.com/magento/magento-cloud/blob/2.1.4/.magento.app.yaml){:target="_blank"}. 2. In the upper right, click **Raw**, as the following figure shows. ![View the raw version of the file]({{ site.baseurl }}/common/images/cloud_cloud-git_raw.png){:width="600px"} @@ -83,7 +83,7 @@ When you push your code, all services are configured into the associated environ To enable install and update commands for {{site.data.var.ece}}, you must have an `auth.json` file in your project's root directory. `auth.json` contains your {{site.data.var.ee}} [authorization credentials]({{ site.baseurl }}/guides/v2.1/install-gde/prereq/connect-auth.html) for {{site.data.var.ece}}. -In some cases, you might already have `auth.json`. Verify if you have the file and add your authentication credentials before you create a new one. It's located in your Magento root directory. You can also [get a sample `auth.json`](https://raw.githubusercontent.com/magento/magento-cloud/master/auth.json.sample){:target="\_blank"}. +In some cases, you might already have `auth.json`. Verify if you have the file and add your authentication credentials before you create a new one. It's located in your Magento root directory. You can also [get a sample `auth.json`](https://raw.githubusercontent.com/magento/magento-cloud/master/auth.json.sample){:target="_blank"}. To create a new `auth.json` in the {% glossarytooltip c57aef7c-97b4-4b2b-a999-8001accef1fe %}event{% endglossarytooltip %} you don't have one: @@ -104,7 +104,7 @@ To create a new `auth.json` in the {% glossarytooltip c57aef7c-97b4-4b2b-a999-80 ## Edit `composer.json` {#composer-json} -Before you push code to the {{site.data.var.ece}} Git repository, modify your `composer.json` for Cloud. You can also [view a sample `composer.json`](https://raw.githubusercontent.com/magento/magento-cloud/master/composer.json){:target="\_blank"}. +Before you push code to the {{site.data.var.ece}} Git repository, modify your `composer.json` for Cloud. You can also [view a sample `composer.json`](https://raw.githubusercontent.com/magento/magento-cloud/master/composer.json){:target="_blank"}. To edit `composer.json`: diff --git a/guides/v2.0/cloud/architecture/pro-architecture-legacy.md b/guides/v2.0/cloud/architecture/pro-architecture-legacy.md index c92fcf11e04..f147c078ecc 100644 --- a/guides/v2.0/cloud/architecture/pro-architecture-legacy.md +++ b/guides/v2.0/cloud/architecture/pro-architecture-legacy.md @@ -163,7 +163,7 @@ The following figure shows the technology used in the Production environment: {{site.data.var.ee}} seamlessly scales from the smallest 6 CPU cluster with 11.25GB of RAM to the largest 96 CPU cluster with 180GB of RAM. Our triple-redundant architecture means we can offer upscaling without downtime. When upscaling, we rotate each of the three instances to upgrade without downtime of your site. -In addition, extra web servers can be added to an existing cluster should the constriction be at the {% glossarytooltip bf703ab1-ca4b-48f9-b2b7-16a81fd46e02 %}PHP{% endglossarytooltip %} level rather than the database level. This provides [*horizontal scaling*](https://en.wikipedia.org/wiki/Scalability#Horizontal_and_vertical_scaling){:target="\_blank"} to complement the vertical scaling provided by extra CPUs on the database level. +In addition, extra web servers can be added to an existing cluster should the constriction be at the {% glossarytooltip bf703ab1-ca4b-48f9-b2b7-16a81fd46e02 %}PHP{% endglossarytooltip %} level rather than the database level. This provides [*horizontal scaling*](https://en.wikipedia.org/wiki/Scalability#Horizontal_and_vertical_scaling){:target="_blank"} to complement the vertical scaling provided by extra CPUs on the database level. ## Services {#cloud-arch-services} {{site.data.var.ece}} currently supports the following services: diff --git a/guides/v2.0/cloud/basic-information/starter-develop-deploy-workflow.md b/guides/v2.0/cloud/basic-information/starter-develop-deploy-workflow.md index 200e1560dc1..cd197041cfd 100644 --- a/guides/v2.0/cloud/basic-information/starter-develop-deploy-workflow.md +++ b/guides/v2.0/cloud/basic-information/starter-develop-deploy-workflow.md @@ -122,9 +122,9 @@ When you are ready to configure your store, have all code pushed to your Integra For the best information on configurations, we recommend reviewing {{site.data.var.ee}} and your extension documentation. Here are some links and ideas to help you get kickstarted: * [Best practices for store configuration]({{ page.baseurl }}/cloud/configure/configure-best-practices.html) for specific best practices in the cloud -* [Basic configuration](http://docs.magento.com/m2/ee/user_guide/configuration/configuration-basic.html){:target="\_blank"} for store admin access, name, languages, currencies, branding, sites, store views and more -* [Theme](http://docs.magento.com/m2/ee/user_guide/design/design-theme.html){:target="\_blank"} for your look and feel of the site and stores including CSS and layouts -* [System configuration](http://docs.magento.com/m2/ee/user_guide/system/system.html){:target="\_blank"} for roles, tools, notifications, and your encryption key for your database +* [Basic configuration](http://docs.magento.com/m2/ee/user_guide/configuration/configuration-basic.html){:target="_blank"} for store admin access, name, languages, currencies, branding, sites, store views and more +* [Theme](http://docs.magento.com/m2/ee/user_guide/design/design-theme.html){:target="_blank"} for your look and feel of the site and stores including CSS and layouts +* [System configuration](http://docs.magento.com/m2/ee/user_guide/system/system.html){:target="_blank"} for roles, tools, notifications, and your encryption key for your database * Extension settings using their documentation Beyond just store settings, you can further configure multiple sites and stores, configured services, and more. For details, see [Configure Magento Commerce]({{ page.baseurl }}/cloud/configure/configuration-overview.html). diff --git a/guides/v2.0/cloud/before/before-setup-env-2_clone.md b/guides/v2.0/cloud/before/before-setup-env-2_clone.md index b755813df3d..c1acdcc178b 100644 --- a/guides/v2.0/cloud/before/before-setup-env-2_clone.md +++ b/guides/v2.0/cloud/before/before-setup-env-2_clone.md @@ -22,7 +22,7 @@ functional_areas: The Magento Commerce project is a Git repository of Magento code with a master origin. Develop your custom code and add extensions in one of eight active Git branches in your local. Each active environment includes a database and services to fully access the Magento site and store in the Integration environment. -To begin, you need to clone the `master` environment to your local and add the Magento Admin URL, username, and password (to include with all branches). If you are new to Git workflow, processes, and commands, see Git [documentation](https://git-scm.com/documentation){:target="\_blank"}. +To begin, you need to clone the `master` environment to your local and add the Magento Admin URL, username, and password (to include with all branches). If you are new to Git workflow, processes, and commands, see Git [documentation](https://git-scm.com/documentation){:target="_blank"}. The commands in these instructions use Magento CLI commands and Git commands to access the `master` environment. For a full list of Magento Cloud CLI commands, enter `magento-cloud list` or see the [Magento CLI reference]({{ page.baseurl }}/cloud/reference/cli-ref-topic.html). @@ -90,7 +90,7 @@ To set Admin variables, you will use this command format: magento-cloud variable:set -e -You can also [log into your project](https://accounts.magento.cloud){:target="\_blank"} in the Project Web Interface to review project variables entered there. Click the Configure environment gear icon ![Configure your environment]({{ site.baseurl }}/common/images/cloud_edit-project.png) next to the Project name. Click the **Variables** tab and review any configured variables there. +You can also [log into your project](https://accounts.magento.cloud){:target="_blank"} in the Project Web Interface to review project variables entered there. Click the Configure environment gear icon ![Configure your environment]({{ site.baseurl }}/common/images/cloud_edit-project.png) next to the Project name. Click the **Variables** tab and review any configured variables there.
        Everytime you add or modify a variable using the web interface or the CLI, the branch will redeploy automatically. @@ -141,7 +141,7 @@ To set variables using the CLI (with example values used): To set variables using the Project Web Interface: -1. Log in to [your {{site.data.var.ece}} account](https://accounts.magento.cloud){:target="\_blank"}. +1. Log in to [your {{site.data.var.ece}} account](https://accounts.magento.cloud){:target="_blank"}. 2. Click the Configure environment gear icon ![Configure your environment]({{ site.baseurl }}/common/images/cloud_edit-project.png) next to the Project name. If you are asked to create the project, click **Continue Later**. ![Project without code]({{ site.baseurl }}/common/images/cloud_project_empty.png) diff --git a/guides/v2.0/cloud/before/before-workspace-cloud-account.md b/guides/v2.0/cloud/before/before-workspace-cloud-account.md index 047577c99a8..45686e49dda 100644 --- a/guides/v2.0/cloud/before/before-workspace-cloud-account.md +++ b/guides/v2.0/cloud/before/before-workspace-cloud-account.md @@ -12,7 +12,7 @@ menu_node: #### Previous step: [Prepare for local environment setup]({{ page.baseurl }}/cloud/before/before-workspace.html) -To begin working with a project and develop your store, you should have received an e-mail invitation to [create a Mangento Enterprise Cloud Edition account](https://accounts.magento.cloud){:target="\_blank"}. The account provides access to your project for Magento development and deployment across all supported environments. +To begin working with a project and develop your store, you should have received an e-mail invitation to [create a Mangento Enterprise Cloud Edition account](https://accounts.magento.cloud){:target="_blank"}. The account provides access to your project for Magento development and deployment across all supported environments. You should receive an e-mail invitation to verify and access the account. If you don't see the invitation, check your junk e-mail folder. Click the **Verify my account** option in the email to verify and access your account. diff --git a/guides/v2.0/cloud/configure/cloud-vcl-custom-snippets.md b/guides/v2.0/cloud/configure/cloud-vcl-custom-snippets.md index 0f6da034659..4a366238ed4 100644 --- a/guides/v2.0/cloud/configure/cloud-vcl-custom-snippets.md +++ b/guides/v2.0/cloud/configure/cloud-vcl-custom-snippets.md @@ -106,7 +106,7 @@ The following are **best practices and recommendations**: - The default VCL snippets you uploaded include a prepended name of `magentomodule_` with a priority of `50`. For your custom VCL snippets, **do not use the `magentomodule_` name**. Also, consider the priority of your custom snippets and whether they should override the default snippets. - Do not forget to _always_ locate and clone the active version, and edit the bash script with the new version! _Version_ is not part of your VCL snippet files. -- If you want to override values and settings from the [default Fastly VCL snippets](https://github.com/fastly/fastly-magento2/tree/master/etc/vcl_snippets){:target="\_blank"}, we recommend creating a new snippet with updated values and code with a higher priority value of `100`. You should not try to override default VCLs. We provide an example for [Custom extend Admin timeout VCL]({{ page.baseurl }}/cloud/configure/fastly-vcl-extend-timeout.html). +- If you want to override values and settings from the [default Fastly VCL snippets](https://github.com/fastly/fastly-magento2/tree/master/etc/vcl_snippets){:target="_blank"}, we recommend creating a new snippet with updated values and code with a higher priority value of `100`. You should not try to override default VCLs. We provide an example for [Custom extend Admin timeout VCL]({{ page.baseurl }}/cloud/configure/fastly-vcl-extend-timeout.html). ## Export Fastly Service ID and API Token @@ -127,7 +127,7 @@ To view a list of all VCL snippets by version: Look for the `active` key from the returned list. You need the version to perform a clone in the next section. -For more information on this Fastly API, see this [get version command](https://docs.fastly.com/api/config#version_dfde9093f4eb0aa2497bbfd1d9415987){:target="\_blank"}. +For more information on this Fastly API, see this [get version command](https://docs.fastly.com/api/config#version_dfde9093f4eb0aa2497bbfd1d9415987){:target="_blank"}. ## Clone the active VCL version and all snippets {#clone} @@ -139,7 +139,7 @@ You can save the new version into a bash environment variable for use in cURL co export FASTLY_VERSION= -For more information on this Fastly API, see this [clone command](https://docs.fastly.com/api/config#version_7f4937d0663a27fbb765820d4c76c709){:target="\_blank"}. +For more information on this Fastly API, see this [clone command](https://docs.fastly.com/api/config#version_7f4937d0663a27fbb765820d4c76c709){:target="_blank"}. ### Create custom VCL snippets {#create-snippet} @@ -159,7 +159,7 @@ The values include: - `name`—Name for the VCL snippet. - `dynamic`—Indicates if this is a dynamic snippet or regular snippet. -- `type`—Specifies a location for the generated snippet, such as `init` (above subroutines) and `recv` (within subroutines). See [Fastly VCL snippet object values](https://docs.fastly.com/api/config#snippet){:target="\_blank"} for information on these values. +- `type`—Specifies a location for the generated snippet, such as `init` (above subroutines) and `recv` (within subroutines). See [Fastly VCL snippet object values](https://docs.fastly.com/api/config#snippet){:target="_blank"} for information on these values. - `priority`—Determines the order VCL snippets call. Lower values run first, from `1` to `100`. All uploaded snippets from a Magento module have a value of `50`. If you want an action to occur last or to override Magento default VCL snippets, use a higher number, such as `100`. To have code occur immediately, use a lower value, such as `5`. - `content`—The snippet of VCL code to run in one line, without line breaks. @@ -211,7 +211,7 @@ To update a snippet, modify the JSON file you prepared on the [Create VCL snippe curl -H "Fastly-Key: ${FASTLY_API_TOKEN}" https://api.fastly.com/service/${FASTLY_SERVICE_ID}/version/${FASTLY_VERSION}/snippet/ -H 'Content-Type: application/json' -X PUT --data @ -If you want to override values and settings from the [default Fastly VCL snippets](https://github.com/fastly/fastly-magento2/tree/master/etc/vcl_snippets){:target="\_blank"}, we recommend creating a new snippet with updated values and code that use a priority of `100`. +If you want to override values and settings from the [default Fastly VCL snippets](https://github.com/fastly/fastly-magento2/tree/master/etc/vcl_snippets){:target="_blank"}, we recommend creating a new snippet with updated values and code that use a priority of `100`. To delete an individual VCL snippet using the API, get a list of snippets and enter a `curl` command with the specific snippet name to delete: @@ -221,12 +221,12 @@ To delete an individual VCL snippet using the API, get a list of snippets and en You can learn more about creating VCL snippets with the following Fastly resources: -- [All Fastly VCL content](https://docs.fastly.com/guides/vcl/){:target="\_blank"} -- [Fastly VCL guide](https://docs.fastly.com/guides/vcl/guide-to-vcl){:target="\_blank"} -- [Mixing and matching Fastly VCL with custom VCL](https://docs.fastly.com/guides/vcl/mixing-and-matching-fastly-vcl-with-custom-vcl){:target="\_blank"} -- [Fastly VCL snippet object values](https://docs.fastly.com/api/config#snippet){:target="\_blank"} +- [All Fastly VCL content](https://docs.fastly.com/guides/vcl/){:target="_blank"} +- [Fastly VCL guide](https://docs.fastly.com/guides/vcl/guide-to-vcl){:target="_blank"} +- [Mixing and matching Fastly VCL with custom VCL](https://docs.fastly.com/guides/vcl/mixing-and-matching-fastly-vcl-with-custom-vcl){:target="_blank"} +- [Fastly VCL snippet object values](https://docs.fastly.com/api/config#snippet){:target="_blank"} Fastly supports two types of snippets: -- [Regular snippets](https://docs.fastly.com/guides/vcl-snippets/using-regular-vcl-snippets){:target="\_blank"} are versioned VCL snippets. The code and settings are locked per version to create, modify, and deploy with the Fastly service. -- [Dynamic snippets](https://docs.fastly.com/guides/vcl-snippets/using-dynamic-vcl-snippets){:target="\_blank"} are snippets you can only create via API calls. These snippets do not have a version and deploy separately from your Fastly service. +- [Regular snippets](https://docs.fastly.com/guides/vcl-snippets/using-regular-vcl-snippets){:target="_blank"} are versioned VCL snippets. The code and settings are locked per version to create, modify, and deploy with the Fastly service. +- [Dynamic snippets](https://docs.fastly.com/guides/vcl-snippets/using-dynamic-vcl-snippets){:target="_blank"} are snippets you can only create via API calls. These snippets do not have a version and deploy separately from your Fastly service. diff --git a/guides/v2.0/cloud/howtos/how-to.md b/guides/v2.0/cloud/howtos/how-to.md index 340a1e36fd7..ea0d746debf 100644 --- a/guides/v2.0/cloud/howtos/how-to.md +++ b/guides/v2.0/cloud/howtos/how-to.md @@ -11,7 +11,7 @@ functional_areas: These topics are intended to get you up to speed quickly using {{site.data.var.ece}}. These are step-by-step instructions that provide instructions about specific tasks or that explain how to achieve a goal. -Have suggestions? Open [an issue](https://github.com/magento/devdocs/issues){:target="\_blank"} or click the **Edit this page on GitHub** link and give us feedback directly. +Have suggestions? Open [an issue](https://github.com/magento/devdocs/issues){:target="_blank"} or click the **Edit this page on GitHub** link and give us feedback directly. Current topics: diff --git a/guides/v2.0/cloud/live/stage-prod-migrate-prereq.md b/guides/v2.0/cloud/live/stage-prod-migrate-prereq.md index 0ba2f126960..06d0d4d7776 100644 --- a/guides/v2.0/cloud/live/stage-prod-migrate-prereq.md +++ b/guides/v2.0/cloud/live/stage-prod-migrate-prereq.md @@ -33,7 +33,7 @@ To prepare your environments for full deployment, you need: You can locate your URLs through the Project Web Interface. For each selected environment or branch, you will find an Access Site link. Your environments begin with Master, which is Production, and any additional branches you create, including Staging (recommended) and development branches for custom code. -1. Log in to [your {{site.data.var.ece}} account](https://accounts.magento.cloud){:target="\_blank"}. +1. Log in to [your {{site.data.var.ece}} account](https://accounts.magento.cloud){:target="_blank"}. 2. Select an environment. 3. Click **Access site** to display the URL and SSH information. diff --git a/guides/v2.0/cloud/live/stage-prod-migrate.md b/guides/v2.0/cloud/live/stage-prod-migrate.md index e2bfbe14b9c..d97dd84c0b4 100644 --- a/guides/v2.0/cloud/live/stage-prod-migrate.md +++ b/guides/v2.0/cloud/live/stage-prod-migrate.md @@ -103,7 +103,7 @@ For these environments, you are pushing code from repository to repository: Inte You will migrate {% glossarytooltip 363662cb-73f1-4347-a15e-2d2adabeb0c2 %}static files{% endglossarytooltip %} from your `pub/media` directory to Staging or Production. -We recommend using the Linux remote synchronization and file transfer command [`rsync`](https://en.wikipedia.org/wiki/Rsync){:target="\_blank"}. rsync uses an algorithm that minimizes the amount of data by moving only the portions of files that have changed; in addition, it supports compression. +We recommend using the Linux remote synchronization and file transfer command [`rsync`](https://en.wikipedia.org/wiki/Rsync){:target="_blank"}. rsync uses an algorithm that minimizes the amount of data by moving only the portions of files that have changed; in addition, it supports compression. We suggest using the following syntax: @@ -116,7 +116,7 @@ Options: v verbose P partial progress -For additional options, see the [rsync man page](http://linux.die.net/man/1/rsync){:target="\_blank"}. +For additional options, see the [rsync man page](http://linux.die.net/man/1/rsync){:target="_blank"}. To migrate static files: @@ -132,7 +132,7 @@ To migrate static files: ## Migrate the database {#cloud-live-migrate-db} -**Prerequisite:** A database dump (see Step 3) should include database triggers. For dumping them, make sure you have the [TRIGGER privilege](https://dev.mysql.com/doc/refman/5.7/en/privileges-provided.html#priv_trigger){:target="\_blank"}. +**Prerequisite:** A database dump (see Step 3) should include database triggers. For dumping them, make sure you have the [TRIGGER privilege](https://dev.mysql.com/doc/refman/5.7/en/privileges-provided.html#priv_trigger){:target="_blank"}. **Important:** The Integration environment database is strictly for development testing and may include data you may not want to migrate into Staging and Production. diff --git a/guides/v2.0/cloud/onboarding/onboarding-tasks.md b/guides/v2.0/cloud/onboarding/onboarding-tasks.md index c8b8f223be0..81abb020316 100644 --- a/guides/v2.0/cloud/onboarding/onboarding-tasks.md +++ b/guides/v2.0/cloud/onboarding/onboarding-tasks.md @@ -21,19 +21,19 @@ To quickly onboard your project to start developing your site and going live, yo The _Project Owner_ is typically a "business user" in your business or finance organization that purchased the subscription and is your point of contact with Magento regarding the account overall. The owner can add user accounts to provide access to code, manage branches, enter tickets, and support environments. These user accounts can include in-house development, consultants, and Magento solution specialists. -Typically, the only user the Project Owner must create is the _Technical Admin_. This user should have a user account with the Super User role. Your Technical Admin can create user accounts for developers, set environment permissions, and manage all branches and environments. Typically, the Technical Admin is a developer, consultant, a [Magento Solution Partner](https://magento.com/find-a-partner){:target="\_blank"}, or yourself. +Typically, the only user the Project Owner must create is the _Technical Admin_. This user should have a user account with the Super User role. Your Technical Admin can create user accounts for developers, set environment permissions, and manage all branches and environments. Typically, the Technical Admin is a developer, consultant, a [Magento Solution Partner](https://magento.com/find-a-partner){:target="_blank"}, or yourself. ## Sign up for a Magento Commerce (Cloud) account {#cloud-first-acct} -Don't have a {{site.data.var.ece}} account yet? Contact [Magento Sales](https://magento.com/explore/contact-sales){:target="\_blank"}. We will create your account and send you a welcome email that provides instructions to access the project. +Don't have a {{site.data.var.ece}} account yet? Contact [Magento Sales](https://magento.com/explore/contact-sales){:target="_blank"}. We will create your account and send you a welcome email that provides instructions to access the project. -The person who signs up for a {{site.data.var.ece}} account is referred to as the _Project Owner_. You receive a welcome e-mail that enables you to set up the project initially. You can also access your project by [logging in to your account](https://accounts.magento.cloud){:target="\_blank"}. +The person who signs up for a {{site.data.var.ece}} account is referred to as the _Project Owner_. You receive a welcome e-mail that enables you to set up the project initially. You can also access your project by [logging in to your account](https://accounts.magento.cloud){:target="_blank"}. ## Your welcome e-mail {#email} After you register for an account, Magento sends you a welcome e-mail at the address at which you registered. The e-mail contains a link to your {{site.data.var.ece}} project. -You can also access your project by [logging in to your account](https://accounts.magento.cloud){:target="\_blank"}. +You can also access your project by [logging in to your account](https://accounts.magento.cloud){:target="_blank"}. ## Get started with the Project Web Interface {#project-setup} @@ -49,7 +49,7 @@ We recommend creating a user account with Super User access as your Technical Ad We provide an {{site.data.var.ece}} environment and service status site. Anyone working on your site and project can subscribe on the site for email notifications and updates. We recommend subscribing and adding a bookmark to check the page daily or as needed. -The site location is [https://status.magento.cloud/](https://status.magento.cloud/){:target="\_blank"}. Scroll to the bottom and click [Subscribe](http://status.magento.cloud/subscribe){:target="\_blank"} at the bottom of the page. Complete the prompts with your email address and types of notifications you want to receive. +The site location is [https://status.magento.cloud/](https://status.magento.cloud/){:target="_blank"}. Scroll to the bottom and click [Subscribe](http://status.magento.cloud/subscribe){:target="_blank"} at the bottom of the page. Complete the prompts with your email address and types of notifications you want to receive. The page lists all component and service status. Any issues, updates, and notices are displayed below these status tables by date. For example, any slow issues, outages, or upgraded services are listed with important information and any updates as available. diff --git a/guides/v2.0/cloud/project/bitbucket-integration.md b/guides/v2.0/cloud/project/bitbucket-integration.md index 8942853f261..253bf8db6db 100644 --- a/guides/v2.0/cloud/project/bitbucket-integration.md +++ b/guides/v2.0/cloud/project/bitbucket-integration.md @@ -22,7 +22,7 @@ We _strongly_ recommend using a private Bitbucket repository for your {{site.dat ## Prepare your repository -This section shows you how to clone your {{site.data.var.ece}} project from and existing environment and add that code to a new, empty Bitbucket repository. If you don't already have an empty Bitbucket repository, [create one](https://confluence.atlassian.com/bitbucket/create-a-git-repository-759857290.html){:target="\_blank"} before proceeding. +This section shows you how to clone your {{site.data.var.ece}} project from and existing environment and add that code to a new, empty Bitbucket repository. If you don't already have an empty Bitbucket repository, [create one](https://confluence.atlassian.com/bitbucket/create-a-git-repository-759857290.html){:target="_blank"} before proceeding. 1. Open a terminal and log in to your {{site.data.var.ece}} project: @@ -61,9 +61,9 @@ This section shows you how to clone your {{site.data.var.ece}} project from and ## Create an OAuth consumer -The Bitbucket integration requires an [OAuth consumer](https://confluence.atlassian.com/x/pwIwDg){:target="\_blank"}. This section shows you how to create one in Bitbucket. You'll need the OAuth `key` and `secret` from this consumer to complete the next section. +The Bitbucket integration requires an [OAuth consumer](https://confluence.atlassian.com/x/pwIwDg){:target="_blank"}. This section shows you how to create one in Bitbucket. You'll need the OAuth `key` and `secret` from this consumer to complete the next section. -1. Log in to your [Bitbucket](https://bitbucket.org/account/signin/){:target="\_blank"} account. +1. Log in to your [Bitbucket](https://bitbucket.org/account/signin/){:target="_blank"} account. 1. Click **Settings** > **Access Management** > **OAuth**. 1. Click **Add consumer** and configure it as follows: diff --git a/guides/v2.0/cloud/project/new-relic.md b/guides/v2.0/cloud/project/new-relic.md index 648645a56c9..9b16de7a09d 100644 --- a/guides/v2.0/cloud/project/new-relic.md +++ b/guides/v2.0/cloud/project/new-relic.md @@ -8,7 +8,7 @@ functional_areas: - Services --- -The software analytics product [New Relic for application performance management (APM)](https://docs.newrelic.com/docs/apm/new-relic-apm/getting-started/introduction-new-relic-apm){:target="\_blank"} helps you to analyze and improve application interactions. Each {{site.data.var.ece}} plan includes a New Relic APM license that supports up to three instances across all environments. You do not need to purchase or install the New Relic extension (different than the APM service). For plan details, see [Subscriptions and plans]({{ page.baseurl }}/cloud/basic-information/cloud-plans.html). +The software analytics product [New Relic for application performance management (APM)](https://docs.newrelic.com/docs/apm/new-relic-apm/getting-started/introduction-new-relic-apm){:target="_blank"} helps you to analyze and improve application interactions. Each {{site.data.var.ece}} plan includes a New Relic APM license that supports up to three instances across all environments. You do not need to purchase or install the New Relic extension (different than the APM service). For plan details, see [Subscriptions and plans]({{ page.baseurl }}/cloud/basic-information/cloud-plans.html). ## Key features {#features} @@ -106,9 +106,9 @@ You can mix the high-level data captured by New Relic APM and the code-level dat ## New Relic APM resources {#resources} -- [Introduction to APM](https://docs.newrelic.com/docs/data-analysis/user-interface-functions/view-your-data/standard-page-functions){:target="\_blank"} -- [View transactions](https://docs.newrelic.com/docs/apm/applications-menu/monitoring/transactions-page#tx_viewing){:target="\_blank"} -- [Analyze database and instance-level performance issues](https://docs.newrelic.com/docs/apm/applications-menu/features/analyze-database-instance-level-performance-issues){:target="\_blank"} -- [Tracking front-end time](https://docs.newrelic.com/docs/apm/applications-menu/features/request-queuing-tracking-front-end-time){:target="\_blank"} -- [APM best practices](https://docs.newrelic.com/docs/apm/new-relic-apm/guides/new-relic-apm-best-practices-guide){:target="\_blank"} -- [New Relic University](https://learn.newrelic.com/courses/intro_apm){:target="\_blank"} +- [Introduction to APM](https://docs.newrelic.com/docs/data-analysis/user-interface-functions/view-your-data/standard-page-functions){:target="_blank"} +- [View transactions](https://docs.newrelic.com/docs/apm/applications-menu/monitoring/transactions-page#tx_viewing){:target="_blank"} +- [Analyze database and instance-level performance issues](https://docs.newrelic.com/docs/apm/applications-menu/features/analyze-database-instance-level-performance-issues){:target="_blank"} +- [Tracking front-end time](https://docs.newrelic.com/docs/apm/applications-menu/features/request-queuing-tracking-front-end-time){:target="_blank"} +- [APM best practices](https://docs.newrelic.com/docs/apm/new-relic-apm/guides/new-relic-apm-best-practices-guide){:target="_blank"} +- [New Relic University](https://learn.newrelic.com/courses/intro_apm){:target="_blank"} diff --git a/guides/v2.0/cloud/project/project-conf-files_magento-app.md b/guides/v2.0/cloud/project/project-conf-files_magento-app.md index d33d32ee10b..3402afe297e 100644 --- a/guides/v2.0/cloud/project/project-conf-files_magento-app.md +++ b/guides/v2.0/cloud/project/project-conf-files_magento-app.md @@ -13,14 +13,14 @@ functional_areas: ## About `.magento.app.yaml` {#cloud-yaml-platform} {{site.data.var.ee}} supports multiple applications per project but typically, a project is composed of a single application, in which case you can simply put a `.magento.app.yaml` at the root of your repository. -This file controls the application and the way it is built and deployed on {{site.data.var.ece}}. To see a sample of the file, see [`.magento.app.yaml`](https://github.com/magento/magento-cloud/blob/master/.magento.app.yaml){:target="\_blank"}. Make sure to review the `.magento.app.yaml` for your installed version. This file can differ across {{site.data.var.ece}} versions. +This file controls the application and the way it is built and deployed on {{site.data.var.ece}}. To see a sample of the file, see [`.magento.app.yaml`](https://github.com/magento/magento-cloud/blob/master/.magento.app.yaml){:target="_blank"}. Make sure to review the `.magento.app.yaml` for your installed version. This file can differ across {{site.data.var.ece}} versions. {% include cloud/note-pro-using-yaml.md %} The following sections discuss properties in `.magento.app.yaml`. ## Defaults {#cloud-yaml-default} -`.magento.app.yaml` has many default values; see the [sample `.magento.app.yaml`](https://github.com/magento/magento-cloud/blob/master/.magento.app.yaml){:target="\_blank"}. +`.magento.app.yaml` has many default values; see the [sample `.magento.app.yaml`](https://github.com/magento/magento-cloud/blob/master/.magento.app.yaml){:target="_blank"}. ## `name` property {#name} `name` identifies the application in the project. {{site.data.var.ee}} supports multiple applications in a project, so each application must have a *unique name* in a project. @@ -295,56 +295,56 @@ To view the current list of PHP extensions, SSH into your environment and enter Magento requires the following PHP extensions that are enabled by default: -* [curl](http://php.net/manual/en/book.curl.php){:target="\_blank"} -* [gd](http://php.net/manual/en/book.image.php){:target="\_blank"} -* [intl](http://php.net/manual/en/book.intl.php){:target="\_blank"} +* [curl](http://php.net/manual/en/book.curl.php){:target="_blank"} +* [gd](http://php.net/manual/en/book.image.php){:target="_blank"} +* [intl](http://php.net/manual/en/book.intl.php){:target="_blank"} * PHP 7 only: - * [json](http://php.net/manual/en/book.json.php){:target="\_blank"} - * [iconv](http://php.net/manual/en/book.iconv.php){:target="\_blank"} -* [mcrypt](http://php.net/manual/en/book.mcrypt.php){:target="\_blank"} -* [PDO/MySQL](http://php.net/manual/en/ref.pdo-mysql.php){:target="\_blank"} -* [bc-math](http://php.net/manual/en/book.bc.php){:target="\_blank"} -* [mbstring](http://php.net/manual/en/book.mbstring.php){:target="\_blank"} -* [mhash](http://php.net/manual/en/book.mhash.php){:target="\_blank"} -* [openssl](http://php.net/manual/en/book.openssl.php){:target="\_blank"} -* [SimpleXML](http://php.net/manual/en/book.simplexml.php){:target="\_blank"} -* [soap](http://php.net/manual/en/book.soap.php){:target="\_blank"} -* [xml](http://php.net/manual/en/book.xml.php){:target="\_blank"} -* [zip](http://php.net/manual/en/book.zip.php){:target="\_blank"} + * [json](http://php.net/manual/en/book.json.php){:target="_blank"} + * [iconv](http://php.net/manual/en/book.iconv.php){:target="_blank"} +* [mcrypt](http://php.net/manual/en/book.mcrypt.php){:target="_blank"} +* [PDO/MySQL](http://php.net/manual/en/ref.pdo-mysql.php){:target="_blank"} +* [bc-math](http://php.net/manual/en/book.bc.php){:target="_blank"} +* [mbstring](http://php.net/manual/en/book.mbstring.php){:target="_blank"} +* [mhash](http://php.net/manual/en/book.mhash.php){:target="_blank"} +* [openssl](http://php.net/manual/en/book.openssl.php){:target="_blank"} +* [SimpleXML](http://php.net/manual/en/book.simplexml.php){:target="_blank"} +* [soap](http://php.net/manual/en/book.soap.php){:target="_blank"} +* [xml](http://php.net/manual/en/book.xml.php){:target="_blank"} +* [zip](http://php.net/manual/en/book.zip.php){:target="_blank"} You must install the following extensions: -* [ImageMagick](http://php.net/manual/en/book.imagick.php){:target="\_blank"} 6.3.7 (or later), ImageMagick can optionally be used with the `gd` extension -* [xsl](http://php.net/manual/en/book.xsl.php){:target="\_blank"} -* [redis](https://pecl.php.net/package/redis){:target="\_blank"} +* [ImageMagick](http://php.net/manual/en/book.imagick.php){:target="_blank"} 6.3.7 (or later), ImageMagick can optionally be used with the `gd` extension +* [xsl](http://php.net/manual/en/book.xsl.php){:target="_blank"} +* [redis](https://pecl.php.net/package/redis){:target="_blank"} In addition, we strongly recommend you enable `opcache`. Other PHP extensions you can optionally install: -* [apcu](http://php.net/manual/en/book.apcu.php){:target="\_blank"} -* [blackfire](https://blackfire.io/docs/up-and-running/installation){:target="\_blank"} -* [enchant](http://php.net/manual/en/book.enchant.php){:target="\_blank"} -* [gearman](http://php.net/manual/en/book.gearman.php){:target="\_blank"} -* [geoip](http://php.net/manual/en/book.geoip.php){:target="\_blank"} -* [imap](http://php.net/manual/en/book.imap.php){:target="\_blank"} -* [ioncube](https://www.ioncube.com/loaders.php){:target="\_blank"} -* [pecl-http](https://pecl.php.net/package/pecl_http){:target="\_blank"} -* [pinba](http://pinba.org){:target="\_blank"} -* [propro](https://pecl.php.net/package/propro){:target="\_blank"} -* [pspell](http://php.net/manual/en/book.pspell.php){:target="\_blank"} -* [raphf](https://pecl.php.net/package/raphf){:target="\_blank"} -* [readline](http://php.net/manual/en/book.readline.php){:target="\_blank"} -* [recode](http://php.net/manual/en/book.recode.php){:target="\_blank"} -* [snmp](http://php.net/manual/en/book.snmp.php){:target="\_blank"} -* [sqlite3](http://php.net/manual/en/book.sqlite3.php){:target="\_blank"} -* [ssh2](http://php.net/manual/en/book.ssh2.php){:target="\_blank"} -* [tidy](http://php.net/manual/en/book.tidy.php){:target="\_blank"} -* [xcache](https://xcache.lighttpd.net){:target="\_blank"} -* [xdebug](https://xdebug.org){:target="\_blank"} -* [xhprof](http://php.net/manual/en/book.xhprof.php){:target="\_blank"} -* [xmlrpc](http://php.net/manual/en/book.xmlrpc.php){:target="\_blank"} +* [apcu](http://php.net/manual/en/book.apcu.php){:target="_blank"} +* [blackfire](https://blackfire.io/docs/up-and-running/installation){:target="_blank"} +* [enchant](http://php.net/manual/en/book.enchant.php){:target="_blank"} +* [gearman](http://php.net/manual/en/book.gearman.php){:target="_blank"} +* [geoip](http://php.net/manual/en/book.geoip.php){:target="_blank"} +* [imap](http://php.net/manual/en/book.imap.php){:target="_blank"} +* [ioncube](https://www.ioncube.com/loaders.php){:target="_blank"} +* [pecl-http](https://pecl.php.net/package/pecl_http){:target="_blank"} +* [pinba](http://pinba.org){:target="_blank"} +* [propro](https://pecl.php.net/package/propro){:target="_blank"} +* [pspell](http://php.net/manual/en/book.pspell.php){:target="_blank"} +* [raphf](https://pecl.php.net/package/raphf){:target="_blank"} +* [readline](http://php.net/manual/en/book.readline.php){:target="_blank"} +* [recode](http://php.net/manual/en/book.recode.php){:target="_blank"} +* [snmp](http://php.net/manual/en/book.snmp.php){:target="_blank"} +* [sqlite3](http://php.net/manual/en/book.sqlite3.php){:target="_blank"} +* [ssh2](http://php.net/manual/en/book.ssh2.php){:target="_blank"} +* [tidy](http://php.net/manual/en/book.tidy.php){:target="_blank"} +* [xcache](https://xcache.lighttpd.net){:target="_blank"} +* [xdebug](https://xdebug.org){:target="_blank"} +* [xhprof](http://php.net/manual/en/book.xhprof.php){:target="_blank"} +* [xmlrpc](http://php.net/manual/en/book.xmlrpc.php){:target="_blank"}
        Important: PHP compiled with debug is not supported and the Probe may conflict with XDebug or XHProf. Disable those extensions when enabling the Probe. The Probe conflicts with some PHP extensions like Pinba or IonCube. diff --git a/guides/v2.0/cloud/project/project-conf-files_services-elastic.md b/guides/v2.0/cloud/project/project-conf-files_services-elastic.md index f19cf0cd742..34591987bcf 100644 --- a/guides/v2.0/cloud/project/project-conf-files_services-elastic.md +++ b/guides/v2.0/cloud/project/project-conf-files_services-elastic.md @@ -7,7 +7,7 @@ functional_areas: - Search --- -[Elasticsearch](https://www.elastic.co){:target="\_blank"} is an open source product that enables you to take data from any source, any format, and search and visualize it in real time. +[Elasticsearch](https://www.elastic.co){:target="_blank"} is an open source product that enables you to take data from any source, any format, and search and visualize it in real time. * Elasticsearch performs quick and advanced searches on products in the product catalog * Elasticsearch Analyzers support multiple languages @@ -57,7 +57,7 @@ elasticsearch: - lang-python {% endhighlight %} -For example, if you are using [Smile ElasticSuite](https://github.com/Smile-SA/elasticsuite){:target="\_blank"}, you should add the following plugins: +For example, if you are using [Smile ElasticSuite](https://github.com/Smile-SA/elasticsuite){:target="_blank"}, you should add the following plugins: {% highlight yaml %} elasticsearch: @@ -87,9 +87,9 @@ The following are supported Elasticsearch plugins for version 2.4: * `mapper-murmur3`: Murmur3 mapper plugin for computing hashes at index-time * `mapper-size`: Size mapper plugin, enables the `_size` meta field -If using [Smile ElasticSuite](https://github.com/Smile-SA/elasticsuite){:target="\_blank"}, the required plugins are `analysis-icu` and `analysis-phonetic`. Make sure to add these to the plugins section of `services.yaml.` See [Add Elasticsearch plugins](#addplugins). +If using [Smile ElasticSuite](https://github.com/Smile-SA/elasticsuite){:target="_blank"}, the required plugins are `analysis-icu` and `analysis-phonetic`. Make sure to add these to the plugins section of `services.yaml.` See [Add Elasticsearch plugins](#addplugins). -For full documentation on these plugins, see [Elasticsearch plugin documentation](https://www.elastic.co/guide/en/elasticsearch/plugins/2.4/index.html){:target="\_blank"}. +For full documentation on these plugins, see [Elasticsearch plugin documentation](https://www.elastic.co/guide/en/elasticsearch/plugins/2.4/index.html){:target="_blank"}. ## Verify environment-related relationships {#cloud-es-config-mg} diff --git a/guides/v2.0/cloud/project/project-conf-files_services-rabbit.md b/guides/v2.0/cloud/project/project-conf-files_services-rabbit.md index 1059bc4221a..5cbab3f975a 100644 --- a/guides/v2.0/cloud/project/project-conf-files_services-rabbit.md +++ b/guides/v2.0/cloud/project/project-conf-files_services-rabbit.md @@ -14,7 +14,7 @@ functional_areas: The [Message Queue Framework (MQF)]({{ page.baseurl }}/config-guide/mq/rabbitmq-overview.html) is a system within {{site.data.var.ee}} that allows a {% glossarytooltip c1e4242b-1f1a-44c3-9d72-1d5b1435e142 %}module{% endglossarytooltip %} to publish messages to queues. It also defines the consumers that will receive the messages asynchronously. -The MQF uses [RabbitMQ](http://www.rabbitmq.com){:target="\_blank"} as the messaging broker, which provides a scalable platform for sending and receiving messages. It also includes a mechanism for storing undelivered messages. RabbitMQ is based on the Advanced Message Queuing Protocol (AMQP) 0.9.1 specification. +The MQF uses [RabbitMQ](http://www.rabbitmq.com){:target="_blank"} as the messaging broker, which provides a scalable platform for sending and receiving messages. It also includes a mechanism for storing undelivered messages. RabbitMQ is based on the Advanced Message Queuing Protocol (AMQP) 0.9.1 specification. We support RabbitMQ version 3.5. diff --git a/guides/v2.0/cloud/project/project-conf-files_services-redis.md b/guides/v2.0/cloud/project/project-conf-files_services-redis.md index 65b0da24cbb..4a0cc18778d 100644 --- a/guides/v2.0/cloud/project/project-conf-files_services-redis.md +++ b/guides/v2.0/cloud/project/project-conf-files_services-redis.md @@ -12,7 +12,7 @@ functional_areas: - Setup --- -[Redis](http://redis.io){:target="\_blank"} is an optional, backend cache solution that replaces the Zend Framework [Zend_Cache_Backend_File](http://framework.zend.com/apidoc/1.0/Zend_Cache/Backend/Zend_Cache_Backend_File.html){:target="\_blank"}, which is used in Magento 2 by default. +[Redis](http://redis.io){:target="_blank"} is an optional, backend cache solution that replaces the Zend Framework [Zend_Cache_Backend_File](http://framework.zend.com/apidoc/1.0/Zend_Cache/Backend/Zend_Cache_Backend_File.html){:target="_blank"}, which is used in Magento 2 by default. We support Redis versions 2.8 and 3.0. Redis 3.0 supports up to 64 different databases per instance of the service, while 2.8 allows for only a single database. See [Configure Redis]({{ page.baseurl }}/config-guide/redis/config-redis.html). diff --git a/guides/v2.0/cloud/project/project-start.md b/guides/v2.0/cloud/project/project-start.md index 939e8d572b4..e9a8184a404 100644 --- a/guides/v2.0/cloud/project/project-start.md +++ b/guides/v2.0/cloud/project/project-start.md @@ -42,7 +42,7 @@ Not including the Magento application itself, your local project has the followi ### .gitignore file {gitignore} Depending on your {{site.data.var.ece}} version, you may need different information added to or commented out in your `.gitignore` file. Git uses this file to determine which files and directories to ignore, before you make a commit to your branches. A .gitignore file should be committed into your root Magento in the repository, in order to share the ignore rules with any other users that clone the repository. -We include a base `.gitignore` file with the project repository. For a review of the {{site.data.var.ece}} file, see [.gitignore file](https://github.com/magento/magento-cloud/blob/master/.gitignore){:target="\_blank"}. You can review the recommended files for your file in the [`.gitignore` reference]({{ site.baseurl }}/guides/v2.2/config-guide/prod/config-reference-gitignore.html). +We include a base `.gitignore` file with the project repository. For a review of the {{site.data.var.ece}} file, see [.gitignore file](https://github.com/magento/magento-cloud/blob/master/.gitignore){:target="_blank"}. You can review the recommended files for your file in the [`.gitignore` reference]({{ site.baseurl }}/guides/v2.2/config-guide/prod/config-reference-gitignore.html). ## Magento application root directory {#rootdir} diff --git a/guides/v2.0/cloud/project/project-webint-basic.md b/guides/v2.0/cloud/project/project-webint-basic.md index f4914e2bf97..57c5780ce88 100644 --- a/guides/v2.0/cloud/project/project-webint-basic.md +++ b/guides/v2.0/cloud/project/project-webint-basic.md @@ -10,7 +10,7 @@ functional_areas: - Configuration --- -The {{site.data.var.ece}} [Project Web Interface](https://accounts.magento.cloud){:target="\_blank"} enables you to do the following for all Starter and Pro environments: +The {{site.data.var.ece}} [Project Web Interface](https://accounts.magento.cloud){:target="_blank"} enables you to do the following for all Starter and Pro environments: * [Access projects](#project-access) * Create and manage projects diff --git a/guides/v2.0/cloud/project/projects.md b/guides/v2.0/cloud/project/projects.md index 0592cf7ed31..c179fe294ad 100644 --- a/guides/v2.0/cloud/project/projects.md +++ b/guides/v2.0/cloud/project/projects.md @@ -44,7 +44,7 @@ To upgrade and patch Magento, see: ## Access the Project Web Interface {#login} -With your {{site.data.var.ece}} account created, you can log into the Project Web Interface at [https://accounts.magento.cloud](https://accounts.magento.cloud){:target="\_blank"}. +With your {{site.data.var.ece}} account created, you can log into the Project Web Interface at [https://accounts.magento.cloud](https://accounts.magento.cloud){:target="_blank"}. ![Log in to a project]({{ site.baseurl }}/common/images/cloud_project-login.png){:width="450px"} diff --git a/guides/v2.0/cloud/release-notes/CloudReleaseNotes2.1.2.md b/guides/v2.0/cloud/release-notes/CloudReleaseNotes2.1.2.md index 8a2b86ea73e..b810176d732 100644 --- a/guides/v2.0/cloud/release-notes/CloudReleaseNotes2.1.2.md +++ b/guides/v2.0/cloud/release-notes/CloudReleaseNotes2.1.2.md @@ -25,7 +25,7 @@ We made the following change in this release: We made the following fixes in this release: * Improved the performance of static file deployment. -* You can now upgrade to version 2.1.2 if you enabled [static file signatures](http://docs.magento.com/m2/ee/user_guide/system/static-file-signature.html){:target="\_blank"}. +* You can now upgrade to version 2.1.2 if you enabled [static file signatures](http://docs.magento.com/m2/ee/user_guide/system/static-file-signature.html){:target="_blank"}. * You no longer need a `pub/front-static.php` in your template. * We now back up `env.php` before disabling the Redis cache during deployment. * Patches are now applied in alphabetical order. diff --git a/guides/v2.0/cloud/requirements/cloud-requirements.md b/guides/v2.0/cloud/requirements/cloud-requirements.md index cf3f2ee5543..fd031367280 100644 --- a/guides/v2.0/cloud/requirements/cloud-requirements.md +++ b/guides/v2.0/cloud/requirements/cloud-requirements.md @@ -53,11 +53,11 @@ Git is the heart of all your code in repositories. It acts as a version control We hope you have a good working knowledge of Git. Need some help? Don't worry, we have you covered with some of our favorite links and information. We'll also include a Git guide to branching and developing soon. -* [Git documentation](https://git-scm.com/documentation){:target="\_blank"} and [videos](https://git-scm.com/videos){:target="\_blank"} from the makers of Git -* [Git cheatsheet](http://rogerdudler.github.io/git-guide/files/git_cheat_sheet.pdf){:target="\_blank"} and [quick guide](http://rogerdudler.github.io/git-guide/){:target="\_blank"} from Roger Dudler -* [Git video](https://www.youtube.com/watch?v=8KCQe9Pm1kg){:target="\_blank"} with DevForge to understand how people use the repo and commands with a fun story +* [Git documentation](https://git-scm.com/documentation){:target="_blank"} and [videos](https://git-scm.com/videos){:target="_blank"} from the makers of Git +* [Git cheatsheet](http://rogerdudler.github.io/git-guide/files/git_cheat_sheet.pdf){:target="_blank"} and [quick guide](http://rogerdudler.github.io/git-guide/){:target="_blank"} from Roger Dudler +* [Git video](https://www.youtube.com/watch?v=8KCQe9Pm1kg){:target="_blank"} with DevForge to understand how people use the repo and commands with a fun story -To get started with Git, you should have [Git installed](https://git-scm.com/downloads){:target="\_blank"} on your local. +To get started with Git, you should have [Git installed](https://git-scm.com/downloads){:target="_blank"} on your local.

        In addition to Git's requirements for valid branch names, {{site.data.var.ee}} adds two additional requirements:

        diff --git a/guides/v2.0/cloud/trouble/trouble_fastly.md b/guides/v2.0/cloud/trouble/trouble_fastly.md index 5ea8883e536..fcdbf87b23f 100644 --- a/guides/v2.0/cloud/trouble/trouble_fastly.md +++ b/guides/v2.0/cloud/trouble/trouble_fastly.md @@ -118,7 +118,7 @@ If you do not have DNS set up for a public hostname, enter a command similar to ### Check response headers {#response-headers} -For detailed information on hits and misses, see Fastly's [Understanding cache HIT and MISS headers with shielded services](https://docs.fastly.com/guides/performance-tuning/understanding-cache-hit-and-miss-headers-with-shielded-services){:target="\_blank"}. +For detailed information on hits and misses, see Fastly's [Understanding cache HIT and MISS headers with shielded services](https://docs.fastly.com/guides/performance-tuning/understanding-cache-hit-and-miss-headers-with-shielded-services){:target="_blank"}. Check the returned response headers and values: @@ -127,8 +127,8 @@ Check the returned response headers and values: * Fastly-Module-Enabled should be either Yes or the Fastly extension version number * X-Cache should be either `HIT` or `HIT, HIT` * x-cache-hits should be 1,1 -* [Cache-Control: max-age](https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9){:target="\_blank"} should be greater than 0 -* [Pragma](https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.32){:target="\_blank"} should be `cache` +* [Cache-Control: max-age](https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9){:target="_blank"} should be greater than 0 +* [Pragma](https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.32){:target="_blank"} should be `cache` The following example shows the correct values for `Pragma`, `X-Magento-Tags`, and `Fastly-Module-Enabled`. @@ -249,7 +249,7 @@ If the credentials are correct, you may have issues with your VCLs. To list and curl -X GET -s https://api.fastly.com/service//version//snippet/ -H "Fastly-Key: " -Review the list of VCLs. If you have issues with the default VCLs from Fastly, you can upload again or verify the content per the [Fastly default VCLs](https://github.com/fastly/fastly-magento2/tree/master/etc/vcl_snippets){:target="\_blank"}. For editing your custom VCLs, see [Custom Fastly VCL snippets]({{ page.baseurl }}/cloud/configure/cloud-vcl-custom-snippets.html). +Review the list of VCLs. If you have issues with the default VCLs from Fastly, you can upload again or verify the content per the [Fastly default VCLs](https://github.com/fastly/fastly-magento2/tree/master/etc/vcl_snippets){:target="_blank"}. For editing your custom VCLs, see [Custom Fastly VCL snippets]({{ page.baseurl }}/cloud/configure/cloud-vcl-custom-snippets.html). ## Activating a deactivated version {#activate} diff --git a/guides/v2.0/comp-mgr/prereq/prereq_auth-token.md b/guides/v2.0/comp-mgr/prereq/prereq_auth-token.md index 83a8d3deef8..6e4e8a82ecb 100644 --- a/guides/v2.0/comp-mgr/prereq/prereq_auth-token.md +++ b/guides/v2.0/comp-mgr/prereq/prereq_auth-token.md @@ -10,7 +10,7 @@ functional_areas: ---
        -

        To upgrade your {{site.data.var.ee}} version or to upgrade from {{site.data.var.ce}} to {{site.data.var.ee}}, you must be authorized to access the {{site.data.var.ee}} repository. Contact Magento Support if you have questions.

        +

        To upgrade your {{site.data.var.ee}} version or to upgrade from {{site.data.var.ce}} to {{site.data.var.ee}}, you must be authorized to access the {{site.data.var.ee}} repository. Contact Magento Support if you have questions.

        To enter your [authentication keys]({{ page.baseurl }}/install-gde/prereq/connect-auth.html): diff --git a/guides/v2.0/config-guide/bootstrap/mage-profiler.md b/guides/v2.0/config-guide/bootstrap/mage-profiler.md index e6477acbab9..2ab2f91a8b8 100644 --- a/guides/v2.0/config-guide/bootstrap/mage-profiler.md +++ b/guides/v2.0/config-guide/bootstrap/mage-profiler.md @@ -22,7 +22,7 @@ Magento profiling enables you to: You should be particularly interested in the list of *unused dependencies*, which are objects that were created because they were requested in some constructor, but were never used (that is, none of their methods were called). As a result, processor time and memory spent to create these dependencies are wasted. -Magento provides the base functionality in Magento\Framework\Profiler. +Magento provides the base functionality in Magento\Framework\Profiler. ## Set MAGE_PROFILER `MAGE_PROFILER` supports the following values: @@ -31,8 +31,8 @@ Magento provides the base functionality in Magento\Framework\Profiler\Driver\Standard\Output\Csvfile - - Any other value (except `2`), including an empty value, which uses Magento\Framework\Profiler\Driver\Standard\Output\Html + - `csvfile` which uses Magento\Framework\Profiler\Driver\Standard\Output\Csvfile + - Any other value (except `2`), including an empty value, which uses Magento\Framework\Profiler\Driver\Standard\Output\Html - `2` to enable dependency graphs. diff --git a/guides/v2.0/config-guide/bootstrap/magento-modes.md b/guides/v2.0/config-guide/bootstrap/magento-modes.md index aa3d1d90702..c43a7098fda 100644 --- a/guides/v2.0/config-guide/bootstrap/magento-modes.md +++ b/guides/v2.0/config-guide/bootstrap/magento-modes.md @@ -65,7 +65,7 @@ In default mode: - Errors are logged to the file reports at server, and never shown to a user - A symlink to a static view file is published to the `pub/static` directory for each requested file -- Default mode is not optimized for a production environment, primarily because of the adverse performance impact of {% glossarytooltip 363662cb-73f1-4347-a15e-2d2adabeb0c2 %}static files{% endglossarytooltip %} being dynamically generated rather than [materialized](https://en.wikipedia.org/wiki/Materialized_view){:target="\_blank"}. In other words, creating static files and caching them has a greater performance impact than generating them using the static files creation tool. +- Default mode is not optimized for a production environment, primarily because of the adverse performance impact of {% glossarytooltip 363662cb-73f1-4347-a15e-2d2adabeb0c2 %}static files{% endglossarytooltip %} being dynamically generated rather than [materialized](https://en.wikipedia.org/wiki/Materialized_view){:target="_blank"}. In other words, creating static files and caching them has a greater performance impact than generating them using the static files creation tool. For more information, see Set the Magento mode. diff --git a/guides/v2.0/config-guide/cli/config-cli-subcommands-compiler.md b/guides/v2.0/config-guide/cli/config-cli-subcommands-compiler.md index fddd7f95914..acc8d4eecbc 100644 --- a/guides/v2.0/config-guide/cli/config-cli-subcommands-compiler.md +++ b/guides/v2.0/config-guide/cli/config-cli-subcommands-compiler.md @@ -28,7 +28,7 @@ This section discusses the basics of code compilation. Code compilation consists - Repositories code generation (that is, generated code for APIs) - Service data attributes generation (that is, generated {% glossarytooltip 55774db9-bf9d-40f3-83db-b10cc5ae3b68 %}extension{% endglossarytooltip %} classes for data objects) -You can find code compilation in classes in the \Magento\Setup\Module\Di\App\Task\Operation {% glossarytooltip 621ef86b-7314-4fbc-a80d-ab7fa45a27cb %}namespace{% endglossarytooltip %}. +You can find code compilation in classes in the \Magento\Setup\Module\Di\App\Task\Operation {% glossarytooltip 621ef86b-7314-4fbc-a80d-ab7fa45a27cb %}namespace{% endglossarytooltip %}. ## Run the single-tenant compiler {#config-cli-subcommands-single} @@ -77,7 +77,7 @@ The following table discusses the meanings of this command's parameters and valu

        --serializer

        -

        Specify either serialize or igbinary. Default is serialize.

        +

        Specify either serialize or igbinary. Default is serialize.

        No

        diff --git a/guides/v2.0/config-guide/cli/config-cli-subcommands-i18n.md b/guides/v2.0/config-guide/cli/config-cli-subcommands-i18n.md index 047f82b035f..af50d487aeb 100644 --- a/guides/v2.0/config-guide/cli/config-cli-subcommands-i18n.md +++ b/guides/v2.0/config-guide/cli/config-cli-subcommands-i18n.md @@ -42,7 +42,7 @@ To translate words and phrases, you must: After that: 1. You can package the translation dictionaries into a language package and provide the package to the Magento store administrator. -2. In the Magento Admin, the store administrator configures the translations. +2. In the Magento Admin, the store administrator configures the translations. Command options: @@ -150,7 +150,7 @@ The following table explains this command's parameters and values:

        <locale>

        -

        ISO 639-1 (language) and ISO 3166 (country) identifier of language used as file name for all resulting .csv files. Examples: de_DE, pt_PT, pt_BR.

        +

        ISO 639-1 (language) and ISO 3166 (country) identifier of language used as file name for all resulting .csv files. Examples: de_DE, pt_PT, pt_BR.

        Yes

        @@ -189,7 +189,7 @@ A language package is a directory under `app/i18n/` in the Magento f The entire path must be all lowercase.
        -For an example, see the de_de language package. +For an example, see the de_de language package. To create these files: @@ -262,7 +262,7 @@ If the Magento application cannot find word or phrase in the `en_GB` package, it 1. `/en_ca_package` 1. `/en_us_package` -Specifying all inheritances between the language packages might result in creating circular inheritance chains. Use Magento\Test\Integrity\App\Language\CircularDependencyTest test to locate and fix such chains. +Specifying all inheritances between the language packages might result in creating circular inheritance chains. Use Magento\Test\Integrity\App\Language\CircularDependencyTest test to locate and fix such chains. ### Configure multiple packages for a language {#m2devgde-xlate-severalpacks} diff --git a/guides/v2.0/config-guide/cli/config-cli-subcommands-perf-data.md b/guides/v2.0/config-guide/cli/config-cli-subcommands-perf-data.md index 03788ce6cd4..ef384353905 100644 --- a/guides/v2.0/config-guide/cli/config-cli-subcommands-perf-data.md +++ b/guides/v2.0/config-guide/cli/config-cli-subcommands-perf-data.md @@ -16,7 +16,7 @@ functional_areas: ## Overview of performance testing data {#config-cli-perf-overview} -To use the [Magento Performance Toolkit]({{ site.mage2000url }}setup/performance-toolkit){:target="\_blank"} or another tool for performance testing, you must generate a large amount of data (for example, stores, categories, products, and so on). +To use the [Magento Performance Toolkit]({{ site.mage2000url }}setup/performance-toolkit){:target="_blank"} or another tool for performance testing, you must generate a large amount of data (for example, stores, categories, products, and so on). You can adjust the amount of data you create using *profiles* (small, medium, large, and extra large). The next section discusses profiles in more detail. diff --git a/guides/v2.0/config-guide/cli/config-cli-subcommands-spt-util.md b/guides/v2.0/config-guide/cli/config-cli-subcommands-spt-util.md index 56368253211..32b20bc43f9 100644 --- a/guides/v2.0/config-guide/cli/config-cli-subcommands-spt-util.md +++ b/guides/v2.0/config-guide/cli/config-cli-subcommands-spt-util.md @@ -16,7 +16,7 @@ functional_areas: ## Overview of the support utilities {#config-cli-spt-utils-over} -The Magento support utilities (also referred to as the [*Data Collector*](http://docs.magento.com/m2/ee/user_guide/system/support-data-collector.html){:target="\_blank"}) enable {{site.data.var.ee}} users to gather troubleshooting information about your system that can be used by our Support team. +The Magento support utilities (also referred to as the [*Data Collector*](http://docs.magento.com/m2/ee/user_guide/system/support-data-collector.html){:target="_blank"}) enable {{site.data.var.ee}} users to gather troubleshooting information about your system that can be used by our Support team. Magento Support uses these backups (also referred to as *dumps*) to analyze issues that require access to your code. A typical scenario follows: diff --git a/guides/v2.0/config-guide/cli/config-cli-subcommands-static-view.md b/guides/v2.0/config-guide/cli/config-cli-subcommands-static-view.md index f565e6e2aa0..b9ed02eed3a 100644 --- a/guides/v2.0/config-guide/cli/config-cli-subcommands-static-view.md +++ b/guides/v2.0/config-guide/cli/config-cli-subcommands-static-view.md @@ -133,7 +133,7 @@ Use the following steps: When creating a custom implementation of the {% glossarytooltip a3e37235-4e8b-464f-a19d-4a120560206a %}static content{% endglossarytooltip %} deployment tool, do not use non atomic writing to files that should be available on the client side. Otherwise, those files might be loaded on the client side with partial content. -One of the options for making it atomic, is writing to files stored in a temporary directory and copying or moving them to the destination directory (from where they are actually loaded to client side) once writing is over. For details about writing to files see [http://php.net/manual/en/function.fwrite.php](http://php.net/manual/en/function.fwrite.php){:target="\_blank"}. +One of the options for making it atomic, is writing to files stored in a temporary directory and copying or moving them to the destination directory (from where they are actually loaded to client side) once writing is over. For details about writing to files see [http://php.net/manual/en/function.fwrite.php](http://php.net/manual/en/function.fwrite.php){:target="_blank"}. Please note, that the default Magento implementation of `\Magento\Framework\Filesystem\Directory\WriteInterface::writeFile` uses non-atomic write to file. diff --git a/guides/v2.0/config-guide/cli/config-cli-subcommands-urn.md b/guides/v2.0/config-guide/cli/config-cli-subcommands-urn.md index d313e926d9f..f84354fa2c8 100644 --- a/guides/v2.0/config-guide/cli/config-cli-subcommands-urn.md +++ b/guides/v2.0/config-guide/cli/config-cli-subcommands-urn.md @@ -15,7 +15,7 @@ functional_areas: ## Overview of URN highlighter -Magento code references all XSD schemas as Uniform Resource Names (URNs). If you're developing code and need to reference XSDs, this command configures your integrated developer environment (IDE) to recognize and highlight URNs. This makes development easier. +Magento code references all XSD schemas as Uniform Resource Names (URNs). If you're developing code and need to reference XSDs, this command configures your integrated developer environment (IDE) to recognize and highlight URNs. This makes development easier. By default, an IDE like PHPStorm is not configured to recognize URNs and, as a result, they display in red text as follows: diff --git a/guides/v2.0/config-guide/cli/config-cli-subcommands.md b/guides/v2.0/config-guide/cli/config-cli-subcommands.md index 255c4fa4d36..2f0a995c602 100644 --- a/guides/v2.0/config-guide/cli/config-cli-subcommands.md +++ b/guides/v2.0/config-guide/cli/config-cli-subcommands.md @@ -32,7 +32,7 @@ You can run the commands in any of the following ways: - `php magento ` - `./magento ` -- `magento ` (after [adding](http://unix.stackexchange.com/questions/117467/how-to-permanently-set-environmental-variables){:target="\_blank"} `/bin` to your system `PATH`) +- `magento ` (after [adding](http://unix.stackexchange.com/questions/117467/how-to-permanently-set-environmental-variables){:target="_blank"} `/bin` to your system `PATH`)
        ## Command summary {#config-cli-summary} diff --git a/guides/v2.0/config-guide/secy/secy-cron.md b/guides/v2.0/config-guide/secy/secy-cron.md index a922515dbcd..672d8ac411b 100644 --- a/guides/v2.0/config-guide/secy/secy-cron.md +++ b/guides/v2.0/config-guide/secy/secy-cron.md @@ -35,10 +35,10 @@ You don't need to do anything if you use the [`magento cron:run`]({{ page.baseur ## Secure cron with Apache -This section discusses how to secure cron using [HTTP Basic authentication](http://tools.ietf.org/html/rfc2617"){:target="_blank"} with Apache. These instructions are based on Apache 2.2 with CentOS 6. For more information, refer to one of the following resources: +This section discusses how to secure cron using [HTTP Basic authentication](http://tools.ietf.org/html/rfc2617"){:target="_blank"} with Apache. These instructions are based on Apache 2.2 with CentOS 6. For more information, refer to one of the following resources: -- [Apache 2.2 authentication and authorization tutorial](http://httpd.apache.org/docs/2.2/howto/auth.html){:target="_blank"} -- [Apache 2.4 authentication and authorization tutorial](http://httpd.apache.org/docs/2.4/howto/auth.html){:target="_blank"} +- [Apache 2.2 authentication and authorization tutorial](http://httpd.apache.org/docs/2.2/howto/auth.html){:target="_blank"} +- [Apache 2.4 authentication and authorization tutorial](http://httpd.apache.org/docs/2.4/howto/auth.html){:target="_blank"} ### Create a password file @@ -113,14 +113,14 @@ This section discusses how to secure cron using the {% glossarytooltip b14ef3d8- Consult one of the following resources to create a password file before continuing: -- [How To Set Up Password Authentication with Nginx on Ubuntu 14.04 (DigitalOcean)](https://www.digitalocean.com/community/tutorials/how-to-set-up-password-authentication-with-nginx-on-ubuntu-14-04){:target="_blank"} -- [Basic HTTP Authentication with nginx (howtoforge)](https://www.howtoforge.com/basic-http-authentication-with-nginx){:target="_blank"} +- [How To Set Up Password Authentication with Nginx on Ubuntu 14.04 (DigitalOcean)](https://www.digitalocean.com/community/tutorials/how-to-set-up-password-authentication-with-nginx-on-ubuntu-14-04){:target="_blank"} +- [Basic HTTP Authentication with nginx (howtoforge)](https://www.howtoforge.com/basic-http-authentication-with-nginx){:target="_blank"} ### Secure cron in `nginx.conf.sample` Magento provides an optimized sample nginx configuration file out of the box. We recommend modifying it to secure cron. -1. Add the following to your Magento [`nginx.sample.conf`]({{ site.mage2000url }}nginx.conf.sample){:target="_blank"} file: +1. Add the following to your Magento [`nginx.sample.conf`]({{ site.mage2000url }}nginx.conf.sample){:target="_blank"} file: ``` shell #Securing cron diff --git a/guides/v2.0/config-guide/varnish/config-varnish-magento.md b/guides/v2.0/config-guide/varnish/config-varnish-magento.md index a8e5e88d170..e94e2daa496 100644 --- a/guides/v2.0/config-guide/varnish/config-varnish-magento.md +++ b/guides/v2.0/config-guide/varnish/config-varnish-magento.md @@ -29,13 +29,13 @@ To configure Magento to use Varnish: Access list -

        Enter the fully qualified hostname, IP address, or Classless Inter-Domain Routing (CIDR) notation IP address range for which to invalidate content.

        -

        More information

        +

        Enter the fully qualified hostname, IP address, or Classless Inter-Domain Routing (CIDR) notation IP address range for which to invalidate content.

        +

        More information

        Backend host

        Enter the fully qualified hostname or IP address and listen port of the Varnish backend or origin server; that is, the server providing the content Varnish will accelerate. Typically, this is your web server.

        -

        More information

        +

        More information

        Backend port diff --git a/guides/v2.0/contributor-guide/contributing.md b/guides/v2.0/contributor-guide/contributing.md index 4e0abe834e9..2bd247d3996 100644 --- a/guides/v2.0/contributor-guide/contributing.md +++ b/guides/v2.0/contributor-guide/contributing.md @@ -39,9 +39,9 @@ Please refer to [Magento Contributor Agreement](http://www.magento.com/legaldocu ## Questions or enhancement requests? {#question} -We use this repository (the Magento 2 GitHub repository) to capture code and documentation issues. We recommend that you post all questions to a question-and-answer site, such as [Stack Exchange](https://magento.stackexchange.com/){:target="\_blank"} and the [Magento Forums](https://community.magento.com/){:target="\_blank"}, where Magento community members can quickly provide recommendations and advice. +We use this repository (the Magento 2 GitHub repository) to capture code and documentation issues. We recommend that you post all questions to a question-and-answer site, such as [Stack Exchange](https://magento.stackexchange.com/){:target="_blank"} and the [Magento Forums](https://community.magento.com/){:target="_blank"}, where Magento community members can quickly provide recommendations and advice. -Submit feature requests or enhancement suggestions to the new [Magento 2 Feature Requests and Improvements forum](https://community.magento.com/t5/Magento-2-Feature-Requests-and/idb-p/feature-requests){:target="\_blank"} (see details [here](https://community.magento.com/t5/News-Announcements/Improvements-to-GitHub-Management/m-p/44572#M96){:target="\_blank"}). +Submit feature requests or enhancement suggestions to the new [Magento 2 Feature Requests and Improvements forum](https://community.magento.com/t5/Magento-2-Feature-Requests-and/idb-p/feature-requests){:target="_blank"} (see details [here](https://community.magento.com/t5/News-Announcements/Improvements-to-GitHub-Management/m-p/44572#M96){:target="_blank"}). ## Contribution requirements {#requirements} @@ -52,17 +52,17 @@ Submit feature requests or enhancement suggestions to the new [Magento 2 Feature 4. PRs that include bug fixes must be accompanied by a step-by-step description of how to reproduce the bug. 3. PRs that include new logic or new features must be submitted along with: * Unit/integration test coverage (we will be releasing more information about writing test coverage in the near future). - * Proposed [documentation]({{ page.baseurl }}/contributor-guide/contributing_docs.html) updates. [Documentation]({{ site.baseurl }}/) contributions can be submitted [here](https://github.com/magento/devdocs){:target="\_blank"}. -4. For large features or changes, please [open an issue](https://github.com/magento/magento2/issues){:target="\_blank"} and discuss it with us first. This may prevent duplicate or unnecessary effort, and it may gain you some additional contributors. -5. To report a bug, please [open an issue](https://github.com/magento/magento2/issues){:target="\_blank"}, and follow these [guidelines about bugfix issues](https://github.com/magento/magento2/wiki/Issue-reporting-guidelines). -5. All automated tests must pass successfully (all builds on [Travis CI](https://travis-ci.org/magento/magento2){:target="\_blank"} must be green). + * Proposed [documentation]({{ page.baseurl }}/contributor-guide/contributing_docs.html) updates. [Documentation]({{ site.baseurl }}/) contributions can be submitted [here](https://github.com/magento/devdocs){:target="_blank"}. +4. For large features or changes, please [open an issue](https://github.com/magento/magento2/issues){:target="_blank"} and discuss it with us first. This may prevent duplicate or unnecessary effort, and it may gain you some additional contributors. +5. To report a bug, please [open an issue](https://github.com/magento/magento2/issues){:target="_blank"}, and follow these [guidelines about bugfix issues](https://github.com/magento/magento2/wiki/Issue-reporting-guidelines). +5. All automated tests must pass successfully (all builds on [Travis CI](https://travis-ci.org/magento/magento2){:target="_blank"} must be green). ## Fork a repository {#fork} To fork a repository on Github: 1. Create or log in to your account on GitHub. -2. Navigate to the [Magento 2 repository](https://github.com/magento/magento2){:target="\_blank"}. +2. Navigate to the [Magento 2 repository](https://github.com/magento/magento2){:target="_blank"}. 3. Click **Fork** at the top right: ![Fork a Repository]({{site.baseurl}}/common/images/fork.png) diff --git a/guides/v2.0/extension-dev-guide/build/composer-integration.md b/guides/v2.0/extension-dev-guide/build/composer-integration.md index b205327db1a..fef0b52db8f 100644 --- a/guides/v2.0/extension-dev-guide/build/composer-integration.md +++ b/guides/v2.0/extension-dev-guide/build/composer-integration.md @@ -11,13 +11,13 @@ redirect_from: ## Overview -Magento 2 uses [Composer][0]{:target="\_blank"}, a {% glossarytooltip bf703ab1-ca4b-48f9-b2b7-16a81fd46e02 %}PHP{% endglossarytooltip %} dependency manager, to package components and product editions. +Magento 2 uses [Composer][0]{:target="_blank"}, a {% glossarytooltip bf703ab1-ca4b-48f9-b2b7-16a81fd46e02 %}PHP{% endglossarytooltip %} dependency manager, to package components and product editions. Composer reads a `composer.json` file in Magento's root directory to download third-party dependencies listed in the file. The [Component Manager][1] uses the `composer.json` file in an extension's root directory to perform the following actions: -* The Component Manager can update, uninstall, enable, or disable an {% glossarytooltip 55774db9-bf9d-40f3-83db-b10cc5ae3b68 %}extension{% endglossarytooltip %} if installed using Composer (including from [Packagist][2]{:target="\_blank"}, [Magento Marketplace][6]{:target="\_blank"}, or other source) *and* it has a `composer.json` file. +* The Component Manager can update, uninstall, enable, or disable an {% glossarytooltip 55774db9-bf9d-40f3-83db-b10cc5ae3b68 %}extension{% endglossarytooltip %} if installed using Composer (including from [Packagist][2]{:target="_blank"}, [Magento Marketplace][6]{:target="_blank"}, or other source) *and* it has a `composer.json` file. * The Component Manager can still enable or disable an extension *not* installed using Composer (e.g. custom code) if it has a `composer.json` file. We recommend you include `composer.json` in your component's root directory even if you do not intend to distribute it to other merchants using Magento. @@ -34,7 +34,7 @@ Keep this in mind while customizing, updating, or troubleshooting composer while ## Project vs product -In Composer, a "project" package is a template used by the [`composer create-project`][9]{:target="\_blank"} to set up the project structure. +In Composer, a "project" package is a template used by the [`composer create-project`][9]{:target="_blank"} to set up the project structure. The [installation instructions for system integrators][10] use the {{site.data.var.ce}} and {{site.data.var.ee}} project packages to set up the Magento directory structure. A "product" package is the actual application pointed to by the `composer.json` file after you download and install the project package using `composer create-project`. @@ -132,7 +132,7 @@ The `composer.json` file for a {% glossarytooltip d2093e4a-2b71-48a3-99b7-b32af7 **Type:** `magento2-language` -For language packages, you must use the correct [ISO code][4]{:target="\_blank"} for the language code in the `composer.json` file. +For language packages, you must use the correct [ISO code][4]{:target="_blank"} for the language code in the `composer.json` file. --- @@ -163,11 +163,11 @@ For example, the vendor name format for extensions released by Magento Inc is `m #### Magento Marketplace Extensions Magento Marketplace uses `vendor-name` to match an extension to a vendor during the extension submission process. -If you plan to submit your extension to the [Magento Marketplace][7]{:target="\_blank"}, you *must* use the unique Vendor Name created or assigned to you when you created your marketplace account. +If you plan to submit your extension to the [Magento Marketplace][7]{:target="_blank"}, you *must* use the unique Vendor Name created or assigned to you when you created your marketplace account. In the `composer.json` file, use the value of 'Vendor Name' in your profile for the `vendor-name` part of the extension name. -Please see the [Marketplace Documentation][5]{:target="\_blank"} for more information about your unique vendor name. +Please see the [Marketplace Documentation][5]{:target="_blank"} for more information about your unique vendor name. ### package-name diff --git a/guides/v2.0/extension-dev-guide/cache/page-caching.md b/guides/v2.0/extension-dev-guide/cache/page-caching.md index ce6bcaaac36..723ed8ff764 100644 --- a/guides/v2.0/extension-dev-guide/cache/page-caching.md +++ b/guides/v2.0/extension-dev-guide/cache/page-caching.md @@ -14,5 +14,5 @@ redirect_from: {% include cache/page-cache-overview.md%}
        -Only HTTP [GET](https://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.3){:target="_blank} and [HEAD](https://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.4){:target="_blank"} requests are cacheable. For more information about caching, see [RFC-2616 section 13](https://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html){:target="_blank}. +Only HTTP [GET](https://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.3){:target="_blank} and [HEAD](https://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.4){:target="_blank"} requests are cacheable. For more information about caching, see [RFC-2616 section 13](https://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html){:target="_blank}.
        diff --git a/guides/v2.0/extension-dev-guide/cache/page-caching/private-content.md b/guides/v2.0/extension-dev-guide/cache/page-caching/private-content.md index 0bd4d767dba..2e2598b8c0d 100644 --- a/guides/v2.0/extension-dev-guide/cache/page-caching/private-content.md +++ b/guides/v2.0/extension-dev-guide/cache/page-caching/private-content.md @@ -21,17 +21,17 @@ redirect_from: Since private content is specific to individual users, it's reasonable to handle it on the client (i.e., web browser). -Use our [customer-data]({{ site.mage2000url }}app/code/Magento/Customer/view/frontend/web/js/customer-data.js){:target="_blank"} JS library to store private data in local storage, invalidate private data using customizable rules, and synchronize data with the backend. +Use our [customer-data]({{ site.mage2000url }}app/code/Magento/Customer/view/frontend/web/js/customer-data.js){:target="_blank"} JS library to store private data in local storage, invalidate private data using customizable rules, and synchronize data with the backend. This example shows a customer's name on a cacheable page. ## Create a section source {#config-cache-priv-how-source} -The section source class is responsible for retrieving data for the section. As a best practice, we recommend you put your code under the `Vendor/ModuleName/CustomerData` namespace. Your classes must implement the [`Magento\Customer\CustomerData\SectionSourceInterface`]({{ site.mage2000url }}app/code/Magento/Customer/CustomerData/SectionSourceInterface.php){:target=" _blank"} interface. +The section source class is responsible for retrieving data for the section. As a best practice, we recommend you put your code under the `Vendor/ModuleName/CustomerData` namespace. Your classes must implement the [`Magento\Customer\CustomerData\SectionSourceInterface`]({{ site.mage2000url }}app/code/Magento/Customer/CustomerData/SectionSourceInterface.php){:target="_blank"} interface. The public method `getSectionData` must return an array with data for private block. -[Example]({{ site.mage2000url }}app/code/Magento/Catalog/CustomerData/CompareProducts.php#L36-L45){:target=" _blank"} +[Example]({{ site.mage2000url }}app/code/Magento/Catalog/CustomerData/CompareProducts.php#L36-L45){:target="_blank"} Add the following to your component's {% glossarytooltip 2be50595-c5c7-4b9d-911c-3bf2cd3f7beb %}dependency injection{% endglossarytooltip %} configuration (`di.xml`): @@ -53,7 +53,7 @@ To render private content, create a block and a template to display user-agnosti Do _not_ use the `$_isScopePrivate` property in your blocks. This property is obsolete and won't work properly.
        -Replace private data in blocks with placeholders (using [Knockout](http://knockoutjs.com/documentation/introduction.html){:target="_blank"} syntax). The init scope on the root element is `data-bind="scope: 'compareProducts'"`, where you define the scope name (`compareProducts` in this example) in your {% glossarytooltip 73ab5daa-5857-4039-97df-11269b626134 %}layout{% endglossarytooltip %}. +Replace private data in blocks with placeholders (using [Knockout](http://knockoutjs.com/documentation/introduction.html){:target="_blank"} syntax). The init scope on the root element is `data-bind="scope: 'compareProducts'"`, where you define the scope name (`compareProducts` in this example) in your {% glossarytooltip 73ab5daa-5857-4039-97df-11269b626134 %}layout{% endglossarytooltip %}. Initialize the component as follows: @@ -63,23 +63,23 @@ Initialize the component as follows: ``` -[Example]({{ site.mage2000url }}app/code/Magento/Catalog/view/frontend/templates/product/compare/sidebar.phtml#L46-L48){:target="_blank"} +[Example]({{ site.mage2000url }}app/code/Magento/Catalog/view/frontend/templates/product/compare/sidebar.phtml#L46-L48){:target="_blank"} ## Configure a UI component {#config-cache-priv-how-ui} The UI component renders block data on the Magento {% glossarytooltip 1a70d3ac-6bd9-475a-8937-5f80ca785c14 %}storefront{% endglossarytooltip %}. To initialize the UI component, you must call the initialization method `_super()`. -[Example]({{ site.mage2000url }}app/code/Magento/Catalog/view/frontend/web/js/view/compare-products.js){:target="_blank"} +[Example]({{ site.mage2000url }}app/code/Magento/Catalog/view/frontend/web/js/view/compare-products.js){:target="_blank"} All properties are available in the template. -[Example of defining a UI component in a layout]({{ site.mage2000url }}app/code/Magento/Catalog/view/frontend/layout/default.xml#L11-L22){:target="_blank"} +[Example of defining a UI component in a layout]({{ site.mage2000url }}app/code/Magento/Catalog/view/frontend/layout/default.xml#L11-L22){:target="_blank"} ## Invalidate private content Specify actions that trigger cache invalidation for private content blocks in a `sections.xml` configuration file in the `Vendor/ModuleName/etc/frontend` directory. Magento invalidates the cache on a POST or PUT request. -The following example adds comments to [app/code/Magento/Catalog/etc/frontend/sections.xml]({{ site.mage2000url }}app/code/Magento/Catalog/etc/frontend/sections.xml){:target="_blank"} to show you what the code is doing. +The following example adds comments to [app/code/Magento/Catalog/etc/frontend/sections.xml]({{ site.mage2000url }}app/code/Magento/Catalog/etc/frontend/sections.xml){:target="_blank"} to show you what the code is doing. ``` xml @@ -108,14 +108,14 @@ The following example adds comments to [app/code/Magento/Catalog/etc/frontend/se ```
        -Use only HTTP POST or PUT methods to change state (e.g., adding to a shopping cart, adding to a wishlist, etc.) and don't expect to see caching on these methods. Using GET or HEAD methods might trigger caching and prevent updates to private content. For more information about caching, see [RFC-2616 section 13](https://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html) {:target="_blank"} +Use only HTTP POST or PUT methods to change state (e.g., adding to a shopping cart, adding to a wishlist, etc.) and don't expect to see caching on these methods. Using GET or HEAD methods might trigger caching and prevent updates to private content. For more information about caching, see [RFC-2616 section 13](https://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html) {:target="_blank"}
        Other examples: -- [Checkout]({{ site.mage2000url }}app/code/Magento/Checkout/etc/frontend/sections.xml){:target="_blank"} +- [Checkout]({{ site.mage2000url }}app/code/Magento/Checkout/etc/frontend/sections.xml){:target="_blank"} -- [Customer]({{ site.mage2000url }}app/code/Magento/Customer/etc/frontend/sections.xml){:target="_blank"} +- [Customer]({{ site.mage2000url }}app/code/Magento/Customer/etc/frontend/sections.xml){:target="_blank"} ## Version private content {#config-priv-vers} diff --git a/guides/v2.0/extension-dev-guide/cache/page-caching/public-content.md b/guides/v2.0/extension-dev-guide/cache/page-caching/public-content.md index 58cc011ded9..aa58f9d05a8 100644 --- a/guides/v2.0/extension-dev-guide/cache/page-caching/public-content.md +++ b/guides/v2.0/extension-dev-guide/cache/page-caching/public-content.md @@ -119,7 +119,7 @@ Context variables should not be specific to individual users because variables a Magento generates a hash based on all context variables (`\Magento\Framework\App\Http\Context::getVaryString`). The hash and current URL are used as keys for cache storage.
        -Use the `X-Magento-Vary` cookie to transfer context on the HTTP layer. HTTP proxies can be configured to calculate a unique identifier for cache based on the cookie and URL. For example, [our sample Varnish 4 configuration]({{ site.mage2000url }}app/code/Magento/PageCache/etc/varnish4.vcl#L63-L68){:target="_blank"} uses the following: +Use the `X-Magento-Vary` cookie to transfer context on the HTTP layer. HTTP proxies can be configured to calculate a unique identifier for cache based on the cookie and URL. For example, [our sample Varnish 4 configuration]({{ site.mage2000url }}app/code/Magento/PageCache/etc/varnish4.vcl#L63-L68){:target="_blank"} uses the following: ``` sub vcl_hash { @@ -161,7 +161,7 @@ class CustomerAgeContextPlugin The `subject->setValue` argument specifies the value for newcomer context and is used to guarantee parity during cache key generation for newcomers and users who already received the `X-Magento-Vary` cookie. -For another example of a context class, see [Magento/Framework/App/Http/Context]({{ site.mage2000url }}lib/internal/Magento/Framework/App/Http/Context.php){:target="_blank"}. +For another example of a context class, see [Magento/Framework/App/Http/Context]({{ site.mage2000url }}lib/internal/Magento/Framework/App/Http/Context.php){:target="_blank"}. ## Invalidate public content @@ -169,7 +169,7 @@ You can clear cached content immediately after a entity changes. Magento uses ` This section shows you how to tell Magento what cache to clear when you change an entity. -First, your entity {% glossarytooltip c1e4242b-1f1a-44c3-9d72-1d5b1435e142 %}module{% endglossarytooltip %} must implement [`Magento/Framework/DataObject/IdentityInterface`]({{ site.mage2000url }}lib/internal/Magento/Framework/DataObject/IdentityInterface.php){:target="_blank"} as follows: +First, your entity {% glossarytooltip c1e4242b-1f1a-44c3-9d72-1d5b1435e142 %}module{% endglossarytooltip %} must implement [`Magento/Framework/DataObject/IdentityInterface`]({{ site.mage2000url }}lib/internal/Magento/Framework/DataObject/IdentityInterface.php){:target="_blank"} as follows: ``` php?start_inline=1 use Magento\Framework\DataObject\IdentityInterface; @@ -213,7 +213,7 @@ class View extends AbstractProduct implements \Magento\Framework\DataObject\Iden Magento uses cache tags for link creation. The performance of cache storage has a direct dependency on the number of tags per cache record, so try to minimize the number of tags and use them only for entities that are used in production mode. In other words, don't use invalidation for actions related to store setup.
        -Use only HTTP POST or PUT methods to change state (e.g., adding to a shopping cart, adding to a wishlist, etc.) and don't expect to see caching on these methods. Using GET or HEAD methods might trigger caching and prevent updates to private content. For more information about caching, see [RFC-2616 section 13](https://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html) {:target="_blank"} +Use only HTTP POST or PUT methods to change state (e.g., adding to a shopping cart, adding to a wishlist, etc.) and don't expect to see caching on these methods. Using GET or HEAD methods might trigger caching and prevent updates to private content. For more information about caching, see [RFC-2616 section 13](https://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html) {:target="_blank"}
        {% include cache/page-cache-checklists.md%} diff --git a/guides/v2.0/extension-dev-guide/cache/partial-caching.md b/guides/v2.0/extension-dev-guide/cache/partial-caching.md index 67904d27d12..4e6c094dc48 100644 --- a/guides/v2.0/extension-dev-guide/cache/partial-caching.md +++ b/guides/v2.0/extension-dev-guide/cache/partial-caching.md @@ -12,7 +12,7 @@ redirect_from: - /guides/v2.3/config-guide/config/caching.html --- -Magento uses Zend_Cache to interact with the cache storage. However, Magento also has the Magento\Cache {% glossarytooltip 08968dbb-2eeb-45c7-ae95-ffca228a7575 %}library{% endglossarytooltip %} for implementing Magento-specific caching. These topics discuss how to configure caching and {% glossarytooltip 0bc9c8bc-de1a-4a06-9c99-a89a29c30645 %}cache{% endglossarytooltip %} types. +Magento uses Zend_Cache to interact with the cache storage. However, Magento also has the Magento\Cache {% glossarytooltip 08968dbb-2eeb-45c7-ae95-ffca228a7575 %}library{% endglossarytooltip %} for implementing Magento-specific caching. These topics discuss how to configure caching and {% glossarytooltip 0bc9c8bc-de1a-4a06-9c99-a89a29c30645 %}cache{% endglossarytooltip %} types.

        By default, file system caching is enabled; no configuration is necessary to use it. This means the cache is located under <your Magento install dir>/var.

        diff --git a/guides/v2.0/get-started/create-integration.md b/guides/v2.0/get-started/create-integration.md index baf62dada49..71db3a02f5c 100644 --- a/guides/v2.0/get-started/create-integration.md +++ b/guides/v2.0/get-started/create-integration.md @@ -151,7 +151,7 @@ Change directories to your `Setup` directory. Create a `InstallData.php` file th * @param ConfigBasedIntegrationManager $integrationManager */ - public function __construct(ConfigBasedIntegrationManager $integrationManager) + public function __construct(ConfigBasedIntegrationManager $integrationManager) { $this->integrationManager = $integrationManager; } diff --git a/guides/v2.0/install-gde/basics/basics_docroot.md b/guides/v2.0/install-gde/basics/basics_docroot.md index daf0b5f514c..84744156834 100644 --- a/guides/v2.0/install-gde/basics/basics_docroot.md +++ b/guides/v2.0/install-gde/basics/basics_docroot.md @@ -28,11 +28,11 @@ As part of the Magento 2 installation process, you specify a subdirectory (usual ## Contact your hosting provider -If you use one, contact your hosting provider to locate the web server docroot. For example, cPanel typically uses `public_html` as its docroot, but you should contact your provider to confirm. +If you use one, contact your hosting provider to locate the web server docroot. For example, cPanel typically uses `public_html` as its docroot, but you should contact your provider to confirm. ## Find the docroot yourself -This section assumes you've already set up a simple web server using [Apache virtual hosts](https://httpd.apache.org/docs/2.4/vhosts/){:target="\_blank"} or [nginx server blocks](https://www.nginx.com/resources/wiki/start/topics/examples/server_blocks/){:target="\_blank"}. +This section assumes you've already set up a simple web server using [Apache virtual hosts](https://httpd.apache.org/docs/2.4/vhosts/){:target="_blank"} or [nginx server blocks](https://www.nginx.com/resources/wiki/start/topics/examples/server_blocks/){:target="_blank"}.
        You can use _virtual hosts_ and _server blocks_ to run more than one web site on a single machine (e.g., `company1.example.com` and `company2.example.com`) or override the web server's default docroot without changing it. diff --git a/guides/v2.0/install-gde/prereq/dev_install.md b/guides/v2.0/install-gde/prereq/dev_install.md index 6255186aecf..ac57e6327cb 100644 --- a/guides/v2.0/install-gde/prereq/dev_install.md +++ b/guides/v2.0/install-gde/prereq/dev_install.md @@ -57,7 +57,7 @@ The Magento 2 GitHub repository requires you to authenticate. The `composer inst You can clone the Magento 2 GitHub repository using either SSH or HTTPS protocols: -* Use SSH for better security (no username and password are exchanged). This requires you to share a public key with GitHub. +* Use SSH for better security (no username and password are exchanged). This requires you to share a public key with GitHub. * Use HTTPS if you don't share an SSH key with GitHub (your username and password are encrypted before being sent to GitHub). See one of the following section: @@ -71,7 +71,7 @@ To clone the Magento GitHub repository using the SSH protocol: 1. Copy to the clipboard the Magento GitHub repository SSH clone {% glossarytooltip a05c59d3-77b9-47d0-92a1-2cbffe3f8622 %}URL{% endglossarytooltip %}. - a. In a web browser, go to the Magento GitHub repository. + a. In a web browser, go to the Magento GitHub repository. b. On the right side of the page, under the *clone URL* field, click **SSH**. @@ -95,12 +95,12 @@ To clone the Magento GitHub repository using the SSH protocol: 3. Wait for the repository to clone on your server.
        -

        If the following error displays, make sure you shared your SSH key with GitHub:

        +

        If the following error displays, make sure you shared your SSH key with GitHub: 

        Cloning into 'magento2'...
 Permission denied (publickey).
 fatal: The remote end hung up unexpectedly
        -4. Optionally switch to a release tag as follows: +4. Optionally switch to a release tag as follows: git checkout tags/ [-b ] @@ -116,7 +116,7 @@ To clone the Magento GitHub repository using the HTTPS protocol: 1. Copy to the clipboard the Magento GitHub repository HTTPS clone URL. - a. In a web browser, go to the Magento GitHub repository. + a. In a web browser, go to the Magento GitHub repository. b. On the right side of the page, under the *clone URL* field, click **HTTPS**. @@ -137,7 +137,7 @@ To clone the Magento GitHub repository using the HTTPS protocol: git clone https://github.com/magento/magento2.git 3. Wait for the repository to clone on your server. -4. Optionally switch to a release tag as follows: +4. Optionally switch to a release tag as follows: git checkout tags/ [-b ] diff --git a/guides/v2.0/install-gde/prereq/install-rabbitmq.md b/guides/v2.0/install-gde/prereq/install-rabbitmq.md index c93038f83d5..f1125fd1fa7 100644 --- a/guides/v2.0/install-gde/prereq/install-rabbitmq.md +++ b/guides/v2.0/install-gde/prereq/install-rabbitmq.md @@ -36,10 +36,10 @@ This command also installs the required Erlang packages. If you have an older version of Ubuntu, RabbitMQ recommends installing the package from their {% glossarytooltip a3c8f20f-b067-414e-9781-06378c193155 %}website{% endglossarytooltip %}. -1. Download [rabbitmq-server_3.6.6-1_all.deb](https://www.rabbitmq.com/releases/rabbitmq-server/v3.6.6/rabbitmq-server_3.6.6-1_all.deb){:target="_blank"}. +1. Download [rabbitmq-server_3.6.6-1_all.deb](https://www.rabbitmq.com/releases/rabbitmq-server/v3.6.6/rabbitmq-server_3.6.6-1_all.deb){:target="_blank"}. 2. Install the package with `dpkg`. -Refer to [Installing on Debian/Ubuntu](https://www.rabbitmq.com/install-debian.html){:target="_blank"} for more information. +Refer to [Installing on Debian/Ubuntu](https://www.rabbitmq.com/install-debian.html){:target="_blank"} for more information. ## Install RabbitMQ on CentOS {#centos-install} @@ -47,7 +47,7 @@ Refer to [Installing on Debian/Ubuntu](https://www.rabbitmq.com/install-debian.h RabbitMQ was written using the Erlang programming language, which must be installed on the same system as RabbitMQ. -See [Manual installation](https://www.erlang-solutions.com/resources/download.html){:target="_blank"} for more information. +See [Manual installation](https://www.erlang-solutions.com/resources/download.html){:target="_blank"} for more information. Run the following commands to install this feature. @@ -58,13 +58,13 @@ Run the following commands to install this feature. The RabbitMQ server is included on CentOS, but the version is often old. RabbitMQ recommends installing the package from their website. -1. Download [rabbitmq-server-3.5.6-1.noarch.rpm](https://www.rabbitmq.com/releases/rabbitmq-server/v3.5.6/rabbitmq-server-3.5.6-1.noarch.rpm){:target="_blank"}. +1. Download [rabbitmq-server-3.5.6-1.noarch.rpm](https://www.rabbitmq.com/releases/rabbitmq-server/v3.5.6/rabbitmq-server-3.5.6-1.noarch.rpm){:target="_blank"}. 2. Run the following commands as a user with root permissions: -`rpm --import https://www.rabbitmq.com/rabbitmq-signing-key-public.asc{:target="_blank"} +`rpm --import https://www.rabbitmq.com/rabbitmq-signing-key-public.asc{:target="_blank"} `yum install rabbitmq-server-3.5.6-1.noarch.rpm` -Refer to [Installing on RPM-based Linux](https://www.rabbitmq.com/install-rpm.html){:target="_blank"} for more information. +Refer to [Installing on RPM-based Linux](https://www.rabbitmq.com/install-rpm.html){:target="_blank"} for more information. ## Configure RabbitMQ {#config} @@ -108,8 +108,8 @@ where: amqp-virtualhost

        The virtual host for connecting to RabbitMQ. The default is /.

        For additional information, see RabbitMQ documentation:

        - + diff --git a/guides/v2.0/install-gde/prereq/mysql.md b/guides/v2.0/install-gde/prereq/mysql.md index a9a65d16a34..b29b2a00766 100644 --- a/guides/v2.0/install-gde/prereq/mysql.md +++ b/guides/v2.0/install-gde/prereq/mysql.md @@ -29,9 +29,9 @@ If you're new to all this and need some help getting started, we suggest the fol Magento _strongly_ recommends you observe the following standard when you set up your Magento database: -* Magento uses [MySQL database triggers](http://dev.mysql.com/doc/refman/5.0/en/triggers.html){:target="_blank"} to improve database access during reindexing. Magento does not support any custom triggers in the Magento database because custom triggers can introduce incompatibilities with future Magento versions. -* Familiarize yourself with [these potential MySQL trigger limitations](http://dev.mysql.com/doc/mysql-reslimits-excerpt/5.1/en/stored-program-restrictions.html){:target="_blank"} before you continue. -* If you use MySQL database replication, be aware that Magento does _not_ support MySQL statement-based replication. Make sure you use _only_ [row-based replication](http://dev.mysql.com/doc/refman/5.1/en/replication-formats.html){:target="_blank"}. +* Magento uses [MySQL database triggers](http://dev.mysql.com/doc/refman/5.0/en/triggers.html){:target="_blank"} to improve database access during reindexing. Magento does not support any custom triggers in the Magento database because custom triggers can introduce incompatibilities with future Magento versions. +* Familiarize yourself with [these potential MySQL trigger limitations](http://dev.mysql.com/doc/mysql-reslimits-excerpt/5.1/en/stored-program-restrictions.html){:target="_blank"} before you continue. +* If you use MySQL database replication, be aware that Magento does _not_ support MySQL statement-based replication. Make sure you use _only_ [row-based replication](http://dev.mysql.com/doc/refman/5.1/en/replication-formats.html){:target="_blank"}.
        @@ -85,7 +85,7 @@ To install MySQL 5.7 on Ubuntu 16: mysql> -4. If you expect to import large numbers of products into Magento, you can increase the value for `max_allowed_packet` that is larger than the default, 16MB. +4. If you expect to import large numbers of products into Magento, you can increase the value for `max_allowed_packet` that is larger than the default, 16MB. {% include install/mysql_max-allowed-packet-ubuntu.md %} @@ -123,7 +123,7 @@ To install MySQL 5.6 on Ubuntu 14: mysql> -4. If you expect to import large numbers of products into Magento, you can increase the value for `max_allowed_packet` that is larger than the default, 16MB. +4. If you expect to import large numbers of products into Magento, you can increase the value for `max_allowed_packet` that is larger than the default, 16MB. {% include install/mysql_max-allowed-packet-ubuntu.md %} @@ -131,7 +131,7 @@ To install MySQL 5.6 on Ubuntu 14: ### Installing MySQL 5.6 on Ubuntu 12 {#instgde-prereq-mysql56ubu12} -To install MySQL 5.6 on Ubuntu 12, use the following instructions from askubuntu.com. +To install MySQL 5.6 on Ubuntu 12, use the following instructions from askubuntu.com. 1. Enter the following commands in the order shown: @@ -164,7 +164,7 @@ To install MySQL 5.6 on Ubuntu 12, use the following instructions from `max_allowed_packet` that is larger than the default, 16MB. +4. If you expect to import large numbers of products into Magento, you can increase the value for `max_allowed_packet` that is larger than the default, 16MB. {% include install/mysql_max-allowed-packet-ubuntu.md %} @@ -180,7 +180,7 @@ The Magento application 2.1.2 and later are compatible with MySQL 5.7. ### Get MySQL 5.7 for CentOS 7 -The following procedure is based on [How to Install Latest MySQL 5.7.9 on RHEL/CentOS 7/6/5 and Fedora 23/22/21](http://www.tecmint.com/install-latest-mysql-on-rhel-centos-and-fedora){:target="_blank"}. +The following procedure is based on [How to Install Latest MySQL 5.7.9 on RHEL/CentOS 7/6/5 and Fedora 23/22/21](http://www.tecmint.com/install-latest-mysql-on-rhel-centos-and-fedora){:target="_blank"}. As a user with `root` privileges, enter the following commands in the order shown: @@ -191,7 +191,7 @@ Continue with [Install and configure MySQL 5.7 on CentOS 6 or 7](#mysql57-centos ### Get MySQL 5.7 for CentOS 6 -The following procedure is based on [How to Install Latest MySQL 5.7.9 on RHEL/CentOS 7/6/5 and Fedora 23/22/21](http://www.tecmint.com/install-latest-mysql-on-rhel-centos-and-fedora){:target="_blank"}. +The following procedure is based on [How to Install Latest MySQL 5.7.9 on RHEL/CentOS 7/6/5 and Fedora 23/22/21](http://www.tecmint.com/install-latest-mysql-on-rhel-centos-and-fedora){:target="_blank"}. As a user with `root` privileges, enter the following commands in the order shown: @@ -227,7 +227,7 @@ Continue with the next section. ## Installing and configuring MySQL 5.6 on CentOS {#instgde-prereq-mysql-centos} -The following procedure is based on Install MySQL Server 5.6 in CentOS 6.x and Red Hat 6.x Linux. +The following procedure is based on Install MySQL Server 5.6 in CentOS 6.x and Red Hat 6.x Linux. 1. *CentOS 6* Install the MySQL database: @@ -268,7 +268,7 @@ The following procedure is based on `max_allowed_packet` parameter. We recommend a value of at least 16MB. +5. If you expect to import large numbers of products into Magento, you can configure MySQL to use the `max_allowed_packet` parameter. We recommend a value of at least 16MB. {% include install/mysql_max-allowed-packet-centos.md %} diff --git a/guides/v2.0/install-gde/prereq/nginx.md b/guides/v2.0/install-gde/prereq/nginx.md index 5bda5ea86e9..0fda2fe4fe7 100644 --- a/guides/v2.0/install-gde/prereq/nginx.md +++ b/guides/v2.0/install-gde/prereq/nginx.md @@ -10,7 +10,7 @@ functional_areas: - Setup --- -Magento supports nginx 1.8 (or the [latest mainline version](http://nginx.org/en/linux_packages.html#mainline){:target="_blank}). You must also install the latest version of `php-fpm`. +Magento supports nginx 1.8 (or the [latest mainline version](http://nginx.org/en/linux_packages.html#mainline){:target="_blank}). You must also install the latest version of `php-fpm`. Installation instructions vary based on which operating system you're using: diff --git a/guides/v2.0/install-gde/prereq/php-centos.md b/guides/v2.0/install-gde/prereq/php-centos.md index 910e6d1c1d5..1ea4049313b 100644 --- a/guides/v2.0/install-gde/prereq/php-centos.md +++ b/guides/v2.0/install-gde/prereq/php-centos.md @@ -44,14 +44,14 @@ To verify if PHP is installed already, enter `php -v`. If {% glossarytooltip bf7
        -

        The preceding message confirms that the Zend OPcache is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the PHP OPcache documentation.

         +

        The preceding message confirms that the Zend OPcache is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the PHP OPcache documentation.

        If PHP is installed, continue with the next prerequisite, MySQL. ## CentOS repositories {#centos-php-repos} -Linux systems provide software like PHP in one or more *repositories*. CentOS, unlike Ubuntu, has a set of [officially recommended repositories](https://wiki.centos.org/AdditionalResources/Repositories){:target="\_blank"}. Other repositories are considered less safe for the reasons stated on the CentOS wiki. +Linux systems provide software like PHP in one or more *repositories*. CentOS, unlike Ubuntu, has a set of [officially recommended repositories](https://wiki.centos.org/AdditionalResources/Repositories){:target="_blank"}. Other repositories are considered less safe for the reasons stated on the CentOS wiki. We're not aware that you can install PHP 5.5, 5.6, or 7.0 from a CentOS-recommended repository. Therefore, you must consider the following: @@ -60,9 +60,9 @@ We're not aware that you can install PHP 5.5, 5.6, or 7.0 from a CentOS-recommen You should also consider upgrading to a later version of CentOS that has the desired PHP version in a recommended repository. * If you're setting up a development system, you can use any repository you wish. -In this topic, we show how to install PHP using the [Inline with Upstream Stable (IUS)](https://ius.io/GettingStarted){:target="\_blank"} repository, which is *not* on the CentOS recommended list. However, packages installed from IUS do not use the same names as CentOS-provided packages, so [no existing system packages are replaced](https://ius.io/Philosophy){:target="\_blank"}. +In this topic, we show how to install PHP using the [Inline with Upstream Stable (IUS)](https://ius.io/GettingStarted){:target="_blank"} repository, which is *not* on the CentOS recommended list. However, packages installed from IUS do not use the same names as CentOS-provided packages, so [no existing system packages are replaced](https://ius.io/Philosophy){:target="_blank"}. -Before you continue, review their [Getting Started topic](https://ius.io/GettingStarted){:target="\_blank"}. +Before you continue, review their [Getting Started topic](https://ius.io/GettingStarted){:target="_blank"}.

        Magento does not officially recommend using the IUS repository. We discuss it here for example purposes only.

        @@ -115,7 +115,7 @@ There is more than one way to install PHP 7.0.2 or later; the following is a sug
        -

        The preceding message confirms that the Zend OPcache is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the PHP OPcache documentation.

         +

        The preceding message confirms that the Zend OPcache is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the PHP OPcache documentation.

        3. Continue with [Required PHP settings]({{ page.baseurl }}/install-gde/prereq/php-settings.html). @@ -172,7 +172,7 @@ There is more than one way to install PHP 5.6 on CentOS; the following is a sugg
        -

        The preceding message confirms that the Zend OPcache is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the PHP OPcache documentation.

         +

        The preceding message confirms that the Zend OPcache is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the PHP OPcache documentation.

        3. Continue with [Required PHP settings]({{ page.baseurl }}/install-gde/prereq/php-settings.html). diff --git a/guides/v2.0/install-gde/prereq/php-ubuntu.md b/guides/v2.0/install-gde/prereq/php-ubuntu.md index db3f197fe77..261bf2e20b9 100644 --- a/guides/v2.0/install-gde/prereq/php-ubuntu.md +++ b/guides/v2.0/install-gde/prereq/php-ubuntu.md @@ -49,7 +49,7 @@ To verify if PHP is installed already, enter `php -v`. If PHP is installed, mess
        -

        The preceding message confirms that the Zend OPcache is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the PHP OPcache documentation.

         +

        The preceding message confirms that the Zend OPcache is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the PHP OPcache documentation.

        If PHP is installed, continue with the next prerequisite, MySQL. @@ -88,7 +88,7 @@ If PHP is *not* installed, see one of the following sections:
        -

        The preceding message confirms that the Zend OPcache is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the PHP OPcache documentation.

         +

        The preceding message confirms that the Zend OPcache is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the PHP OPcache documentation.

        3. Continue with [Required PHP settings]({{ page.baseurl }}/install-gde/prereq/php-settings.html). @@ -119,7 +119,7 @@ If PHP is *not* installed, see one of the following sections:
        -

        The preceding message confirms that the Zend OPcache is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the PHP OPcache documentation.

         +

        The preceding message confirms that the Zend OPcache is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the PHP OPcache documentation.

        3. Continue with [Required PHP settings]({{ page.baseurl }}/install-gde/prereq/php-settings.html). @@ -143,7 +143,7 @@ If PHP is *not* installed, see one of the following sections:
        -

        The preceding message confirms that the Zend OPcache is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the PHP OPcache documentation.

         +

        The preceding message confirms that the Zend OPcache is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the PHP OPcache documentation.

        3. Continue with [Required PHP settings]({{ page.baseurl }}/install-gde/prereq/php-settings.html). diff --git a/guides/v2.0/install-gde/tutorials/change-docroot-to-pub.md b/guides/v2.0/install-gde/tutorials/change-docroot-to-pub.md index 9ff7bd17874..4861254fbb2 100644 --- a/guides/v2.0/install-gde/tutorials/change-docroot-to-pub.md +++ b/guides/v2.0/install-gde/tutorials/change-docroot-to-pub.md @@ -12,7 +12,7 @@ If you're accustomed to using the Web Setup Wizard during development, be aware
        -If you're using [nginx]({{ page.baseurl }}/install-gde/prereq/nginx.html) and the [`nginx.conf.sample`]({{ site.mage2200url }}nginx.conf.sample){:target="\_blank"} file included in the Magento installation directory, you're probably already serving files from the `pub/` directory. +If you're using [nginx]({{ page.baseurl }}/install-gde/prereq/nginx.html) and the [`nginx.conf.sample`]({{ site.mage2200url }}nginx.conf.sample){:target="_blank"} file included in the Magento installation directory, you're probably already serving files from the `pub/` directory. The sample configuration overrides your server's docroot settings to serve files from Magento's `pub/` directory; assuming you've referenced the `nginx.conf.sample` in the server block that defines your site. For example, see the last line in the following configuration: @@ -34,7 +34,7 @@ The sample configuration overrides your server's docroot settings to serve files ## Before you begin -To complete this tutorial, you'll need access to a working Magento installation running on a [LAMP](https://en.wikipedia.org/wiki/LAMP_(software_bundle)){:target="\_blank"} stack: +To complete this tutorial, you'll need access to a working Magento installation running on a [LAMP](https://en.wikipedia.org/wiki/LAMP_(software_bundle)){:target="_blank"} stack: - Linux - Apache (2.2+) diff --git a/guides/v2.0/migration/migration-tool-internal-spec.md b/guides/v2.0/migration/migration-tool-internal-spec.md index 41fd338b885..88e05d78148 100644 --- a/guides/v2.0/migration/migration-tool-internal-spec.md +++ b/guides/v2.0/migration/migration-tool-internal-spec.md @@ -16,11 +16,11 @@ This section describes an implementation details of Data Migration Tool and how ### Repositories {#repositories} -Data Migration Tool repository migration-tool +Data Migration Tool repository migration-tool ### System requirements {#system-requirements} -Same as for Magento 2 +Same as for Magento 2 ## Internal structure {#migrate-is} diff --git a/guides/v2.0/migration/migration-troubleshooting.md b/guides/v2.0/migration/migration-troubleshooting.md index 224508e4a89..08e40ce20d9 100644 --- a/guides/v2.0/migration/migration-troubleshooting.md +++ b/guides/v2.0/migration/migration-troubleshooting.md @@ -33,7 +33,7 @@ This message appears because the Data Migration Tool runs internal tests to veri #### Possible solutions -* Install the corresponding Magento 2 extensions from [Magento Marketplace](https://marketplace.magento.com/){:target:"_blank"} +* Install the corresponding Magento 2 extensions from [Magento Marketplace](https://marketplace.magento.com/){:target:"_blank"} If the conflicting data originates from an extension which adds own database structure elements, then the Magento 2 version of the same extension may add such elements to the destination (Magento 2) database, thus fixing the issue. diff --git a/guides/v2.0/mtf/mtf_entities/mtf_block.md b/guides/v2.0/mtf/mtf_entities/mtf_block.md index fd8c7841544..20ba02a09df 100644 --- a/guides/v2.0/mtf/mtf_entities/mtf_block.md +++ b/guides/v2.0/mtf/mtf_entities/mtf_block.md @@ -18,7 +18,7 @@ This topic shows how to create a new block and explore its structure. It discuss ## Example {#mtf_block_class} -A block `Magento\Ui\Test\Block\Messages` extends a basic block [`Magento\Mtf\Block\Block`]{:target=_blank} and implements methods to interact with messages. +A block `Magento\Ui\Test\Block\Messages` extends a basic block [`Magento\Mtf\Block\Block`]{:target="_blank"} and implements methods to interact with messages. {% collapsible Show/hide the code %} {% highlight php inline=true %} @@ -190,16 +190,16 @@ class Messages extends Block Magento contains basic blocks for the functional testing with a logic that you can reuse. The most popular are the following: -* [`Magento\Mtf\Block\Block`]{:target=_blank} -* [`Magento\Mtf\Block\Form`]{:target=_blank} -* [`Magento\Backend\Test\Block\Widget\Tab`]{:target=_blank} -* [`Magento\Backend\Test\Block\Widget\FormTabs`]{:target=_blank} -* [`Magento\Backend\Test\Block\Widget\Grid`]{:target=_blank} -* [`Magento\Ui\Test\Block\Adminhtml\DataGrid`]{:target=_blank} +* [`Magento\Mtf\Block\Block`]{:target="_blank"} +* [`Magento\Mtf\Block\Form`]{:target="_blank"} +* [`Magento\Backend\Test\Block\Widget\Tab`]{:target="_blank"} +* [`Magento\Backend\Test\Block\Widget\FormTabs`]{:target="_blank"} +* [`Magento\Backend\Test\Block\Widget\Grid`]{:target="_blank"} +* [`Magento\Ui\Test\Block\Adminhtml\DataGrid`]{:target="_blank"} ## Block identifier {#mtf_block_identifier} -Each block has an identifier that includes selector and searching strategy. This identifier is determined by the [`Magento\Mtf\Client\Element\Locator`]{:target=_blank} class and is stored in the `_rootElement` property of the [`Magento\Mtf\Block\Block`]{:target=_blank} class. +Each block has an identifier that includes selector and searching strategy. This identifier is determined by the [`Magento\Mtf\Client\Element\Locator`]{:target="_blank"} class and is stored in the `_rootElement` property of the [`Magento\Mtf\Block\Block`]{:target="_blank"} class. You can use the `_rootElement` to find an element in the current block. diff --git a/guides/v2.1/cloud/access-acct/fastly.md b/guides/v2.1/cloud/access-acct/fastly.md index 205fbb8bddd..96aa5bfd7fc 100644 --- a/guides/v2.1/cloud/access-acct/fastly.md +++ b/guides/v2.1/cloud/access-acct/fastly.md @@ -150,13 +150,13 @@ Complete the following configuration steps in Staging and Production environment 4. For **Caching Application**, uncheck the **Use system value** checkbox and select **Fastly CDN** from the drop-down list. ![Choose Fastly]({{ site.baseurl }}/common/images/cloud-fastly_enable-admin.png){:width="550px"} -5. Expand **Fastly Configuration**. You can then [choose caching options](https://github.com/fastly/fastly-magento2/blob/master/Documentation/CONFIGURATION.md#configure-the-module){:target="\_blank"}. +5. Expand **Fastly Configuration**. You can then [choose caching options](https://github.com/fastly/fastly-magento2/blob/master/Documentation/CONFIGURATION.md#configure-the-module){:target="_blank"}. 6. When you're done, click **Save Config** at the top of the page. 7. Clear the cache according to the notification. After you have cleared the cache, navigate back to **Stores** > **Configuration** > **Advanced** > **System** > **Fastly Configuration** and continue your configurations. -Configure the following features and enable additional [configuration options](https://github.com/fastly/fastly-magento2/blob/master/Documentation/CONFIGURATION.md#further-configuration-options){:target="\_blank"}: +Configure the following features and enable additional [configuration options](https://github.com/fastly/fastly-magento2/blob/master/Documentation/CONFIGURATION.md#further-configuration-options){:target="_blank"}: * [Upload Fastly VCL snippets](#upload-vcl-snippets) * [Configure backends and Origin shielding](#backend) @@ -173,7 +173,7 @@ the **Upload VCL to Fastly** button to upload your default [VCL snippets](#custo You don't have to create or code VCL snippets. We provide a default set of snippets for Fastly. You only need to click **Upload VCL to Fastly** to finish this step. -The installed Fastly module includes the following default [VCL snippets](https://github.com/fastly/fastly-magento2/tree/master/etc/vcl_snippets){:target="\blank"} +The installed Fastly module includes the following default [VCL snippets](https://github.com/fastly/fastly-magento2/tree/master/etc/vcl_snippets){:target="_blank"} that drive the integration with Fastly. These VCL snippets are not available until you upload them. When you click Upload, you push a set of these default VCL snippets to Fastly for your specific Service ID and extension. @@ -203,7 +203,7 @@ After the upload completes, you can create and upload custom VCL snippets with advanced settings and options. You use APIs to add these VCL snippets, further adding them in your site code depending on the actions. -For more information, see [Fastly VCL documentation](https://docs.fastly.com/guides/vcl/guide-to-vcl){:target="\_blank"} and [Fastly VCL snippets](https://docs.fastly.com/guides/vcl-snippets/about-vcl-snippets){:target="\_blank"}. +For more information, see [Fastly VCL documentation](https://docs.fastly.com/guides/vcl/guide-to-vcl){:target="_blank"} and [Fastly VCL snippets](https://docs.fastly.com/guides/vcl-snippets/about-vcl-snippets){:target="_blank"}. ## Configure backends and Origin shielding {#backend} @@ -258,7 +258,7 @@ handle your blog. 6. Click **Upload** to save. The settings are communicated to Fastly. 7. In the Magento Admin, click **Save Config**. -For more information from Fastly, see the Magento 2 [Backend settings guide](https://github.com/fastly/fastly-magento2/blob/21b61c8189971275589219d418332798efc7db41/Documentation/Guides/BACKEND-SETTINGS.md){:target="\_blank"}. +For more information from Fastly, see the Magento 2 [Backend settings guide](https://github.com/fastly/fastly-magento2/blob/21b61c8189971275589219d418332798efc7db41/Documentation/Guides/BACKEND-SETTINGS.md){:target="_blank"}. ## Configure purge options {#purge} @@ -299,7 +299,7 @@ purge caches through the Cache Management page. 4. After the page reloads, click **Upload VCL to Fastly** in the *Fastly Configuration* section. -For more information, see [the Fastly configuration options](https://github.com/fastly/fastly-magento2/blob/21b61c8189971275589219d418332798efc7db41/Documentation/CONFIGURATION.md#further-configuration-options){:target="\_blank"}. +For more information, see [the Fastly configuration options](https://github.com/fastly/fastly-magento2/blob/21b61c8189971275589219d418332798efc7db41/Documentation/CONFIGURATION.md#further-configuration-options){:target="_blank"}. ## Create a custom error/maintenance page {#fastly-errpg} @@ -320,7 +320,7 @@ To create a custom error/maintenance page: {:#info .bs-callout .bs-callout-info} Avoid using images on your site in the event Fastly is not available. To use - images, refer to [Data URIs on the css-tricks site](https://css-tricks.com/data-uris/){:target="\_blank"}. + images, refer to [Data URIs on the css-tricks site](https://css-tricks.com/data-uris/){:target="_blank"}. 4. When you're done, click **Upload** to send your updates to Fastly. 5. Click **Save Config** at the top of the page. @@ -359,13 +359,13 @@ Fastly options. 3. For GeoIP Action, select if the visitor is automatically redirected with **Redirect** or provided a list of stores to select from with **Dialog**. 4. For **Country Mapping**, click **Add** to enter a two-letter country code to - map with a specific Magento store from a list. For a list of country codes, see [this site](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2){:target="\_blank"}. + map with a specific Magento store from a list. For a list of country codes, see [this site](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2){:target="_blank"}. ![Add GeoIP country maps]({{ site.baseurl }}/common/images/cloud_fastly-geo-code.png) 5. Click **Save Config** at the top of the page. 6. After page reload, click *Upload VCL to Fastly* in the *Fastly Configuration* section. -Fastly also provides a series of [geolocation-related VCL features](https://docs.fastly.com/guides/vcl/geolocation-related-vcl-features){:target="\_blank"} +Fastly also provides a series of [geolocation-related VCL features](https://docs.fastly.com/guides/vcl/geolocation-related-vcl-features){:target="_blank"} for customized geolocation coding. ## Configure DNS for Fastly {#fastly-dns} @@ -378,17 +378,17 @@ add a CNAME record for your website that points to the Fastly service: you must add a CNAME record for each one. {:#info .bs-callout .bs-callout-info} -This does not work for an [apex domain](https://blog.cloudflare.com/zone-apex-naked-domain-root-domain-cname-supp){:target="\_blank"} (also referred to as a _naked_ domain). You must use a DNS +This does not work for an [apex domain](https://blog.cloudflare.com/zone-apex-naked-domain-root-domain-cname-supp){:target="_blank"} (also referred to as a _naked_ domain). You must use a DNS provider that supports forwarding DNS queries to use an apex domain. The following list contains examples of DNS providers for informational purposes. Use your preferred DNS provider. -* CNAME with ALIAS record from [Dyn](http://dyn.com){:target="\_blank"} -* ANAME record on [DNS Made Easy](http://www.dnsmadeeasy.com){:target="\_blank"} -* ANAME at [easyDNS](https://www.easydns.com){:target="\_blank"} -* ACNAME at [CloudFlare](https://www.cloudflare.com){:target="\_blank"} -* ALIAS at [PointDNS](https://pointhq.com){:target="\_blank"} +* CNAME with ALIAS record from [Dyn](http://dyn.com){:target="_blank"} +* ANAME record on [DNS Made Easy](http://www.dnsmadeeasy.com){:target="_blank"} +* ANAME at [easyDNS](https://www.easydns.com){:target="_blank"} +* ACNAME at [CloudFlare](https://www.cloudflare.com){:target="_blank"} +* ALIAS at [PointDNS](https://pointhq.com){:target="_blank"} Many other DNS providers also offer workarounds to accomplish this goal. The most common is to add a CNAME record for the `www` host on the domain and then use the @@ -416,13 +416,13 @@ DNS information and going live, let us know you are using TLS, provide your domain names, and request the TXT record. You can then send this record to your DNS provider. The domain validation process is executed by Fastly. -For details on this TXT record, see the Fastly [DNS TXT record validation](https://docs.fastly.com/guides/securing-communications/domain-validation-for-tls-certificates#dns-text-record-verification){:target="\_blank"}. +For details on this TXT record, see the Fastly [DNS TXT record validation](https://docs.fastly.com/guides/securing-communications/domain-validation-for-tls-certificates#dns-text-record-verification){:target="_blank"}. ## Upgrade Fastly {#upgrade} Fastly updates the Magento module to resolve issues, increase performance, and -provide new features. You can check the [Magento Marketplace](https://marketplace.magento.com/fastly-magento2.html){:target="\_blank"} -and [GitHub](https://github.com/fastly/fastly-magento2/releases){:target="\_blank"} +provide new features. You can check the [Magento Marketplace](https://marketplace.magento.com/fastly-magento2.html){:target="_blank"} +and [GitHub](https://github.com/fastly/fastly-magento2/releases){:target="_blank"} for updates on the latest releases. When you upgrade Fastly, you get the upgraded subset of default VCL snippets. diff --git a/guides/v2.1/cloud/access-acct/first-time-setup.md b/guides/v2.1/cloud/access-acct/first-time-setup.md index d682ff4bca3..c1f7974923e 100644 --- a/guides/v2.1/cloud/access-acct/first-time-setup.md +++ b/guides/v2.1/cloud/access-acct/first-time-setup.md @@ -30,10 +30,10 @@ After you receive an invitation, you can complete tasks to create your local, pu We highly recommend having experience with the following technologies and methodologies: * Magento [technology stack]({{ page.baseurl }}/architecture/tech-stack.html) -* [Git](https://git-scm.com/){:target="\_blank"} for repository and code management, [branching methodologies](https://git-scm.com/book/en/v2/Git-Branching-Branching-Workflows){:target="\_blank"}, and working with Magento Git code -* [GitHub](https://github.com/){:target="\_blank"} for managing your code and accessing Magento repositories -* [Fastly](https://www.fastly.com/){:target="\_blank"} for CDN and caching, used in Staging and Production -* [Galera Cluster](http://galeracluster.com/){:target="\_blank"} for databases, used in Staging and Production (with triple redundancy failover in Production) +* [Git](https://git-scm.com/){:target="_blank"} for repository and code management, [branching methodologies](https://git-scm.com/book/en/v2/Git-Branching-Branching-Workflows){:target="_blank"}, and working with Magento Git code +* [GitHub](https://github.com/){:target="_blank"} for managing your code and accessing Magento repositories +* [Fastly](https://www.fastly.com/){:target="_blank"} for CDN and caching, used in Staging and Production +* [Galera Cluster](http://galeracluster.com/){:target="_blank"} for databases, used in Staging and Production (with triple redundancy failover in Production) ## Gather credentials {#credentials} diff --git a/guides/v2.1/cloud/access-acct/first-time-setup_import-first-steps.md b/guides/v2.1/cloud/access-acct/first-time-setup_import-first-steps.md index 59e7b2045ae..7e456c75c68 100644 --- a/guides/v2.1/cloud/access-acct/first-time-setup_import-first-steps.md +++ b/guides/v2.1/cloud/access-acct/first-time-setup_import-first-steps.md @@ -91,7 +91,7 @@ The complete workflow for importing existing code includes the following steps: ## Create a new {{site.data.var.ece}} project {#cloud-import-proj} -1. Access your account. Open the email you received from Magento Cloud (accounts@magento.cloud) and click the _Access your project now_ link. Or you can log in to [your Magento Commerce account](https://accounts.magento.cloud){:target="\_blank"}. +1. Access your account. Open the email you received from Magento Cloud (accounts@magento.cloud) and click the _Access your project now_ link. Or you can log in to [your Magento Commerce account](https://accounts.magento.cloud){:target="_blank"}. 1. Click the _This project has no code yet_ link next to the project name. diff --git a/guides/v2.1/cloud/access-acct/first-time-setup_import-prepare.md b/guides/v2.1/cloud/access-acct/first-time-setup_import-prepare.md index faa1dd1c5bb..770f6e67b80 100644 --- a/guides/v2.1/cloud/access-acct/first-time-setup_import-prepare.md +++ b/guides/v2.1/cloud/access-acct/first-time-setup_import-prepare.md @@ -30,7 +30,7 @@ To import {{site.data.var.ee}} code to a {{site.data.var.ece}} project, you must Add these files to your {{site.data.var.ee}} code: -1. In the [{{site.data.var.ece}} GitHub repository](https://github.com/magento/magento-cloud){:target="\_blank"}, select the branch corresponding to the {{site.data.var.ee}} version you currently have. +1. In the [{{site.data.var.ece}} GitHub repository](https://github.com/magento/magento-cloud){:target="_blank"}, select the branch corresponding to the {{site.data.var.ee}} version you currently have. The following figure shows an example of selecting the `2.1.4` branch. @@ -56,7 +56,7 @@ Add these files to your {{site.data.var.ee}} code: For example, to create `/.magento.app.yaml` from the 2.1.4 branch: - 1. In the {{site.data.var.ece}} GitHub, click [**.magento.app.yaml**](https://github.com/magento/magento-cloud/blob/2.1.4/.magento.app.yaml){:target="\_blank"}. + 1. In the {{site.data.var.ece}} GitHub, click [**.magento.app.yaml**](https://github.com/magento/magento-cloud/blob/2.1.4/.magento.app.yaml){:target="_blank"}. 2. In the upper right, click **Raw**, as the following figure shows. ![View the raw version of the file]({{ site.baseurl }}/common/images/cloud_cloud-git_raw.png){:width="600px"} @@ -79,7 +79,7 @@ You must have an authentication key to access the {{site.data.var.ee}} repositor #### To create a new `auth.json` file: -First, verify if you have an `auth.json` file, located in your Magento root directory. You can also [get a sample `auth.json`](https://github.com/magento/magento2/blob/2.2-develop/auth.json.sample){:target="\_blank"}. +First, verify if you have an `auth.json` file, located in your Magento root directory. You can also [get a sample `auth.json`](https://github.com/magento/magento2/blob/2.2-develop/auth.json.sample){:target="_blank"}. 1. Using a text editor, create an `auth.json` file and save it in your Magento root directory. @@ -132,7 +132,7 @@ This method is best to prevent accidental exposure of credentials, such as pushi ## Edit `composer.json` {#composer-json} -Before you push code to the {{site.data.var.ece}} Git repository, modify your `composer.json` for Cloud. You can also [view a sample `composer.json`](https://raw.githubusercontent.com/magento/magento-cloud/master/composer.json){:target="\_blank"}. +Before you push code to the {{site.data.var.ece}} Git repository, modify your `composer.json` for Cloud. You can also [view a sample `composer.json`](https://raw.githubusercontent.com/magento/magento-cloud/master/composer.json){:target="_blank"}. To edit `composer.json`: diff --git a/guides/v2.1/cloud/architecture/pro-architecture-legacy.md b/guides/v2.1/cloud/architecture/pro-architecture-legacy.md index 607d35ad45b..0c23f2606a1 100644 --- a/guides/v2.1/cloud/architecture/pro-architecture-legacy.md +++ b/guides/v2.1/cloud/architecture/pro-architecture-legacy.md @@ -158,7 +158,7 @@ The following figure shows the technology used in the Production environment: {{site.data.var.ee}} seamlessly scales from the smallest 6 CPU cluster with 11.25GB of RAM to the largest 96 CPU cluster with 180GB of RAM. Our triple-redundant architecture means we can offer upscaling without downtime. When upscaling, we rotate each of the three instances to upgrade without downtime of your site. -In addition, extra web servers can be added to an existing cluster should the constriction be at the {% glossarytooltip bf703ab1-ca4b-48f9-b2b7-16a81fd46e02 %}PHP{% endglossarytooltip %} level rather than the database level. This provides [*horizontal scaling*](https://en.wikipedia.org/wiki/Scalability#Horizontal_and_vertical_scaling){:target="\_blank"} to complement the vertical scaling provided by extra CPUs on the database level. +In addition, extra web servers can be added to an existing cluster should the constriction be at the {% glossarytooltip bf703ab1-ca4b-48f9-b2b7-16a81fd46e02 %}PHP{% endglossarytooltip %} level rather than the database level. This provides [*horizontal scaling*](https://en.wikipedia.org/wiki/Scalability#Horizontal_and_vertical_scaling){:target="_blank"} to complement the vertical scaling provided by extra CPUs on the database level. ## Services {#cloud-arch-services} {{site.data.var.ece}} currently supports the following services: diff --git a/guides/v2.1/cloud/basic-information/starter-develop-deploy-workflow.md b/guides/v2.1/cloud/basic-information/starter-develop-deploy-workflow.md index 75764704d77..f90bc01dedf 100644 --- a/guides/v2.1/cloud/basic-information/starter-develop-deploy-workflow.md +++ b/guides/v2.1/cloud/basic-information/starter-develop-deploy-workflow.md @@ -92,9 +92,9 @@ Configure your store settings from the Magento Admin panel for the Integration e For the best information on configurations, review the documentation for {{site.data.var.ee}} and the installed extensions. Here are some links and ideas to help you get kickstarted: * [Best practices for store configuration]({{ page.baseurl }}/cloud/configure/configure-best-practices.html) for specific best practices in the cloud -* [Basic configuration](http://docs.magento.com/m2/ee/user_guide/configuration/configuration-basic.html){:target="\_blank"} for store admin access, name, languages, currencies, branding, sites, store views and more -* [Theme](http://docs.magento.com/m2/ee/user_guide/design/design-theme.html){:target="\_blank"} for your look and feel of the site and stores including CSS and layouts -* [System configuration](http://docs.magento.com/m2/ee/user_guide/system/system.html){:target="\_blank"} for roles, tools, notifications, and your encryption key for your database +* [Basic configuration](http://docs.magento.com/m2/ee/user_guide/configuration/configuration-basic.html){:target="_blank"} for store admin access, name, languages, currencies, branding, sites, store views and more +* [Theme](http://docs.magento.com/m2/ee/user_guide/design/design-theme.html){:target="_blank"} for your look and feel of the site and stores including CSS and layouts +* [System configuration](http://docs.magento.com/m2/ee/user_guide/system/system.html){:target="_blank"} for roles, tools, notifications, and your encryption key for your database * Extension settings using their documentation Beyond just store settings, you can further configure multiple sites and stores, configured services, and more. For details, see [Configure Magento Commerce]({{ page.baseurl }}/cloud/configure/configuration-overview.html). diff --git a/guides/v2.1/cloud/before/before-setup-env-2_clone.md b/guides/v2.1/cloud/before/before-setup-env-2_clone.md index 1f24eb4b02b..44405007a5f 100644 --- a/guides/v2.1/cloud/before/before-setup-env-2_clone.md +++ b/guides/v2.1/cloud/before/before-setup-env-2_clone.md @@ -22,7 +22,7 @@ functional_areas: The Magento Commerce project is a Git repository of Magento code with a master origin. Develop your custom code and add extensions in one of eight active Git branches in your local. Each active environment includes a database and services to fully access the Magento site and store in the Integration environment. -To begin, you need to clone the `master` environment to your local and add the Magento Admin URL, username, and password (to include with all branches). If you are new to Git workflow, processes, and commands, see Git [documentation](https://git-scm.com/documentation){:target="\_blank"}. +To begin, you need to clone the `master` environment to your local and add the Magento Admin URL, username, and password (to include with all branches). If you are new to Git workflow, processes, and commands, see Git [documentation](https://git-scm.com/documentation){:target="_blank"}. The commands in these instructions use Magento CLI commands and Git commands to access the `master` environment. For a full list of Magento Cloud CLI commands, enter `magento-cloud list` or see the [Magento CLI reference]({{ page.baseurl }}/cloud/reference/cli-ref-topic.html). @@ -92,7 +92,7 @@ To set Admin variables, you will use this command format: magento-cloud variable:set -e -You can also [log into your project](https://accounts.magento.cloud){:target="\_blank"} in the Project Web Interface to review project variables entered there. Click the Configure environment gear icon ![Configure your environment]({{ site.baseurl }}/common/images/cloud_edit-project.png) next to the Project name. Click the **Variables** tab and review any configured variables there. +You can also [log into your project](https://accounts.magento.cloud){:target="_blank"} in the Project Web Interface to review project variables entered there. Click the Configure environment gear icon ![Configure your environment]({{ site.baseurl }}/common/images/cloud_edit-project.png) next to the Project name. Click the **Variables** tab and review any configured variables there. {: .bs-callout .bs-callout-warning} Every time you add or modify a variable using the web interface or the CLI, the branch will redeploy automatically. @@ -142,7 +142,7 @@ To set variables using the CLI (with example values used): To set variables using the Project Web Interface: -1. Log in to [your {{site.data.var.ece}} account](https://accounts.magento.cloud){:target="\_blank"}. +1. Log in to [your {{site.data.var.ece}} account](https://accounts.magento.cloud){:target="_blank"}. 2. Click the Configure environment gear icon ![Configure your environment]({{ site.baseurl }}/common/images/cloud_edit-project.png) next to the Project name. If you are asked to create the project, click **Continue Later**. ![Project without code]({{ site.baseurl }}/common/images/cloud_project_empty.png) diff --git a/guides/v2.1/cloud/before/before-workspace-cloud-account.md b/guides/v2.1/cloud/before/before-workspace-cloud-account.md index 82a2649cc8f..65ae929a172 100644 --- a/guides/v2.1/cloud/before/before-workspace-cloud-account.md +++ b/guides/v2.1/cloud/before/before-workspace-cloud-account.md @@ -10,7 +10,7 @@ menu_node: #### Previous step: [Prepare for local environment setup]({{ page.baseurl }}/cloud/before/before-workspace.html) -To begin working with a project and develop your store, you should have received an e-mail invitation to [create a Mangento Enterprise Cloud Edition account](https://accounts.magento.cloud){:target="\_blank"}. The account provides access to your project for Magento development and deployment across all supported environments. +To begin working with a project and develop your store, you should have received an e-mail invitation to [create a Mangento Enterprise Cloud Edition account](https://accounts.magento.cloud){:target="_blank"}. The account provides access to your project for Magento development and deployment across all supported environments. You should receive an e-mail invitation to verify and access the account. If you don't see the invitation, check your junk e-mail folder. Click the **Verify my account** option in the email to verify and access your account. diff --git a/guides/v2.1/cloud/cdn/cloud-fastly.md b/guides/v2.1/cloud/cdn/cloud-fastly.md index 1ed713d7e93..94a69833927 100644 --- a/guides/v2.1/cloud/cdn/cloud-fastly.md +++ b/guides/v2.1/cloud/cdn/cloud-fastly.md @@ -12,8 +12,8 @@ functional_areas: --- Fastly is a CDN based on Varnish caching, basically a cloud varnish service. When -working with Fastly, you are also working directly with a heavily customized version of Varnish (2.1). [Fastly](https://docs.fastly.com/){:target="\_blank"} -with [Varnish](https://varnish-cache.org/docs/){:target="\_blank"} caches your +working with Fastly, you are also working directly with a heavily customized version of Varnish (2.1). [Fastly](https://docs.fastly.com/){:target="_blank"} +with [Varnish](https://varnish-cache.org/docs/){:target="_blank"} caches your site pages, assets, CSS, and more in backend data centers you set up. As customers access your site and stores, the requests hit Fastly to load cached pages faster. @@ -149,14 +149,14 @@ instructions on creating [custom Fastly VCL snippets]({{ page.baseurl }}/cloud/c Fastly supports forcing unencrypted requests to TLS through the Force TLS feature. Set up a secure base URL in Magento and turn on the Force TLS option -in the Fastly extension. For details and instructions, see the Fastly [Force TLS guide](https://github.com/fastly/fastly-magento2/blob/master/Documentation/Guides/FORCE-TLS.md){:target="\_blank"}. +in the Fastly extension. For details and instructions, see the Fastly [Force TLS guide](https://github.com/fastly/fastly-magento2/blob/master/Documentation/Guides/FORCE-TLS.md){:target="_blank"}. ## GeoIP service support {#geoip} Fastly provides a GeoIP service and supports some GeoIP functionality. GeoIP handling manages visitor redirection (automatically) and store matching (select from list) based on their obtained country code. For more information, -see the Fastly [GeoIP documentation](https://github.com/fastly/fastly-magento2/blob/21b61c8189971275589219d418332798efc7db41/Documentation/CONFIGURATION.md#geoip-handling){:target="\_blank"}. +see the Fastly [GeoIP documentation](https://github.com/fastly/fastly-magento2/blob/21b61c8189971275589219d418332798efc7db41/Documentation/CONFIGURATION.md#geoip-handling){:target="_blank"}. ## Image Optimization support diff --git a/guides/v2.1/cloud/cdn/fastly-image-optimization.md b/guides/v2.1/cloud/cdn/fastly-image-optimization.md index 12791e5e4a2..f6e84fd515f 100644 --- a/guides/v2.1/cloud/cdn/fastly-image-optimization.md +++ b/guides/v2.1/cloud/cdn/fastly-image-optimization.md @@ -23,7 +23,7 @@ images through image optimizers, using default configurations. #### To enable Fastly IO: 1. Log in to your local - [Magento Admin]({{ page.baseurl }}/cloud/onboarding/onboarding-tasks.html#admin){:target="\_blank"} + [Magento Admin]({{ page.baseurl }}/cloud/onboarding/onboarding-tasks.html#admin){:target="_blank"} panel as an administrator. 1. Click **Stores** > **Settings** > **Configuration** > **Advanced** > **System**. @@ -199,8 +199,8 @@ following example: alt="Fusion Backpack"/> ``` -See `srcset` [browser support](https://caniuse.com/#feat=srcset){:target="\_blank"} -and [specification](https://html.spec.whatwg.org/multipage/embedded-content.html#attr-img-srcset){:target="\_blank"}. +See `srcset` [browser support](https://caniuse.com/#feat=srcset){:target="_blank"} +and [specification](https://html.spec.whatwg.org/multipage/embedded-content.html#attr-img-srcset){:target="_blank"}. ## Validate Fastly IO diff --git a/guides/v2.1/cloud/configure/cloud-vcl-custom-snippets.md b/guides/v2.1/cloud/configure/cloud-vcl-custom-snippets.md index dfef71eb467..a15446bd7c3 100644 --- a/guides/v2.1/cloud/configure/cloud-vcl-custom-snippets.md +++ b/guides/v2.1/cloud/configure/cloud-vcl-custom-snippets.md @@ -106,7 +106,7 @@ The following are **best practices and recommendations**: - The default VCL snippets you uploaded include a prepended name of `magentomodule_` with a priority of `50`. For your custom VCL snippets, **do not use the `magentomodule_` name**. Also, consider the priority of your custom snippets and whether they should override the default snippets. - Do not forget to _always_ locate and clone the active version, and edit the bash script with the new version! _Version_ is not part of your VCL snippet files. -- If you want to override values and settings from the [default Fastly VCL snippets](https://github.com/fastly/fastly-magento2/tree/master/etc/vcl_snippets){:target="\_blank"}, we recommend creating a new snippet with updated values and code with a higher priority value of `100`. You should not try to override default VCLs. We provide an example for [Custom extend Admin timeout VCL]({{ page.baseurl }}/cloud/configure/fastly-vcl-extend-timeout.html). +- If you want to override values and settings from the [default Fastly VCL snippets](https://github.com/fastly/fastly-magento2/tree/master/etc/vcl_snippets){:target="_blank"}, we recommend creating a new snippet with updated values and code with a higher priority value of `100`. You should not try to override default VCLs. We provide an example for [Custom extend Admin timeout VCL]({{ page.baseurl }}/cloud/configure/fastly-vcl-extend-timeout.html). ## Export Fastly Service ID and API Token @@ -127,7 +127,7 @@ To view a list of all VCL snippets by version: Look for the `active` key from the returned list. You need the version to perform a clone in the next section. -For more information on this Fastly API, see this [get version command](https://docs.fastly.com/api/config#version_dfde9093f4eb0aa2497bbfd1d9415987){:target="\_blank"}. +For more information on this Fastly API, see this [get version command](https://docs.fastly.com/api/config#version_dfde9093f4eb0aa2497bbfd1d9415987){:target="_blank"}. ## Clone the active VCL version and all snippets {#clone} @@ -139,7 +139,7 @@ You can save the new version into a bash environment variable for use in cURL co export FASTLY_VERSION= -For more information on this Fastly API, see this [clone command](https://docs.fastly.com/api/config#version_7f4937d0663a27fbb765820d4c76c709){:target="\_blank"}. +For more information on this Fastly API, see this [clone command](https://docs.fastly.com/api/config#version_7f4937d0663a27fbb765820d4c76c709){:target="_blank"}. ### Create custom VCL snippets {#create-snippet} @@ -159,7 +159,7 @@ The values include: - `name`—Name for the VCL snippet. - `dynamic`—Indicates if this is a [dynamicsnippet](https://docs.fastly.com/guides/vcl-snippets/using-dynamic-vcl-snippets)or [regularsnippet](https://docs.fastly.com/guides/vcl-snippets/using-regular-vcl-snippets). -- `type`—Specifies a location for the generated snippet, such as `init` (above subroutines) and `recv` (within subroutines). See [Fastly VCL snippet object values](https://docs.fastly.com/api/config#snippet){:target="\_blank"} for information on these values. +- `type`—Specifies a location for the generated snippet, such as `init` (above subroutines) and `recv` (within subroutines). See [Fastly VCL snippet object values](https://docs.fastly.com/api/config#snippet){:target="_blank"} for information on these values. - `priority`—Determines the order VCL snippets call. Lower values run first, from `1` to `100`. All uploaded snippets from a Magento module have a value of `50`. If you want an action to occur last or to override Magento default VCL snippets, use a higher number, such as `100`. To have code occur immediately, use a lower value, such as `5`. - `content`—The snippet of VCL code to run in one line, without line breaks. @@ -211,7 +211,7 @@ To update a snippet, modify the JSON file you prepared on the [Create VCL snippe curl -H "Fastly-Key: ${FASTLY_API_TOKEN}" https://api.fastly.com/service/${FASTLY_SERVICE_ID}/version/${FASTLY_VERSION}/snippet/ -H 'Content-Type: application/json' -X PUT --data @ -If you want to override values and settings from the [default Fastly VCL snippets](https://github.com/fastly/fastly-magento2/tree/master/etc/vcl_snippets){:target="\_blank"}, we recommend creating a new snippet with updated values and code that use a priority of `100`. +If you want to override values and settings from the [default Fastly VCL snippets](https://github.com/fastly/fastly-magento2/tree/master/etc/vcl_snippets){:target="_blank"}, we recommend creating a new snippet with updated values and code that use a priority of `100`. To delete an individual VCL snippet using the API, get a list of snippets and enter a `curl` command with the specific snippet name to delete: @@ -221,13 +221,13 @@ To delete an individual VCL snippet using the API, get a list of snippets and en You can learn more about creating VCL snippets with the following Fastly resources: -- [All Fastly VCL content](https://docs.fastly.com/guides/vcl/){:target="\_blank"} -- [Fastly VCL guide](https://docs.fastly.com/guides/vcl/guide-to-vcl){:target="\_blank"} -- [Mixing and matching Fastly VCL with custom VCL](https://docs.fastly.com/guides/vcl/mixing-and-matching-fastly-vcl-with-custom-vcl){:target="\_blank"} -- [Fastly VCL snippet object values](https://docs.fastly.com/api/config#snippet){:target="\_blank"} +- [All Fastly VCL content](https://docs.fastly.com/guides/vcl/){:target="_blank"} +- [Fastly VCL guide](https://docs.fastly.com/guides/vcl/guide-to-vcl){:target="_blank"} +- [Mixing and matching Fastly VCL with custom VCL](https://docs.fastly.com/guides/vcl/mixing-and-matching-fastly-vcl-with-custom-vcl){:target="_blank"} +- [Fastly VCL snippet object values](https://docs.fastly.com/api/config#snippet){:target="_blank"} Fastly supports two types of snippets: -- [Regular snippets](https://docs.fastly.com/guides/vcl-snippets/using-regular-vcl-snippets){:target="\_blank"} are versioned VCL snippets. The code and settings are locked per version to create, modify, and deploy with the Fastly service. -- [Dynamic snippets](https://docs.fastly.com/guides/vcl-snippets/using-dynamic-vcl-snippets){:target="\_blank"} are snippets you can only create via API calls. These snippets do not have a version and deploy separately from your Fastly service. +- [Regular snippets](https://docs.fastly.com/guides/vcl-snippets/using-regular-vcl-snippets){:target="_blank"} are versioned VCL snippets. The code and settings are locked per version to create, modify, and deploy with the Fastly service. +- [Dynamic snippets](https://docs.fastly.com/guides/vcl-snippets/using-dynamic-vcl-snippets){:target="_blank"} are snippets you can only create via API calls. These snippets do not have a version and deploy separately from your Fastly service. diff --git a/guides/v2.1/cloud/configure/configuration-overview.md b/guides/v2.1/cloud/configure/configuration-overview.md index aca6a8a1d8b..ea652dfede4 100644 --- a/guides/v2.1/cloud/configure/configuration-overview.md +++ b/guides/v2.1/cloud/configure/configuration-overview.md @@ -24,7 +24,7 @@ The following options, tools, and features can be set up and configured in your * [Multiple websites or stores]({{ page.baseurl }}/cloud/project/project-multi-sites.html) details how to create and configure multi-sites for your store, for example multiple locales including English, French, and Spanish * [Install, manage, and upgrade modules]({{ page.baseurl }}/cloud/howtos/install-components.html) * [Install a theme]({{ page.baseurl }}/cloud/howtos/custom-theme.html) for your site and store -* Install the [Magento Google reCAPTCHA and Two-Factor Authentication extensions](https://docs.magento.com/m2/2.1/ee/user_guide/magento/magento-extensions.html){:target="\_blank"} to provide additional security for account access to the Admin panel and storefront. +* Install the [Magento Google reCAPTCHA and Two-Factor Authentication extensions](https://docs.magento.com/m2/2.1/ee/user_guide/magento/magento-extensions.html){:target="_blank"} to provide additional security for account access to the Admin panel and storefront. ## Configure your deployment: build hooks, services, and routes {#deploy} diff --git a/guides/v2.1/cloud/env/setup-notifications.md b/guides/v2.1/cloud/env/setup-notifications.md index cb42760be6b..1ee4c03cbda 100644 --- a/guides/v2.1/cloud/env/setup-notifications.md +++ b/guides/v2.1/cloud/env/setup-notifications.md @@ -70,7 +70,7 @@ log: min_level: "info" ``` -- `token`—Your Slack [user token](https://api.slack.com/docs/token-types#user){:target="\_blank"}. Your user token authorizes {{site.data.var.ece}} to send messages. +- `token`—Your Slack [user token](https://api.slack.com/docs/token-types#user){:target="_blank"}. Your user token authorizes {{site.data.var.ece}} to send messages. - `channel`—Name of the Slack channel {{site.data.var.ece}} sends notifications. - `username`—Username {{site.data.var.ece}} uses to send notification messages in Slack. - `min_level`—Minimum log level for notification messages. We recommend using `info`. diff --git a/guides/v2.1/cloud/env/variables-build.md b/guides/v2.1/cloud/env/variables-build.md index e80eab72752..29f3d43e885 100644 --- a/guides/v2.1/cloud/env/variables-build.md +++ b/guides/v2.1/cloud/env/variables-build.md @@ -26,7 +26,7 @@ For more information about customizing the build and deploy process: - **Default**—`6` - **Version**—Magento 2.1.4 and later -Specifies which [gzip](https://www.gnu.org/software/gzip){:target="\_blank"} compression level (`0` to `9`) to use when compressing static content; `0` disables compression. +Specifies which [gzip](https://www.gnu.org/software/gzip){:target="_blank"} compression level (`0` to `9`) to use when compressing static content; `0` disables compression. ```yaml stage: @@ -128,7 +128,7 @@ stage: - **Default**—_Not set_ - **Version**—Magento 2.1.4 and later - Enables or disables the [Symfony](https://symfony.com/doc/current/console/verbosity.html){:target="\_blank"} debug verbosity level for your logs. Choose the level of detail provided in the logs: `-v`, `-vv`, or `-vvv`. + Enables or disables the [Symfony](https://symfony.com/doc/current/console/verbosity.html){:target="_blank"} debug verbosity level for your logs. Choose the level of detail provided in the logs: `-v`, `-vv`, or `-vvv`. ```yaml stage: diff --git a/guides/v2.1/cloud/env/variables-deploy.md b/guides/v2.1/cloud/env/variables-deploy.md index 830d767d23c..1131a955050 100644 --- a/guides/v2.1/cloud/env/variables-deploy.md +++ b/guides/v2.1/cloud/env/variables-deploy.md @@ -196,7 +196,7 @@ The read-only connection is not available for use in the Integration environment - **Default**—`6` - **Version**—Magento 2.1.4 and later -Specifies which [gzip](https://www.gnu.org/software/gzip){:target="\_blank"} compression level (`0` to `9`) to use when compressing static content; `0` disables compression. +Specifies which [gzip](https://www.gnu.org/software/gzip){:target="_blank"} compression level (`0` to `9`) to use when compressing static content; `0` disables compression. ```yaml stage: @@ -379,7 +379,7 @@ You should set this variable to `false` _only_ in Staging or Production environm - **Default**—_Not set_ - **Version**—Magento 2.1.4 and later - Enables or disables the [Symfony](https://symfony.com/doc/current/console/verbosity.html){:target="\_blank"} debug verbosity level for your logs. Choose the level of detail provided in the logs: `-v`, `-vv`, or `-vvv`. + Enables or disables the [Symfony](https://symfony.com/doc/current/console/verbosity.html){:target="_blank"} debug verbosity level for your logs. Choose the level of detail provided in the logs: `-v`, `-vv`, or `-vvv`. ```yaml stage: diff --git a/guides/v2.1/cloud/howtos/how-to.md b/guides/v2.1/cloud/howtos/how-to.md index ef5aff0cbe7..7551a7f7899 100644 --- a/guides/v2.1/cloud/howtos/how-to.md +++ b/guides/v2.1/cloud/howtos/how-to.md @@ -13,7 +13,7 @@ functional_areas: These topics are intended to get you up to speed quickly using {{site.data.var.ece}}. These are step-by-step instructions that provide instructions about specific tasks or that explain how to achieve a goal. -Have suggestions? Open [an issue](https://github.com/magento/devdocs/issues){:target="\_blank"} or click the **Edit this page on GitHub** link and give us feedback directly. +Have suggestions? Open [an issue](https://github.com/magento/devdocs/issues){:target="_blank"} or click the **Edit this page on GitHub** link and give us feedback directly. Current topics: diff --git a/guides/v2.1/cloud/integrations/bitbucket-integration.md b/guides/v2.1/cloud/integrations/bitbucket-integration.md index ae72321522e..44f5c6a8d2f 100644 --- a/guides/v2.1/cloud/integrations/bitbucket-integration.md +++ b/guides/v2.1/cloud/integrations/bitbucket-integration.md @@ -80,11 +80,11 @@ You need to clone your {{site.data.var.ece}} project from an existing environmen ## Create an OAuth consumer -The Bitbucket integration requires an [OAuth consumer](https://confluence.atlassian.com/x/pwIwDg){:target="\_blank"}. You need the OAuth `key` and `secret` from this consumer to complete the next section. +The Bitbucket integration requires an [OAuth consumer](https://confluence.atlassian.com/x/pwIwDg){:target="_blank"}. You need the OAuth `key` and `secret` from this consumer to complete the next section. #### To create an OAuth consumer in Bitbucket: -1. Log in to your [Bitbucket](https://bitbucket.org/account/signin/){:target="\_blank"} account. +1. Log in to your [Bitbucket](https://bitbucket.org/account/signin/){:target="_blank"} account. 1. Click **Settings** > **Access Management** > **OAuth**. diff --git a/guides/v2.1/cloud/integrations/github-integration.md b/guides/v2.1/cloud/integrations/github-integration.md index 91bece88009..e7ee2f6539e 100644 --- a/guides/v2.1/cloud/integrations/github-integration.md +++ b/guides/v2.1/cloud/integrations/github-integration.md @@ -20,7 +20,7 @@ You must obtain a GitHub token and a webhook to continue the process. ## Generate a GitHub token -You must be a member of a group with write-access to the GitHub repository, so that you can _push_ to the repository. See [GitHub: Create](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/){:target="\_blank"}. +You must be a member of a group with write-access to the GitHub repository, so that you can _push_ to the repository. See [GitHub: Create](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/){:target="_blank"}. ## Enable the GitHub integration diff --git a/guides/v2.1/cloud/live/go-live-checklist.md b/guides/v2.1/cloud/live/go-live-checklist.md index 180d57d52b2..5da6549d419 100644 --- a/guides/v2.1/cloud/live/go-live-checklist.md +++ b/guides/v2.1/cloud/live/go-live-checklist.md @@ -43,7 +43,7 @@ You need to complete configurations for your DNS including: After checking with your registrar about where to change your DNS settings, add a CNAME record for your website that points to the Fastly service: `prod.magentocloud.map.fastly.net`. If you use multiple hostnames for your site, you must add a CNAME record for each one. {:.bs-callout .bs-callout-info} -This does not work for an [apex domain](https://blog.cloudflare.com/zone-apex-naked-domain-root-domain-cname-supp){:target="\_blank"} (also referred to as a _naked_ domain). You must use a DNS provider that supports forwarding DNS queries to use an apex domain. +This does not work for an [apex domain](https://blog.cloudflare.com/zone-apex-naked-domain-root-domain-cname-supp){:target="_blank"} (also referred to as a _naked_ domain). You must use a DNS provider that supports forwarding DNS queries to use an apex domain. The following list contains examples of DNS providers for informational purposes. Use your preferred DNS provider. diff --git a/guides/v2.1/cloud/live/sens-data-initial.md b/guides/v2.1/cloud/live/sens-data-initial.md index b56be5b04ee..d6917352ab2 100644 --- a/guides/v2.1/cloud/live/sens-data-initial.md +++ b/guides/v2.1/cloud/live/sens-data-initial.md @@ -65,7 +65,7 @@ To change locale and static file optimization settings: ![Set static file optimization settings]({{ site.baseurl }}/common/images/cloud_vars_set-minify.png){:width="550px"} 8. Click **Save Config**. -9. If prompted, [flush the Magento cache](http://docs.magento.com/m2/ee/user_guide/system/cache-management.html){:target="\_blank"}. +9. If prompted, [flush the Magento cache](http://docs.magento.com/m2/ee/user_guide/system/cache-management.html){:target="_blank"}. 10. Log out of the Magento Admin. ## Export values and transfer config.local.php to your local workstation {#export} diff --git a/guides/v2.1/cloud/live/stage-prod-migrate-prereq.md b/guides/v2.1/cloud/live/stage-prod-migrate-prereq.md index 0ba2f126960..06d0d4d7776 100644 --- a/guides/v2.1/cloud/live/stage-prod-migrate-prereq.md +++ b/guides/v2.1/cloud/live/stage-prod-migrate-prereq.md @@ -33,7 +33,7 @@ To prepare your environments for full deployment, you need: You can locate your URLs through the Project Web Interface. For each selected environment or branch, you will find an Access Site link. Your environments begin with Master, which is Production, and any additional branches you create, including Staging (recommended) and development branches for custom code. -1. Log in to [your {{site.data.var.ece}} account](https://accounts.magento.cloud){:target="\_blank"}. +1. Log in to [your {{site.data.var.ece}} account](https://accounts.magento.cloud){:target="_blank"}. 2. Select an environment. 3. Click **Access site** to display the URL and SSH information. diff --git a/guides/v2.1/cloud/live/stage-prod-migrate.md b/guides/v2.1/cloud/live/stage-prod-migrate.md index 0a1acf61eb7..e084018e811 100644 --- a/guides/v2.1/cloud/live/stage-prod-migrate.md +++ b/guides/v2.1/cloud/live/stage-prod-migrate.md @@ -146,7 +146,7 @@ To migrate static files from remote-to-remote environments directly (fast approa ## Migrate the database {#cloud-live-migrate-db} -**Prerequisite:** A database dump (see Step 3) should include database triggers. For dumping them, make sure you have the [TRIGGER privilege](https://dev.mysql.com/doc/refman/5.7/en/privileges-provided.html#priv_trigger){:target="\_blank"}. +**Prerequisite:** A database dump (see Step 3) should include database triggers. For dumping them, make sure you have the [TRIGGER privilege](https://dev.mysql.com/doc/refman/5.7/en/privileges-provided.html#priv_trigger){:target="_blank"}. **Important:** The Integration environment database is strictly for development testing and may include data you may not want to migrate into Staging and Production. diff --git a/guides/v2.1/cloud/onboarding/onboarding-tasks.md b/guides/v2.1/cloud/onboarding/onboarding-tasks.md index aa3a6ca1ec6..46dce8dcf49 100644 --- a/guides/v2.1/cloud/onboarding/onboarding-tasks.md +++ b/guides/v2.1/cloud/onboarding/onboarding-tasks.md @@ -44,7 +44,7 @@ site. ## Sign up for a Magento Commerce (Cloud) account {#cloud-first-acct} -Don't have a {{site.data.var.ece}} account yet? Contact [Magento Sales](https://magento.com/explore/contact-sales){:target="\_blank"}. +Don't have a {{site.data.var.ece}} account yet? Contact [Magento Sales](https://magento.com/explore/contact-sales){:target="_blank"}. We will create your account and send you a welcome email that provides instructions to access the project. The person who signs up for a {{site.data.var.ece}} account is referred to as @@ -56,7 +56,7 @@ Magento sends a welcome email to the Project Owner using the address that was provided during the sign up process. The email contains a link to access your {{site.data.var.ece}} project and complete initial project set up. -You can also access your project by [logging in to your account](https://accounts.magento.cloud){:target="\_blank"}. +You can also access your project by [logging in to your account](https://accounts.magento.cloud){:target="_blank"}. ## Project access and users {#users} @@ -68,7 +68,7 @@ Typically, the only user the Project Owner must create is the _Technical Admin_. The Technical Admin needs a user account with admin access to create user accounts for developers, set environment permissions, and manage all branches and environments. The Technical Admin can be a developer, -a consultant, a [Magento Solution Partner](https://magento.com/find-a-partner){:target="\_blank"}, +a consultant, a [Magento Solution Partner](https://magento.com/find-a-partner){:target="_blank"}, or yourself. You can create a Technical Admin through the Project portal, from the Project @@ -96,7 +96,7 @@ For details, see [Project Web Interface]({{ page.baseurl }}/cloud/project/projec Get updates about {{site.data.var.ece}} platform environments and related services from the -[Status page](https://status.magento.cloud){:target="\_blank"}. +[Status page](https://status.magento.cloud){:target="_blank"}. The page lists current status for all {{site.data.var.ece}} components and services followed by notifications about incident reports, service upgrades, @@ -108,7 +108,7 @@ Anyone working on your project can subscribe to the {{site.data.var.ece}} status site to receive event notifications and updates through email. You can customize your subscription to select only the platform and services that you want to track. Sign up from the -[Subscription page](https://status.magento.cloud/subscribe){:target="\_blank"}. +[Subscription page](https://status.magento.cloud/subscribe){:target="_blank"}. ## Access your Magento Admin panel {#admin} diff --git a/guides/v2.1/cloud/project/new-relic.md b/guides/v2.1/cloud/project/new-relic.md index 184721d517e..7dc94cc075b 100644 --- a/guides/v2.1/cloud/project/new-relic.md +++ b/guides/v2.1/cloud/project/new-relic.md @@ -8,7 +8,7 @@ functional_areas: - Services --- -The software analytics product [New Relic for application performance management (APM)](https://docs.newrelic.com/docs/apm/new-relic-apm/getting-started/introduction-new-relic-apm){:target="\_blank"} helps you to analyze and improve application interactions. Each {{site.data.var.ece}} plan includes a New Relic APM license that supports up to three instances across all environments. +The software analytics product [New Relic for application performance management (APM)](https://docs.newrelic.com/docs/apm/new-relic-apm/getting-started/introduction-new-relic-apm){:target="_blank"} helps you to analyze and improve application interactions. Each {{site.data.var.ece}} plan includes a New Relic APM license that supports up to three instances across all environments. New Relic APM provides the following features to Magento: diff --git a/guides/v2.1/cloud/project/project-conf-files_magento-app.md b/guides/v2.1/cloud/project/project-conf-files_magento-app.md index 9445a8fb4a9..02cdc384b1f 100644 --- a/guides/v2.1/cloud/project/project-conf-files_magento-app.md +++ b/guides/v2.1/cloud/project/project-conf-files_magento-app.md @@ -12,7 +12,7 @@ functional_areas: 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. -The `.magento.app.yaml` has many default values, see [a sample `.magento.app.yaml` file](https://github.com/magento/magento-cloud/blob/master/.magento.app.yaml){:target="\_blank"}. Make sure to review the `.magento.app.yaml` for your installed version. This file can differ across {{site.data.var.ece}} versions. +The `.magento.app.yaml` has many default values, see [a sample `.magento.app.yaml` file](https://github.com/magento/magento-cloud/blob/master/.magento.app.yaml){:target="_blank"}. Make sure to review the `.magento.app.yaml` for your installed version. This file can differ across {{site.data.var.ece}} versions. {% include cloud/note-pro-using-yaml.md %} @@ -318,56 +318,56 @@ To view the current list of PHP extensions, SSH into your environment and enter Magento requires the following PHP extensions that are enabled by default: -- [curl](http://php.net/manual/en/book.curl.php){:target="\_blank"} -- [gd](http://php.net/manual/en/book.image.php){:target="\_blank"} -- [intl](http://php.net/manual/en/book.intl.php){:target="\_blank"} +- [curl](http://php.net/manual/en/book.curl.php){:target="_blank"} +- [gd](http://php.net/manual/en/book.image.php){:target="_blank"} +- [intl](http://php.net/manual/en/book.intl.php){:target="_blank"} - PHP 7 only: - - [json](http://php.net/manual/en/book.json.php){:target="\_blank"} - - [iconv](http://php.net/manual/en/book.iconv.php){:target="\_blank"} -- [mcrypt](http://php.net/manual/en/book.mcrypt.php){:target="\_blank"} -- [PDO/MySQL](http://php.net/manual/en/ref.pdo-mysql.php){:target="\_blank"} -- [bc-math](http://php.net/manual/en/book.bc.php){:target="\_blank"} -- [mbstring](http://php.net/manual/en/book.mbstring.php){:target="\_blank"} -- [mhash](http://php.net/manual/en/book.mhash.php){:target="\_blank"} -- [openssl](http://php.net/manual/en/book.openssl.php){:target="\_blank"} -- [SimpleXML](http://php.net/manual/en/book.simplexml.php){:target="\_blank"} -- [soap](http://php.net/manual/en/book.soap.php){:target="\_blank"} -- [xml](http://php.net/manual/en/book.xml.php){:target="\_blank"} -- [zip](http://php.net/manual/en/book.zip.php){:target="\_blank"} + - [json](http://php.net/manual/en/book.json.php){:target="_blank"} + - [iconv](http://php.net/manual/en/book.iconv.php){:target="_blank"} +- [mcrypt](http://php.net/manual/en/book.mcrypt.php){:target="_blank"} +- [PDO/MySQL](http://php.net/manual/en/ref.pdo-mysql.php){:target="_blank"} +- [bc-math](http://php.net/manual/en/book.bc.php){:target="_blank"} +- [mbstring](http://php.net/manual/en/book.mbstring.php){:target="_blank"} +- [mhash](http://php.net/manual/en/book.mhash.php){:target="_blank"} +- [openssl](http://php.net/manual/en/book.openssl.php){:target="_blank"} +- [SimpleXML](http://php.net/manual/en/book.simplexml.php){:target="_blank"} +- [soap](http://php.net/manual/en/book.soap.php){:target="_blank"} +- [xml](http://php.net/manual/en/book.xml.php){:target="_blank"} +- [zip](http://php.net/manual/en/book.zip.php){:target="_blank"} You must install the following extensions: -- [ImageMagick](http://php.net/manual/en/book.imagick.php){:target="\_blank"} 6.3.7 (or later), ImageMagick can optionally be used with the `gd` extension -- [xsl](http://php.net/manual/en/book.xsl.php){:target="\_blank"} -- [redis](https://pecl.php.net/package/redis){:target="\_blank"} +- [ImageMagick](http://php.net/manual/en/book.imagick.php){:target="_blank"} 6.3.7 (or later), ImageMagick can optionally be used with the `gd` extension +- [xsl](http://php.net/manual/en/book.xsl.php){:target="_blank"} +- [redis](https://pecl.php.net/package/redis){:target="_blank"} In addition, we strongly recommend you enable `opcache`. Optional PHP extensions available to install: -- [apcu](http://php.net/manual/en/book.apcu.php){:target="\_blank"} -- [blackfire](https://blackfire.io/docs/up-and-running/installation){:target="\_blank"} -- [enchant](http://php.net/manual/en/book.enchant.php){:target="\_blank"} -- [gearman](http://php.net/manual/en/book.gearman.php){:target="\_blank"} -- [geoip](http://php.net/manual/en/book.geoip.php){:target="\_blank"} -- [imap](http://php.net/manual/en/book.imap.php){:target="\_blank"} -- [ioncube](https://www.ioncube.com/loaders.php){:target="\_blank"} -- [pecl-http](https://pecl.php.net/package/pecl_http){:target="\_blank"} -- [pinba](http://pinba.org){:target="\_blank"} -- [propro](https://pecl.php.net/package/propro){:target="\_blank"} -- [pspell](http://php.net/manual/en/book.pspell.php){:target="\_blank"} -- [raphf](https://pecl.php.net/package/raphf){:target="\_blank"} -- [readline](http://php.net/manual/en/book.readline.php){:target="\_blank"} -- [recode](http://php.net/manual/en/book.recode.php){:target="\_blank"} -- [snmp](http://php.net/manual/en/book.snmp.php){:target="\_blank"} -- [sqlite3](http://php.net/manual/en/book.sqlite3.php){:target="\_blank"} -- [ssh2](http://php.net/manual/en/book.ssh2.php){:target="\_blank"} -- [tidy](http://php.net/manual/en/book.tidy.php){:target="\_blank"} -- [xcache](https://xcache.lighttpd.net){:target="\_blank"} -- [xdebug](https://xdebug.org){:target="\_blank"} -- [xhprof](http://php.net/manual/en/book.xhprof.php){:target="\_blank"} -- [xmlrpc](http://php.net/manual/en/book.xmlrpc.php){:target="\_blank"} +- [apcu](http://php.net/manual/en/book.apcu.php){:target="_blank"} +- [blackfire](https://blackfire.io/docs/up-and-running/installation){:target="_blank"} +- [enchant](http://php.net/manual/en/book.enchant.php){:target="_blank"} +- [gearman](http://php.net/manual/en/book.gearman.php){:target="_blank"} +- [geoip](http://php.net/manual/en/book.geoip.php){:target="_blank"} +- [imap](http://php.net/manual/en/book.imap.php){:target="_blank"} +- [ioncube](https://www.ioncube.com/loaders.php){:target="_blank"} +- [pecl-http](https://pecl.php.net/package/pecl_http){:target="_blank"} +- [pinba](http://pinba.org){:target="_blank"} +- [propro](https://pecl.php.net/package/propro){:target="_blank"} +- [pspell](http://php.net/manual/en/book.pspell.php){:target="_blank"} +- [raphf](https://pecl.php.net/package/raphf){:target="_blank"} +- [readline](http://php.net/manual/en/book.readline.php){:target="_blank"} +- [recode](http://php.net/manual/en/book.recode.php){:target="_blank"} +- [snmp](http://php.net/manual/en/book.snmp.php){:target="_blank"} +- [sqlite3](http://php.net/manual/en/book.sqlite3.php){:target="_blank"} +- [ssh2](http://php.net/manual/en/book.ssh2.php){:target="_blank"} +- [tidy](http://php.net/manual/en/book.tidy.php){:target="_blank"} +- [xcache](https://xcache.lighttpd.net){:target="_blank"} +- [xdebug](https://xdebug.org){:target="_blank"} +- [xhprof](http://php.net/manual/en/book.xhprof.php){:target="_blank"} +- [xmlrpc](http://php.net/manual/en/book.xmlrpc.php){:target="_blank"} {:.bs-callout .bs-callout-warning} PHP compiled with debug is not supported and the Probe may conflict with XDebug or XHProf. Disable those extensions when enabling the Probe. The Probe conflicts with some PHP extensions like Pinba or IonCube. diff --git a/guides/v2.1/cloud/project/project-conf-files_services-elastic.md b/guides/v2.1/cloud/project/project-conf-files_services-elastic.md index 79c68509ff1..68cf2aa5698 100644 --- a/guides/v2.1/cloud/project/project-conf-files_services-elastic.md +++ b/guides/v2.1/cloud/project/project-conf-files_services-elastic.md @@ -13,7 +13,7 @@ functional_areas: - Search --- -[Elasticsearch](https://www.elastic.co){:target="\_blank"} is an open source product that enables you to take data from any source, any format, and search and visualize it in real time. +[Elasticsearch](https://www.elastic.co){:target="_blank"} is an open source product that enables you to take data from any source, any format, and search and visualize it in real time. * Elasticsearch performs quick and advanced searches on products in the product catalog * Elasticsearch Analyzers support multiple languages @@ -61,7 +61,7 @@ elasticsearch: - lang-python ``` -For example, if you are using [Smile ElasticSuite](https://github.com/Smile-SA/elasticsuite){:target="\_blank"}, you should add the following plugins: +For example, if you are using [Smile ElasticSuite](https://github.com/Smile-SA/elasticsuite){:target="_blank"}, you should add the following plugins: ```yaml elasticsearch: @@ -91,9 +91,9 @@ The following are supported Elasticsearch plugins for version 2.4: * `mapper-murmur3`: Murmur3 mapper plugin for computing hashes at index-time * `mapper-size`: Size mapper plugin, enables the `_size` meta field -If using [Smile ElasticSuite](https://github.com/Smile-SA/elasticsuite){:target="\_blank"}, the required plugins are `analysis-icu` and `analysis-phonetic`. Make sure to add these to the plugins section of `services.yaml.` See [Add Elasticsearch plugins](#addplugins). +If using [Smile ElasticSuite](https://github.com/Smile-SA/elasticsuite){:target="_blank"}, the required plugins are `analysis-icu` and `analysis-phonetic`. Make sure to add these to the plugins section of `services.yaml.` See [Add Elasticsearch plugins](#addplugins). -For full documentation on these plugins, see [Elasticsearch plugin documentation](https://www.elastic.co/guide/en/elasticsearch/plugins/2.4/index.html){:target="\_blank"}. +For full documentation on these plugins, see [Elasticsearch plugin documentation](https://www.elastic.co/guide/en/elasticsearch/plugins/2.4/index.html){:target="_blank"}. ## Verify environment-related relationships {#cloud-es-config-mg} diff --git a/guides/v2.1/cloud/project/project-conf-files_services-rabbit.md b/guides/v2.1/cloud/project/project-conf-files_services-rabbit.md index 856baee6887..0f816c4f5aa 100644 --- a/guides/v2.1/cloud/project/project-conf-files_services-rabbit.md +++ b/guides/v2.1/cloud/project/project-conf-files_services-rabbit.md @@ -14,7 +14,7 @@ functional_areas: The [Message Queue Framework (MQF)]({{ page.baseurl }}/config-guide/mq/rabbitmq-overview.html) is a system within {{site.data.var.ee}} that allows a {% glossarytooltip c1e4242b-1f1a-44c3-9d72-1d5b1435e142 %}module{% endglossarytooltip %} to publish messages to queues. It also defines the consumers that will receive the messages asynchronously. -The MQF uses [RabbitMQ](http://www.rabbitmq.com){:target="\_blank"} as the messaging broker, which provides a scalable platform for sending and receiving messages. It also includes a mechanism for storing undelivered messages. RabbitMQ is based on the Advanced Message Queuing Protocol (AMQP) 0.9.1 specification. +The MQF uses [RabbitMQ](http://www.rabbitmq.com){:target="_blank"} as the messaging broker, which provides a scalable platform for sending and receiving messages. It also includes a mechanism for storing undelivered messages. RabbitMQ is based on the Advanced Message Queuing Protocol (AMQP) 0.9.1 specification. We support RabbitMQ version 3.5. diff --git a/guides/v2.1/cloud/project/project-conf-files_services-redis.md b/guides/v2.1/cloud/project/project-conf-files_services-redis.md index 65b0da24cbb..4a0cc18778d 100644 --- a/guides/v2.1/cloud/project/project-conf-files_services-redis.md +++ b/guides/v2.1/cloud/project/project-conf-files_services-redis.md @@ -12,7 +12,7 @@ functional_areas: - Setup --- -[Redis](http://redis.io){:target="\_blank"} is an optional, backend cache solution that replaces the Zend Framework [Zend_Cache_Backend_File](http://framework.zend.com/apidoc/1.0/Zend_Cache/Backend/Zend_Cache_Backend_File.html){:target="\_blank"}, which is used in Magento 2 by default. +[Redis](http://redis.io){:target="_blank"} is an optional, backend cache solution that replaces the Zend Framework [Zend_Cache_Backend_File](http://framework.zend.com/apidoc/1.0/Zend_Cache/Backend/Zend_Cache_Backend_File.html){:target="_blank"}, which is used in Magento 2 by default. We support Redis versions 2.8 and 3.0. Redis 3.0 supports up to 64 different databases per instance of the service, while 2.8 allows for only a single database. See [Configure Redis]({{ page.baseurl }}/config-guide/redis/config-redis.html). diff --git a/guides/v2.1/cloud/project/project-start.md b/guides/v2.1/cloud/project/project-start.md index e283580872c..3a00678f12e 100644 --- a/guides/v2.1/cloud/project/project-start.md +++ b/guides/v2.1/cloud/project/project-start.md @@ -25,7 +25,7 @@ When you push your local environment to the remote server, our deploy script use ## Ignoring files -We include a base `.gitignore` file with the {{site.data.var.ece}} project repository. See [.gitignore file](https://github.com/magento/magento-cloud/blob/master/.gitignore){:target="\_blank"}. You can add an ignored file when staging a commit by using the `-f` option: +We include a base `.gitignore` file with the {{site.data.var.ece}} project repository. See [.gitignore file](https://github.com/magento/magento-cloud/blob/master/.gitignore){:target="_blank"}. You can add an ignored file when staging a commit by using the `-f` option: ```bash git add -f diff --git a/guides/v2.1/cloud/project/project-webint-basic.md b/guides/v2.1/cloud/project/project-webint-basic.md index c6cf92d053e..a52e9a30ad3 100644 --- a/guides/v2.1/cloud/project/project-webint-basic.md +++ b/guides/v2.1/cloud/project/project-webint-basic.md @@ -10,7 +10,7 @@ functional_areas: - Configuration --- -The {{site.data.var.ece}} [Project Web Interface](https://accounts.magento.cloud){:target="\_blank"} enables you to do the following for all Starter and Pro environments: +The {{site.data.var.ece}} [Project Web Interface](https://accounts.magento.cloud){:target="_blank"} enables you to do the following for all Starter and Pro environments: * [Access projects](#project-access) * Create and manage projects diff --git a/guides/v2.1/cloud/project/projects.md b/guides/v2.1/cloud/project/projects.md index 8b87c16cf68..8075bd7444a 100644 --- a/guides/v2.1/cloud/project/projects.md +++ b/guides/v2.1/cloud/project/projects.md @@ -45,7 +45,7 @@ To upgrade and patch Magento, see: ## Access the Project Web Interface {#login} -With your {{site.data.var.ece}} account created, you can log into the Project Web Interface at [https://accounts.magento.cloud](https://accounts.magento.cloud){:target="\_blank"}. +With your {{site.data.var.ece}} account created, you can log into the Project Web Interface at [https://accounts.magento.cloud](https://accounts.magento.cloud){:target="_blank"}. ![Log in to a project]({{ site.baseurl }}/common/images/cloud_project-login.png){:width="450px"} diff --git a/guides/v2.1/cloud/project/sendgrid.md b/guides/v2.1/cloud/project/sendgrid.md index f44f24c1a3b..f26073a68e7 100644 --- a/guides/v2.1/cloud/project/sendgrid.md +++ b/guides/v2.1/cloud/project/sendgrid.md @@ -7,7 +7,7 @@ functional_areas: - Services --- -The SendGrid-based SMTP proxy service provides email authentication, reputation monitoring, and dedicated IP addresses. A basic set up includes 12,000 emails per month and excludes use in marketing campaigns. See [SendGrid and Magento—Email Delivery. Simplified](https://sendgrid.com/partners/magento/){:target="\_blank"}. +The SendGrid-based SMTP proxy service provides email authentication, reputation monitoring, and dedicated IP addresses. A basic set up includes 12,000 emails per month and excludes use in marketing campaigns. See [SendGrid and Magento—Email Delivery. Simplified](https://sendgrid.com/partners/magento/){:target="_blank"}. Magento automates the SendGrid integration for Starter and Pro Integration environments. The Pro Production and Staging environments require manual provisioning and configuration during the IaaS hardware provisioning process. @@ -23,4 +23,4 @@ s2.example.com IN CNAME The CNAME records resolve to the Domain Keys Identified Mail (DKIM) and Sender Policy Framework (SPF) records managed by SendGrid, so that spam filters are less likely to inhibit your messages. -Magento does not support whitelisting, but you can review the [Sender Policy Framework (SPF)](https://sendgrid.com/docs/Glossary/spf.html){:target="\_blank"} guidelines to improve delivery. +Magento does not support whitelisting, but you can review the [Sender Policy Framework (SPF)](https://sendgrid.com/docs/Glossary/spf.html){:target="_blank"} guidelines to improve delivery. diff --git a/guides/v2.1/cloud/reference/cloud-composer.md b/guides/v2.1/cloud/reference/cloud-composer.md index 9d877141c80..6e97dd37a16 100644 --- a/guides/v2.1/cloud/reference/cloud-composer.md +++ b/guides/v2.1/cloud/reference/cloud-composer.md @@ -8,7 +8,7 @@ functional_areas: - Cloud - Upgrade --- -We use [Composer](https://getcomposer.org/doc){:target="\_blank"} 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. +We use [Composer](https://getcomposer.org/doc){:target="_blank"} 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. Composer manages required libraries and dependencies for your project and installs them in the `vendor` directory. diff --git a/guides/v2.1/cloud/reference/discover-deploy.md b/guides/v2.1/cloud/reference/discover-deploy.md index 2dc3e62834d..057d705edca 100644 --- a/guides/v2.1/cloud/reference/discover-deploy.md +++ b/guides/v2.1/cloud/reference/discover-deploy.md @@ -76,7 +76,7 @@ For detailed instructions, see [Build and deploy full steps](#steps). ### Phase 1: Code and configuration validation {#cloud-deploy-over-phases-conf} -When you initially set up a project from a template, we retrieve the code from the [the {{site.data.var.ee}} template](https://github.com/magento/magento-cloud){:target="\_blank"}. This code repo is cloned to your project as the `master` branch. +When you initially set up a project from a template, we retrieve the code from the [the {{site.data.var.ee}} template](https://github.com/magento/magento-cloud){:target="_blank"}. This code repo is cloned to your project as the `master` branch. - **For Starter**—`master` branch is your Production environment. - **For Pro**—`master` begins as origin branch for the Integration environment. diff --git a/guides/v2.1/cloud/reference/docker-config.md b/guides/v2.1/cloud/reference/docker-config.md index 867ae01921d..e799ce162a3 100644 --- a/guides/v2.1/cloud/reference/docker-config.md +++ b/guides/v2.1/cloud/reference/docker-config.md @@ -9,7 +9,7 @@ functional_areas: {{site.data.var.ece}} provides a Docker environment option for those who use their local environment for development, test, or automation tasks. The {{site.data.var.ece}} Docker environment requires three, essential components: a Magento 2 template, Docker Compose, and {{site.data.var.ece}} `ece-tools` package. -The [Magento Cloud Docker repository](https://github.com/magento/magento-cloud-docker){:target="\_blank"} contains build information for the following [Docker hub](https://hub.docker.com/r/magento/){:target="\_blank"} images: +The [Magento Cloud Docker repository](https://github.com/magento/magento-cloud-docker){:target="_blank"} contains build information for the following [Docker hub](https://hub.docker.com/r/magento/){:target="_blank"} images: - PHP: magento/magento-cloud-docker-php - PHP-CLI - version 7 and later @@ -33,7 +33,7 @@ You can use the `ece-tools` package to generate the Docker compose configuration #### To launch Docker with `ece-tools` v2002.0.13 and later: -1. Download a template from the [Magento Cloud repository](https://github.com/magento/magento-cloud){:target="\_blank"}. +1. Download a template from the [Magento Cloud repository](https://github.com/magento/magento-cloud){:target="_blank"}. 1. Add your credentials to the `auth.json` file. @@ -94,13 +94,13 @@ You can use the `ece-tools` package to generate the Docker compose configuration 1. Access your local Magento Cloud template by opening one of the following secure URLs in a browser: - - [`http://localhost:8080`](http://localhost:8080){:target="\_blank"} + - [`http://localhost:8080`](http://localhost:8080){:target="_blank"} - - [`https://localhost`](https://localhost){:target="\_blank"} + - [`https://localhost`](https://localhost){:target="_blank"} #### To launch Docker with `ece-tools` v2002.0.12: -1. Download a template from the [Magento Cloud repository](https://github.com/magento/magento-cloud){:target="\_blank"}. +1. Download a template from the [Magento Cloud repository](https://github.com/magento/magento-cloud){:target="_blank"}. 1. Add your credentials to `auth.json` file. @@ -143,7 +143,7 @@ You can use the `ece-tools` package to generate the Docker compose configuration 1. Access your local Magento Cloud template by opening the following URL in a browser: - [`http://localhost:8080`](http://localhost:8080){:target="\_blank"} + [`http://localhost:8080`](http://localhost:8080){:target="_blank"} ## Stop and remove the Docker configuration diff --git a/guides/v2.1/cloud/reference/git-integration.md b/guides/v2.1/cloud/reference/git-integration.md index 4812d1064c5..863f1ed5034 100644 --- a/guides/v2.1/cloud/reference/git-integration.md +++ b/guides/v2.1/cloud/reference/git-integration.md @@ -15,18 +15,18 @@ Git is the center of all code management, build, and deployment for your {{site. If you need help understand Git, you can review the following resources: -* [Git documentation](https://git-scm.com/documentation){:target="\_blank"} and [videos](https://git-scm.com/videos){:target="\_blank"} from the makers of Git -* [Git cheatsheet](http://rogerdudler.github.io/git-guide/files/git_cheat_sheet.pdf){:target="\_blank"} and [quick guide](http://rogerdudler.github.io/git-guide/){:target="\_blank"} from Roger Dudler -* [Git video](https://www.youtube.com/watch?v=8KCQe9Pm1kg){:target="\_blank"} with DevForge to understand how people use the repo and commands with a fun story +* [Git documentation](https://git-scm.com/documentation){:target="_blank"} and [videos](https://git-scm.com/videos){:target="_blank"} from the makers of Git +* [Git cheatsheet](http://rogerdudler.github.io/git-guide/files/git_cheat_sheet.pdf){:target="_blank"} and [quick guide](http://rogerdudler.github.io/git-guide/){:target="_blank"} from Roger Dudler +* [Git video](https://www.youtube.com/watch?v=8KCQe9Pm1kg){:target="_blank"} with DevForge to understand how people use the repo and commands with a fun story ## Git CLI and clients {#clients} -You can interact with Git using [CLI commands](https://git-scm.com/documentation){:target="\_blank"} or using a Git client. Git provides a [Git client](https://git-scm.com/downloads){:target="\_blank"} option, or you can use other clients such as installed on your computer to be able to interact with {{site.data.var.ece}}. +You can interact with Git using [CLI commands](https://git-scm.com/documentation){:target="_blank"} or using a Git client. Git provides a [Git client](https://git-scm.com/downloads){:target="_blank"} option, or you can use other clients such as installed on your computer to be able to interact with {{site.data.var.ece}}. -Not everyone remembers [Git](https://git-scm.com/docs){:target="\_blank"} commands with ease. If you want a Git client, use any client of your choice. Some developers use clients including [GitKraken](https://www.gitkraken.com/){:target="\_blank"} and [SmartGit](https://www.syntevo.com/smartgit/){:target="\_blank"}. +Not everyone remembers [Git](https://git-scm.com/docs){:target="_blank"} commands with ease. If you want a Git client, use any client of your choice. Some developers use clients including [GitKraken](https://www.gitkraken.com/){:target="_blank"} and [SmartGit](https://www.syntevo.com/smartgit/){:target="_blank"}. ## Git branch naming {#requirements} -In addition to Git's requirements for [valid branch names](https://www.kernel.org/pub/software/scm/git/docs/git-check-ref-format.html){:target="\_blank"}, {{site.data.var.ece}} adds two additional requirements: +In addition to Git's requirements for [valid branch names](https://www.kernel.org/pub/software/scm/git/docs/git-check-ref-format.html){:target="_blank"}, {{site.data.var.ece}} adds two additional requirements: * The `/` character isn't allowed in a branch name. * Branch names must be case-insensitively unique. In other words, the names must be entirely unique regardless of the case you use. For example, if you have a branch named `Sprint`, you cannot create another branch named `sprint`. A branch name of `Sprint2` and `sprint2` are just fine. @@ -41,11 +41,11 @@ For specifics on creating Git branches, see the following topics: ## .gitignore file {#gitignore} Depending on your {{site.data.var.ece}} version, you may need different information added to or commented out in your `.gitignore` file. Git uses this file to determine which files and directories to ignore, before you make a commit to your branches. A .gitignore file should be committed into your root Magento in the repository, in order to share the ignore rules with any other users that clone the repository. -We include a base `.gitignore` file with the project repository. For a review of the {{site.data.var.ece}} file, see [.gitignore file](https://github.com/magento/magento-cloud/blob/master/.gitignore){:target="\_blank"}. You can review the recommended files for your file in the [`.gitignore` reference]({{ site.baseurl }}/guides/v2.2/config-guide/prod/config-reference-gitignore.html). +We include a base `.gitignore` file with the project repository. For a review of the {{site.data.var.ece}} file, see [.gitignore file](https://github.com/magento/magento-cloud/blob/master/.gitignore){:target="_blank"}. You can review the recommended files for your file in the [`.gitignore` reference]({{ site.baseurl }}/guides/v2.2/config-guide/prod/config-reference-gitignore.html). ## Git and SSH {#ssh} -You must use Secure Shell (SSH) and not HTTPS to connect to the Git repository. For more information, see [GitHub documentation](https://help.github.com/articles/generating-an-ssh-key){:target="\_blank"}. +You must use Secure Shell (SSH) and not HTTPS to connect to the Git repository. For more information, see [GitHub documentation](https://help.github.com/articles/generating-an-ssh-key){:target="_blank"}. When setting up your SSH, review our information at [SSH and sFTP]({{ page.baseurl }}/cloud/env/environments-ssh.html). diff --git a/guides/v2.1/cloud/release-notes/CloudReleaseNotes2.1.2.md b/guides/v2.1/cloud/release-notes/CloudReleaseNotes2.1.2.md index 9f160b325ed..123a78a8905 100644 --- a/guides/v2.1/cloud/release-notes/CloudReleaseNotes2.1.2.md +++ b/guides/v2.1/cloud/release-notes/CloudReleaseNotes2.1.2.md @@ -25,7 +25,7 @@ We made the following change in this release: We made the following fixes in this release: * Improved the performance of static file deployment. -* You can now upgrade to version 2.1.2 if you enabled [static file signatures](http://docs.magento.com/m2/ee/user_guide/system/static-file-signature.html){:target="\_blank"}. +* You can now upgrade to version 2.1.2 if you enabled [static file signatures](http://docs.magento.com/m2/ee/user_guide/system/static-file-signature.html){:target="_blank"}. * You no longer need a `pub/front-static.php` in your template. * We now back up `env.php` before disabling the Redis cache during deployment. * Patches are now applied in alphabetical order. diff --git a/guides/v2.1/cloud/release-notes/cloud-tools.md b/guides/v2.1/cloud/release-notes/cloud-tools.md index b83d7c82999..616ccbf4c42 100644 --- a/guides/v2.1/cloud/release-notes/cloud-tools.md +++ b/guides/v2.1/cloud/release-notes/cloud-tools.md @@ -22,7 +22,7 @@ The following updates describe the latest improvements to the `ece-tools` packag #### New features -- **Enable zero-downtime deployment**—Now {{site.data.var.ece}} queues requests with required database changes during deployment and applies the changes as soon as the deployment completes. Requests can be held for up to 5 minutes to ensure that no sessions are lost. See [Static content deployment options to reduce deployment downtime on Cloud](https://support.magento.com/hc/en-us/articles/360004861194-Static-content-deployment-options-to-reduce-deployment-downtime-on-Cloud){:target="\_blank"}. +- **Enable zero-downtime deployment**—Now {{site.data.var.ece}} queues requests with required database changes during deployment and applies the changes as soon as the deployment completes. Requests can be held for up to 5 minutes to ensure that no sessions are lost. See [Static content deployment options to reduce deployment downtime on Cloud](https://support.magento.com/hc/en-us/articles/360004861194-Static-content-deployment-options-to-reduce-deployment-downtime-on-Cloud){:target="_blank"}. - **Docker Compose for Cloud**—Made the following improvements to the [Docker configuration]({{ page.baseurl }}/cloud/reference/docker-config.html) process: @@ -87,7 +87,7 @@ The following updates describe the latest improvements to the `ece-tools` packag - Fixed an issue that prevented the `php ./vendor/bin/ece-tools config:dump` command from removing redundant sections from the `config.local.php` file during the dump process if the store locale is not specified. Now you can easily move your configuration files between environments. After you update to `ece-tools` v2002.0.13, regenerate older `config.local.php` files with the improved `config:dump` command. See [Configuration management for store settings]({{ page.baseurl }}/cloud/live/sens-data-over.html). -- Fixed an issue that caused an error during the deploy phase if the route configuration in the `.magento/routes.yaml` file redirects from an [apex](https://blog.cloudflare.com/zone-apex-naked-domain-root-domain-cname-supp/){:target="\_blank"} domain to a `www` domain. +- Fixed an issue that caused an error during the deploy phase if the route configuration in the `.magento/routes.yaml` file redirects from an [apex](https://blog.cloudflare.com/zone-apex-naked-domain-root-domain-cname-supp/){:target="_blank"} domain to a `www` domain. - Fixed an issue with the `_merge` option for the [`SEARCH_CONFIGURATION`]({{ page.baseurl }}/cloud/env/variables-deploy.html#search_configuration) variable that caused incorrect merge results if the updated `.magento.env.yaml` configuration file did not include the `engine` parameter value along with other updated values. Now, the merge operation correctly overwrites only the parameter values included in the updated `.magento.env.yaml` without requiring you to specify the `engine` parameter value. @@ -297,7 +297,7 @@ We merged `vendor/magento/ece-patches` with `vendor/magento/ece-tools` in this r - **Build/deploy notifications**—We added a new configuration file that you can use to [set up Slack and/or email notifications]({{ site.baseurl }}/guides/v2.1/cloud/env/setup-notifications.html) for build/deploy actions in all your environments. -- **Static content compression**—We now compress static content using [gzip](https://www.gnu.org/software/gzip/){:target="\_blank"} during the build and deploy phases. This compression, coupled with Fastly compression, helps reduce the size of your store and increase deployment speed. If necessary, you can disable compression using a [build option]({{ site.baseurl }}/guides/v2.1/cloud/env/variables-build.html) or [deploy variable]({{ site.baseurl }}/guides/v2.1/cloud/env/variables-deploy.html). See the following topics for more information: +- **Static content compression**—We now compress static content using [gzip](https://www.gnu.org/software/gzip/){:target="_blank"} during the build and deploy phases. This compression, coupled with Fastly compression, helps reduce the size of your store and increase deployment speed. If necessary, you can disable compression using a [build option]({{ site.baseurl }}/guides/v2.1/cloud/env/variables-build.html) or [deploy variable]({{ site.baseurl }}/guides/v2.1/cloud/env/variables-deploy.html). See the following topics for more information: - [Magento application environment variables]({{ site.baseurl }}/guides/v2.1/cloud/env/environment-vars_magento.html) - [Static content deployment performance]({{ site.baseurl }}/guides/v2.1/cloud/live/sens-data-over.html#cloud-confman-scd-over) diff --git a/guides/v2.1/cloud/requirements/cloud-requirements.md b/guides/v2.1/cloud/requirements/cloud-requirements.md index 139af549372..16c3d09596a 100644 --- a/guides/v2.1/cloud/requirements/cloud-requirements.md +++ b/guides/v2.1/cloud/requirements/cloud-requirements.md @@ -53,9 +53,9 @@ Git is the heart of all your code in repositories. It acts as a version control We hope you have a good working knowledge of Git. Need some help? Don't worry, we have you covered with some of our favorite links and information. We'll also include a Git guide to branching and developing soon. -* [Git documentation](https://git-scm.com/documentation){:target="\_blank"} and [videos](https://git-scm.com/videos){:target="\_blank"} from the makers of Git -* [Git cheatsheet](http://rogerdudler.github.io/git-guide/files/git_cheat_sheet.pdf){:target="\_blank"} and [quick guide](http://rogerdudler.github.io/git-guide/){:target="\_blank"} from Roger Dudler -* [Git video](https://www.youtube.com/watch?v=8KCQe9Pm1kg){:target="\_blank"} with DevForge to understand how people use the repo and commands with a fun story +* [Git documentation](https://git-scm.com/documentation){:target="_blank"} and [videos](https://git-scm.com/videos){:target="_blank"} from the makers of Git +* [Git cheatsheet](http://rogerdudler.github.io/git-guide/files/git_cheat_sheet.pdf){:target="_blank"} and [quick guide](http://rogerdudler.github.io/git-guide/){:target="_blank"} from Roger Dudler +* [Git video](https://www.youtube.com/watch?v=8KCQe9Pm1kg){:target="_blank"} with DevForge to understand how people use the repo and commands with a fun story To get started with Git, install Git on your local workstation. diff --git a/guides/v2.1/cloud/trouble/robots-sitemap.md b/guides/v2.1/cloud/trouble/robots-sitemap.md index 8ba19adc709..ecd4c8ad72d 100644 --- a/guides/v2.1/cloud/trouble/robots-sitemap.md +++ b/guides/v2.1/cloud/trouble/robots-sitemap.md @@ -15,7 +15,7 @@ With {{site.data.var.ece}}, you can only write to specific directories, such as For version 2.1.11 and later, you do not have to generate a `robots.txt` because it generates on demand and stores the contents in the database. It does not create a file, but you can view the content in your browser with the url: `/robots.txt` -This requires ECE-Tools version 2002.0.12 and later with an updated `.magento.app.yaml` file. See an example of these rules in the [magento-cloud repository](https://github.com/magento/magento-cloud/blob/master/.magento.app.yaml#L43-L49){:target="\_blank"}. +This requires ECE-Tools version 2002.0.12 and later with an updated `.magento.app.yaml` file. See an example of these rules in the [magento-cloud repository](https://github.com/magento/magento-cloud/blob/master/.magento.app.yaml#L43-L49){:target="_blank"}. #### To generate a `sitemap.xml` file in version 2.1.11 and later: diff --git a/guides/v2.1/cloud/trouble/trouble_fastly.md b/guides/v2.1/cloud/trouble/trouble_fastly.md index a1da60d6d60..db210dd3e2e 100644 --- a/guides/v2.1/cloud/trouble/trouble_fastly.md +++ b/guides/v2.1/cloud/trouble/trouble_fastly.md @@ -118,7 +118,7 @@ If you do not have DNS set up for a public hostname, enter a command similar to ### Check response headers {#response-headers} -For detailed information on hits and misses, see Fastly's [Understanding cache HIT and MISS headers with shielded services](https://docs.fastly.com/guides/performance-tuning/understanding-cache-hit-and-miss-headers-with-shielded-services){:target="\_blank"}. +For detailed information on hits and misses, see Fastly's [Understanding cache HIT and MISS headers with shielded services](https://docs.fastly.com/guides/performance-tuning/understanding-cache-hit-and-miss-headers-with-shielded-services){:target="_blank"}. Check the returned response headers and values: @@ -127,8 +127,8 @@ Check the returned response headers and values: * Fastly-Module-Enabled should be either Yes or the Fastly extension version number * X-Cache should be either `HIT` or `HIT, HIT` * x-cache-hits should be 1,1 -* [Cache-Control: max-age](https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9){:target="\_blank"} should be greater than 0 -* [Pragma](https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.32){:target="\_blank"} should be `cache` +* [Cache-Control: max-age](https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9){:target="_blank"} should be greater than 0 +* [Pragma](https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.32){:target="_blank"} should be `cache` The following example shows the correct values for `Pragma`, `X-Magento-Tags`, and `Fastly-Module-Enabled`. @@ -249,7 +249,7 @@ If the credentials are correct, you may have issues with your VCLs. To list and curl -X GET -s https://api.fastly.com/service//version//snippet/ -H "Fastly-Key: " -Review the list of VCLs. If you have issues with the default VCLs from Fastly, you can upload again or verify the content per the [Fastly default VCLs](https://github.com/fastly/fastly-magento2/tree/master/etc/vcl_snippets){:target="\_blank"}. For editing your custom VCLs, see [Custom Fastly VCL snippets]({{ page.baseurl }}/cloud/configure/cloud-vcl-custom-snippets.html). +Review the list of VCLs. If you have issues with the default VCLs from Fastly, you can upload again or verify the content per the [Fastly default VCLs](https://github.com/fastly/fastly-magento2/tree/master/etc/vcl_snippets){:target="_blank"}. For editing your custom VCLs, see [Custom Fastly VCL snippets]({{ page.baseurl }}/cloud/configure/cloud-vcl-custom-snippets.html). ## Activating a deactivated version {#activate} diff --git a/guides/v2.1/comp-mgr/install-extensions.md b/guides/v2.1/comp-mgr/install-extensions.md index 9724255bbad..4b718cc045e 100644 --- a/guides/v2.1/comp-mgr/install-extensions.md +++ b/guides/v2.1/comp-mgr/install-extensions.md @@ -3,7 +3,7 @@ group: compman title: Install extensions from the command line --- -Code that extends or customizes Magento behavior is called an extension. You can optionally package and distribute extensions on the [Magento Marketplace](https://marketplace.magento.com){:target="_blank"} or another Magento extension distribution system. Extensions include: +Code that extends or customizes Magento behavior is called an extension. You can optionally package and distribute extensions on the [Magento Marketplace](https://marketplace.magento.com){:target="_blank"} or another Magento extension distribution system. Extensions include: - Modules (extend Magento capabilities) - Themes (change the look and feel of your {% glossarytooltip 1a70d3ac-6bd9-475a-8937-5f80ca785c14 %}storefront{% endglossarytooltip %} and Admin) @@ -27,7 +27,7 @@ If you already know the extension's Composer name and version, skip this step an To get the extension's Composer name and version from the Magento Marketplace: -1. Log in to [Magento Marketplace](https://marketplace.magento.com){:target="_blank"} with the username and password you used to purchase the extension. +1. Log in to [Magento Marketplace](https://marketplace.magento.com){:target="_blank"} with the username and password you used to purchase the extension. 2. In the upper-right corner, click **Your name** > **My Profile**. diff --git a/guides/v2.1/comp-mgr/prereq/prereq_auth-token.md b/guides/v2.1/comp-mgr/prereq/prereq_auth-token.md index 83a8d3deef8..6e4e8a82ecb 100644 --- a/guides/v2.1/comp-mgr/prereq/prereq_auth-token.md +++ b/guides/v2.1/comp-mgr/prereq/prereq_auth-token.md @@ -10,7 +10,7 @@ functional_areas: ---
        -

        To upgrade your {{site.data.var.ee}} version or to upgrade from {{site.data.var.ce}} to {{site.data.var.ee}}, you must be authorized to access the {{site.data.var.ee}} repository. Contact Magento Support if you have questions.

        +

        To upgrade your {{site.data.var.ee}} version or to upgrade from {{site.data.var.ce}} to {{site.data.var.ee}}, you must be authorized to access the {{site.data.var.ee}} repository. Contact Magento Support if you have questions.

        To enter your [authentication keys]({{ page.baseurl }}/install-gde/prereq/connect-auth.html): diff --git a/guides/v2.1/comp-mgr/trouble/cman/tshoot_backup.md b/guides/v2.1/comp-mgr/trouble/cman/tshoot_backup.md index e3078160912..85f41164737 100644 --- a/guides/v2.1/comp-mgr/trouble/cman/tshoot_backup.md +++ b/guides/v2.1/comp-mgr/trouble/cman/tshoot_backup.md @@ -19,17 +19,17 @@ A backup can fail for any of the following reasons: If the backup failed because of insufficient disk space, you should typically free up disk space by moving some files to another storage device or drive. However, there might be other ways to resolve the issue. See one of the following resources for tips: -* [8 Tips to Solve Linux & Unix Systems Hard Disk Problems Like Disk Full Or Can’t Write to the Disk](http://www.cyberciti.biz/datacenter/linux-unix-bsd-osx-cannot-write-to-hard-disk){:target="_blank"} -* [serverfault: df says disk is full, but it is not](http://serverfault.com/questions/315181/df-says-disk-is-full-but-it-is-not){:target="_blank"} -* [unix.stackexchange.com: Tracking down where disk space has gone on Linux?](http://unix.stackexchange.com/questions/125429/tracking-down-where-disk-space-has-gone-on-linux){:target="_blank"} +* [8 Tips to Solve Linux & Unix Systems Hard Disk Problems Like Disk Full Or Can’t Write to the Disk](http://www.cyberciti.biz/datacenter/linux-unix-bsd-osx-cannot-write-to-hard-disk){:target="_blank"} +* [serverfault: df says disk is full, but it is not](http://serverfault.com/questions/315181/df-says-disk-is-full-but-it-is-not){:target="_blank"} +* [unix.stackexchange.com: Tracking down where disk space has gone on Linux?](http://unix.stackexchange.com/questions/125429/tracking-down-where-disk-space-has-gone-on-linux){:target="_blank"} ### Operating system error {#trouble-backup-os} Unfortunately, we can't recommend anything specific because of the variety of errors you might encounter. We can suggest, however, you: * Contact your system administrator -* Search public forums like [Stack Exchange](http://unix.stackexchange.com){:target="_blank"} or [Stack Overflow](http://stackoverflow.com){:target="_blank"} -* Open a [GitHub issue](https://github.com/magento/magento2/issues){:target="_blank"} and we'll try to help +* Search public forums like [Stack Exchange](http://unix.stackexchange.com){:target="_blank"} or [Stack Overflow](http://stackoverflow.com){:target="_blank"} +* Open a [GitHub issue](https://github.com/magento/magento2/issues){:target="_blank"} and we'll try to help ### Backup fails {#trouble-backup-all} diff --git a/guides/v2.1/comp-mgr/upgrader/ce-ee-upgrade-start.md b/guides/v2.1/comp-mgr/upgrader/ce-ee-upgrade-start.md index 49ead0d6ca1..dbbd553a42b 100644 --- a/guides/v2.1/comp-mgr/upgrader/ce-ee-upgrade-start.md +++ b/guides/v2.1/comp-mgr/upgrader/ce-ee-upgrade-start.md @@ -20,13 +20,13 @@ You must be authorized for {{site.data.var.ee}} to perform the tasks discussed i Before continuing, complete all tasks discussed in [Prerequisites]({{ page.baseurl }}/comp-mgr/prereq/prereq_compman.html). -In addition, you might need to install the {% glossarytooltip bf703ab1-ca4b-48f9-b2b7-16a81fd46e02 %}PHP{% endglossarytooltip %} [`bcmath`](http://php.net/manual/en/book.bc.php){:target="_blank"} extension, which is required by {{site.data.var.ee}}. Examples follow: +In addition, you might need to install the {% glossarytooltip bf703ab1-ca4b-48f9-b2b7-16a81fd46e02 %}PHP{% endglossarytooltip %} [`bcmath`](http://php.net/manual/en/book.bc.php){:target="_blank"} extension, which is required by {{site.data.var.ee}}. Examples follow: * CentOS (using the `webtatic` repository): `yum -y install php56w-bcmath` * Ubuntu (using the `ppa:ondrej/php5-5.6` repository): `apt-get -y install php5-bcmath` {:.bs-callout .bs-callout-info} -Make sure you are authorized for {{site.data.var.ee}} access before you continue. Contact [Magento Support](http://support.magentocommerce.com){:target="_blank"} if you have questions. +Make sure you are authorized for {{site.data.var.ee}} access before you continue. Contact [Magento Support](http://support.magentocommerce.com){:target="_blank"} if you have questions. ## Start System Upgrade from the Magento Admin {#compman-access} diff --git a/guides/v2.1/config-guide/bootstrap/mage-dirs.md b/guides/v2.1/config-guide/bootstrap/mage-dirs.md index 6974ac63a06..0bcba8fd0aa 100644 --- a/guides/v2.1/config-guide/bootstrap/mage-dirs.md +++ b/guides/v2.1/config-guide/bootstrap/mage-dirs.md @@ -14,7 +14,7 @@ The `MAGE_DIRS` environment variable enables you to specify custom base director ## Set MAGE_DIRS {#dirs-set} -Specify an associative array where keys are constants from [\\Magento\\App\\Filesystem\\DirectoryList]({{ site.mage2000url }}lib/internal/Magento/Framework/App/Filesystem/DirectoryList.php){:target="_blank"} and values are absolute paths of directories or their {% glossarytooltip a05c59d3-77b9-47d0-92a1-2cbffe3f8622 %}URL{% endglossarytooltip %} paths, respectively. +Specify an associative array where keys are constants from [\\Magento\\App\\Filesystem\\DirectoryList]({{ site.mage2000url }}lib/internal/Magento/Framework/App/Filesystem/DirectoryList.php){:target="_blank"} and values are absolute paths of directories or their {% glossarytooltip a05c59d3-77b9-47d0-92a1-2cbffe3f8622 %}URL{% endglossarytooltip %} paths, respectively. You can set `MAGE_DIRS` in any of the following ways: diff --git a/guides/v2.1/config-guide/bootstrap/mage-profiler.md b/guides/v2.1/config-guide/bootstrap/mage-profiler.md index 36b243bb9ba..a486fea244b 100644 --- a/guides/v2.1/config-guide/bootstrap/mage-profiler.md +++ b/guides/v2.1/config-guide/bootstrap/mage-profiler.md @@ -18,7 +18,7 @@ Magento profiling enables you to: You should be particularly interested in the list of *unused dependencies*, which are objects that were created because they were requested in some constructor, but were never used (that is, none of their methods were called). As a result, processor time and memory spent to create these dependencies are wasted. -Magento provides the base functionality in [Magento\\Framework\\Profiler]({{ site.mage2000url }}lib/internal/Magento/Framework/Profiler.php){:target="_blank"}. +Magento provides the base functionality in [Magento\\Framework\\Profiler]({{ site.mage2000url }}lib/internal/Magento/Framework/Profiler.php){:target="_blank"}. ## Set MAGE_PROFILER {#variable} @@ -28,8 +28,8 @@ Magento provides the base functionality in [Magento\\Framework\\Profiler]({{ sit You can also use one of the following values to enable a specific profiler: - - `csvfile` which uses [Magento\\Framework\\Profiler\\Driver\\Standard\\Output\\Csvfile]({{ site.mage2000url }}lib/internal/Magento/Framework/Profiler/Driver/Standard/Output/Csvfile.php){:target="_blank"} - - Any other value (except `2`), including an empty value, which uses [Magento\\Framework\\Profiler\\Driver\\Standard\\Output\\Html]({{ site.mage2000url }}lib/internal/Magento/Framework/Profiler/Driver/Standard/Output/Html.php){:target="_blank"} + - `csvfile` which uses [Magento\\Framework\\Profiler\\Driver\\Standard\\Output\\Csvfile]({{ site.mage2000url }}lib/internal/Magento/Framework/Profiler/Driver/Standard/Output/Csvfile.php){:target="_blank"} + - Any other value (except `2`), including an empty value, which uses [Magento\\Framework\\Profiler\\Driver\\Standard\\Output\\Html]({{ site.mage2000url }}lib/internal/Magento/Framework/Profiler/Driver/Standard/Output/Html.php){:target="_blank"} - `2` to enable dependency graphs. diff --git a/guides/v2.1/config-guide/bootstrap/magento-bootstrap.md b/guides/v2.1/config-guide/bootstrap/magento-bootstrap.md index 693e92b3b21..02ef6b58a6c 100644 --- a/guides/v2.1/config-guide/bootstrap/magento-bootstrap.md +++ b/guides/v2.1/config-guide/bootstrap/magento-bootstrap.md @@ -10,19 +10,19 @@ functional_areas: ## Overview of bootstrapping {#config-boot-overview} -To run the Magento application, the following actions are implemented in [index.php]({{ site.mage2000url }}index.php){:target="_blank"}: +To run the Magento application, the following actions are implemented in [index.php]({{ site.mage2000url }}index.php){:target="_blank"}: -* Include [app/bootstrap.php]({{ site.mage2000url }}app/bootstrap.php){:target="_blank"} which performs essential initialization routines, such as error handling, initializing the autoloader, setting profiling options, setting the default timezone, and so on. -* Create an instance of [\Magento\Framework\App\Bootstrap]({{ site.mage2000url }}lib/internal/Magento/Framework/App/Bootstrap.php){:target="_blank"}. -* Create a Magento application instance ([\Magento\Framework\AppInterface]({{ site.mage2000url }}lib/internal/Magento/Framework/AppInterface.php){:target="_blank"}). +* Include [app/bootstrap.php]({{ site.mage2000url }}app/bootstrap.php){:target="_blank"} which performs essential initialization routines, such as error handling, initializing the autoloader, setting profiling options, setting the default timezone, and so on. +* Create an instance of [\Magento\Framework\App\Bootstrap]({{ site.mage2000url }}lib/internal/Magento/Framework/App/Bootstrap.php){:target="_blank"}. +* Create a Magento application instance ([\Magento\Framework\AppInterface]({{ site.mage2000url }}lib/internal/Magento/Framework/AppInterface.php){:target="_blank"}). * Run Magento ## Bootstrap run logic {#config-boot-logic} -[The bootstrap object]({{ site.mage2000url }}app/bootstrap.php){:target="_blank"} uses the following algorithm to run the Magento application: +[The bootstrap object]({{ site.mage2000url }}app/bootstrap.php){:target="_blank"} uses the following algorithm to run the Magento application: 1. Initializes the error handler. -2. Creates the [object manager]({{ site.mage2000url }}lib/internal/Magento/Framework/ObjectManager){:target="_blank"} and basic shared services that are used everywhere and are affected by the environment. The environment parameters are injected properly into these objects. +2. Creates the [object manager]({{ site.mage2000url }}lib/internal/Magento/Framework/ObjectManager){:target="_blank"} and basic shared services that are used everywhere and are affected by the environment. The environment parameters are injected properly into these objects. 3. Asserts that maintenance mode is *not* enabled; otherwise, terminates. 4. Asserts that the Magento application is installed; otherwise, terminates. 5. Starts the Magento application. @@ -67,7 +67,7 @@ We have the following entry point applications (that is, applications defined by * [Media resource entry point](#config-boot-entry-media) ### HTTP entry point {#config-boot-entry-http} -[\Magento\Framework\App\Http]({{ site.mage2000url }}lib/internal/Magento/Framework/App/Http){:target="_blank"} operates as follows: +[\Magento\Framework\App\Http]({{ site.mage2000url }}lib/internal/Magento/Framework/App/Http){:target="_blank"} operates as follows: 1. Determines the [application area]({{ page.baseurl }}/architecture/archi_perspectives/components/modules/mod_and_areas.html). 2. Starts the front controller and routing systems in order to find and execute a controller action. @@ -83,7 +83,7 @@ We have the following entry point applications (that is, applications defined by 6. On any other error, display a user-friendly "Service Unavailable" page with HTTP response 503 and generate an error report and display its ID on the page. ### Static resource entry point {#config-boot-entry-static} -[\Magento\Framework\App\StaticResource]({{ site.mage2000url }}lib/internal/Magento/Framework/App/StaticResource.php){:target="_blank"} is an application for retrieving static resources (for example, CSS, JavaScript, and images). It postpones any actions with a static resource until the resource is requested. +[\Magento\Framework\App\StaticResource]({{ site.mage2000url }}lib/internal/Magento/Framework/App/StaticResource.php){:target="_blank"} is an application for retrieving static resources (for example, CSS, JavaScript, and images). It postpones any actions with a static resource until the resource is requested. {:.bs-callout .bs-callout-info} The entry point for static view files is not used in [production mode]({{ page.baseurl }}/config-guide/bootstrap/magento-modes.html#production-mode) to avoid potential exploits on the server. In production mode, the Magento application expects that all necessary resources already exist in the <your Magento install dir>/pub/static directory. @@ -97,7 +97,7 @@ When the request is redirected to the entry point, the Magento application parse All future requests for the static resource are processed by the server the same as static files; that is, without involving the entry point. If it's necessary to synchronize published files with original ones, the `pub/static` directory should be removed; as a result, files are automatically republished with the next request. ### Media resource entry point {#config-boot-entry-media} -[Magento\MediaStorage\App\Media]({{ site.mage2000url }}app/code/Magento/MediaStorage/App/Media.php){:target="_blank"} retrieves media resources (that is, any files uploaded to media storage) from the database. It is used whenever the database is configured as a {% glossarytooltip d95142d7-023f-451c-a2e9-dd88763dcd70 %}media storage{% endglossarytooltip %}. +[Magento\MediaStorage\App\Media]({{ site.mage2000url }}app/code/Magento/MediaStorage/App/Media.php){:target="_blank"} retrieves media resources (that is, any files uploaded to media storage) from the database. It is used whenever the database is configured as a {% glossarytooltip d95142d7-023f-451c-a2e9-dd88763dcd70 %}media storage{% endglossarytooltip %}. `\Magento\Core\App\Media` attempts to find the media file in the configured database storage and write it into the `pub/static` directory, then return its contents. On error, it returns an HTTP 404 (Not Found) status code in the header with no contents. diff --git a/guides/v2.1/config-guide/bootstrap/magento-how-to-set.md b/guides/v2.1/config-guide/bootstrap/magento-how-to-set.md index 55604db72bd..33718621183 100644 --- a/guides/v2.1/config-guide/bootstrap/magento-how-to-set.md +++ b/guides/v2.1/config-guide/bootstrap/magento-how-to-set.md @@ -36,7 +36,7 @@ For example, you can use the `MAGE_PROFILER` system environment variable to spec MAGE_PROFILER={firebug|csv|} -Set the variable using a shell-specific command. Because shells have differing syntax, consult a reference like [unix.stackexchange.com](http://unix.stackexchange.com/questions/117467/how-to-permanently-set-environmental-variables){:target="_blank"}. +Set the variable using a shell-specific command. Because shells have differing syntax, consult a reference like [unix.stackexchange.com](http://unix.stackexchange.com/questions/117467/how-to-permanently-set-environmental-variables){:target="_blank"}. bash shell example for CentOS: @@ -57,7 +57,7 @@ See one of the following sections for more information: ### Specify a variable using an nginx setting {#mode-specify-web-nginx} -See the [nginx sample configuration]({{ site.mage2000url }}nginx.conf.sample#L16){:target="_blank"} on GitHub. +See the [nginx sample configuration]({{ site.mage2000url }}nginx.conf.sample#L16){:target="_blank"} on GitHub. ### Specify a variable using .htaccess (Apache only) {#mode-specify-web-htaccess} @@ -88,7 +88,7 @@ To set a variable: The Apache web server supports setting the Magento mode using `mod_env` directives. -The Apache `mod_env` directive is slightly different in [version 2.2](http://httpd.apache.org/docs/2.2/mod/mod_env.html#setenv){:target="_blank"} and [version 2.4](http://httpd.apache.org/docs/2.4/mod/mod_env.html#setenv){:target="_blank"}. +The Apache `mod_env` directive is slightly different in [version 2.2](http://httpd.apache.org/docs/2.2/mod/mod_env.html#setenv){:target="_blank"} and [version 2.4](http://httpd.apache.org/docs/2.4/mod/mod_env.html#setenv){:target="_blank"}. The procedures that follows show how to set the Magento mode in an Apache virtual host. This is not the only way to use `mod_env` directives; consult the Apache documentation for details. @@ -97,7 +97,7 @@ The procedures that follows show how to set the Magento mode in an Apache virtua #### Specify a bootstrap variable for Apache on Ubuntu {#mode-specify-ubuntu} -This section assumes you've already set up your virtual host. If you have not, consult a resource such as [this DigitalOcean tutorial](https://www.digitalocean.com/community/tutorials/how-to-set-up-apache-virtual-hosts-on-ubuntu-14-04-lts){:target="_blank"}. +This section assumes you've already set up your virtual host. If you have not, consult a resource such as [this DigitalOcean tutorial](https://www.digitalocean.com/community/tutorials/how-to-set-up-apache-virtual-hosts-on-ubuntu-14-04-lts){:target="_blank"}. To set a Magento bootstrap variable using your web server's environment: @@ -132,7 +132,7 @@ To set a Magento bootstrap variable using your web server's environment: #### Specify a bootstrap variable for Apache on CentOS {#mode-specify-centos} -This section assumes you've already set up your virtual host. If you have not, consult a resource such as [this DigitalOcean tutorial](https://www.digitalocean.com/community/tutorials/how-to-set-up-apache-virtual-hosts-on-centos-6){:target="_blank"}. +This section assumes you've already set up your virtual host. If you have not, consult a resource such as [this DigitalOcean tutorial](https://www.digitalocean.com/community/tutorials/how-to-set-up-apache-virtual-hosts-on-centos-6){:target="_blank"}. To set a Magento bootstrap variable using your web server's environment: diff --git a/guides/v2.1/config-guide/cache/cache-options.md b/guides/v2.1/config-guide/cache/cache-options.md index 27f341f696a..a316bc288bd 100644 --- a/guides/v2.1/config-guide/cache/cache-options.md +++ b/guides/v2.1/config-guide/cache/cache-options.md @@ -15,11 +15,11 @@ The Magento application uses a low-level {% glossarytooltip 0bc9c8bc-de1a-4a06-9 ## Low-level frontend cache {#cache-lowlevel-front} -Magento extends [Zend_Cache_Core](http://framework.zend.com/manual/1.12/en/zend.cache.frontends.html){:target="_blank"} by implementing [Magento\Framework\Cache\Core]({{ site.mage2000url }}lib/internal/Magento/Framework/Cache/Core.php){:target="_blank"} frontend cache. +Magento extends [Zend_Cache_Core](http://framework.zend.com/manual/1.12/en/zend.cache.frontends.html){:target="_blank"} by implementing [Magento\Framework\Cache\Core]({{ site.mage2000url }}lib/internal/Magento/Framework/Cache/Core.php){:target="_blank"} frontend cache. ## Low-level backend cache {#cache-lowlevel-front} -In general, the Magento application works with any backend cache that [Zend_Cache Backends](http://framework.zend.com/manual/1.12/en/zend.cache.backends.html){:target="_blank"} supports. However, this guide covers only the following low-level backend caches: +In general, the Magento application works with any backend cache that [Zend_Cache Backends](http://framework.zend.com/manual/1.12/en/zend.cache.backends.html){:target="_blank"} supports. However, this guide covers only the following low-level backend caches: * [Redis]({{ page.baseurl }}/config-guide/redis/config-redis.html) * [Database]({{ page.baseurl }}/config-guide/cache/caching-database.html) diff --git a/guides/v2.1/config-guide/cache/cache-types.md b/guides/v2.1/config-guide/cache/cache-types.md index e4cd3ae75f8..2a615cc9342 100644 --- a/guides/v2.1/config-guide/cache/cache-types.md +++ b/guides/v2.1/config-guide/cache/cache-types.md @@ -65,11 +65,11 @@ You can specify frontend and {% glossarytooltip 74d6d228-34bd-4475-a6f8-0c0f4d6d where -* `` is the low-level frontend {% glossarytooltip 65f9a5a1-79ee-4f27-aac7-29abe24db40d %}cache type{% endglossarytooltip %}. Specify the name of a class that is compatible with [Zend\Cache\Core](http://framework.zend.com/apidoc/1.7/Zend_Cache/Zend_Cache_Core.html){:target="_blank"}. +* `` is the low-level frontend {% glossarytooltip 65f9a5a1-79ee-4f27-aac7-29abe24db40d %}cache type{% endglossarytooltip %}. Specify the name of a class that is compatible with [Zend\Cache\Core](http://framework.zend.com/apidoc/1.7/Zend_Cache/Zend_Cache_Core.html){:target="_blank"}. - If you omit ``, [Magento\Framework\Cache\Core]({{ site.mage2000url }}lib/internal/Magento/Framework/Cache/Core.php){:target="_blank"} is used. + If you omit ``, [Magento\Framework\Cache\Core]({{ site.mage2000url }}lib/internal/Magento/Framework/Cache/Core.php){:target="_blank"} is used. * ``, `` are the name and value of options the Magento framework passes as an associative array to the frontend cache upon its creation. -* `` is the low-level backend cache type. Specify the name of a class that is compatible with [Zend_Cache_Backend](http://framework.zend.com/apidoc/1.7/Zend_Cache/Zend_Cache_Backend/Zend_Cache_Backend.html){:target="_blank"} and that implements [Zend_Cache_Backend_Interface](http://framework.zend.com/apidoc/1.6/Zend_Cache/Zend_Cache_Backend/Zend_Cache_Backend_Interface.html){:target="_blank"}. +* `` is the low-level backend cache type. Specify the name of a class that is compatible with [Zend_Cache_Backend](http://framework.zend.com/apidoc/1.7/Zend_Cache/Zend_Cache_Backend/Zend_Cache_Backend.html){:target="_blank"} and that implements [Zend_Cache_Backend_Interface](http://framework.zend.com/apidoc/1.6/Zend_Cache/Zend_Cache_Backend/Zend_Cache_Backend_Interface.html){:target="_blank"}. * ``, `` are the name and value of options the Magento framework passes as an associative array to backend cache upon its creation. #### Next step diff --git a/guides/v2.1/config-guide/secy/secy-cron.md b/guides/v2.1/config-guide/secy/secy-cron.md index 72ffd4584d3..2388df8551c 100644 --- a/guides/v2.1/config-guide/secy/secy-cron.md +++ b/guides/v2.1/config-guide/secy/secy-cron.md @@ -29,10 +29,10 @@ You don't need to do anything if you use the [`magento cron:run`]({{ page.baseur ## Secure cron with Apache -This section discusses how to secure cron using [HTTP Basic authentication](http://tools.ietf.org/html/rfc2617"){:target="_blank"} with Apache. These instructions are based on Apache 2.2 with CentOS 6. For more information, refer to one of the following resources: +This section discusses how to secure cron using [HTTP Basic authentication](http://tools.ietf.org/html/rfc2617"){:target="_blank"} with Apache. These instructions are based on Apache 2.2 with CentOS 6. For more information, refer to one of the following resources: -- [Apache 2.2 authentication and authorization tutorial](http://httpd.apache.org/docs/2.2/howto/auth.html){:target="_blank"} -- [Apache 2.4 authentication and authorization tutorial](http://httpd.apache.org/docs/2.4/howto/auth.html){:target="_blank"} +- [Apache 2.2 authentication and authorization tutorial](http://httpd.apache.org/docs/2.2/howto/auth.html){:target="_blank"} +- [Apache 2.4 authentication and authorization tutorial](http://httpd.apache.org/docs/2.4/howto/auth.html){:target="_blank"} ### Create a password file @@ -107,14 +107,14 @@ This section discusses how to secure cron using the {% glossarytooltip b14ef3d8- Consult one of the following resources to create a password file before continuing: -- [How To Set Up Password Authentication with Nginx on Ubuntu 14.04 (DigitalOcean)](https://www.digitalocean.com/community/tutorials/how-to-set-up-password-authentication-with-nginx-on-ubuntu-14-04){:target="_blank"} -- [Basic HTTP Authentication with nginx (howtoforge)](https://www.howtoforge.com/basic-http-authentication-with-nginx){:target="_blank"} +- [How To Set Up Password Authentication with Nginx on Ubuntu 14.04 (DigitalOcean)](https://www.digitalocean.com/community/tutorials/how-to-set-up-password-authentication-with-nginx-on-ubuntu-14-04){:target="_blank"} +- [Basic HTTP Authentication with nginx (howtoforge)](https://www.howtoforge.com/basic-http-authentication-with-nginx){:target="_blank"} ### Secure cron in `nginx.conf.sample` Magento provides an optimized sample nginx configuration file out of the box. We recommend modifying it to secure cron. -1. Add the following to your Magento [`nginx.sample.conf`]({{ site.mage2000url }}nginx.conf.sample){:target="_blank"} file: +1. Add the following to your Magento [`nginx.sample.conf`]({{ site.mage2000url }}nginx.conf.sample){:target="_blank"} file: ```terminal #Securing cron diff --git a/guides/v2.1/contributor-guide/contributing.md b/guides/v2.1/contributor-guide/contributing.md index e2ed801ddf1..ba9fd9136b5 100644 --- a/guides/v2.1/contributor-guide/contributing.md +++ b/guides/v2.1/contributor-guide/contributing.md @@ -43,9 +43,9 @@ For details, see [Configuring Two-Factor Authentication via a mobile app guide]( ## Questions or enhancement requests? {#question} -We use this repository (the Magento 2 GitHub repository) to capture code and documentation issues. We recommend that you post all questions to a question-and-answer site, such as [Stack Exchange](https://magento.stackexchange.com/){:target="\_blank"} and the [Magento Forums](https://community.magento.com/){:target="\_blank"}, where Magento community members can quickly provide recommendations and advice. +We use this repository (the Magento 2 GitHub repository) to capture code and documentation issues. We recommend that you post all questions to a question-and-answer site, such as [Stack Exchange](https://magento.stackexchange.com/){:target="_blank"} and the [Magento Forums](https://community.magento.com/){:target="_blank"}, where Magento community members can quickly provide recommendations and advice. -Submit feature requests or enhancement suggestions to the new [Magento 2 Feature Requests and Improvements forum](https://community.magento.com/t5/Magento-2-Feature-Requests-and/idb-p/feature-requests){:target="\_blank"} (see details [here](https://community.magento.com/t5/News-Announcements/Improvements-to-GitHub-Management/m-p/44572#M96){:target="\_blank"}). +Submit feature requests or enhancement suggestions to the new [Magento 2 Feature Requests and Improvements forum](https://community.magento.com/t5/Magento-2-Feature-Requests-and/idb-p/feature-requests){:target="_blank"} (see details [here](https://community.magento.com/t5/News-Announcements/Improvements-to-GitHub-Management/m-p/44572#M96){:target="_blank"}). ## Accepted pull requests and ported code {#rules} @@ -59,24 +59,24 @@ Please review the following supported and accepted pull request rules. We define ## Contribution requirements {#requirements} -1. Contributions must adhere to [Magento coding standards]({{page.baseurl}}/coding-standards/bk-coding-standards.html){:target="\_blank"}. +1. Contributions must adhere to [Magento coding standards]({{page.baseurl}}/coding-standards/bk-coding-standards.html){:target="_blank"}. 1. Refer to the Magento development team's [Definition of Done]({{page.baseurl}}/contributor-guide/contributing_dod.html). We use these guidelines internally to ensure that we deliver well-tested, well-documented, and solid code. We encourage you to use this as well! 1. Pull requests (PRs) must be accompanied by a meaningful description of their purpose. Comprehensive descriptions increase the chances that a pull request is merged quickly and without additional clarification requests. 1. Commits must be accompanied by meaningful commit messages. 1. PRs that include bug fixes must be accompanied by a step-by-step description of how to reproduce the bug. 1. PRs that include new logic or new features must be submitted along with: * Unit/integration test coverage (we will be releasing more information about writing test coverage in the near future). - * Proposed [documentation](https://github.com/magento/devdocs/blob/master/.github/CONTRIBUTING.md){:target="\_blank"} updates. [Documentation]({{site.baseurl}}/){:target="\_blank"} contributions can be submitted [here](https://github.com/magento/devdocs){:target="\_blank"}. -1. For large features or changes, please [open an issue](https://github.com/magento/magento2/issues){:target="\_blank"} and discuss it with us first. This may prevent duplicate or unnecessary effort, and it may gain you some additional contributors. -1. To report a bug, please [open an issue](https://github.com/magento/magento2/issues){:target="\_blank"}, and follow these [guidelines about bugfix issues](https://github.com/magento/magento2/wiki/Issue-reporting-guidelines){:target="\_blank"}. -1. All automated tests must pass successfully (all builds on [Travis CI](https://travis-ci.org/magento/magento2){:target="\_blank"} must be green). + * Proposed [documentation](https://github.com/magento/devdocs/blob/master/.github/CONTRIBUTING.md){:target="_blank"} updates. [Documentation]({{site.baseurl}}/){:target="_blank"} contributions can be submitted [here](https://github.com/magento/devdocs){:target="_blank"}. +1. For large features or changes, please [open an issue](https://github.com/magento/magento2/issues){:target="_blank"} and discuss it with us first. This may prevent duplicate or unnecessary effort, and it may gain you some additional contributors. +1. To report a bug, please [open an issue](https://github.com/magento/magento2/issues){:target="_blank"}, and follow these [guidelines about bugfix issues](https://github.com/magento/magento2/wiki/Issue-reporting-guidelines){:target="_blank"}. +1. All automated tests must pass successfully (all builds on [Travis CI](https://travis-ci.org/magento/magento2){:target="_blank"} must be green). ## Fork a repository {#fork} To fork a repository on Github: 1. Create or log in to your account on GitHub. -2. Navigate to the [Magento 2 repository](https://github.com/magento/magento2){:target="\_blank"}. +2. Navigate to the [Magento 2 repository](https://github.com/magento/magento2){:target="_blank"}. 3. Click **Fork** at the top right: ![Fork a Repository]({{site.baseurl}}/common/images/fork.png) diff --git a/guides/v2.1/contributor-guide/devdocs-maintainers.md b/guides/v2.1/contributor-guide/devdocs-maintainers.md index 01f7b91a85b..93fb85c7053 100644 --- a/guides/v2.1/contributor-guide/devdocs-maintainers.md +++ b/guides/v2.1/contributor-guide/devdocs-maintainers.md @@ -9,7 +9,7 @@ Luckily, the Magento community is full of knowledgeable people that enjoy sharin ## New team -We have decided to form a [devdocs-maintainers](https://github.com/orgs/magento/teams/devdocs-maintainers/members){:target="\_blank"} team on GitHub. This team is similar to the [Community Maintainers](https://magento.com/magento-contributors#maintainers){:target="_blank"} team that supports the Magento application codebase. +We have decided to form a [devdocs-maintainers](https://github.com/orgs/magento/teams/devdocs-maintainers/members){:target="_blank"} team on GitHub. This team is similar to the [Community Maintainers](https://magento.com/magento-contributors#maintainers){:target="_blank"} team that supports the Magento application codebase. {:.text-center} ![Future Maintainers page](img/maintainers-sneak-peek.jpg){:width="600"} diff --git a/guides/v2.1/contributor-guide/maintainers.md b/guides/v2.1/contributor-guide/maintainers.md index ec504da4e9e..a37ab9858ea 100644 --- a/guides/v2.1/contributor-guide/maintainers.md +++ b/guides/v2.1/contributor-guide/maintainers.md @@ -9,14 +9,14 @@ redirect_from: - guides/v2.3/contributor-guide/devdocs-maintainers.html --- -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){:target="\_blank"} take part in discussions, reviews, and help process pull requests. +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){:target="_blank"} take part in discussions, reviews, and help process pull requests. ## Who becomes a Maintainer? When considering new maintainers, we look for contributors who have shown a propensity for: - Contributing good and accepted code to multiple Magento projects, including fixes for issues and new features -- Participating in discussions in our development projects, including the [architecture](https://github.com/magento/architecture){:target="\_blank"} and [backlog](https://github.com/magento/backlog){:target="\_blank"} projects +- Participating in discussions in our development projects, including the [architecture](https://github.com/magento/architecture){:target="_blank"} and [backlog](https://github.com/magento/backlog){:target="_blank"} projects - Reviewing and discussing pull requests from other contributors - Helping other contributors with complex decisions and questions, like architecture questions, and providing advice according to [Magento technical guidelines]({{ page.baseurl }}/coding-standards/technical-guidelines.html) diff --git a/guides/v2.1/ext-best-practices/bk-ext-best-practices.md b/guides/v2.1/ext-best-practices/bk-ext-best-practices.md index 55a1ae4fe03..1f1f1e9501a 100644 --- a/guides/v2.1/ext-best-practices/bk-ext-best-practices.md +++ b/guides/v2.1/ext-best-practices/bk-ext-best-practices.md @@ -15,7 +15,7 @@ functional_areas: {:.bs-callout .bs-callout-info} DRAFT/PROPOSAL: This Best Practices Guide is a first draft! The guide combines Best Practices that we have heard the community ask for, along with guidelines that our Magento UX, Engineering, and Product teams are working on. -We want your feedback; please do a pull request on [feedback-placement-and-design.md](https://github.com/magento/devdocs/tree/develop/guides/v2.0/ext-best-practices/admin/feedback-placement-and-design.md){target="_blank"} and let us know what your best practices are, your challenges, and how you would like Magento to help standardize (where needed). +We want your feedback; please do a pull request on [feedback-placement-and-design.md](https://github.com/magento/devdocs/tree/develop/guides/v2.0/ext-best-practices/admin/feedback-placement-and-design.md){target="_blank"} and let us know what your best practices are, your challenges, and how you would like Magento to help standardize (where needed). Magento consists of the core product code plus optional components that enhance or replace the core product code. There are over 100 out-of-the-box components in the form of modules, themes, and language packages available for Magento 2. diff --git a/guides/v2.1/extension-dev-guide/build/composer-integration.md b/guides/v2.1/extension-dev-guide/build/composer-integration.md index 5b2b42a2937..0787239ecfa 100644 --- a/guides/v2.1/extension-dev-guide/build/composer-integration.md +++ b/guides/v2.1/extension-dev-guide/build/composer-integration.md @@ -11,13 +11,13 @@ redirect_from: ## Overview -Magento 2 uses [Composer][0]{:target="\_blank"}, a {% glossarytooltip bf703ab1-ca4b-48f9-b2b7-16a81fd46e02 %}PHP{% endglossarytooltip %} dependency manager, to package components and product editions. +Magento 2 uses [Composer][0]{:target="_blank"}, a {% glossarytooltip bf703ab1-ca4b-48f9-b2b7-16a81fd46e02 %}PHP{% endglossarytooltip %} dependency manager, to package components and product editions. Composer reads a `composer.json` file in Magento's root directory to download third-party dependencies listed in the file. The [Component Manager][1] uses the `composer.json` file in an extension's root directory to perform the following actions: -* The Component Manager can update, uninstall, enable, or disable an {% glossarytooltip 55774db9-bf9d-40f3-83db-b10cc5ae3b68 %}extension{% endglossarytooltip %} if installed using Composer (including from [Packagist][2]{:target="\_blank"}, [Magento Marketplace][6]{:target="\_blank"}, or other source) *and* it has a `composer.json` file. +* The Component Manager can update, uninstall, enable, or disable an {% glossarytooltip 55774db9-bf9d-40f3-83db-b10cc5ae3b68 %}extension{% endglossarytooltip %} if installed using Composer (including from [Packagist][2]{:target="_blank"}, [Magento Marketplace][6]{:target="_blank"}, or other source) *and* it has a `composer.json` file. * The Component Manager can still enable or disable an extension *not* installed using Composer (e.g. custom code) if it has a `composer.json` file. We recommend you include `composer.json` in your component's root directory even if you do not intend to distribute it to other merchants using Magento. @@ -34,7 +34,7 @@ Keep this in mind while customizing, updating, or troubleshooting composer while ## Project vs product -In Composer, a "project" package is a template used by the [`composer create-project`][9]{:target="\_blank"} to set up the project structure. +In Composer, a "project" package is a template used by the [`composer create-project`][9]{:target="_blank"} to set up the project structure. The [installation instructions for system integrators][10] use the {{site.data.var.ce}} and {{site.data.var.ee}} project packages to set up the Magento directory structure. A "product" package is the actual application pointed to by the `composer.json` file after you download and install the project package using `composer create-project`. @@ -130,7 +130,7 @@ The `composer.json` file for a {% glossarytooltip d2093e4a-2b71-48a3-99b7-b32af7 **Type:** `magento2-language` -For language packages, you must use the correct [ISO code][4]{:target="\_blank"} for the language code in the `composer.json` file. +For language packages, you must use the correct [ISO code][4]{:target="_blank"} for the language code in the `composer.json` file. --- @@ -161,11 +161,11 @@ For example, the vendor name format for extensions released by Magento Inc is `m #### Magento Marketplace Extensions Magento Marketplace uses `vendor-name` to match an extension to a vendor during the extension submission process. -If you plan to submit your extension to the [Magento Marketplace][7]{:target="\_blank"}, you *must* use the unique Vendor Name created or assigned to you when you created your marketplace account. +If you plan to submit your extension to the [Magento Marketplace][7]{:target="_blank"}, you *must* use the unique Vendor Name created or assigned to you when you created your marketplace account. In the `composer.json` file, use the value of 'Vendor Name' in your profile for the `vendor-name` part of the extension name. -Please see the [Marketplace Documentation][5]{:target="\_blank"} for more information about your unique vendor name. +Please see the [Marketplace Documentation][5]{:target="_blank"} for more information about your unique vendor name. ### package-name diff --git a/guides/v2.1/extension-dev-guide/cache/page-caching.md b/guides/v2.1/extension-dev-guide/cache/page-caching.md index ce6bcaaac36..723ed8ff764 100644 --- a/guides/v2.1/extension-dev-guide/cache/page-caching.md +++ b/guides/v2.1/extension-dev-guide/cache/page-caching.md @@ -14,5 +14,5 @@ redirect_from: {% include cache/page-cache-overview.md%}
        -Only HTTP [GET](https://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.3){:target="_blank} and [HEAD](https://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.4){:target="_blank"} requests are cacheable. For more information about caching, see [RFC-2616 section 13](https://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html){:target="_blank}. +Only HTTP [GET](https://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.3){:target="_blank} and [HEAD](https://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.4){:target="_blank"} requests are cacheable. For more information about caching, see [RFC-2616 section 13](https://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html){:target="_blank}.
        diff --git a/guides/v2.1/extension-dev-guide/cache/page-caching/private-content.md b/guides/v2.1/extension-dev-guide/cache/page-caching/private-content.md index 9c980dc6137..c0b5eec76ae 100644 --- a/guides/v2.1/extension-dev-guide/cache/page-caching/private-content.md +++ b/guides/v2.1/extension-dev-guide/cache/page-caching/private-content.md @@ -21,17 +21,17 @@ redirect_from: Since private content is specific to individual users, it's reasonable to handle it on the client (i.e., web browser). -Use our [customer-data]({{ site.mage2000url }}app/code/Magento/Customer/view/frontend/web/js/customer-data.js){:target="_blank"} JS library to store private data in local storage, invalidate private data using customizable rules, and synchronize data with the backend. +Use our [customer-data]({{ site.mage2000url }}app/code/Magento/Customer/view/frontend/web/js/customer-data.js){:target="_blank"} JS library to store private data in local storage, invalidate private data using customizable rules, and synchronize data with the backend. This example shows a customer's name on a cacheable page. ## Create a section source {#config-cache-priv-how-source} -The section source class is responsible for retrieving data for the section. As a best practice, we recommend you put your code under the `Vendor/ModuleName/CustomerData` namespace. Your classes must implement the [`Magento\Customer\CustomerData\SectionSourceInterface`]({{ site.mage2000url }}app/code/Magento/Customer/CustomerData/SectionSourceInterface.php){:target=" _blank"} interface. +The section source class is responsible for retrieving data for the section. As a best practice, we recommend you put your code under the `Vendor/ModuleName/CustomerData` namespace. Your classes must implement the [`Magento\Customer\CustomerData\SectionSourceInterface`]({{ site.mage2000url }}app/code/Magento/Customer/CustomerData/SectionSourceInterface.php){:target="_blank"} interface. The public method `getSectionData` must return an array with data for private block. -[Example]({{ site.mage2000url }}app/code/Magento/Catalog/CustomerData/CompareProducts.php#L36-L45){:target=" _blank"} +[Example]({{ site.mage2000url }}app/code/Magento/Catalog/CustomerData/CompareProducts.php#L36-L45){:target="_blank"} Add the following to your component's {% glossarytooltip 2be50595-c5c7-4b9d-911c-3bf2cd3f7beb %}dependency injection{% endglossarytooltip %} configuration (`di.xml`): @@ -53,7 +53,7 @@ To render private content, create a block and a template to display user-agnosti Do _not_ use the `$_isScopePrivate` property in your blocks. This property is obsolete and won't work properly.
        -Replace private data in blocks with placeholders (using [Knockout](http://knockoutjs.com/documentation/introduction.html){:target="_blank"} syntax). The init scope on the root element is `data-bind="scope: 'compareProducts'"`, where you define the scope name (`compareProducts` in this example) in your {% glossarytooltip 73ab5daa-5857-4039-97df-11269b626134 %}layout{% endglossarytooltip %}. +Replace private data in blocks with placeholders (using [Knockout](http://knockoutjs.com/documentation/introduction.html){:target="_blank"} syntax). The init scope on the root element is `data-bind="scope: 'compareProducts'"`, where you define the scope name (`compareProducts` in this example) in your {% glossarytooltip 73ab5daa-5857-4039-97df-11269b626134 %}layout{% endglossarytooltip %}. Initialize the component as follows: @@ -63,23 +63,23 @@ Initialize the component as follows: ``` -[Example]({{ site.mage2000url }}app/code/Magento/Catalog/view/frontend/templates/product/compare/sidebar.phtml#L46-L48){:target="_blank"} +[Example]({{ site.mage2000url }}app/code/Magento/Catalog/view/frontend/templates/product/compare/sidebar.phtml#L46-L48){:target="_blank"} ## Configure a UI component {#config-cache-priv-how-ui} The UI component renders block data on the Magento {% glossarytooltip 1a70d3ac-6bd9-475a-8937-5f80ca785c14 %}storefront{% endglossarytooltip %}. To initialize the UI component, you must call the initialization method `_super()`. -[Example]({{ site.mage2000url }}app/code/Magento/Catalog/view/frontend/web/js/view/compare-products.js){:target="_blank"} +[Example]({{ site.mage2000url }}app/code/Magento/Catalog/view/frontend/web/js/view/compare-products.js){:target="_blank"} All properties are available in the template. -[Example of defining a UI component in a layout]({{ site.mage2000url }}app/code/Magento/Catalog/view/frontend/layout/default.xml#L11-L22){:target="_blank"} +[Example of defining a UI component in a layout]({{ site.mage2000url }}app/code/Magento/Catalog/view/frontend/layout/default.xml#L11-L22){:target="_blank"} ## Invalidate private content Specify actions that trigger cache invalidation for private content blocks in a `sections.xml` configuration file in the `Vendor/ModuleName/etc/frontend` directory. Magento invalidates the cache on a POST or PUT request. -The following example adds comments to [app/code/Magento/Catalog/etc/frontend/sections.xml]({{ site.mage2000url }}app/code/Magento/Catalog/etc/frontend/sections.xml){:target="_blank"} to show you what the code is doing. +The following example adds comments to [app/code/Magento/Catalog/etc/frontend/sections.xml]({{ site.mage2000url }}app/code/Magento/Catalog/etc/frontend/sections.xml){:target="_blank"} to show you what the code is doing. ``` xml @@ -108,14 +108,14 @@ The following example adds comments to [app/code/Magento/Catalog/etc/frontend/se ```
        -Use only HTTP POST or PUT methods to change state (e.g., adding to a shopping cart, adding to a wishlist, etc.) and don't expect to see caching on these methods. Using GET or HEAD methods might trigger caching and prevent updates to private content. For more information about caching, see [RFC-2616 section 13](https://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html){:target="_blank"} +Use only HTTP POST or PUT methods to change state (e.g., adding to a shopping cart, adding to a wishlist, etc.) and don't expect to see caching on these methods. Using GET or HEAD methods might trigger caching and prevent updates to private content. For more information about caching, see [RFC-2616 section 13](https://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html){:target="_blank"}
        Other examples: -- [Checkout]({{ site.mage2000url }}app/code/Magento/Checkout/etc/frontend/sections.xml){:target="_blank"} +- [Checkout]({{ site.mage2000url }}app/code/Magento/Checkout/etc/frontend/sections.xml){:target="_blank"} -- [Customer]({{ site.mage2000url }}app/code/Magento/Customer/etc/frontend/sections.xml){:target="_blank"} +- [Customer]({{ site.mage2000url }}app/code/Magento/Customer/etc/frontend/sections.xml){:target="_blank"} ## Version private content {#config-priv-vers} diff --git a/guides/v2.1/extension-dev-guide/cache/page-caching/public-content.md b/guides/v2.1/extension-dev-guide/cache/page-caching/public-content.md index 85e7009f673..bad7f1f3297 100644 --- a/guides/v2.1/extension-dev-guide/cache/page-caching/public-content.md +++ b/guides/v2.1/extension-dev-guide/cache/page-caching/public-content.md @@ -119,7 +119,7 @@ Context variables should not be specific to individual users because variables a Magento generates a hash based on all context variables (`\Magento\Framework\App\Http\Context::getVaryString`). The hash and current URL are used as keys for cache storage.
        -Use the `X-Magento-Vary` cookie to transfer context on the HTTP layer. HTTP proxies can be configured to calculate a unique identifier for cache based on the cookie and URL. For example, [our sample Varnish 4 configuration]({{ site.mage2000url }}app/code/Magento/PageCache/etc/varnish4.vcl#L63-L68){:target="_blank"} uses the following: +Use the `X-Magento-Vary` cookie to transfer context on the HTTP layer. HTTP proxies can be configured to calculate a unique identifier for cache based on the cookie and URL. For example, [our sample Varnish 4 configuration]({{ site.mage2000url }}app/code/Magento/PageCache/etc/varnish4.vcl#L63-L68){:target="_blank"} uses the following: ``` sub vcl_hash { @@ -160,7 +160,7 @@ class CustomerAgeContextPlugin The `subject->setValue` argument specifies the value for newcomer context and is used to guarantee parity during cache key generation for newcomers and users who already received the `X-Magento-Vary` cookie. -For another example of a context class, see [Magento/Framework/App/Http/Context]({{ site.mage2000url }}lib/internal/Magento/Framework/App/Http/Context.php){:target="_blank"}. +For another example of a context class, see [Magento/Framework/App/Http/Context]({{ site.mage2000url }}lib/internal/Magento/Framework/App/Http/Context.php){:target="_blank"}. ## Invalidate public content @@ -168,7 +168,7 @@ You can clear cached content immediately after a entity changes. Magento uses ` This section shows you how to tell Magento what cache to clear when you change an entity. -First, your entity {% glossarytooltip c1e4242b-1f1a-44c3-9d72-1d5b1435e142 %}module{% endglossarytooltip %} must implement [`Magento/Framework/DataObject/IdentityInterface`]({{ site.mage2000url }}lib/internal/Magento/Framework/DataObject/IdentityInterface.php){:target="_blank"} as follows: +First, your entity {% glossarytooltip c1e4242b-1f1a-44c3-9d72-1d5b1435e142 %}module{% endglossarytooltip %} must implement [`Magento/Framework/DataObject/IdentityInterface`]({{ site.mage2000url }}lib/internal/Magento/Framework/DataObject/IdentityInterface.php){:target="_blank"} as follows: ``` php?start_inline=1 use Magento\Framework\DataObject\IdentityInterface; @@ -210,7 +210,7 @@ class View extends AbstractProduct implements \Magento\Framework\DataObject\Iden Magento uses cache tags for link creation. The performance of cache storage has a direct dependency on the number of tags per cache record, so try to minimize the number of tags and use them only for entities that are used in production mode. In other words, don't use invalidation for actions related to store setup.
        -Use only HTTP POST or PUT methods to change state (e.g., adding to a shopping cart, adding to a wishlist, etc.) and don't expect to see caching on these methods. Using GET or HEAD methods might trigger caching and prevent updates to private content. For more information about caching, see [RFC-2616 section 13](https://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html) {:target="_blank"} +Use only HTTP POST or PUT methods to change state (e.g., adding to a shopping cart, adding to a wishlist, etc.) and don't expect to see caching on these methods. Using GET or HEAD methods might trigger caching and prevent updates to private content. For more information about caching, see [RFC-2616 section 13](https://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html) {:target="_blank"}
        {% include cache/page-cache-checklists.md%} diff --git a/guides/v2.1/extension-dev-guide/cache/partial-caching.md b/guides/v2.1/extension-dev-guide/cache/partial-caching.md index 6bee4588018..42e151a9bdd 100644 --- a/guides/v2.1/extension-dev-guide/cache/partial-caching.md +++ b/guides/v2.1/extension-dev-guide/cache/partial-caching.md @@ -11,7 +11,7 @@ redirect_from: - /guides/v2.2/config-guide/config/caching.html --- -Magento uses [Zend_Cache](http://framework.zend.com/manual/1.12/en/zend.cache.html){:target="_blank"} to interact with the cache storage. However, Magento also has the [Magento\Cache]({{ site.mage2000url }}lib/internal/Magento/Framework/Cache){:target="_blank"} {% glossarytooltip 08968dbb-2eeb-45c7-ae95-ffca228a7575 %}library{% endglossarytooltip %} for implementing Magento-specific caching. These topics discuss how to configure caching and {% glossarytooltip 0bc9c8bc-de1a-4a06-9c99-a89a29c30645 %}cache{% endglossarytooltip %} types. +Magento uses [Zend_Cache](http://framework.zend.com/manual/1.12/en/zend.cache.html){:target="_blank"} to interact with the cache storage. However, Magento also has the [Magento\Cache]({{ site.mage2000url }}lib/internal/Magento/Framework/Cache){:target="_blank"} {% glossarytooltip 08968dbb-2eeb-45c7-ae95-ffca228a7575 %}library{% endglossarytooltip %} for implementing Magento-specific caching. These topics discuss how to configure caching and {% glossarytooltip 0bc9c8bc-de1a-4a06-9c99-a89a29c30645 %}cache{% endglossarytooltip %} types.

        By default, file system caching is enabled; no configuration is necessary to use it. This means the cache is located under <your Magento install dir>/var.

        diff --git a/guides/v2.1/get-started/create-integration.md b/guides/v2.1/get-started/create-integration.md index bbdbabe5e54..2e494bf57a4 100644 --- a/guides/v2.1/get-started/create-integration.md +++ b/guides/v2.1/get-started/create-integration.md @@ -138,7 +138,7 @@ Change directories to your `Setup` directory. Create a `InstallData.php` file th * @param ConfigBasedIntegrationManager $integrationManager */ - public function __construct(ConfigBasedIntegrationManager $integrationManager) + public function __construct(ConfigBasedIntegrationManager $integrationManager) { $this->integrationManager = $integrationManager; } diff --git a/guides/v2.1/install-gde/basics/basics_docroot.md b/guides/v2.1/install-gde/basics/basics_docroot.md index e843e9d9605..6aab2770871 100644 --- a/guides/v2.1/install-gde/basics/basics_docroot.md +++ b/guides/v2.1/install-gde/basics/basics_docroot.md @@ -27,11 +27,11 @@ As part of the Magento 2 installation process, you specify a subdirectory (usual ## Contact your hosting provider -If you use one, contact your hosting provider to locate the web server docroot. For example, [cPanel](http://support.hostgator.com/articles/cpanel/what-is-a-document-root-folder){:target="\_blank"} typically uses `public_html` as its docroot, but you should contact your provider to confirm. +If you use one, contact your hosting provider to locate the web server docroot. For example, [cPanel](http://support.hostgator.com/articles/cpanel/what-is-a-document-root-folder){:target="_blank"} typically uses `public_html` as its docroot, but you should contact your provider to confirm. ## Find the docroot yourself -This section assumes you've already set up a simple web server using [Apache virtual hosts](https://httpd.apache.org/docs/2.4/vhosts/){:target="\_blank"} or [nginx server blocks](https://www.nginx.com/resources/wiki/start/topics/examples/server_blocks/){:target="\_blank"}. +This section assumes you've already set up a simple web server using [Apache virtual hosts](https://httpd.apache.org/docs/2.4/vhosts/){:target="_blank"} or [nginx server blocks](https://www.nginx.com/resources/wiki/start/topics/examples/server_blocks/){:target="_blank"}. {:.bs-callout .bs-callout-info} You can use _virtual hosts_ and _server blocks_ to run more than one web site on a single machine (e.g., `company1.example.com` and `company2.example.com`) or override the web server's default docroot without changing it. diff --git a/guides/v2.1/install-gde/composer.md b/guides/v2.1/install-gde/composer.md index d99b248ec37..30749e624af 100644 --- a/guides/v2.1/install-gde/composer.md +++ b/guides/v2.1/install-gde/composer.md @@ -28,7 +28,7 @@ Before you continue, you must do the following: - Set up a server that meets our [system requirements]({{ page.baseurl }}/install-gde/system-requirements2.html) - Create the [Magento file system owner]({{ page.baseurl }}/install-gde/prereq/file-sys-perms-over.html) -- [Install Composer](https://getcomposer.org/download/){:target="\_blank"} +- [Install Composer](https://getcomposer.org/download/){:target="_blank"} - Obtain [authentication keys]({{page.baseurl}}/install-gde/prereq/connect-auth.html) for the Magento code repository ## Get the metapackage diff --git a/guides/v2.1/install-gde/install/cli/install-cli-install.md b/guides/v2.1/install-gde/install/cli/install-cli-install.md index 38e04143f97..cec1e388cc5 100644 --- a/guides/v2.1/install-gde/install/cli/install-cli-install.md +++ b/guides/v2.1/install-gde/install/cli/install-cli-install.md @@ -77,7 +77,7 @@ Any options that contain spaces or special characters must be enclosed in either | `--admin-password` | Magento administrator user password. The password must be at least 7 characters in length and must include at least one alphabetic and at least one numeric character.

        We recommend a longer, more complex password. Enclose the entire password string in single quotes. For example, `--admin-password='A0b9%t3\'` | Yes | | `--base-url` | Base URL to use to access your Magento Admin and storefront in any of the following formats:

        - `http[s]:////`.

        **Note:** The scheme (http:// or https://) and a trailing slash are both required.

        `` is the docroot-relative path in which to install the Magento software. Depending on how you set up your web server and virtual hosts, the path might be magento2 or it might be blank.

        To access Magento on localhost, you can use either `http://127.0.0.1//` or `http://127.0.0.1//`.

        - `{{base_url}}` which represents a base URL defined by a virtual host setting or by a virtualization environment like Docker. For example, if you set up a virtual host for Magento with the hostname magento.example.com, you can install the Magento software with `--base-url={{base_url}}` and access the Magento Admin with a URL like . | No | | --backend-frontname | Uniform Resource Identifier ([URI](http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.2){:target="_blank"}) to access the Magento Admin or omit this parameter to let Magento generate a random URI for you.

        We recommend a random URI for security purposes. A random URI is harder for hackers or malicious software to exploit.

        The URI displays at the end of the installation. You can display it later at any time using the [magento info:adminuri](<{{ page.baseurl }}/install-gde/install/cli/install-cli-adminurl.html>) command.

        If you choose to enter a value, we recommend you not use a common word like admin, backend, and so on. The Admin URI can contain alphanumeric values and the underscore character (\`_\`) only. | No | -| `--db-host` | Use any of the following:

        - The database server's fully qualified hostname or IP address.

        - `localhost` (default) or `127.0.0.1` if your database server is on the same host as your web server. `localhost` means the MySQL client library uses UNIX sockets to connect to the database. `127.0.0.1` causes the client library to use the TCP protocol. For more information about sockets, see the [PHP PDO_MYSQL documentation](http://php.net/manual/en/ref.pdo-mysql.php){:target="\_blank"}.

        **Note:** You can optionally specify the database server port in its hostname like www.example.com:9000 | No | +| `--db-host` | Use any of the following:

        - The database server's fully qualified hostname or IP address.

        - `localhost` (default) or `127.0.0.1` if your database server is on the same host as your web server. `localhost` means the MySQL client library uses UNIX sockets to connect to the database. `127.0.0.1` causes the client library to use the TCP protocol. For more information about sockets, see the [PHP PDO_MYSQL documentation](http://php.net/manual/en/ref.pdo-mysql.php){:target="_blank"}.

        **Note:** You can optionally specify the database server port in its hostname like www.example.com:9000 | No | | `--db-name` | Name of the Magento database instance in which you want to install the Magento database tables.

        Default is `magento2`. | No | | `--db-user` | Username of the Magento database instance owner.

        Default is `root`. | No | | `--db-password` | Magento database instance owner's password. | No | @@ -89,11 +89,11 @@ Any options that contain spaces or special characters must be enclosed in either | `--use-secure` | `1` enables the use of Secure Sockets Layer (SSL) in storefront URLs. Make sure your web server supports SSL before you select this option.

        `0` disables the use of SSL with Magento. In this case, all other secure URL options are assumed to also be `0`. This is the default. | No | | `--base-url-secure` | Secure base URL to use to access your Magento Admin and storefront in the following format:

        `http[s]:////` | No | | `--use-secure-admin` | 1 means you use SSL to access the Magento Admin. Make sure your web server supports SSL before you select this option.

        `0` means you do not use SSL with the Admin. This is the default. | No | -| `--admin-use-security-key` | `1` causes the Magento software to use a randomly generated key value to access pages in the Magento Admin and in forms. These key values help prevent [cross-site script forgery attacks](https://www.owasp.org/index.php/Cross-Site_Request_Forgery_%28CSRF%29){:target="\_blank"}. This is the default.

        `0` disables the use of the key. | No | +| `--admin-use-security-key` | `1` causes the Magento software to use a randomly generated key value to access pages in the Magento Admin and in forms. These key values help prevent [cross-site script forgery attacks](https://www.owasp.org/index.php/Cross-Site_Request_Forgery_%28CSRF%29){:target="_blank"}. This is the default.

        `0` disables the use of the key. | No | | `--session-save` | Use any of the following:

        - `db` to store session data in the [database](<{{ page.baseurl }}/config-guide/cache/caching-database.html>). Choose database storage if you have a clustered database; otherwise, there might not be much benefit over file-based storage.

        - `files` to store session data in the file system. File-based session storage is appropriate unless the Magento file system access is slow or you have a clustered database. | No | | `--key` | If you have one, specify a key to encrypt [sensitive data](#sens-data) in the Magento database. If you don't have one, Magento generates one for you. | No | | `--cleanup-database` | To drop database tables before installing the Magento software, specify this parameter without a value. Otherwise, the Magento database is left intact. | No | -| `--db-init-statements` | Advanced MySQL configuration parameter. Uses database initialization statements to run when connecting to the MySQL database. Consult a reference similar to [this one](http://dev.mysql.com/doc/refman/5.6/en/server-options.html){:target="\_blank"} before you set any values.

        Default is `SET NAMES utf8;`. | No | +| `--db-init-statements` | Advanced MySQL configuration parameter. Uses database initialization statements to run when connecting to the MySQL database. Consult a reference similar to [this one](http://dev.mysql.com/doc/refman/5.6/en/server-options.html){:target="_blank"} before you set any values.

        Default is `SET NAMES utf8;`. | No | | `--sales-order-increment-prefix` | Specify a string value to use as a prefix for sales orders. Typically, this is used to guarantee unique order numbers for payment processors. | No | | `--amqp-host` | {{site.data.var.ee}} only. Do not use the `--amqp` options unless you have already set up an installation of RabbitMQ. See [RabbitMQ installation](<{{ page.baseurl }}/install-gde/prereq/install-rabbitmq.html>) for more information about installing and configuring RabbitMQ.

        The hostname where RabbitMQ is installed. | No | | `--amqp-port` | {{site.data.var.ee}} only. The port to use to connect to RabbitMQ. The default is `5672`. | No | diff --git a/guides/v2.1/install-gde/prereq/apache.md b/guides/v2.1/install-gde/prereq/apache.md index e76e4e56e25..1ab4dcbae83 100644 --- a/guides/v2.1/install-gde/prereq/apache.md +++ b/guides/v2.1/install-gde/prereq/apache.md @@ -26,7 +26,7 @@ If you're new to all this and need some help getting started, we suggest the fol ## Important: Apache rewrites and .htaccess {#apache-help-rewrite} -This topic discusses how to enable Apache 2.2 rewrites and specify a setting for the [distributed configuration file, `.htaccess`](http://httpd.apache.org/docs/current/howto/htaccess.html){:target="_blank"}. +This topic discusses how to enable Apache 2.2 rewrites and specify a setting for the [distributed configuration file, `.htaccess`](http://httpd.apache.org/docs/current/howto/htaccess.html){:target="_blank"}. Magento uses server rewrites and `.htaccess` to provide directory-level instructions for Apache. The following instructions are included in all of the other sections in this topic as well. @@ -113,7 +113,7 @@ To upgrade to Apache 2.4: apt-get install -y apache2 {:.bs-callout .bs-callout-info} -If the `apt-get install` command fails because of unmet dependencies, consult a resource like [http://askubuntu.com](http://askubuntu.com/questions/140246/how-do-i-resolve-unmet-dependencies-after-adding-a-ppa){:target="_blank"}. +If the `apt-get install` command fails because of unmet dependencies, consult a resource like [http://askubuntu.com](http://askubuntu.com/questions/140246/how-do-i-resolve-unmet-dependencies-after-adding-a-ppa){:target="_blank"}. 3. Verify the installation. @@ -183,7 +183,7 @@ If you encounter 403 Forbidden errors when trying to access the Magento site, yo #### Solving 403 Forbidden errors for Apache 2.4 {#install-apache-403_2.4} -To enable web site visitors to access your site, use one of the [Require directives](http://httpd.apache.org/docs/2.4/howto/access.html){:target="_blank"}. +To enable web site visitors to access your site, use one of the [Require directives](http://httpd.apache.org/docs/2.4/howto/access.html){:target="_blank"}. For example: @@ -195,11 +195,11 @@ For example: {:.bs-callout .bs-callout-info} -The preceding values for `Order` might not work in all cases. For more information, see the [Apache documentation](https://httpd.apache.org/docs/2.4/mod/mod_access_compat.html#order){:target="_blank"}. +The preceding values for `Order` might not work in all cases. For more information, see the [Apache documentation](https://httpd.apache.org/docs/2.4/mod/mod_access_compat.html#order){:target="_blank"}. #### Solving 403 Forbidden errors for Apache 2.2 {#install-apache-403_2.2} -To enable web site visitors to access your site, use the [Allow directive](http://httpd.apache.org/docs/2.2/mod/mod_authz_host.html#allow){:target="_blank"}. +To enable web site visitors to access your site, use the [Allow directive](http://httpd.apache.org/docs/2.2/mod/mod_authz_host.html#allow){:target="_blank"}. For example: @@ -212,7 +212,7 @@ For example:
        {:.bs-callout .bs-callout-info} -The preceding values for `Order` might not work in all cases. For more information, see the [Apache documentation](https://httpd.apache.org/docs/2.2/mod/mod_authz_host.html#order){:target="_blank"}. +The preceding values for `Order` might not work in all cases. For more information, see the [Apache documentation](https://httpd.apache.org/docs/2.2/mod/mod_authz_host.html#order){:target="_blank"}. {% endcollapsible %} #### Related topics: diff --git a/guides/v2.1/install-gde/prereq/dev_install.md b/guides/v2.1/install-gde/prereq/dev_install.md index b6e770dee76..41db2e0e471 100644 --- a/guides/v2.1/install-gde/prereq/dev_install.md +++ b/guides/v2.1/install-gde/prereq/dev_install.md @@ -31,7 +31,7 @@ If you clone the Magento 2 GitHub repository, you _cannot_ use the Magento softw ## Clone the Magento repository {#instgde-prereq-compose-clone} -This section discusses how to get current code by cloning [Magento's GitHub repository](https://github.com/magento/magento2){:target="\_blank"} and checking out branches. You can either checkout a release branch or a development branch: +This section discusses how to get current code by cloning [Magento's GitHub repository](https://github.com/magento/magento2){:target="_blank"} and checking out branches. You can either checkout a release branch or a development branch: * Release branches, like `2.1.0`, are more stable. You _must_ use a release branch with the [Data Migration Tool]({{page.baseurl}}/migration/bk-migration-guide.html). @@ -40,7 +40,7 @@ This section discusses how to get current code by cloning [Magento's GitHub repo Currently, the `2.2-develop` branch is the default, but you can checkout a release branch, like `2.1.0`, after cloning. {:.bs-callout .bs-callout-info} -Refer to [GitHub's documentation](https://help.github.com/articles/cloning-a-repository-from-github/){:target="\_blank"} for instructions on cloning a repository. +Refer to [GitHub's documentation](https://help.github.com/articles/cloning-a-repository-from-github/){:target="_blank"} for instructions on cloning a repository. ### Creating an authorization file {#instgde-prereq-compose-clone-auth} diff --git a/guides/v2.1/install-gde/prereq/install-rabbitmq.md b/guides/v2.1/install-gde/prereq/install-rabbitmq.md index 4a3e80acfcd..5c67e9c843f 100644 --- a/guides/v2.1/install-gde/prereq/install-rabbitmq.md +++ b/guides/v2.1/install-gde/prereq/install-rabbitmq.md @@ -36,10 +36,10 @@ This command also installs the required Erlang packages. If you have an older version of Ubuntu, RabbitMQ recommends installing the package from their {% glossarytooltip a3c8f20f-b067-414e-9781-06378c193155 %}website{% endglossarytooltip %}. -1. Download [rabbitmq-server_3.6.6-1_all.deb](https://www.rabbitmq.com/releases/rabbitmq-server/v3.6.6/rabbitmq-server_3.6.6-1_all.deb){:target="_blank"}. +1. Download [rabbitmq-server_3.6.6-1_all.deb](https://www.rabbitmq.com/releases/rabbitmq-server/v3.6.6/rabbitmq-server_3.6.6-1_all.deb){:target="_blank"}. 2. Install the package with `dpkg`. -Refer to [Installing on Debian/Ubuntu](https://www.rabbitmq.com/install-debian.html){:target="_blank"} for more information. +Refer to [Installing on Debian/Ubuntu](https://www.rabbitmq.com/install-debian.html){:target="_blank"} for more information. ## Install RabbitMQ on CentOS {#centos-install} @@ -47,7 +47,7 @@ Refer to [Installing on Debian/Ubuntu](https://www.rabbitmq.com/install-debian.h RabbitMQ was written using the Erlang programming language, which must be installed on the same system as RabbitMQ. -See [Manual installation](https://www.erlang-solutions.com/resources/download.html){:target="_blank"} for more information. +See [Manual installation](https://www.erlang-solutions.com/resources/download.html){:target="_blank"} for more information. Run the following commands to install this feature. ```bash @@ -61,7 +61,7 @@ rpm -Uvh erlang-solutions-1.0-1.noarch.rpm The RabbitMQ server is included on CentOS, but the version is often old. RabbitMQ recommends installing the package from their website. -1. Download [rabbitmq-server-3.5.6-1.noarch.rpm](https://www.rabbitmq.com/releases/rabbitmq-server/v3.5.6/rabbitmq-server-3.5.6-1.noarch.rpm){:target="_blank"}. +1. Download [rabbitmq-server-3.5.6-1.noarch.rpm](https://www.rabbitmq.com/releases/rabbitmq-server/v3.5.6/rabbitmq-server-3.5.6-1.noarch.rpm){:target="_blank"}. 2. Run the following commands as a user with root permissions: ```bash @@ -71,7 +71,7 @@ rpm --import https://www.rabbitmq.com/rabbitmq-signing-key-public.asc yum install rabbitmq-server-3.5.6-1.noarch.rpm ``` -Refer to [Installing on RPM-based Linux](https://www.rabbitmq.com/install-rpm.html){:target="_blank"} for more information. +Refer to [Installing on RPM-based Linux](https://www.rabbitmq.com/install-rpm.html){:target="_blank"} for more information. ## Configure RabbitMQ {#config} diff --git a/guides/v2.1/install-gde/prereq/mysql.md b/guides/v2.1/install-gde/prereq/mysql.md index ba3542871e9..26ee3c4b430 100644 --- a/guides/v2.1/install-gde/prereq/mysql.md +++ b/guides/v2.1/install-gde/prereq/mysql.md @@ -27,9 +27,9 @@ The Magento application requires MySQL 5.6.x. Magento versions 2.1.2 and later a Magento _strongly_ recommends you observe the following standard when you set up your Magento database: -* Magento uses [MySQL database triggers](http://dev.mysql.com/doc/refman/5.0/en/triggers.html){:target="_blank"} to improve database access during reindexing. Magento does not support any custom triggers in the Magento database because custom triggers can introduce incompatibilities with future Magento versions. -* Familiarize yourself with [these potential MySQL trigger limitations](http://dev.mysql.com/doc/mysql-reslimits-excerpt/5.1/en/stored-program-restrictions.html){:target="_blank"} before you continue. -* If you use MySQL database replication, be aware that Magento does _not_ support MySQL statement-based replication. Make sure you use _only_ [row-based replication](http://dev.mysql.com/doc/refman/5.1/en/replication-formats.html){:target="_blank"}. +* Magento uses [MySQL database triggers](http://dev.mysql.com/doc/refman/5.0/en/triggers.html){:target="_blank"} to improve database access during reindexing. Magento does not support any custom triggers in the Magento database because custom triggers can introduce incompatibilities with future Magento versions. +* Familiarize yourself with [these potential MySQL trigger limitations](http://dev.mysql.com/doc/mysql-reslimits-excerpt/5.1/en/stored-program-restrictions.html){:target="_blank"} before you continue. +* If you use MySQL database replication, be aware that Magento does _not_ support MySQL statement-based replication. Make sure you use _only_ [row-based replication](http://dev.mysql.com/doc/refman/5.1/en/replication-formats.html){:target="_blank"}. {:.bs-callout .bs-callout-info} If your web server and database server are on different hosts, perform the tasks discussed in this topic on the database server host then see [Set up a remote MySQL database connection]({{ page.baseurl }}/install-gde/prereq/mysql_remote.html). @@ -83,7 +83,7 @@ To install MySQL 5.7 on Ubuntu 16: mysql> -5. If you expect to import large numbers of products into Magento, you can increase the value for [`max_allowed_packet`](http://dev.mysql.com/doc/refman/5.6/en/program-variables.html){:target="_blank"} that is larger than the default, 16MB. +5. If you expect to import large numbers of products into Magento, you can increase the value for [`max_allowed_packet`](http://dev.mysql.com/doc/refman/5.6/en/program-variables.html){:target="_blank"} that is larger than the default, 16MB. {% include install/mysql_max-allowed-packet-ubuntu.md %} @@ -125,7 +125,7 @@ To install MySQL 5.6 on Ubuntu 14: mysql> -5. If you expect to import large numbers of products into Magento, you can increase the value for [`max_allowed_packet`](http://dev.mysql.com/doc/refman/5.6/en/program-variables.html){:target="_blank"} that is larger than the default, 16MB. +5. If you expect to import large numbers of products into Magento, you can increase the value for [`max_allowed_packet`](http://dev.mysql.com/doc/refman/5.6/en/program-variables.html){:target="_blank"} that is larger than the default, 16MB. {% include install/mysql_max-allowed-packet-ubuntu.md %} @@ -133,7 +133,7 @@ To install MySQL 5.6 on Ubuntu 14: ### Installing MySQL 5.6 on Ubuntu 12 {#instgde-prereq-mysql56ubu12} -To install MySQL 5.6 on Ubuntu 12, use the following instructions from [askubuntu.com](http://askubuntu.com/questions/433014/unable-to-install-mysql-5-6-in-ubuntu-12-04){:target="_blank"}. +To install MySQL 5.6 on Ubuntu 12, use the following instructions from [askubuntu.com](http://askubuntu.com/questions/433014/unable-to-install-mysql-5-6-in-ubuntu-12-04){:target="_blank"}. 1. Enter the following commands in the order shown: @@ -170,7 +170,7 @@ To install MySQL 5.6 on Ubuntu 12, use the following instructions from [askubunt mysql> -5. If you expect to import large numbers of products into Magento, you can increase the value for [`max_allowed_packet`](http://dev.mysql.com/doc/refman/5.6/en/program-variables.html){:target="_blank"} that is larger than the default, 16MB. +5. If you expect to import large numbers of products into Magento, you can increase the value for [`max_allowed_packet`](http://dev.mysql.com/doc/refman/5.6/en/program-variables.html){:target="_blank"} that is larger than the default, 16MB. {% include install/mysql_max-allowed-packet-ubuntu.md %} @@ -185,7 +185,7 @@ The Magento application 2.1.2 and later are compatible with MySQL 5.7. ### Get MySQL 5.7 for CentOS 7 -The following procedure is based on [How to Install Latest MySQL 5.7.9 on RHEL/CentOS 7/6/5 and Fedora 23/22/21](http://www.tecmint.com/install-latest-mysql-on-rhel-centos-and-fedora){:target="_blank"}. +The following procedure is based on [How to Install Latest MySQL 5.7.9 on RHEL/CentOS 7/6/5 and Fedora 23/22/21](http://www.tecmint.com/install-latest-mysql-on-rhel-centos-and-fedora){:target="_blank"}. As a user with `root` privileges, enter the following commands in the order shown: @@ -196,7 +196,7 @@ Continue with [Install and configure MySQL 5.7 on CentOS 6 or 7](#mysql57-centos ### Get MySQL 5.7 for CentOS 6 -The following procedure is based on [How to Install Latest MySQL 5.7.9 on RHEL/CentOS 7/6/5 and Fedora 23/22/21](http://www.tecmint.com/install-latest-mysql-on-rhel-centos-and-fedora){:target="_blank"}. +The following procedure is based on [How to Install Latest MySQL 5.7.9 on RHEL/CentOS 7/6/5 and Fedora 23/22/21](http://www.tecmint.com/install-latest-mysql-on-rhel-centos-and-fedora){:target="_blank"}. As a user with `root` privileges, enter the following commands in the order shown: @@ -232,7 +232,7 @@ Continue with the next section. ## Installing and configuring MySQL 5.6 on CentOS {#instgde-prereq-mysql-centos} -The following procedure is based on [Install MySQL Server 5.6 in CentOS 6.x and Red Hat 6.x Linux](http://sharadchhetri.com/2013/12/26/install-mysql-server-5-6-in-centos-6-x-and-red-hat-6-x-linux/){:target="_blank"}. +The following procedure is based on [Install MySQL Server 5.6 in CentOS 6.x and Red Hat 6.x Linux](http://sharadchhetri.com/2013/12/26/install-mysql-server-5-6-in-centos-6-x-and-red-hat-6-x-linux/){:target="_blank"}. 1. *CentOS 6* Install the MySQL database: @@ -273,7 +273,7 @@ The following procedure is based on [Install MySQL Server 5.6 in CentOS 6.x and Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. -5. If you expect to import large numbers of products into Magento, you can configure MySQL to use the [`max_allowed_packet`](http://dev.mysql.com/doc/refman/5.6/en/program-variables.html){:target="_blank"} parameter. We recommend a value of at least 16MB. +5. If you expect to import large numbers of products into Magento, you can configure MySQL to use the [`max_allowed_packet`](http://dev.mysql.com/doc/refman/5.6/en/program-variables.html){:target="_blank"} parameter. We recommend a value of at least 16MB. {% include install/mysql_max-allowed-packet-centos.md %} diff --git a/guides/v2.1/install-gde/prereq/nginx.md b/guides/v2.1/install-gde/prereq/nginx.md index 8dd58a0e2d7..95dc9e039fd 100644 --- a/guides/v2.1/install-gde/prereq/nginx.md +++ b/guides/v2.1/install-gde/prereq/nginx.md @@ -10,7 +10,7 @@ functional_areas: - Setup --- -Magento supports nginx 1.8 (or the [latest mainline version](http://nginx.org/en/linux_packages.html#mainline){:target="_blank}). You must also install the latest version of `php-fpm`. +Magento supports nginx 1.8 (or the [latest mainline version](http://nginx.org/en/linux_packages.html#mainline){:target="_blank}). You must also install the latest version of `php-fpm`. Installation instructions vary based on which operating system you're using: diff --git a/guides/v2.1/install-gde/prereq/optional.md b/guides/v2.1/install-gde/prereq/optional.md index 028bb0eb48b..bc15925cef5 100644 --- a/guides/v2.1/install-gde/prereq/optional.md +++ b/guides/v2.1/install-gde/prereq/optional.md @@ -18,7 +18,7 @@ We strongly recommend you install NTP because otherwise, cron-related tasks migh The other optional utilities discussed in this topic might assist you with your installation; however, they are not required to install or use Magento. ## Installing and Configuring Network Time Protocol (NTP) {#install-optional-ntp} -[NTP](http://www.ntp.org) enables servers to synchronize their system clocks using [globally available pool servers](http://www.pool.ntp.org/en){:target="_blank"}. Magento recommends you use NTP servers you trust, whether they are dedicated hardware solutions your internal network or external, public servers. +[NTP](http://www.ntp.org) enables servers to synchronize their system clocks using [globally available pool servers](http://www.pool.ntp.org/en){:target="_blank"}. Magento recommends you use NTP servers you trust, whether they are dedicated hardware solutions your internal network or external, public servers. If you are deploying Magento on multiple hosts, NTP is a simple way to guarantee their clocks are all synchronized, no matter what time zone the servers are in. Also, cron-related tasks (such as indexing and transactional e-mails) depend on the server clock being accurate. @@ -58,7 +58,7 @@ To install and configure NTP: ### Use NTP pool servers {#install-optional-ntp-servers} -Selecting pool servers is up to you. If you use NTP pool servers, ntp.org recommends you use [pool servers](http://www.pool.ntp.org/en){:target="_blank"} that are close to your servers' time zone as discussed on the [NTP pool project help page](http://www.pool.ntp.org/en/use.html){:target="_blank"}. If you have a private NTP server that is available to all hosts in your Magento deployment, you can use that server instead. +Selecting pool servers is up to you. If you use NTP pool servers, ntp.org recommends you use [pool servers](http://www.pool.ntp.org/en){:target="_blank"} that are close to your servers' time zone as discussed on the [NTP pool project help page](http://www.pool.ntp.org/en/use.html){:target="_blank"}. If you have a private NTP server that is available to all hosts in your Magento deployment, you can use that server instead. 1. Open `/etc/ntp.conf` in a text editor. @@ -93,7 +93,7 @@ Selecting pool servers is up to you. If you use NTP pool servers, ntp.org recomm If all else fails, try rebooting the server. ## Create phpinfo.php {#install-optional-phpinfo} -[`phpinfo.php`](http://php.net/manual/en/function.phpinfo.php){:target="_blank"} displays a large amount of information about {% glossarytooltip bf703ab1-ca4b-48f9-b2b7-16a81fd46e02 %}PHP{% endglossarytooltip %} and its extensions. +[`phpinfo.php`](http://php.net/manual/en/function.phpinfo.php){:target="_blank"} displays a large amount of information about {% glossarytooltip bf703ab1-ca4b-48f9-b2b7-16a81fd46e02 %}PHP{% endglossarytooltip %} and its extensions. {:.bs-callout .bs-callout-info} Use `phpinfo.php` in a development system _only_. It can be a security issue in production. @@ -104,7 +104,7 @@ Add the following code anywhere in your web server's docroot: // Show all information, defaults to INFO_ALL phpinfo(); -For more information, see the [phpinfo manual page](http://php.net/manual/en/function.phpinfo.php){:target="_blank"}. +For more information, see the [phpinfo manual page](http://php.net/manual/en/function.phpinfo.php){:target="_blank"}. To view the results, enter the following {% glossarytooltip a05c59d3-77b9-47d0-92a1-2cbffe3f8622 %}URL{% endglossarytooltip %} in your browser's location or address field: @@ -115,16 +115,16 @@ If a 404 (Not Found) error displays, check the following: * Start the web server if necessary. * Make sure your firewall allows traffic on port 80. - [Help for Ubuntu](https://help.ubuntu.com/community/UFW){:target="_blank"} + [Help for Ubuntu](https://help.ubuntu.com/community/UFW){:target="_blank"} - [Help for CentOS](http://wiki.centos.org/HowTos/Network/IPTables){:target="_blank"} + [Help for CentOS](http://wiki.centos.org/HowTos/Network/IPTables){:target="_blank"} ## Install phpmyadmin {#install-optional-phpmyadmin} `phpmyadmin` is an easy-to-use, free database administration utility. You can use it to check and manipulate the contents of your database. You must log in to `phpmyadmin` as the MySQL database administrative user. -For more information about `phpmyadmin`, see the [phpmyadmin home page](http://www.phpmyadmin.net/home_page/index.php){:target="_blank"}. +For more information about `phpmyadmin`, see the [phpmyadmin home page](http://www.phpmyadmin.net/home_page/index.php){:target="_blank"}. -For more detailed information about installation, see the [phpmyadmin installation documentation](http://docs.phpmyadmin.net/en/latest/setup.html#quick-install){:target="_blank"}. +For more detailed information about installation, see the [phpmyadmin installation documentation](http://docs.phpmyadmin.net/en/latest/setup.html#quick-install){:target="_blank"}. {:.bs-callout .bs-callout-info} Use phpmyadmin in a development system _only_. It can be a security issue in production. diff --git a/guides/v2.1/install-gde/prereq/php-centos.md b/guides/v2.1/install-gde/prereq/php-centos.md index ab30a54a907..354b615f2ee 100644 --- a/guides/v2.1/install-gde/prereq/php-centos.md +++ b/guides/v2.1/install-gde/prereq/php-centos.md @@ -40,13 +40,13 @@ To verify if PHP is installed already, enter `php -v`. If {% glossarytooltip bf7 with Zend OPcache v7.0.4-dev, Copyright (c) 1999-2014, by Zend Technologies {:.bs-callout .bs-callout-info} -The preceding message confirms that the `Zend OPcache` is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}. +The preceding message confirms that the `Zend OPcache` is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}. If PHP is installed, continue with the next prerequisite, [MySQL]({{ page.baseurl }}/install-gde/prereq/mysql.html). ## CentOS repositories {#centos-php-repos} -Linux systems provide software like PHP in one or more *repositories*. CentOS, unlike Ubuntu, has a set of [officially recommended repositories](https://wiki.centos.org/AdditionalResources/Repositories){:target="_blank"}. Other repositories are considered less safe for the reasons stated on the CentOS wiki. +Linux systems provide software like PHP in one or more *repositories*. CentOS, unlike Ubuntu, has a set of [officially recommended repositories](https://wiki.centos.org/AdditionalResources/Repositories){:target="_blank"}. Other repositories are considered less safe for the reasons stated on the CentOS wiki. We're not aware that you can install PHP 5.6 or 7.0 from a CentOS-recommended repository. Therefore, you must consider the following: @@ -55,9 +55,9 @@ We're not aware that you can install PHP 5.6 or 7.0 from a CentOS-recommended re You should also consider upgrading to a later version of CentOS that has the desired PHP version in a recommended repository. * If you're setting up a development system, you can use any repository you wish. -In this topic, we show how to install PHP using the [Inline with Upstream Stable (IUS)](https://ius.io/GettingStarted){:target="_blank"} repository, which is *not* on the CentOS recommended list. However, packages installed from IUS do not use the same names as CentOS-provided packages, so [no existing system packages are replaced](https://ius.io/Philosophy){:target="_blank"}. +In this topic, we show how to install PHP using the [Inline with Upstream Stable (IUS)](https://ius.io/GettingStarted){:target="_blank"} repository, which is *not* on the CentOS recommended list. However, packages installed from IUS do not use the same names as CentOS-provided packages, so [no existing system packages are replaced](https://ius.io/Philosophy){:target="_blank"}. -Before you continue, review their [Getting Started topic](https://ius.io/GettingStarted){:target="_blank"}. +Before you continue, review their [Getting Started topic](https://ius.io/GettingStarted){:target="_blank"}. {:.bs-callout .bs-callout-info} Magento does _not_ officially recommend using the IUS repository. We discuss it here for example purposes only. @@ -106,7 +106,7 @@ There is more than one way to install PHP 7.0 on CentOS; the following is a sugg with Zend OPcache v7.0.6-dev, Copyright (c) 1999-2016, by Zend Technologies {:.bs-callout .bs-callout-info} - The preceding message confirms that the `Zend OPcache` is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}. + The preceding message confirms that the `Zend OPcache` is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}. 3. Continue with [Required PHP settings]({{ page.baseurl }}/install-gde/prereq/php-settings.html). {% endcollapsible %} @@ -159,7 +159,7 @@ There is more than one way to install PHP 5.6 on CentOS; the following is a sugg with Zend OPcache v7.0.6-dev, Copyright (c) 1999-2016, by Zend Technologies {:.bs-callout .bs-callout-info} - The preceding message confirms that the `Zend OPcache` is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}. + The preceding message confirms that the `Zend OPcache` is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}. 3. Continue with [Required PHP settings]({{ page.baseurl }}/install-gde/prereq/php-settings.html). {% endcollapsible %} diff --git a/guides/v2.1/install-gde/prereq/php-settings.md b/guides/v2.1/install-gde/prereq/php-settings.md index 21d54b494f4..8ac353d039b 100644 --- a/guides/v2.1/install-gde/prereq/php-settings.md +++ b/guides/v2.1/install-gde/prereq/php-settings.md @@ -19,7 +19,7 @@ This topic discusses how to set required {% glossarytooltip bf703ab1-ca4b-48f9-b * Set the system time zone for PHP; otherwise, errors like the following display during the installation and time-related operations like cron might not work: PHP Warning: date(): It is not safe to rely on the system's timezone settings. [more messages follow] -* Set [`always_populate_raw_post_data = -1`](http://php.net/manual/en/ini.core.php#ini.always-populate-raw-post-data){:target="_blank"} +* Set [`always_populate_raw_post_data = -1`](http://php.net/manual/en/ini.core.php#ini.always-populate-raw-post-data){:target="_blank"} `always_populate_raw_post_data` is deprecated in PHP 5.6 and is dropped in PHP 7.0.x. This setting causes PHP to always populate `$HTTP_RAW_POST_DATA` with raw POST data. Failure to set this properly in PHP 5.5 or 5.6 results in errors when connecting to the database. * Set the PHP memory limit. @@ -29,16 +29,16 @@ This topic discusses how to set required {% glossarytooltip bf703ab1-ca4b-48f9-b * Compiling code or deploying static assets, `756M` * Installing and updating Magento components from Magento Marketplace, `2G` * Testing, `2G` -* Disable [`asp_tags`](http://php.net/manual/en/ini.core.php#ini.asp-tags){:target="_blank"} +* Disable [`asp_tags`](http://php.net/manual/en/ini.core.php#ini.asp-tags){:target="_blank"} If `asp_tags are` enabled, errors display when accessing PHTML templates. `asp_tags` will be removed in PHP 7. -* Enable [`opcache.save_comments`](http://php.net/manual/en/opcache.configuration.php#ini.opcache.save_comments){:target="_blank"}, which is required for Magento 2.1 and later. +* Enable [`opcache.save_comments`](http://php.net/manual/en/opcache.configuration.php#ini.opcache.save_comments){:target="_blank"}, which is required for Magento 2.1 and later. - We recommend you enable the [PHP OpCache](http://php.net/manual/en/intro.opcache.php){:target="_blank"} for performance reasons. The OPcache is enabled in many PHP distributions. + We recommend you enable the [PHP OpCache](http://php.net/manual/en/intro.opcache.php){:target="_blank"} for performance reasons. The OPcache is enabled in many PHP distributions. - Magento 2.1 and later use PHP code comments in the `getDocComment` validation call in the [`getExtensionAttributes`]({{ site.mage2100url }}lib/internal/Magento/Framework/Api/ExtensionAttributesFactory.php#L64-L73){:target="_blank"} method in `Magento\Framework\Api\ExtensionAttributesFactory.php`. + Magento 2.1 and later use PHP code comments in the `getDocComment` validation call in the [`getExtensionAttributes`]({{ site.mage2100url }}lib/internal/Magento/Framework/Api/ExtensionAttributesFactory.php#L64-L73){:target="_blank"} method in `Magento\Framework\Api\ExtensionAttributesFactory.php`. {:.bs-callout .bs-callout-info} To avoid issues during installation and upgrade, we strongly recommend you apply the same PHP settings to both the PHP command-line configuration and to the PHP web server plug-in's configuration. For more information, see the next section. @@ -92,7 +92,7 @@ If you have more than one `opcache.ini`, modify all of them. {% collapsible To set PHP options: %} 1. Open a `php.ini` in a text editor. -3. Locate your server's time zone in the available [time zone settings](http://php.net/manual/en/timezones.php){:target="_blank"} +3. Locate your server's time zone in the available [time zone settings](http://php.net/manual/en/timezones.php){:target="_blank"} 4. Locate the following setting and uncomment it if necessary: date.timezone = diff --git a/guides/v2.1/install-gde/prereq/php-ubuntu.md b/guides/v2.1/install-gde/prereq/php-ubuntu.md index e9cd4037312..c9239be1f4c 100644 --- a/guides/v2.1/install-gde/prereq/php-ubuntu.md +++ b/guides/v2.1/install-gde/prereq/php-ubuntu.md @@ -40,7 +40,7 @@ To verify if PHP is installed already, enter `php -v`. If PHP is installed, mess with Zend OPcache v7.0.4-dev, Copyright (c) 1999-2014, by Zend Technologies {:.bs-callout .bs-callout-info} -The preceding message confirms that the `Zend OPcache` is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}. +The preceding message confirms that the `Zend OPcache` is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}. If PHP is installed, continue with the next prerequisite, [MySQL]({{ page.baseurl }}/install-gde/prereq/mysql.html). @@ -75,7 +75,7 @@ If PHP is *not* installed, see one of the following sections: with Zend OPcache v7.0.8-2+deb.sury.org~trusty+1, Copyright (c) 1999-2016, by Zend Technologies {:.bs-callout .bs-callout-info} - The preceding message confirms that the `Zend OPcache` is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}. + The preceding message confirms that the `Zend OPcache` is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}. 3. Continue with [Required PHP settings]({{ page.baseurl }}/install-gde/prereq/php-settings.html). @@ -104,7 +104,7 @@ If PHP is *not* installed, see one of the following sections: with Zend OPcache v7.0.6-dev, Copyright (c) 1999-2016, by Zend Technologies {:.bs-callout .bs-callout-info} - The preceding message confirms that the `Zend OPcache` is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}. + The preceding message confirms that the `Zend OPcache` is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}. 3. Continue with [Required PHP settings]({{ page.baseurl }}/install-gde/prereq/php-settings.html). diff --git a/guides/v2.1/install-gde/prereq/prereq-overview.md b/guides/v2.1/install-gde/prereq/prereq-overview.md index 9ac24b633ab..6675fcc241b 100644 --- a/guides/v2.1/install-gde/prereq/prereq-overview.md +++ b/guides/v2.1/install-gde/prereq/prereq-overview.md @@ -20,7 +20,7 @@ Before you install Magento, you must do all of the following: * Make sure you can back up your entire system at various points during the installation so you can roll back in the {% glossarytooltip c57aef7c-97b4-4b2b-a999-8001accef1fe %}event{% endglossarytooltip %} of issues. {:.bs-callout .bs-callout-info} -We assume you're installing the Magento 2 software in a _development environment_, which means you have [root user](http://www.linfo.org/root.html){:target="_blank"} access to the machine _and_ that the machine does not need to be highly secure. If you're setting up a more secure machine, we strongly recommend you consult a network administrator for additional assistance. +We assume you're installing the Magento 2 software in a _development environment_, which means you have [root user](http://www.linfo.org/root.html){:target="_blank"} access to the machine _and_ that the machine does not need to be highly secure. If you're setting up a more secure machine, we strongly recommend you consult a network administrator for additional assistance. We strongly recommend you update and upgrade your operating system software. These upgrades can provide security and software fixes that might prevent future problems. diff --git a/guides/v2.1/install-gde/system-requirements-tech.md b/guides/v2.1/install-gde/system-requirements-tech.md index 1b3a8724ef3..e68542ed9f6 100644 --- a/guides/v2.1/install-gde/system-requirements-tech.md +++ b/guides/v2.1/install-gde/system-requirements-tech.md @@ -25,10 +25,10 @@ Upgrading the Magento applications and extensions you obtain from Magento Market ### Web servers -* [Apache 2.2 or 2.4](http://httpd.apache.org/download.cgi){:target="_blank"} +* [Apache 2.2 or 2.4](http://httpd.apache.org/download.cgi){:target="_blank"} In addition, the apache `mod_rewrite` module must be enabled. `mod_rewrite` enables the server to perform URL rewriting. For more information, see [our Apache documentation]({{ page.baseurl }}/install-gde/prereq/apache.html). -* {% glossarytooltip b14ef3d8-51fd-48fe-94df-ed069afb2cdc %}nginx{% endglossarytooltip %} 1.8 (or [latest mainline version](http://nginx.org/en/linux_packages.html#mainline){:target="_blank"}) +* {% glossarytooltip b14ef3d8-51fd-48fe-94df-ed069afb2cdc %}nginx{% endglossarytooltip %} 1.8 (or [latest mainline version](http://nginx.org/en/linux_packages.html#mainline){:target="_blank"}) ### Database @@ -42,24 +42,24 @@ MariaDB and Percona are compatible with Magento because we support MySQL 5.6 API {% include install/php_2.1.md %} -PHP documentation: [CentOS]({{ page.baseurl }}/install-gde/prereq/php-centos.html){:target="_blank"}, [Ubuntu]({{ page.baseurl }}/install-gde/prereq/php-ubuntu.html){:target="_blank"} +PHP documentation: [CentOS]({{ page.baseurl }}/install-gde/prereq/php-centos.html){:target="_blank"}, [Ubuntu]({{ page.baseurl }}/install-gde/prereq/php-ubuntu.html){:target="_blank"} #### Required PHP extensions: -* [bc-math](http://php.net/manual/en/book.bc.php){:target="_blank"} ({{site.data.var.ee}} only) -* [curl](http://php.net/manual/en/book.curl.php){:target="_blank"} -* [gd](http://php.net/manual/en/book.image.php){:target="_blank"}, [ImageMagick 6.3.7](http://php.net/manual/en/book.imagick.php){:target="_blank"} (or later) or both -* [intl](http://php.net/manual/en/book.intl.php){:target="_blank"} -* [mbstring](http://php.net/manual/en/book.mbstring.php){:target="_blank"} -* [mcrypt](http://php.net/manual/en/book.mcrypt.php){:target="_blank"} -* [hash](http://php.net/manual/en/book.hash.php){:target="_blank"} -* [openssl](http://php.net/manual/en/book.openssl.php){:target="_blank"} -* [PDO/MySQL](http://php.net/manual/en/ref.pdo-mysql.php){:target="_blank"} -* [SimpleXML](http://php.net/manual/en/book.simplexml.php){:target="_blank"} -* [soap](http://php.net/manual/en/book.soap.php){:target="_blank"} -* [xml](http://php.net/manual/en/book.xml.php){:target="_blank"} -* [xsl](http://php.net/manual/en/book.xsl.php){:target="_blank"} -* [zip](http://php.net/manual/en/book.zip.php){:target="_blank"} +* [bc-math](http://php.net/manual/en/book.bc.php){:target="_blank"} ({{site.data.var.ee}} only) +* [curl](http://php.net/manual/en/book.curl.php){:target="_blank"} +* [gd](http://php.net/manual/en/book.image.php){:target="_blank"}, [ImageMagick 6.3.7](http://php.net/manual/en/book.imagick.php){:target="_blank"} (or later) or both +* [intl](http://php.net/manual/en/book.intl.php){:target="_blank"} +* [mbstring](http://php.net/manual/en/book.mbstring.php){:target="_blank"} +* [mcrypt](http://php.net/manual/en/book.mcrypt.php){:target="_blank"} +* [hash](http://php.net/manual/en/book.hash.php){:target="_blank"} +* [openssl](http://php.net/manual/en/book.openssl.php){:target="_blank"} +* [PDO/MySQL](http://php.net/manual/en/ref.pdo-mysql.php){:target="_blank"} +* [SimpleXML](http://php.net/manual/en/book.simplexml.php){:target="_blank"} +* [soap](http://php.net/manual/en/book.soap.php){:target="_blank"} +* [xml](http://php.net/manual/en/book.xml.php){:target="_blank"} +* [xsl](http://php.net/manual/en/book.xsl.php){:target="_blank"} +* [zip](http://php.net/manual/en/book.zip.php){:target="_blank"} * {% glossarytooltip bf703ab1-ca4b-48f9-b2b7-16a81fd46e02 %}PHP{% endglossarytooltip %} 7 only: * [json](http://php.net/manual/en/book.json.php){:target="_blank"} @@ -67,9 +67,9 @@ PHP documentation: [CentOS]({{ page.baseurl }}/install-gde/prereq/php-centos.htm #### PHP OPcache -We strongly recommend you verify the [PHP OPcache](http://php.net/manual/en/intro.opcache.php){:target="_blank"} is enabled for performance reasons. The OPcache is enabled in many PHP distributions. To verify if it is installed, see our PHP documentation for [CentOS]({{ page.baseurl }}/install-gde/prereq/php-centos.html){:target="_blank"} or [Ubuntu]({{ page.baseurl }}/install-gde/prereq/php-ubuntu.html){:target="_blank"}. +We strongly recommend you verify the [PHP OPcache](http://php.net/manual/en/intro.opcache.php){:target="_blank"} is enabled for performance reasons. The OPcache is enabled in many PHP distributions. To verify if it is installed, see our PHP documentation for [CentOS]({{ page.baseurl }}/install-gde/prereq/php-centos.html){:target="_blank"} or [Ubuntu]({{ page.baseurl }}/install-gde/prereq/php-ubuntu.html){:target="_blank"}. -If you must install it separately, see the [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}. +If you must install it separately, see the [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}. #### PHP settings @@ -119,7 +119,7 @@ Mail Transfer Agent (MTA) or an SMTP server ### Optional but recommended: -* [php_xdebug2.2.0](http://xdebug.org/download.php){:target="_blank"} or later (development environments only; can have an adverse effect on performance) +* [php_xdebug2.2.0](http://xdebug.org/download.php){:target="_blank"} or later (development environments only; can have an adverse effect on performance) {:.bs-callout .bs-callout-info} There is a known issue with xdebug that can affect Magento installations or access to the storefront or Magento Admin after installation. diff --git a/guides/v2.1/install-gde/tutorials/change-docroot-to-pub.md b/guides/v2.1/install-gde/tutorials/change-docroot-to-pub.md index 1b0a019bd82..057b69f27b9 100644 --- a/guides/v2.1/install-gde/tutorials/change-docroot-to-pub.md +++ b/guides/v2.1/install-gde/tutorials/change-docroot-to-pub.md @@ -12,7 +12,7 @@ If you're accustomed to using the Web Setup Wizard during development, be aware
        -If you're using [nginx]({{ page.baseurl }}/install-gde/prereq/nginx.html) and the [`nginx.conf.sample`]({{ site.mage2200url }}nginx.conf.sample){:target="\_blank"} file included in the Magento installation directory, you're probably already serving files from the `pub/` directory. +If you're using [nginx]({{ page.baseurl }}/install-gde/prereq/nginx.html) and the [`nginx.conf.sample`]({{ site.mage2200url }}nginx.conf.sample){:target="_blank"} file included in the Magento installation directory, you're probably already serving files from the `pub/` directory. The sample configuration overrides your server's docroot settings to serve files from Magento's `pub/` directory; assuming you've referenced the `nginx.conf.sample` in the server block that defines your site. For example, see the last line in the following configuration: @@ -34,7 +34,7 @@ The sample configuration overrides your server's docroot settings to serve files ## Before you begin -To complete this tutorial, you'll need access to a working Magento installation running on a [LAMP](https://en.wikipedia.org/wiki/LAMP_(software_bundle)){:target="\_blank"} stack: +To complete this tutorial, you'll need access to a working Magento installation running on a [LAMP](https://en.wikipedia.org/wiki/LAMP_(software_bundle)){:target="_blank"} stack: - Linux - Apache (2.2+) diff --git a/guides/v2.1/migration/migration-tool-internal-spec.md b/guides/v2.1/migration/migration-tool-internal-spec.md index c9f254cc79e..e4911b76b25 100644 --- a/guides/v2.1/migration/migration-tool-internal-spec.md +++ b/guides/v2.1/migration/migration-tool-internal-spec.md @@ -16,11 +16,11 @@ This section describes an implementation details of Data Migration Tool and how ### Repositories {#repositories} -Data Migration Tool repository [migration-tool](https://github.com/magento/data-migration-tool){:target="_blank"} +Data Migration Tool repository [migration-tool](https://github.com/magento/data-migration-tool){:target="_blank"} ### System requirements {#system-requirements} -Same as for [Magento 2]({{ site.baseurl }}/guides/v1.0/install-gde/system-requirements.html){:target="_blank"} +Same as for [Magento 2]({{ site.baseurl }}/guides/v1.0/install-gde/system-requirements.html){:target="_blank"} ## Internal structure {#migrate-is} diff --git a/guides/v2.1/migration/migration-troubleshooting.md b/guides/v2.1/migration/migration-troubleshooting.md index 224508e4a89..08e40ce20d9 100644 --- a/guides/v2.1/migration/migration-troubleshooting.md +++ b/guides/v2.1/migration/migration-troubleshooting.md @@ -33,7 +33,7 @@ This message appears because the Data Migration Tool runs internal tests to veri #### Possible solutions -* Install the corresponding Magento 2 extensions from [Magento Marketplace](https://marketplace.magento.com/){:target:"_blank"} +* Install the corresponding Magento 2 extensions from [Magento Marketplace](https://marketplace.magento.com/){:target:"_blank"} If the conflicting data originates from an extension which adds own database structure elements, then the Magento 2 version of the same extension may add such elements to the destination (Magento 2) database, thus fixing the issue. diff --git a/guides/v2.1/mtf/mtf_entities/mtf_block.md b/guides/v2.1/mtf/mtf_entities/mtf_block.md index 5f1c81cac9a..b788ee7d7bc 100644 --- a/guides/v2.1/mtf/mtf_entities/mtf_block.md +++ b/guides/v2.1/mtf/mtf_entities/mtf_block.md @@ -18,7 +18,7 @@ This topic shows how to create a new block and explore its structure. It discuss ## Example {#mtf_block_class} -A block `Magento\Ui\Test\Block\Messages` extends a basic block [`Magento\Mtf\Block\Block`]{:target=_blank} and implements methods to interact with messages. +A block `Magento\Ui\Test\Block\Messages` extends a basic block [`Magento\Mtf\Block\Block`]{:target="_blank"} and implements methods to interact with messages. {% collapsible Show/hide the code %} ```php?start_inline=1 @@ -190,16 +190,16 @@ class Messages extends Block Magento contains basic blocks for the functional testing with a logic that you can reuse. The most popular are the following: -* [`Magento\Mtf\Block\Block`]{:target=_blank} -* [`Magento\Mtf\Block\Form`]{:target=_blank} -* [`Magento\Backend\Test\Block\Widget\Tab`]{:target=_blank} -* [`Magento\Backend\Test\Block\Widget\FormTabs`]{:target=_blank} -* [`Magento\Backend\Test\Block\Widget\Grid`]{:target=_blank} -* [`Magento\Ui\Test\Block\Adminhtml\DataGrid`]{:target=_blank} +* [`Magento\Mtf\Block\Block`]{:target="_blank"} +* [`Magento\Mtf\Block\Form`]{:target="_blank"} +* [`Magento\Backend\Test\Block\Widget\Tab`]{:target="_blank"} +* [`Magento\Backend\Test\Block\Widget\FormTabs`]{:target="_blank"} +* [`Magento\Backend\Test\Block\Widget\Grid`]{:target="_blank"} +* [`Magento\Ui\Test\Block\Adminhtml\DataGrid`]{:target="_blank"} ## Block identifier {#mtf_block_identifier} -Each block has an identifier that includes selector and searching strategy. This identifier is determined by the [`Magento\Mtf\Client\Element\Locator`]{:target=_blank} class and is stored in the `_rootElement` property of the [`Magento\Mtf\Block\Block`]{:target=_blank} class. +Each block has an identifier that includes selector and searching strategy. This identifier is determined by the [`Magento\Mtf\Client\Element\Locator`]{:target="_blank"} class and is stored in the `_rootElement` property of the [`Magento\Mtf\Block\Block`]{:target="_blank"} class. You can use the `_rootElement` to find an element in the current block. diff --git a/guides/v2.1/pattern-library/general/accessibilityguideline/accessibilityGuideline.md b/guides/v2.1/pattern-library/general/accessibilityguideline/accessibilityGuideline.md index 756f4ae17fe..800b39d41f8 100644 --- a/guides/v2.1/pattern-library/general/accessibilityguideline/accessibilityGuideline.md +++ b/guides/v2.1/pattern-library/general/accessibilityguideline/accessibilityGuideline.md @@ -14,9 +14,9 @@ Don't make textual content too long or too short. #### Provide adequate contrast Be extra careful with light shades of gray, orange, and yellow. Check your contrast levels here: -[http://webaim.org/resources/contrastchecker/](http://webaim.org/resources/contrastchecker/){:target=_"blank"} +[http://webaim.org/resources/contrastchecker/](http://webaim.org/resources/contrastchecker/){:target="_blank"} or here: -[http://www.paciellogroup.com/resources/contrastAnalyser](http://www.paciellogroup.com/resources/contrastAnalyser){:target=_"blank"} +[http://www.paciellogroup.com/resources/contrastAnalyser](http://www.paciellogroup.com/resources/contrastAnalyser){:target="_blank"} Acceptable @@ -50,11 +50,11 @@ A link for keyboard users to skip navigation should be at the top of the page. I Examples: -* [http://www.nomensa.com/](http://www.nomensa.com/){:target=_"blank"} -* [https://www.paypal.com/](https://www.paypal.com/){:target=_"blank"} -* [http://www.standardchartered.com/en/](http://www.standardchartered.com/en/){:target=_"blank"} -* [http://nemesisdesign.net/blog/accessibility/nice-css-skip-links-appearing-focus/](http://nemesisdesign.net/blog/accessibility/nice-css-skip-links-appearing-focus/){:target=_"blank"} -* [Skip-To Widget](https://github.com/paypal/skipto){:target=_"blank"} +* [http://www.nomensa.com/](http://www.nomensa.com/){:target="_blank"} +* [https://www.paypal.com/](https://www.paypal.com/){:target="_blank"} +* [http://www.standardchartered.com/en/](http://www.standardchartered.com/en/){:target="_blank"} +* [http://nemesisdesign.net/blog/accessibility/nice-css-skip-links-appearing-focus/](http://nemesisdesign.net/blog/accessibility/nice-css-skip-links-appearing-focus/){:target="_blank"} +* [Skip-To Widget](https://github.com/paypal/skipto){:target="_blank"} #### Use animation, video and audio with caution @@ -136,6 +136,6 @@ Cascading style sheets (CSS) for purely decorative images. Hyperlinked images wi ## Resources -* Overview: [http://www.w3.org/WAI/WCAG20/glance/](http://www.w3.org/WAI/WCAG20/glance/){:target=_"blank"} -* Authoring Tool Accessibility Guidelines (ATAG) 1.0: [http://www.w3.org/TR/WCAG10-HTML-TECHS/](http://www.w3.org/TR/WCAG10-HTML-TECHS/){:target=_"blank"} -* Authoring Tool Accessibility Guidelines (ATAG) 2.0: [http://www.w3.org/TR/WCAG20-HTML-TECHS/](http://www.w3.org/TR/WCAG20-HTML-TECHS/){:target=_"blank"} +* Overview: [http://www.w3.org/WAI/WCAG20/glance/](http://www.w3.org/WAI/WCAG20/glance/){:target="_blank"} +* Authoring Tool Accessibility Guidelines (ATAG) 1.0: [http://www.w3.org/TR/WCAG10-HTML-TECHS/](http://www.w3.org/TR/WCAG10-HTML-TECHS/){:target="_blank"} +* Authoring Tool Accessibility Guidelines (ATAG) 2.0: [http://www.w3.org/TR/WCAG20-HTML-TECHS/](http://www.w3.org/TR/WCAG20-HTML-TECHS/){:target="_blank"} diff --git a/guides/v2.2/cloud/basic-information/starter-develop-deploy-workflow.md b/guides/v2.2/cloud/basic-information/starter-develop-deploy-workflow.md index c3997a4ad44..b371eb987d8 100644 --- a/guides/v2.2/cloud/basic-information/starter-develop-deploy-workflow.md +++ b/guides/v2.2/cloud/basic-information/starter-develop-deploy-workflow.md @@ -90,9 +90,9 @@ Configure your store settings from the Magento Admin panel for the Integration e For the best information on configurations, review the documentation for {{site.data.var.ee}} and the installed extensions. Here are some links and ideas to help you get kickstarted: * [Best practices for store configuration]({{ page.baseurl }}/cloud/configure/configure-best-practices.html) for specific best practices in the cloud -* [Basic configuration](http://docs.magento.com/m2/ee/user_guide/configuration/configuration-basic.html){:target="\_blank"} for store admin access, name, languages, currencies, branding, sites, store views and more -* [Theme](http://docs.magento.com/m2/ee/user_guide/design/design-theme.html){:target="\_blank"} for your look and feel of the site and stores including CSS and layouts -* [System configuration](http://docs.magento.com/m2/ee/user_guide/system/system.html){:target="\_blank"} for roles, tools, notifications, and your encryption key for your database +* [Basic configuration](http://docs.magento.com/m2/ee/user_guide/configuration/configuration-basic.html){:target="_blank"} for store admin access, name, languages, currencies, branding, sites, store views and more +* [Theme](http://docs.magento.com/m2/ee/user_guide/design/design-theme.html){:target="_blank"} for your look and feel of the site and stores including CSS and layouts +* [System configuration](http://docs.magento.com/m2/ee/user_guide/system/system.html){:target="_blank"} for roles, tools, notifications, and your encryption key for your database * Extension settings using their documentation Beyond just store settings, you can further configure multiple sites and stores, configured services, and more. See [Configure Magento Commerce]({{ page.baseurl }}/cloud/configure/configuration-overview.html). diff --git a/guides/v2.2/cloud/configure/configuration-overview.md b/guides/v2.2/cloud/configure/configuration-overview.md index 88265ecc1cc..f16c071f9a2 100644 --- a/guides/v2.2/cloud/configure/configuration-overview.md +++ b/guides/v2.2/cloud/configure/configuration-overview.md @@ -25,7 +25,7 @@ The following options, tools, and features can be set up and configured in your * [Multiple websites or stores]({{ page.baseurl }}/cloud/project/project-multi-sites.html) details how to create and configure multi-sites for your store, for example multiple locales including English, French, and Spanish * [Install, manage, and upgrade modules]({{ page.baseurl }}/cloud/howtos/install-components.html) * [Install a theme]({{ page.baseurl }}/cloud/howtos/custom-theme.html) for your site and store -* Install the [Magento Google reCAPTCHA and Two-Factor Authentication extensions](https://docs.magento.com/m2/ee/user_guide/magento/magento-extensions.html){:target="\_blank"} to provide additional security for account access to the Magento Admin panel and storefront. +* Install the [Magento Google reCAPTCHA and Two-Factor Authentication extensions](https://docs.magento.com/m2/ee/user_guide/magento/magento-extensions.html){:target="_blank"} to provide additional security for account access to the Magento Admin panel and storefront. ## Configure your deploy: build hooks, services, and routes {#deploy} diff --git a/guides/v2.2/cloud/env/variables-build.md b/guides/v2.2/cloud/env/variables-build.md index 4dcdd9057b8..c06486e9645 100644 --- a/guides/v2.2/cloud/env/variables-build.md +++ b/guides/v2.2/cloud/env/variables-build.md @@ -31,7 +31,7 @@ The following variables were removed in v2.2: - **Default**—`6` - **Version**—Magento 2.1.4 and later -Specifies which [gzip](https://www.gnu.org/software/gzip){:target="\_blank"} compression level (`0` to `9`) to use when compressing static content; `0` disables compression. +Specifies which [gzip](https://www.gnu.org/software/gzip){:target="_blank"} compression level (`0` to `9`) to use when compressing static content; `0` disables compression. ```yaml stage: @@ -139,7 +139,7 @@ stage: - **Default**—_Not set_ - **Version**—Magento 2.1.4 and later - Enables or disables the [Symfony](https://symfony.com/doc/current/console/verbosity.html){:target="\_blank"} debug verbosity level for your logs. Choose the level of detail provided in the logs: `-v`, `-vv`, or `-vvv`. + Enables or disables the [Symfony](https://symfony.com/doc/current/console/verbosity.html){:target="_blank"} debug verbosity level for your logs. Choose the level of detail provided in the logs: `-v`, `-vv`, or `-vvv`. ```yaml stage: diff --git a/guides/v2.2/cloud/env/variables-deploy.md b/guides/v2.2/cloud/env/variables-deploy.md index dcad5fbaa9b..331a56bdfb1 100644 --- a/guides/v2.2/cloud/env/variables-deploy.md +++ b/guides/v2.2/cloud/env/variables-deploy.md @@ -209,7 +209,7 @@ The read-only connection is not available for use in the Integration environment - **Default**—`6` - **Version**—Magento 2.1.4 and later -Specifies which [gzip](https://www.gnu.org/software/gzip){:target="\_blank} compression level (`0` to `9`) to use when compressing static content; `0` disables compression. +Specifies which [gzip](https://www.gnu.org/software/gzip){:target="_blank"} compression level (`0` to `9`) to use when compressing static content; `0` disables compression. ```yaml stage: @@ -411,7 +411,7 @@ You should set this variable to `false` _only_ in Staging or Production environm - **Default**—_Not set_ - **Version**—Magento 2.1.4 and later - Enables or disables the [Symfony](https://symfony.com/doc/current/console/verbosity.html){:target="\_blank"} debug verbosity level for your logs. Choose the level of detail provided in the logs: `-v`, `-vv`, or `-vvv`. + Enables or disables the [Symfony](https://symfony.com/doc/current/console/verbosity.html){:target="_blank"} debug verbosity level for your logs. Choose the level of detail provided in the logs: `-v`, `-vv`, or `-vvv`. ```yaml stage: diff --git a/guides/v2.2/cloud/live/sens-data-initial.md b/guides/v2.2/cloud/live/sens-data-initial.md index a71c96599af..1bbaf203be3 100644 --- a/guides/v2.2/cloud/live/sens-data-initial.md +++ b/guides/v2.2/cloud/live/sens-data-initial.md @@ -66,7 +66,7 @@ To change locale and static file optimization settings: ![Set static file optimization settings]({{ site.baseurl }}/common/images/cloud_vars_set-minify.png){:width="550px"} 8. Click **Save Config**. -9. If prompted, [flush the Magento cache](http://docs.magento.com/m2/ee/user_guide/system/cache-management.html){:target="\_blank"}. +9. If prompted, [flush the Magento cache](http://docs.magento.com/m2/ee/user_guide/system/cache-management.html){:target="_blank"}. 10. Log out of the Magento Admin. ## Export values and transfer config.php to your local system {#export} diff --git a/guides/v2.2/cloud/project/project-conf-files_magento-app.md b/guides/v2.2/cloud/project/project-conf-files_magento-app.md index b4e5e738ea7..1ccb0e8d0e1 100644 --- a/guides/v2.2/cloud/project/project-conf-files_magento-app.md +++ b/guides/v2.2/cloud/project/project-conf-files_magento-app.md @@ -12,7 +12,7 @@ functional_areas: 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. -The `.magento.app.yaml` has many default values, see [a sample `.magento.app.yaml` file](https://github.com/magento/magento-cloud/blob/master/.magento.app.yaml){:target="\_blank"}. Make sure to review the `.magento.app.yaml` for your installed version. This file can differ across {{site.data.var.ece}} versions. +The `.magento.app.yaml` has many default values, see [a sample `.magento.app.yaml` file](https://github.com/magento/magento-cloud/blob/master/.magento.app.yaml){:target="_blank"}. Make sure to review the `.magento.app.yaml` for your installed version. This file can differ across {{site.data.var.ece}} versions. {% include cloud/note-pro-using-yaml.md %} @@ -318,56 +318,56 @@ To view the current list of PHP extensions, SSH into your environment and enter Magento requires the following PHP extensions that are enabled by default: -- [curl](http://php.net/manual/en/book.curl.php){:target="\_blank"} -- [gd](http://php.net/manual/en/book.image.php){:target="\_blank"} -- [intl](http://php.net/manual/en/book.intl.php){:target="\_blank"} +- [curl](http://php.net/manual/en/book.curl.php){:target="_blank"} +- [gd](http://php.net/manual/en/book.image.php){:target="_blank"} +- [intl](http://php.net/manual/en/book.intl.php){:target="_blank"} - PHP 7 only: - - [json](http://php.net/manual/en/book.json.php){:target="\_blank"} - - [iconv](http://php.net/manual/en/book.iconv.php){:target="\_blank"} -- [mcrypt](http://php.net/manual/en/book.mcrypt.php){:target="\_blank"} -- [PDO/MySQL](http://php.net/manual/en/ref.pdo-mysql.php){:target="\_blank"} -- [bc-math](http://php.net/manual/en/book.bc.php){:target="\_blank"} -- [mbstring](http://php.net/manual/en/book.mbstring.php){:target="\_blank"} -- [mhash](http://php.net/manual/en/book.mhash.php){:target="\_blank"} -- [openssl](http://php.net/manual/en/book.openssl.php){:target="\_blank"} -- [SimpleXML](http://php.net/manual/en/book.simplexml.php){:target="\_blank"} -- [soap](http://php.net/manual/en/book.soap.php){:target="\_blank"} -- [xml](http://php.net/manual/en/book.xml.php){:target="\_blank"} -- [zip](http://php.net/manual/en/book.zip.php){:target="\_blank"} + - [json](http://php.net/manual/en/book.json.php){:target="_blank"} + - [iconv](http://php.net/manual/en/book.iconv.php){:target="_blank"} +- [mcrypt](http://php.net/manual/en/book.mcrypt.php){:target="_blank"} +- [PDO/MySQL](http://php.net/manual/en/ref.pdo-mysql.php){:target="_blank"} +- [bc-math](http://php.net/manual/en/book.bc.php){:target="_blank"} +- [mbstring](http://php.net/manual/en/book.mbstring.php){:target="_blank"} +- [mhash](http://php.net/manual/en/book.mhash.php){:target="_blank"} +- [openssl](http://php.net/manual/en/book.openssl.php){:target="_blank"} +- [SimpleXML](http://php.net/manual/en/book.simplexml.php){:target="_blank"} +- [soap](http://php.net/manual/en/book.soap.php){:target="_blank"} +- [xml](http://php.net/manual/en/book.xml.php){:target="_blank"} +- [zip](http://php.net/manual/en/book.zip.php){:target="_blank"} You must install the following extensions: -- [ImageMagick](http://php.net/manual/en/book.imagick.php){:target="\_blank"} 6.3.7 (or later), ImageMagick can optionally be used with the `gd` extension -- [xsl](http://php.net/manual/en/book.xsl.php){:target="\_blank"} -- [redis](https://pecl.php.net/package/redis){:target="\_blank"} +- [ImageMagick](http://php.net/manual/en/book.imagick.php){:target="_blank"} 6.3.7 (or later), ImageMagick can optionally be used with the `gd` extension +- [xsl](http://php.net/manual/en/book.xsl.php){:target="_blank"} +- [redis](https://pecl.php.net/package/redis){:target="_blank"} In addition, we strongly recommend you enable `opcache`. Optional PHP extensions available to install: -- [apcu](http://php.net/manual/en/book.apcu.php){:target="\_blank"} -- [blackfire](https://blackfire.io/docs/up-and-running/installation){:target="\_blank"} -- [enchant](http://php.net/manual/en/book.enchant.php){:target="\_blank"} -- [gearman](http://php.net/manual/en/book.gearman.php){:target="\_blank"} -- [geoip](http://php.net/manual/en/book.geoip.php){:target="\_blank"} -- [imap](http://php.net/manual/en/book.imap.php){:target="\_blank"} -- [ioncube](https://www.ioncube.com/loaders.php){:target="\_blank"} -- [pecl-http](https://pecl.php.net/package/pecl_http){:target="\_blank"} -- [pinba](http://pinba.org){:target="\_blank"} -- [propro](https://pecl.php.net/package/propro){:target="\_blank"} -- [pspell](http://php.net/manual/en/book.pspell.php){:target="\_blank"} -- [raphf](https://pecl.php.net/package/raphf){:target="\_blank"} -- [readline](http://php.net/manual/en/book.readline.php){:target="\_blank"} -- [recode](http://php.net/manual/en/book.recode.php){:target="\_blank"} -- [snmp](http://php.net/manual/en/book.snmp.php){:target="\_blank"} -- [sqlite3](http://php.net/manual/en/book.sqlite3.php){:target="\_blank"} -- [ssh2](http://php.net/manual/en/book.ssh2.php){:target="\_blank"} -- [tidy](http://php.net/manual/en/book.tidy.php){:target="\_blank"} -- [xcache](https://xcache.lighttpd.net){:target="\_blank"} -- [xdebug](https://xdebug.org){:target="\_blank"} -- [xhprof](http://php.net/manual/en/book.xhprof.php){:target="\_blank"} -- [xmlrpc](http://php.net/manual/en/book.xmlrpc.php){:target="\_blank"} +- [apcu](http://php.net/manual/en/book.apcu.php){:target="_blank"} +- [blackfire](https://blackfire.io/docs/up-and-running/installation){:target="_blank"} +- [enchant](http://php.net/manual/en/book.enchant.php){:target="_blank"} +- [gearman](http://php.net/manual/en/book.gearman.php){:target="_blank"} +- [geoip](http://php.net/manual/en/book.geoip.php){:target="_blank"} +- [imap](http://php.net/manual/en/book.imap.php){:target="_blank"} +- [ioncube](https://www.ioncube.com/loaders.php){:target="_blank"} +- [pecl-http](https://pecl.php.net/package/pecl_http){:target="_blank"} +- [pinba](http://pinba.org){:target="_blank"} +- [propro](https://pecl.php.net/package/propro){:target="_blank"} +- [pspell](http://php.net/manual/en/book.pspell.php){:target="_blank"} +- [raphf](https://pecl.php.net/package/raphf){:target="_blank"} +- [readline](http://php.net/manual/en/book.readline.php){:target="_blank"} +- [recode](http://php.net/manual/en/book.recode.php){:target="_blank"} +- [snmp](http://php.net/manual/en/book.snmp.php){:target="_blank"} +- [sqlite3](http://php.net/manual/en/book.sqlite3.php){:target="_blank"} +- [ssh2](http://php.net/manual/en/book.ssh2.php){:target="_blank"} +- [tidy](http://php.net/manual/en/book.tidy.php){:target="_blank"} +- [xcache](https://xcache.lighttpd.net){:target="_blank"} +- [xdebug](https://xdebug.org){:target="_blank"} +- [xhprof](http://php.net/manual/en/book.xhprof.php){:target="_blank"} +- [xmlrpc](http://php.net/manual/en/book.xmlrpc.php){:target="_blank"} {:.bs-callout .bs-callout-warning} diff --git a/guides/v2.2/cloud/project/project-conf-files_services-elastic.md b/guides/v2.2/cloud/project/project-conf-files_services-elastic.md index acad1984cf1..14a26ae1361 100644 --- a/guides/v2.2/cloud/project/project-conf-files_services-elastic.md +++ b/guides/v2.2/cloud/project/project-conf-files_services-elastic.md @@ -7,7 +7,7 @@ functional_areas: - Search --- -[Elasticsearch](https://www.elastic.co){:target="\_blank"} is an open source product that enables you to take data from any source, any format, and search and visualize it in real time. +[Elasticsearch](https://www.elastic.co){:target="_blank"} is an open source product that enables you to take data from any source, any format, and search and visualize it in real time. * Elasticsearch performs quick and advanced searches on products in the product catalog * Elasticsearch Analyzers support multiple languages @@ -55,7 +55,7 @@ elasticsearch: - lang-python ``` -For example, if you are using [Smile ElasticSuite](https://github.com/Smile-SA/elasticsuite){:target="\_blank"}, you should add the following plugins: +For example, if you are using [Smile ElasticSuite](https://github.com/Smile-SA/elasticsuite){:target="_blank"}, you should add the following plugins: ```yaml elasticsearch: @@ -85,9 +85,9 @@ The following are supported Elasticsearch plugins for version 2.4: * `mapper-murmur3`: Murmur3 mapper plugin for computing hashes at index-time * `mapper-size`: Size mapper plugin, enables the `_size` meta field -If using [Smile ElasticSuite](https://github.com/Smile-SA/elasticsuite){:target="\_blank"}, the required plugins are `analysis-icu` and `analysis-phonetic`. Make sure to add these to the plugins section of `services.yaml.` See [Add Elasticsearch plugins](#addplugins). +If using [Smile ElasticSuite](https://github.com/Smile-SA/elasticsuite){:target="_blank"}, the required plugins are `analysis-icu` and `analysis-phonetic`. Make sure to add these to the plugins section of `services.yaml.` See [Add Elasticsearch plugins](#addplugins). -For full documentation on these plugins, see [Elasticsearch plugin documentation](https://www.elastic.co/guide/en/elasticsearch/plugins/2.4/index.html){:target="\_blank"}. +For full documentation on these plugins, see [Elasticsearch plugin documentation](https://www.elastic.co/guide/en/elasticsearch/plugins/2.4/index.html){:target="_blank"}. ## Verify environment-related relationships {#cloud-es-config-mg} diff --git a/guides/v2.2/cloud/project/project-start.md b/guides/v2.2/cloud/project/project-start.md index 56c444e27c2..dc67b7bb08b 100644 --- a/guides/v2.2/cloud/project/project-start.md +++ b/guides/v2.2/cloud/project/project-start.md @@ -26,7 +26,7 @@ When you push your local environment to the remote server, our deploy script use ## Ignoring files -We include a base `.gitignore` file with the {{site.data.var.ece}} project repository. See [.gitignore file](https://github.com/magento/magento-cloud/blob/master/.gitignore){:target="\_blank"}. You can add an ignored file when staging a commit by using the `-f` option: +We include a base `.gitignore` file with the {{site.data.var.ece}} project repository. See [.gitignore file](https://github.com/magento/magento-cloud/blob/master/.gitignore){:target="_blank"}. You can add an ignored file when staging a commit by using the `-f` option: ```bash git add -f diff --git a/guides/v2.2/cloud/project/project-upgrade.md b/guides/v2.2/cloud/project/project-upgrade.md index 80fa3f536fe..58cb1c6c041 100644 --- a/guides/v2.2/cloud/project/project-upgrade.md +++ b/guides/v2.2/cloud/project/project-upgrade.md @@ -25,7 +25,7 @@ Prepare your environment with the following tasks: {{site.data.var.ece}} 2.2 supports PHP 7.1 and later. Make sure to upgrade the version of PHP on your local development workspace as well. For more information, see the following: * [PHP]({{ site.baseurl }}/guides/v2.2/cloud/before/before-workspace-magento-prereqs.html#php) information for your local Magento workstation -* [Migrating PHP](http://php.net/manual/en/migration71.php){:target="\_blank"} +* [Migrating PHP](http://php.net/manual/en/migration71.php){:target="_blank"} * [Magento 2.2.x technology stack requirements]({{ site.baseurl }}/guides/v2.2/install-gde/system-requirements-tech.html#php) {: .bs-callout .bs-callout-info} diff --git a/guides/v2.2/cloud/reference/cloud-composer.md b/guides/v2.2/cloud/reference/cloud-composer.md index 9f76d988b81..ab32bf5d157 100644 --- a/guides/v2.2/cloud/reference/cloud-composer.md +++ b/guides/v2.2/cloud/reference/cloud-composer.md @@ -8,7 +8,7 @@ functional_areas: - Upgrade --- -We use [Composer](https://getcomposer.org/doc){:target="\_blank"} 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. +We use [Composer](https://getcomposer.org/doc){:target="_blank"} 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. Composer manages required libraries and dependencies for your project and installs them in the `vendor` directory. @@ -38,7 +38,7 @@ During the [build phase]({{ page.baseurl }}/cloud/reference/discover-deploy.html ## magento/magento-cloud-metapackage {#cloud-composer-cloudmeta} -The `vendor/magento/magento-cloud-metapackage` should be the only package in the `require` section of your `composer.json`. This is a [_metapackage_](https://getcomposer.org/doc/04-schema.md#type){:target="\_blank"} and does not contain any code. +The `vendor/magento/magento-cloud-metapackage` should be the only package in the `require` section of your `composer.json`. This is a [_metapackage_](https://getcomposer.org/doc/04-schema.md#type){:target="_blank"} and does not contain any code. The metapackage depends on the appropriate versions of `vendor/magento/ece-patches`, [`vendor/magento/ece-tools`](#ece-tools), and [`vendor/magento/product-enterprise-edition`](#cloud-composer-prodee). At any given version, this package requires the same version of `magento/product-enterprise-edition`. For example, to use {{site.data.var.ee}} version 2.2.0, for example, `composer.json` must specify a requirement for `magento/magento-cloud-metapackage` version 2.2.0. diff --git a/guides/v2.2/cloud/reference/discover-deploy.md b/guides/v2.2/cloud/reference/discover-deploy.md index ffe8461760a..3277b825147 100644 --- a/guides/v2.2/cloud/reference/discover-deploy.md +++ b/guides/v2.2/cloud/reference/discover-deploy.md @@ -78,7 +78,7 @@ For detailed instructions, see [Build and deploy full steps](#steps). ### Phase 1: Code and configuration validation {#cloud-deploy-over-phases-conf} -When you initially set up a project from a template, we retrieve the code from the [the {{site.data.var.ee}} template](https://github.com/magento/magento-cloud){:target="\_blank"}. This code repo is cloned to your project as the `master` branch. +When you initially set up a project from a template, we retrieve the code from the [the {{site.data.var.ee}} template](https://github.com/magento/magento-cloud){:target="_blank"}. This code repo is cloned to your project as the `master` branch. - **For Starter**—`master` branch is your Production environment. - **For Pro**—`master` begins as origin branch for the Integration environment. diff --git a/guides/v2.2/cloud/release-notes/CloudReleaseNotes2.2.md b/guides/v2.2/cloud/release-notes/CloudReleaseNotes2.2.md index df02c58bead..7691bd6b0c0 100644 --- a/guides/v2.2/cloud/release-notes/CloudReleaseNotes2.2.md +++ b/guides/v2.2/cloud/release-notes/CloudReleaseNotes2.2.md @@ -52,7 +52,7 @@ Magento 2.2.0 includes multiple security enhancements. Although this release inc In general, we’ve removed serialize/unserialize from most the code to improve protection against remote code execution attacks. We’ve enhanced protection of code where use of object serialization or unserialization was unavoidable. Additionally, we’ve increased our use of output escaping to protect against cross-site scripting (XSS) attacks. -[Contact us](https://magento.com/company/contact-us){:target="\_blank"} for more information. +[Contact us](https://magento.com/company/contact-us){:target="_blank"} for more information. ## Known issues {#known} @@ -117,7 +117,7 @@ We are grateful to the wider Magento community and would like to acknowledge the For {{site.data.var.ece}} requirements, see [Technologies and Requirements]({{ site.baseurl }}/guides/v2.2/cloud/requirements/cloud-requirements.html). -The {{site.data.var.ee}} technology stack is built on PHP and MySQL. For details, see [Technology stack requirements]({{ page.baseurl }}/install-gde/system-requirements-tech.html) and [System Requirements]({{ site.baseurl }}/magento-system-requirements.html){:target="\_blank"}. +The {{site.data.var.ee}} technology stack is built on PHP and MySQL. For details, see [Technology stack requirements]({{ page.baseurl }}/install-gde/system-requirements-tech.html) and [System Requirements]({{ site.baseurl }}/magento-system-requirements.html){:target="_blank"}. ## Installation and upgrade instructions {#install-upgrade} diff --git a/guides/v2.2/cloud/release-notes/cloud-tools.md b/guides/v2.2/cloud/release-notes/cloud-tools.md index 30b767339d5..a4b760c6c88 100644 --- a/guides/v2.2/cloud/release-notes/cloud-tools.md +++ b/guides/v2.2/cloud/release-notes/cloud-tools.md @@ -22,7 +22,7 @@ The following updates describe the latest improvements to the `ece-tools` packag #### New features -- **Enable zero-downtime deployment**—Now {{site.data.var.ece}} queues requests with required database changes during deployment and applies the changes as soon as the deployment completes. Requests can be held for up to 5 minutes to ensure that no sessions are lost. See [Static content deployment options to reduce deployment downtime on Cloud](https://support.magento.com/hc/en-us/articles/360004861194-Static-content-deployment-options-to-reduce-deployment-downtime-on-Cloud){:target="\_blank"}. +- **Enable zero-downtime deployment**—Now {{site.data.var.ece}} queues requests with required database changes during deployment and applies the changes as soon as the deployment completes. Requests can be held for up to 5 minutes to ensure that no sessions are lost. See [Static content deployment options to reduce deployment downtime on Cloud](https://support.magento.com/hc/en-us/articles/360004861194-Static-content-deployment-options-to-reduce-deployment-downtime-on-Cloud){:target="_blank"}. - **Docker Compose for Cloud**—Made the following improvements to the [Docker setup and configuration]({{ page.baseurl }}/cloud/reference/docker-config.html) process: @@ -88,7 +88,7 @@ Made the following changes to improve log messages and reduce log size: Now you can easily move your configuration files between environments. After you update to `ece-tools` v2002.0.13, regenerate older `config.php` files with the improved `config:dump` command. See [Configuration management for store settings]({{ page.baseurl }}/cloud/live/sens-data-over.html). -- Fixed an issue that caused an error during the deploy phase if the route configuration in the `.magento/routes.yaml` file redirects from an [apex](https://blog.cloudflare.com/zone-apex-naked-domain-root-domain-cname-supp/){:target="\_blank"} domain to a `www`domain. +- Fixed an issue that caused an error during the deploy phase if the route configuration in the `.magento/routes.yaml` file redirects from an [apex](https://blog.cloudflare.com/zone-apex-naked-domain-root-domain-cname-supp/){:target="_blank"} domain to a `www`domain. - Fixed an issue with the `_merge` option for the [`SEARCH_CONFIGURATION`]({{ page.baseurl }}/cloud/env/variables-deploy.html#search_configuration) variable that caused incorrect merge results if you do not include the `engine` parameter in the updated `.magento.env.yaml` configuration file. Now, the merge operation correctly overwrites only the values you specify in the updated `.magento.env.yaml` without requiring you to set the `engine` parameter. @@ -297,7 +297,7 @@ We merged [`vendor/magento/ece-patches`]({{ site.baseurl }}/guides/v2.2/cloud/co - **Build/deploy notifications**—We added a configuration file that you can use to [set up Slack and/or email notifications]({{ site.baseurl }}/guides/v2.2/cloud/env/setup-notifications.html) for build/deploy actions in all your environments. -- **Static content compression**—We now compress static content using [gzip](https://www.gnu.org/software/gzip/){:target="\_blank"} during the build and deploy phases. This compression, coupled with Fastly compression, helps reduce the size of your store and increase deployment speed. If necessary, you can disable compression using a [build option]({{ site.baseurl }}/guides/v2.2/cloud/env/variables-build.html) or [deploy variable]({{ site.baseurl }}/guides/v2.2/cloud/env/variables-deploy.html). See the following topics for more information: +- **Static content compression**—We now compress static content using [gzip](https://www.gnu.org/software/gzip/){:target="_blank"} during the build and deploy phases. This compression, coupled with Fastly compression, helps reduce the size of your store and increase deployment speed. If necessary, you can disable compression using a [build option]({{ site.baseurl }}/guides/v2.2/cloud/env/variables-build.html) or [deploy variable]({{ site.baseurl }}/guides/v2.2/cloud/env/variables-deploy.html). See the following topics for more information: - [Magento application environment variables]({{ site.baseurl }}/guides/v2.2/cloud/env/environment-vars_magento.html) - [Static content deployment performance]({{ site.baseurl }}/guides/v2.2/cloud/live/sens-data-over.html#cloud-confman-scd-over) diff --git a/guides/v2.2/cloud/requirements/cloud-requirements.md b/guides/v2.2/cloud/requirements/cloud-requirements.md index 4a9c10b2164..f7e65350159 100644 --- a/guides/v2.2/cloud/requirements/cloud-requirements.md +++ b/guides/v2.2/cloud/requirements/cloud-requirements.md @@ -53,11 +53,11 @@ Git is the heart of all your code in repositories. It acts as a version control We hope you have a good working knowledge of Git. Need some help? Don't worry, we have you covered with some of our favorite links and information. We'll also include a Git guide to branching and developing soon. -* [Git documentation](https://git-scm.com/documentation){:target="\_blank"} and [videos](https://git-scm.com/videos){:target="\_blank"} from the makers of Git -* [Git cheatsheet](http://rogerdudler.github.io/git-guide/files/git_cheat_sheet.pdf){:target="\_blank"} and [quick guide](http://rogerdudler.github.io/git-guide/){:target="\_blank"} from Roger Dudler -* [Git video](https://www.youtube.com/watch?v=8KCQe9Pm1kg){:target="\_blank"} with DevForge to understand how people use the repo and commands with a fun story +* [Git documentation](https://git-scm.com/documentation){:target="_blank"} and [videos](https://git-scm.com/videos){:target="_blank"} from the makers of Git +* [Git cheatsheet](http://rogerdudler.github.io/git-guide/files/git_cheat_sheet.pdf){:target="_blank"} and [quick guide](http://rogerdudler.github.io/git-guide/){:target="_blank"} from Roger Dudler +* [Git video](https://www.youtube.com/watch?v=8KCQe9Pm1kg){:target="_blank"} with DevForge to understand how people use the repo and commands with a fun story -To get started with Git, you should have [Git installed](https://git-scm.com/downloads){:target="\_blank"} on your local. +To get started with Git, you should have [Git installed](https://git-scm.com/downloads){:target="_blank"} on your local. {:.bs-callout .bs-callout-info} In addition to Git requirements for valid branch names, {{site.data.var.ee}} adds two additional requirements: diff --git a/guides/v2.2/cloud/trouble/robots-sitemap.md b/guides/v2.2/cloud/trouble/robots-sitemap.md index 5385f43f0c5..a2fe635888a 100644 --- a/guides/v2.2/cloud/trouble/robots-sitemap.md +++ b/guides/v2.2/cloud/trouble/robots-sitemap.md @@ -15,7 +15,7 @@ With {{site.data.var.ece}}, you can only write to specific directories, such as You do not have to generate a `robots.txt` because it generates on demand and stores the contents in the database. It does not create a file, but you can view the content in your browser with the url: `/robots.txt` -This requires ECE-Tools version 2002.0.12 and later with an updated `.magento.app.yaml` file. See an example of these rules in the [magento-cloud repository](https://github.com/magento/magento-cloud/blob/master/.magento.app.yaml#L43-L49){:target="\_blank"}. +This requires ECE-Tools version 2002.0.12 and later with an updated `.magento.app.yaml` file. See an example of these rules in the [magento-cloud repository](https://github.com/magento/magento-cloud/blob/master/.magento.app.yaml#L43-L49){:target="_blank"}. #### To generate a `sitemap.xml` file in version 2.2 and later: diff --git a/guides/v2.2/comp-mgr/upgrader/ce-ee-upgrade-start.md b/guides/v2.2/comp-mgr/upgrader/ce-ee-upgrade-start.md index 435b0c0fd1e..02ca43edc59 100644 --- a/guides/v2.2/comp-mgr/upgrader/ce-ee-upgrade-start.md +++ b/guides/v2.2/comp-mgr/upgrader/ce-ee-upgrade-start.md @@ -22,7 +22,7 @@ In addition, you might need to install the {% glossarytooltip bf703ab1-ca4b-48f9 * Ubuntu (using the `ppa:ondrej/php5-5.6` repository): `apt-get -y install php5-bcmath` {:.bs-callout .bs-callout-info} -Make sure you are authorized for {{site.data.var.ee}} access before you continue. Contact [Magento Support](http://support.magentocommerce.com){:target="_blank"} if you have questions. +Make sure you are authorized for {{site.data.var.ee}} access before you continue. Contact [Magento Support](http://support.magentocommerce.com){:target="_blank"} if you have questions. ## Start System Upgrade from the Magento Admin {#compman-access} diff --git a/guides/v2.2/config-guide/cli/config-cli-subcommands-perf-data.md b/guides/v2.2/config-guide/cli/config-cli-subcommands-perf-data.md index 0b0093e5ebf..82043a6e398 100644 --- a/guides/v2.2/config-guide/cli/config-cli-subcommands-perf-data.md +++ b/guides/v2.2/config-guide/cli/config-cli-subcommands-perf-data.md @@ -521,7 +521,7 @@ Generates store views. Store views are distributed normally among store groups. Generates tax rates. XML profile node: -
        <!-- Accepts name of {% glossarytooltip 6341499b-ead9-4836-9794-53d95eb48ea5 %}csv{% endglossarytooltip %} file with tax rates (<path to magento folder>/setup/src/Magento/Setup/Fixtures/_files) -->
+
        <!-- Accepts name of {% glossarytooltip 6341499b-ead9-4836-9794-53d95eb48ea5 %}csv{% endglossarytooltip %} file with tax rates (<path to magento folder>/setup/src/Magento/Setup/Fixtures/_files) -->
 <tax_rates_file>{csv file name}</tax_rates_file>
        
 
 ## Additional information    
diff --git a/guides/v2.2/frontend-dev-guide/templates/template-sample.md b/guides/v2.2/frontend-dev-guide/templates/template-sample.md
index cd80cd361d5..cd22ab0c147 100644
--- a/guides/v2.2/frontend-dev-guide/templates/template-sample.md
+++ b/guides/v2.2/frontend-dev-guide/templates/template-sample.md
@@ -16,7 +16,7 @@ In the Magento basic Blank theme, in the mini shopping cart, products are listed
 
 OrangeCo decided they want to change this and display the product list before the **Go to Checkout** button.
 
-The template responsible for displaying the mini-shopping cart items and controls is [`/view/frontend/web/template/minicart/content.html`]({{site.mage2200url}}app/code/Magento/Checkout/view/frontend/web/template/minicart/content.html){:target="\_blank"}.
+The template responsible for displaying the mini-shopping cart items and controls is [`/view/frontend/web/template/minicart/content.html`]({{site.mage2200url}}app/code/Magento/Checkout/view/frontend/web/template/minicart/content.html){:target="_blank"}.
 Here is the part of the code OrangeCo worked with:
 
 ![code1]({{site.baseurl}}/common/images/templ_overview_code121.png)
diff --git a/guides/v2.2/frontend-dev-guide/themes/theme-create.md b/guides/v2.2/frontend-dev-guide/themes/theme-create.md
index 8f1c083fad4..f770ba2686a 100644
--- a/guides/v2.2/frontend-dev-guide/themes/theme-create.md
+++ b/guides/v2.2/frontend-dev-guide/themes/theme-create.md
@@ -30,7 +30,7 @@ The high-level steps required to add a new theme in the Magento system are the f
 
 ## Recommended reading
 
-* [Checklist of modules]({{site.mage2200url}}app/code/Magento){:target="\_blank"}
+* [Checklist of modules]({{site.mage2200url}}app/code/Magento){:target="_blank"}
 * [Static view files processing]({{page.baseurl}}/config-guide/cli/config-cli-subcommands-static-view.html)
 
 ## Create a theme directory
@@ -84,9 +84,9 @@ If you change the theme title or parent theme information in `theme.xml` after a
 
 ## Make your theme a Composer package {#fedg_create_theme_composer}
 
-Magento default themes are distributed as [Composer](https://getcomposer.org/){:target="\_blank"} packages.
+Magento default themes are distributed as [Composer](https://getcomposer.org/){:target="_blank"} packages.
 
-To distribute your theme as a package, add a `composer.json` file to the theme directory and register the package on a packaging server. A default public packaging server is [https://packagist.org/](https://packagist.org/){:target="\_blank"}.
+To distribute your theme as a package, add a `composer.json` file to the theme directory and register the package on a packaging server. A default public packaging server is [https://packagist.org/](https://packagist.org/){:target="_blank"}.
 
 The `composer.json` file provides theme dependency information. Refer to a current `theme.xml` file for the correct dependancies and their versions. If your parent theme is something other than `Magento/blank`, you may need additional modules in the `"require"` section.
 
@@ -136,7 +136,7 @@ To register your theme in the system, add a `registration.php` file in your them
 
 Where `` is your vendor name and `` is the theme code.
 
-For illustration, see the [registration.php]({{site.mage2200url}}app/design/frontend/Magento/luma/registration.php){:target="\_blank"} file in the Magento Luma theme.
+For illustration, see the [registration.php]({{site.mage2200url}}app/design/frontend/Magento/luma/registration.php){:target="_blank"} file in the Magento Luma theme.
 
 ## Configure images {#fedg_create_theme_how-to-images}
 
diff --git a/guides/v2.2/get-started/create-integration.md b/guides/v2.2/get-started/create-integration.md
index 3e482be81da..0f6e45c7133 100644
--- a/guides/v2.2/get-started/create-integration.md
+++ b/guides/v2.2/get-started/create-integration.md
@@ -151,7 +151,7 @@ Change directories to your `Setup` directory. Create a `InstallData.php` file th
          * @param ConfigBasedIntegrationManager $integrationManager
          */
 
-        public function __construct(ConfigBasedIntegrationManager $integrationManager)
+        public function __construct(ConfigBasedIntegrationManager $integrationManager)
         {
             $this->integrationManager = $integrationManager;
         }
diff --git a/guides/v2.2/install-gde/prereq/mysql.md b/guides/v2.2/install-gde/prereq/mysql.md
index 28f43ceb387..dd945aeab1a 100644
--- a/guides/v2.2/install-gde/prereq/mysql.md
+++ b/guides/v2.2/install-gde/prereq/mysql.md
@@ -23,9 +23,9 @@ The Magento application requires MySQL 5.6.x. Magento versions 2.1.2 and later a
 
 Magento _strongly_ recommends you observe the following standard when you set up your Magento database:
 
-*	Magento uses [MySQL database triggers](http://dev.mysql.com/doc/refman/5.0/en/triggers.html){:target="_blank"} to improve database access during reindexing. Magento does not support any custom triggers in the Magento database because custom triggers can introduce incompatibilities with future Magento versions.
-*	Familiarize yourself with [these potential MySQL trigger limitations](http://dev.mysql.com/doc/mysql-reslimits-excerpt/5.1/en/stored-program-restrictions.html){:target="_blank"} before you continue.
-*	If you use MySQL database replication, be aware that Magento does _not_ support MySQL statement-based replication. Make sure you use _only_ [row-based replication](http://dev.mysql.com/doc/refman/5.1/en/replication-formats.html){:target="_blank"}.
+*	Magento uses [MySQL database triggers](http://dev.mysql.com/doc/refman/5.0/en/triggers.html){:target="_blank"} to improve database access during reindexing. Magento does not support any custom triggers in the Magento database because custom triggers can introduce incompatibilities with future Magento versions.
+*	Familiarize yourself with [these potential MySQL trigger limitations](http://dev.mysql.com/doc/mysql-reslimits-excerpt/5.1/en/stored-program-restrictions.html){:target="_blank"} before you continue.
+*	If you use MySQL database replication, be aware that Magento does _not_ support MySQL statement-based replication. Make sure you use _only_ [row-based replication](http://dev.mysql.com/doc/refman/5.1/en/replication-formats.html){:target="_blank"}.
 
 {:.bs-callout .bs-callout-info}
 If your web server and database server are on different hosts, perform the tasks discussed in this topic on the database server host then see [Set up a remote MySQL database connection]({{ page.baseurl }}/install-gde/prereq/mysql_remote.html).
@@ -79,7 +79,7 @@ To install MySQL 5.7 on Ubuntu 16:
 
 		mysql>
 
-5.	If you expect to import large numbers of products into Magento, you can increase the value for [`max_allowed_packet`](http://dev.mysql.com/doc/refman/5.6/en/program-variables.html){:target="_blank"} that is larger than the default, 16MB.
+5.	If you expect to import large numbers of products into Magento, you can increase the value for [`max_allowed_packet`](http://dev.mysql.com/doc/refman/5.6/en/program-variables.html){:target="_blank"} that is larger than the default, 16MB.
 
 	{% include install/mysql_max-allowed-packet-ubuntu.md %}
 
@@ -121,7 +121,7 @@ To install MySQL 5.6 on Ubuntu 14:
 
 		mysql>
 
-5.	If you expect to import large numbers of products into Magento, you can increase the value for [`max_allowed_packet`](http://dev.mysql.com/doc/refman/5.6/en/program-variables.html){:target="_blank"} that is larger than the default, 16MB.
+5.	If you expect to import large numbers of products into Magento, you can increase the value for [`max_allowed_packet`](http://dev.mysql.com/doc/refman/5.6/en/program-variables.html){:target="_blank"} that is larger than the default, 16MB.
 
 	{% include install/mysql_max-allowed-packet-ubuntu.md %}
 
@@ -129,7 +129,7 @@ To install MySQL 5.6 on Ubuntu 14:
 
 ### Installing MySQL 5.6 on Ubuntu 12 {#instgde-prereq-mysql56ubu12}
 
-To install MySQL 5.6 on Ubuntu 12, use the following instructions from [askubuntu.com][http://askubuntu.com/questions/433014/unable-to-install-mysql-5-6-in-ubuntu-12-04]{:target="_blank"}.
+To install MySQL 5.6 on Ubuntu 12, use the following instructions from [askubuntu.com][http://askubuntu.com/questions/433014/unable-to-install-mysql-5-6-in-ubuntu-12-04]{:target="_blank"}.
 
 1.	Enter the following commands in the order shown:
 
@@ -166,7 +166,7 @@ To install MySQL 5.6 on Ubuntu 12, use the following instructions from [askubunt
 
 		mysql>
 
-5.	If you expect to import large numbers of products into Magento, you can increase the value for [`max_allowed_packet`](http://dev.mysql.com/doc/refman/5.6/en/program-variables.html){:target="_blank"} that is larger than the default, 16MB.
+5.	If you expect to import large numbers of products into Magento, you can increase the value for [`max_allowed_packet`](http://dev.mysql.com/doc/refman/5.6/en/program-variables.html){:target="_blank"} that is larger than the default, 16MB.
 
 	{% include install/mysql_max-allowed-packet-ubuntu.md %}
 
@@ -181,7 +181,7 @@ The Magento application 2.1.2 and later are compatible with MySQL 5.7.
 
 ### Get MySQL 5.7 for CentOS 7
 
-The following procedure is based on [How to Install Latest MySQL 5.7.9 on RHEL/CentOS 7/6/5 and Fedora 23/22/21](http://www.tecmint.com/install-latest-mysql-on-rhel-centos-and-fedora){:target="_blank"}.
+The following procedure is based on [How to Install Latest MySQL 5.7.9 on RHEL/CentOS 7/6/5 and Fedora 23/22/21](http://www.tecmint.com/install-latest-mysql-on-rhel-centos-and-fedora){:target="_blank"}.
 
 As a user with `root` privileges, enter the following commands in the order shown:
 
@@ -192,7 +192,7 @@ Continue with [Install and configure MySQL 5.7 on CentOS 6 or 7](#mysql57-centos
 
 ### Get MySQL 5.7 for CentOS 6
 
-The following procedure is based on [How to Install Latest MySQL 5.7.9 on RHEL/CentOS 7/6/5 and Fedora 23/22/21](http://www.tecmint.com/install-latest-mysql-on-rhel-centos-and-fedora){:target="_blank"}.
+The following procedure is based on [How to Install Latest MySQL 5.7.9 on RHEL/CentOS 7/6/5 and Fedora 23/22/21](http://www.tecmint.com/install-latest-mysql-on-rhel-centos-and-fedora){:target="_blank"}.
 
 As a user with `root` privileges, enter the following commands in the order shown:
 
@@ -228,7 +228,7 @@ Continue with the next section.
 
 ## Installing and configuring MySQL 5.6 on CentOS {#instgde-prereq-mysql-centos}
 
-The following procedure is based on [Install MySQL Server 5.6 in CentOS 6.x and Red Hat 6.x Linux](http://sharadchhetri.com/2013/12/26/install-mysql-server-5-6-in-centos-6-x-and-red-hat-6-x-linux/){:target="_blank"}.
+The following procedure is based on [Install MySQL Server 5.6 in CentOS 6.x and Red Hat 6.x Linux](http://sharadchhetri.com/2013/12/26/install-mysql-server-5-6-in-centos-6-x-and-red-hat-6-x-linux/){:target="_blank"}.
 
 1.	*CentOS 6* Install the MySQL database:
 
@@ -269,7 +269,7 @@ The following procedure is based on [Install MySQL Server 5.6 in CentOS 6.x and
 
 		Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
 
-5.	If you expect to import large numbers of products into Magento, you can configure MySQL to use the [`max_allowed_packet`](http://dev.mysql.com/doc/refman/5.6/en/program-variables.html){:target="_blank"} parameter. We recommend a value of at least 16MB.
+5.	If you expect to import large numbers of products into Magento, you can configure MySQL to use the [`max_allowed_packet`](http://dev.mysql.com/doc/refman/5.6/en/program-variables.html){:target="_blank"} parameter. We recommend a value of at least 16MB.
 
 	{% include install/mysql_max-allowed-packet-centos.md %}
 
diff --git a/guides/v2.2/install-gde/prereq/nginx.md b/guides/v2.2/install-gde/prereq/nginx.md
index 3e4888022bf..5498bdeeceb 100644
--- a/guides/v2.2/install-gde/prereq/nginx.md
+++ b/guides/v2.2/install-gde/prereq/nginx.md
@@ -10,7 +10,7 @@ functional_areas:
   - Setup
 ---
 
-Magento supports nginx 1.8 (or the [latest mainline version](http://nginx.org/en/linux_packages.html#mainline){:target="_blank}). You must also install the latest version of `php-fpm`.
+Magento supports nginx 1.8 (or the [latest mainline version](http://nginx.org/en/linux_packages.html#mainline){:target="_blank}). You must also install the latest version of `php-fpm`.
 
 Installation instructions vary based on which operating system you're using:
 
diff --git a/guides/v2.2/install-gde/prereq/php-centos.md b/guides/v2.2/install-gde/prereq/php-centos.md
index a26401559c3..a6774af02b6 100644
--- a/guides/v2.2/install-gde/prereq/php-centos.md
+++ b/guides/v2.2/install-gde/prereq/php-centos.md
@@ -37,7 +37,7 @@ To verify if PHP is installed already, enter `php -v`. If {% glossarytooltip bf7
       with Zend OPcache v7.0.20, Copyright (c) 1999-2017, by Zend Technologies
 
 {:.bs-callout .bs-callout-info}
-The preceding message confirms that the `Zend OPcache` is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}.
+The preceding message confirms that the `Zend OPcache` is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}.
 
 If PHP is installed, continue with the next prerequisite, [MySQL]({{ page.baseurl }}/install-gde/prereq/mysql.html).
 
@@ -48,7 +48,7 @@ If PHP is *not* installed, see one of the following sections:
 
 ## CentOS repositories {#centos-php-repos}
 
-Linux systems provide software like PHP in one or more *repositories*. CentOS, unlike Ubuntu, has a set of [officially recommended repositories](https://wiki.centos.org/AdditionalResources/Repositories){:target="_blank"}. Other repositories are considered less safe for the reasons stated on the CentOS wiki.
+Linux systems provide software like PHP in one or more *repositories*. CentOS, unlike Ubuntu, has a set of [officially recommended repositories](https://wiki.centos.org/AdditionalResources/Repositories){:target="_blank"}. Other repositories are considered less safe for the reasons stated on the CentOS wiki.
 
 We're not aware that you can install PHP 7.0 or 7.1 from a CentOS-recommended repository. Therefore, you must consider the following:
 
@@ -57,9 +57,9 @@ We're not aware that you can install PHP 7.0 or 7.1 from a CentOS-recommended re
 	You should also consider upgrading to a later version of CentOS that has the desired PHP version in a recommended repository.
 *	If you're setting up a development system, you can use any repository you wish.
 
-In this topic, we show how to install PHP using the [Inline with Upstream Stable (IUS)](https://ius.io/GettingStarted){:target="_blank"} repository, which is *not* on the CentOS recommended list. However, packages installed from IUS do not use the same names as CentOS-provided packages, so [no existing system packages are replaced](https://ius.io/Philosophy){:target="_blank"}.
+In this topic, we show how to install PHP using the [Inline with Upstream Stable (IUS)](https://ius.io/GettingStarted){:target="_blank"} repository, which is *not* on the CentOS recommended list. However, packages installed from IUS do not use the same names as CentOS-provided packages, so [no existing system packages are replaced](https://ius.io/Philosophy){:target="_blank"}.
 
-Before you continue, review their [Getting Started topic](https://ius.io/GettingStarted){:target="_blank"}.
+Before you continue, review their [Getting Started topic](https://ius.io/GettingStarted){:target="_blank"}.
 
 {:.bs-callout .bs-callout-info}
 Magento does _not_ officially recommend using the IUS repository. We discuss it here for example purposes only.
@@ -102,7 +102,7 @@ There is more than one way to install PHP 7.0 on CentOS; the following is a sugg
 		Zend Engine v3.0.0, Copyright (c) 1998-2016 Zend Technologies with Zend OPcache v7.0.6-dev, Copyright (c) 1999-2016, by Zend Technologies
 
     {:.bs-callout .bs-callout-info}
-    The preceding message confirms that the `Zend OPcache` is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}.
+    The preceding message confirms that the `Zend OPcache` is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}.
 
 6.	Verify that all [required PHP extensions]({{ page.baseurl }}/install-gde/system-requirements-tech.html#required-php-extensions) were installed:
 
@@ -203,7 +203,7 @@ There is more than one way to install PHP 7.1 on CentOS; the following is a sugg
 		Zend Engine v3.1.0, Copyright (c) 1998-2017 Zend Technologies with Zend OPcache v7.1.6, Copyright (c) 1999-2017, by Zend Technologies
 
     {:.bs-callout .bs-callout-info}
-    The preceding message confirms that the `Zend OPcache` is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}.
+    The preceding message confirms that the `Zend OPcache` is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}.
 
 6.	Verify that all [required PHP extensions]({{ page.baseurl }}/install-gde/system-requirements-tech.html#required-php-extensions) were installed:
 
diff --git a/guides/v2.2/install-gde/prereq/php-ubuntu.md b/guides/v2.2/install-gde/prereq/php-ubuntu.md
index d77395ca184..e8348edc3bd 100644
--- a/guides/v2.2/install-gde/prereq/php-ubuntu.md
+++ b/guides/v2.2/install-gde/prereq/php-ubuntu.md
@@ -37,7 +37,7 @@ To verify if PHP is installed already, enter `php -v`. If PHP is installed, a me
       with Zend OPcache v7.0.21-1~ubuntu14.04.1+deb.sury.org+1, Copyright (c) 1999-2017, by Zend Technologies
 
 {:.bs-callout .bs-callout-info}
-The preceding message confirms that the `Zend OPcache` is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with OPcache, see the [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}
+The preceding message confirms that the `Zend OPcache` is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with OPcache, see the [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}
 
 If PHP is installed, continue with the next prerequisite, [MySQL]({{ page.baseurl }}/install-gde/prereq/mysql.html).
 
@@ -70,7 +70,7 @@ If PHP is *not* installed, see one of the following sections:
 		Zend Engine v3.0.0, Copyright (c) 1998-2016 Zend Technologies with Zend OPcache v7.0.21-1~ubuntu16.04.1+deb.sury.org+1, Copyright (c) 1999-2016, by Zend Technologies
 
     {:.bs-callout .bs-callout-info}
-    The preceding message confirms that the `Zend OPcache` is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}.
+    The preceding message confirms that the `Zend OPcache` is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}.
 
 3.	Verify that all [required PHP extensions]({{ page.baseurl }}/install-gde/system-requirements-tech.html#required-php-extensions) were installed:
 
@@ -157,7 +157,7 @@ If PHP is *not* installed, see one of the following sections:
 		Zend Engine v3.1.0, Copyright (c) 1998-2017 Zend Technologies with Zend OPcache v7.1.7-1~ubuntu14.04.1+deb.sury.org+1, Copyright (c) 1999-2017, by Zend Technologies
 
     {:.bs-callout .bs-callout-info}
-    The preceding message confirms that the `Zend OPcache` is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}.
+    The preceding message confirms that the `Zend OPcache` is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}.
 
 3.	Verify that all [required PHP extensions]({{ page.baseurl }}/install-gde/system-requirements-tech.html#required-php-extensions) were installed:
 
diff --git a/guides/v2.2/install-gde/prereq/prereq-overview.md b/guides/v2.2/install-gde/prereq/prereq-overview.md
index 3eedb02117a..2970675bbc5 100644
--- a/guides/v2.2/install-gde/prereq/prereq-overview.md
+++ b/guides/v2.2/install-gde/prereq/prereq-overview.md
@@ -20,7 +20,7 @@ Before you install Magento, you must do all of the following:
 *	Make sure you can back up your entire system at various points during the installation so you can roll back in the {% glossarytooltip c57aef7c-97b4-4b2b-a999-8001accef1fe %}event{% endglossarytooltip %} of issues.
 
 {:.bs-callout .bs-callout-info}
-We assume you're installing the Magento 2 software in a _development environment_, which means you have [root user](http://www.linfo.org/root.html){:target="_blank"} access to the machine _and_ that the machine does not need to be highly secure. If you're setting up a more secure machine, we strongly recommend you consult a network administrator for additional assistance.
+We assume you're installing the Magento 2 software in a _development environment_, which means you have [root user](http://www.linfo.org/root.html){:target="_blank"} access to the machine _and_ that the machine does not need to be highly secure. If you're setting up a more secure machine, we strongly recommend you consult a network administrator for additional assistance.
 
 We strongly recommend you update and upgrade your operating system software. These upgrades can provide security and software fixes that might prevent future problems.
 
diff --git a/guides/v2.2/install-gde/system-requirements-tech.md b/guides/v2.2/install-gde/system-requirements-tech.md
index 2371ef67ba5..9276833c3c3 100644
--- a/guides/v2.2/install-gde/system-requirements-tech.md
+++ b/guides/v2.2/install-gde/system-requirements-tech.md
@@ -24,11 +24,11 @@ Upgrading the Magento applications and extensions you obtain from Magento Market
 
 ### Web servers
 
-*	[Apache 2.2 or 2.4](http://httpd.apache.org/download.cgi){:target="_blank"}
+*	[Apache 2.2 or 2.4](http://httpd.apache.org/download.cgi){:target="_blank"}
 
 	In addition, you must enable the Apache `mod_rewrite` and `mod_version` modules. The [`mod_rewrite`](https://httpd.apache.org/docs/2.4/mod/mod_rewrite.html) module enables the server to perform URL rewriting. The [`mod_version`](https://httpd.apache.org/docs/2.4/mod/mod_version.html) module provides flexible version checking for different `httpd` versions. For more information, see [our Apache documentation]({{ page.baseurl }}/install-gde/prereq/apache.html).
 
-*	[nginx 1.x](https://nginx.org/en/download.html){:target="_blank"}
+*	[nginx 1.x](https://nginx.org/en/download.html){:target="_blank"}
 
 ### Database
 
@@ -47,31 +47,31 @@ Magento only uses MySQL features compatible with MariaDB. MariaDB may not be com
 {:.bs-callout bs-callout-info}
 The [CentOS]({{ page.baseurl }}/install-gde/prereq/php-centos.html) and [Ubuntu]({{ page.baseurl }}/install-gde/prereq/php-ubuntu.html) PHP installation instructions include a step for installing these extensions.
 
-*	[bc-math](http://php.net/manual/en/book.bc.php){:target="_blank"} ({{site.data.var.ee}} only for 2.2.0 - 2.2.3. {{site.data.var.ee}} and {{site.data.var.ce}} as of 2.2.4.)\
-*   [ctype](http://php.net/manual/en/book.ctype.php){:target="_blank"}
-*   [curl](http://php.net/manual/en/book.curl.php){:target="_blank"}
-*   [dom](http://php.net/manual/en/book.dom.php){:target="_blank"}
-*   [gd](http://php.net/manual/en/book.image.php){:target="_blank"}, [ImageMagick 6.3.7](http://php.net/manual/en/book.imagick.php){:target="_blank"} (or later) or both
-*   [intl](http://php.net/manual/en/book.intl.php){:target="_blank"}
-*   [mbstring](http://php.net/manual/en/book.mbstring.php){:target="_blank"}
-*   [mcrypt](http://php.net/manual/en/book.mcrypt.php){:target="_blank"}
-*   [hash](http://php.net/manual/en/book.hash.php){:target="_blank"}
-*   [openssl](http://php.net/manual/en/book.openssl.php){:target="_blank"}
-*   [PDO/MySQL](http://php.net/manual/en/ref.pdo-mysql.php){:target="_blank"}
-*   [SimpleXML](http://php.net/manual/en/book.simplexml.php){:target="_blank"}
-*   [soap](http://php.net/manual/en/book.soap.php){:target="_blank"}
-*   [spl](http://php.net/manual/en/book.spl.php){:target="_blank"}
-*   [libxml](http://php.net/manual/en/book.libxml.php){:target="_blank"}
-*   [xsl](http://php.net/manual/en/book.xsl.php){:target="_blank"}
-*   [zip](http://php.net/manual/en/book.zip.php){:target="_blank"}
-*	[json](http://php.net/manual/en/book.json.php){:target="_blank"}
-*	[iconv](http://php.net/manual/en/book.iconv.php){:target="_blank"}
+*	[bc-math](http://php.net/manual/en/book.bc.php){:target="_blank"} ({{site.data.var.ee}} only for 2.2.0 - 2.2.3. {{site.data.var.ee}} and {{site.data.var.ce}} as of 2.2.4.)\
+*   [ctype](http://php.net/manual/en/book.ctype.php){:target="_blank"}
+*   [curl](http://php.net/manual/en/book.curl.php){:target="_blank"}
+*   [dom](http://php.net/manual/en/book.dom.php){:target="_blank"}
+*   [gd](http://php.net/manual/en/book.image.php){:target="_blank"}, [ImageMagick 6.3.7](http://php.net/manual/en/book.imagick.php){:target="_blank"} (or later) or both
+*   [intl](http://php.net/manual/en/book.intl.php){:target="_blank"}
+*   [mbstring](http://php.net/manual/en/book.mbstring.php){:target="_blank"}
+*   [mcrypt](http://php.net/manual/en/book.mcrypt.php){:target="_blank"}
+*   [hash](http://php.net/manual/en/book.hash.php){:target="_blank"}
+*   [openssl](http://php.net/manual/en/book.openssl.php){:target="_blank"}
+*   [PDO/MySQL](http://php.net/manual/en/ref.pdo-mysql.php){:target="_blank"}
+*   [SimpleXML](http://php.net/manual/en/book.simplexml.php){:target="_blank"}
+*   [soap](http://php.net/manual/en/book.soap.php){:target="_blank"}
+*   [spl](http://php.net/manual/en/book.spl.php){:target="_blank"}
+*   [libxml](http://php.net/manual/en/book.libxml.php){:target="_blank"}
+*   [xsl](http://php.net/manual/en/book.xsl.php){:target="_blank"}
+*   [zip](http://php.net/manual/en/book.zip.php){:target="_blank"}
+*	[json](http://php.net/manual/en/book.json.php){:target="_blank"}
+*	[iconv](http://php.net/manual/en/book.iconv.php){:target="_blank"}
 
 #### PHP OPcache
 
-We strongly recommend you verify that [PHP OPcache](http://php.net/manual/en/intro.opcache.php){:target="_blank"} is enabled for performance reasons. The OPcache is enabled in many PHP distributions. To verify if it is installed, see our PHP documentation for [CentOS]({{ page.baseurl }}/install-gde/prereq/php-centos.html){:target="_blank"} or [Ubuntu]({{ page.baseurl }}/install-gde/prereq/php-ubuntu.html){:target="_blank"}.
+We strongly recommend you verify that [PHP OPcache](http://php.net/manual/en/intro.opcache.php){:target="_blank"} is enabled for performance reasons. The OPcache is enabled in many PHP distributions. To verify if it is installed, see our PHP documentation for [CentOS]({{ page.baseurl }}/install-gde/prereq/php-centos.html){:target="_blank"} or [Ubuntu]({{ page.baseurl }}/install-gde/prereq/php-ubuntu.html){:target="_blank"}.
 
-If you must install it separately, see the [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}.
+If you must install it separately, see the [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}.
 
 #### PHP settings
 
@@ -105,14 +105,14 @@ Mail Transfer Agent (MTA) or an SMTP server
 
     {{site.data.var.ee}} version 2.2.x supports the following Elasticsearch versions:
 
-    *	Elasticsearch [5.x](https://www.elastic.co/downloads/past-releases/elasticsearch-5-2-2){:target="_blank"}
-    *	Elasticsearch [2.x](https://www.elastic.co/downloads/past-releases/elasticsearch-2-4-5){:target="_blank"}
+    *	Elasticsearch [5.x](https://www.elastic.co/downloads/past-releases/elasticsearch-5-2-2){:target="_blank"}
+    *	Elasticsearch [2.x](https://www.elastic.co/downloads/past-releases/elasticsearch-2-4-5){:target="_blank"}
 
-    Magento 2.2.3 uses [Elasticsearch PHP client](https://github.com/elastic/elasticsearch-php){:target="_blank"} version 5.1. Before version 2.2.3, Magento used PHP client version 2.0.
+    Magento 2.2.3 uses [Elasticsearch PHP client](https://github.com/elastic/elasticsearch-php){:target="_blank"} version 5.1. Before version 2.2.3, Magento used PHP client version 2.0.
 
 *	RabbitMQ 3.5.x (compatible with 2.0 and later)
 
-    [RabbitMQ]({{ page.baseurl }}/config-guide/mq/rabbitmq-overview.html){:target="_blank"} can be used to publish messages to queue and to define the consumers that receive the messages asynchronously.
+    [RabbitMQ]({{ page.baseurl }}/config-guide/mq/rabbitmq-overview.html){:target="_blank"} can be used to publish messages to queue and to define the consumers that receive the messages asynchronously.
 
 *	Three master databases
 
@@ -120,7 +120,7 @@ Mail Transfer Agent (MTA) or an SMTP server
 
 ### Optional but recommended:
 
-*	[php_xdebug2.2.0](http://xdebug.org/download.php){:target="_blank"}> or later (development environments only; can have an adverse effect on performance)
+*	[php_xdebug2.2.0](http://xdebug.org/download.php){:target="_blank"}> or later (development environments only; can have an adverse effect on performance)
 
 {:.bs-callout .bs-callout-info}
 There is a known issue with xdebug that can affect Magento installations or access to the storefront or Magento Admin after installation.
diff --git a/guides/v2.2/magento-functional-testing-framework/2.3/test/actions.md b/guides/v2.2/magento-functional-testing-framework/2.3/test/actions.md
index d3dd7cc357d..68d474da6ee 100644
--- a/guides/v2.2/magento-functional-testing-framework/2.3/test/actions.md
+++ b/guides/v2.2/magento-functional-testing-framework/2.3/test/actions.md
@@ -414,7 +414,7 @@ Attribute|Type|Use|Description
 
 ### clickWithRightButton
 
-See [clickWithRightButton docs on codeception.com](http://codeception.com/docs/modules/WebDriver#clickWithRightButton){:target='"_blank"}.
+See [clickWithRightButton docs on codeception.com](http://codeception.com/docs/modules/WebDriver#clickWithRightButton){:target="_blank"}.
 
 Attribute|Type|Use|Description
 ---|---|---|---
diff --git a/guides/v2.2/migration/migration-troubleshooting.md b/guides/v2.2/migration/migration-troubleshooting.md
index 136187679fe..73f28c66388 100644
--- a/guides/v2.2/migration/migration-troubleshooting.md
+++ b/guides/v2.2/migration/migration-troubleshooting.md
@@ -31,7 +31,7 @@ This message appears because the Data Migration Tool runs internal tests to veri
 
 #### Possible solutions
 
-* Install the corresponding Magento 2 extensions from [Magento Marketplace](https://marketplace.magento.com/){:target:"_blank"}
+* Install the corresponding Magento 2 extensions from [Magento Marketplace](https://marketplace.magento.com/){:target:"_blank"}
 
     If the conflicting data originates from an extension which adds own database structure elements, then the Magento 2 version of the same extension may add such elements to the destination (Magento 2) database, thus fixing the issue.
 
diff --git a/guides/v2.3/architecture/tech-stack.md b/guides/v2.3/architecture/tech-stack.md
index c17ff017c08..99d590d81eb 100644
--- a/guides/v2.3/architecture/tech-stack.md
+++ b/guides/v2.3/architecture/tech-stack.md
@@ -70,4 +70,4 @@ For more information, see the [Functional Testing Framework]({{page.baseurl}}/mt
 
 ## Related topics
 
-[Architecturalbasics]({{ page.baseurl%7D%7D/architecture/archi_perspectives/ABasics_intro.html)
+[Architecturalbasics]({{ page.baseurl }}/architecture/archi_perspectives/ABasics_intro.html)
diff --git a/guides/v2.3/config-guide/cli/config-cli-subcommands-perf-data.md b/guides/v2.3/config-guide/cli/config-cli-subcommands-perf-data.md
index a339a562489..9c6cc7c8246 100644
--- a/guides/v2.3/config-guide/cli/config-cli-subcommands-perf-data.md
+++ b/guides/v2.3/config-guide/cli/config-cli-subcommands-perf-data.md
@@ -519,7 +519,7 @@ Generates store views. Store views are distributed normally among store groups.
 
 Generates tax rates. XML profile node:
 
-
        <!-- Accepts name of {% glossarytooltip 6341499b-ead9-4836-9794-53d95eb48ea5 %}csv{% endglossarytooltip %} file with tax rates (<path to magento folder>/setup/src/Magento/Setup/Fixtures/_files) -->
+
        <!-- Accepts name of {% glossarytooltip 6341499b-ead9-4836-9794-53d95eb48ea5 %}csv{% endglossarytooltip %} file with tax rates (<path to magento folder>/setup/src/Magento/Setup/Fixtures/_files) -->
 <tax_rates_file>{csv file name}</tax_rates_file>
        
 
 ## Additional information    
diff --git a/guides/v2.3/config-guide/elasticsearch/es-overview.md b/guides/v2.3/config-guide/elasticsearch/es-overview.md
index 2e2d7dfb250..d3a73a89562 100644
--- a/guides/v2.3/config-guide/elasticsearch/es-overview.md
+++ b/guides/v2.3/config-guide/elasticsearch/es-overview.md
@@ -33,10 +33,10 @@ In Magento 2.1 for the first time, you can use [Elasticsearch](https://www.elast
 ### Supported versions {#es-spt-versions}
 {{site.data.var.ee}} version 2.2.x supports the following Elasticsearch versions:
 
-*	Elasticsearch [5.x](https://www.elastic.co/downloads/past-releases/elasticsearch-5-2-2){:target="_blank"}
-*	Elasticsearch [2.x](https://www.elastic.co/downloads/past-releases/elasticsearch-2-4-5){:target="_blank"}
+*	Elasticsearch [5.x](https://www.elastic.co/downloads/past-releases/elasticsearch-5-2-2){:target="_blank"}
+*	Elasticsearch [2.x](https://www.elastic.co/downloads/past-releases/elasticsearch-2-4-5){:target="_blank"}
 
-Magento 2.2.3 uses [Elasticsearch PHP client](https://github.com/elastic/elasticsearch-php){:target="_blank"} version 5.1. (Before version 2.2.3, Magento used PHP client version 2.0.)
+Magento 2.2.3 uses [Elasticsearch PHP client](https://github.com/elastic/elasticsearch-php){:target="_blank"} version 5.1. (Before version 2.2.3, Magento used PHP client version 2.0.)
 
 ### Recommended configuration {#es-arch}
 
@@ -196,7 +196,7 @@ Elasticsearch 5.x requires JDK 1.8 or higher. Elasticsearch 2.x requires JDK 1.7
 
 ## Additional resources {#es-resources}
 
-For additional information, see [Elasticsearch documentation](https://www.elastic.co/guide/en/elasticsearch/reference/2.4/index.html){:target=_"blank"}
+For additional information, see [Elasticsearch documentation](https://www.elastic.co/guide/en/elasticsearch/reference/2.4/index.html){:target="_blank"}
 
 #### Next
 
diff --git a/guides/v2.3/extension-dev-guide/message-queues/config-mq.md b/guides/v2.3/extension-dev-guide/message-queues/config-mq.md
index 57f7fdbc622..11a2fea1fb0 100644
--- a/guides/v2.3/extension-dev-guide/message-queues/config-mq.md
+++ b/guides/v2.3/extension-dev-guide/message-queues/config-mq.md
@@ -237,6 +237,6 @@ See [Migrate message queue configuration]({{page.baseurl}}/extension-dev-guide/m
 
 ### Related Topics
 
-*	[Message QueuesOverview]({{ page.baseurl%7D%7D/config-guide/mq/rabbitmq-overview.html)
-*	[Manage message queues withMySQL]({{ page.baseurl%7D%7D/config-guide/mq/manage-mysql.html)
-*	[InstallRabbitMQ]({{ page.baseurl%7D%7D/install-gde/prereq/install-rabbitmq.html)
+*	[Message QueuesOverview]({{ page.baseurl }}/config-guide/mq/rabbitmq-overview.html)
+*	[Manage message queues withMySQL]({{ page.baseurl }}/config-guide/mq/manage-mysql.html)
+*	[InstallRabbitMQ]({{ page.baseurl }}/install-gde/prereq/install-rabbitmq.html)
diff --git a/guides/v2.3/extension-dev-guide/message-queues/queue-migration.md b/guides/v2.3/extension-dev-guide/message-queues/queue-migration.md
index 8f20b36306a..1e90a6ed7a3 100644
--- a/guides/v2.3/extension-dev-guide/message-queues/queue-migration.md
+++ b/guides/v2.3/extension-dev-guide/message-queues/queue-migration.md
@@ -127,5 +127,5 @@ The first column in the following table lists the all the parameters in the `que
 
 #### Related topics
 
-*	[Message QueuesOverview]({{ page.baseurl%7D%7D/config-guide/mq/rabbitmq-overview.html)
-*	[Configure messagequeues]({{ page.baseurl%7D%7D/extension-dev-guide/message-queues/config-mq.html)
+*	[Message QueuesOverview]({{ page.baseurl }}/config-guide/mq/rabbitmq-overview.html)
+*	[Configure messagequeues]({{ page.baseurl }}/extension-dev-guide/message-queues/config-mq.html)
diff --git a/guides/v2.3/frontend-dev-guide/templates/template-sample.md b/guides/v2.3/frontend-dev-guide/templates/template-sample.md
index 3adfae8acec..df80d2094a5 100644
--- a/guides/v2.3/frontend-dev-guide/templates/template-sample.md
+++ b/guides/v2.3/frontend-dev-guide/templates/template-sample.md
@@ -16,7 +16,7 @@ In the Magento basic Blank theme, in the mini shopping cart, products are listed
 
 OrangeCo decided they want to change this and display the product list before the **Go to Checkout** button.
 
-The template responsible for displaying the mini-shopping cart items and controls is [`/view/frontend/web/template/minicart/content.html`]({{site.mage2300url}}app/code/Magento/Checkout/view/frontend/web/template/minicart/content.html){:target="\_blank"}.
+The template responsible for displaying the mini-shopping cart items and controls is [`/view/frontend/web/template/minicart/content.html`]({{site.mage2300url}}app/code/Magento/Checkout/view/frontend/web/template/minicart/content.html){:target="_blank"}.
 Here is the part of the code OrangeCo worked with:
 
 ![code1]({{site.baseurl}}/common/images/templ_overview_code121.png)
diff --git a/guides/v2.3/frontend-dev-guide/themes/theme-create.md b/guides/v2.3/frontend-dev-guide/themes/theme-create.md
index 7e3c9828140..67fb6132e92 100644
--- a/guides/v2.3/frontend-dev-guide/themes/theme-create.md
+++ b/guides/v2.3/frontend-dev-guide/themes/theme-create.md
@@ -31,7 +31,7 @@ The high-level steps required to add a new theme in the Magento system are the f
 
 ## Recommended reading
 
-* [Checklist of modules]({{site.mage2300url}}app/code/Magento){:target="\_blank"}
+* [Checklist of modules]({{site.mage2300url}}app/code/Magento){:target="_blank"}
 * [Static view files processing]({{page.baseurl}}/config-guide/cli/config-cli-subcommands-static-view.html)
 
 ## Create a theme directory
@@ -85,9 +85,9 @@ If you change the theme title or parent theme information in `theme.xml` after a
 
 ## Make your theme a Composer package {#fedg_create_theme_composer}
 
-Magento default themes are distributed as [Composer](https://getcomposer.org/){:target="\_blank"} packages.
+Magento default themes are distributed as [Composer](https://getcomposer.org/){:target="_blank"} packages.
 
-To distribute your theme as a package, add a `composer.json` file to the theme directory and register the package on a packaging server. A default public packaging server is [https://packagist.org/](https://packagist.org/){:target="\_blank"}.
+To distribute your theme as a package, add a `composer.json` file to the theme directory and register the package on a packaging server. A default public packaging server is [https://packagist.org/](https://packagist.org/){:target="_blank"}.
 
 The `composer.json` file provides theme dependency information. Refer to a current `theme.xml` file for the correct dependancies and their versions. If your parent theme is something other than `Magento/blank`, you may need additional modules in the `"require"` section.
 
@@ -137,7 +137,7 @@ To register your theme in the system, add a `registration.php` file in your them
 
 Where `` is your vendor name and `` is the theme code.
 
-For illustration, see the [registration.php]({{site.mage2300url}}app/design/frontend/Magento/luma/registration.php){:target="\_blank"} file in the Magento Luma theme.
+For illustration, see the [registration.php]({{site.mage2300url}}app/design/frontend/Magento/luma/registration.php){:target="_blank"} file in the Magento Luma theme.
 
 ## Configure images {#fedg_create_theme_how-to-images}
 
diff --git a/guides/v2.3/get-started/create-integration.md b/guides/v2.3/get-started/create-integration.md
index dc35200f5b1..7afd01b82f2 100644
--- a/guides/v2.3/get-started/create-integration.md
+++ b/guides/v2.3/get-started/create-integration.md
@@ -151,7 +151,7 @@ Change directories to your `Setup` directory. Create a `InstallData.php` file th
          * @param ConfigBasedIntegrationManager $integrationManager
          */
 
-        public function __construct(ConfigBasedIntegrationManager $integrationManager)
+        public function __construct(ConfigBasedIntegrationManager $integrationManager)
         {
             $this->integrationManager = $integrationManager;
         }
diff --git a/guides/v2.3/install-gde/prereq/apache.md b/guides/v2.3/install-gde/prereq/apache.md
index 95ac2e22cd3..33cbfe3d0a0 100644
--- a/guides/v2.3/install-gde/prereq/apache.md
+++ b/guides/v2.3/install-gde/prereq/apache.md
@@ -26,7 +26,7 @@ If you're new to all this and need some help getting started, we suggest the fol
 
 ## Important: Apache rewrites and .htaccess {#apache-help-rewrite}
 
-This topic discusses how to enable Apache 2.2 rewrites and specify a setting for the [distributed configuration file, `.htaccess`](http://httpd.apache.org/docs/current/howto/htaccess.html){:target="_blank"}.
+This topic discusses how to enable Apache 2.2 rewrites and specify a setting for the [distributed configuration file, `.htaccess`](http://httpd.apache.org/docs/current/howto/htaccess.html){:target="_blank"}.
 
 Magento uses server rewrites and `.htaccess` to provide directory-level instructions for Apache. The following instructions are included in all of the other sections in this topic as well.
 
@@ -113,7 +113,7 @@ To upgrade to Apache 2.4:
 		apt-get install -y apache2
 
 {:.bs-callout .bs-callout-info}
-If the 'apt-get install' command fails because of unmet dependencies, consult a resource like [http://askubuntu.com](http://askubuntu.com/questions/140246/how-do-i-resolve-unmet-dependencies-after-adding-a-ppa){:target="_blank"}.
+If the 'apt-get install' command fails because of unmet dependencies, consult a resource like [http://askubuntu.com](http://askubuntu.com/questions/140246/how-do-i-resolve-unmet-dependencies-after-adding-a-ppa){:target="_blank"}.
 
 3.	Verify the installation.
 
@@ -183,7 +183,7 @@ If you encounter 403 Forbidden errors when trying to access the Magento site, yo
 
 #### Solving 403 Forbidden errors for Apache 2.4 {#install-apache-403_2.4}
 
-To enable web site visitors to access your site, use one of the [Require directives](http://httpd.apache.org/docs/2.4/howto/access.html){:target="_blank"}.
+To enable web site visitors to access your site, use one of the [Require directives](http://httpd.apache.org/docs/2.4/howto/access.html){:target="_blank"}.
 
 For example:
 
@@ -195,11 +195,11 @@ For example:
 	
 
 {:.bs-callout .bs-callout-info}
-The preceding values for `Order` might not work in all cases. For more information, see the [Apache documentation](https://httpd.apache.org/docs/2.4/mod/mod_access_compat.html#order){:target="_blank"}.
+The preceding values for `Order` might not work in all cases. For more information, see the [Apache documentation](https://httpd.apache.org/docs/2.4/mod/mod_access_compat.html#order){:target="_blank"}.
 
 #### Solving 403 Forbidden errors for Apache 2.2 {#install-apache-403_2.2}
 
-To enable web site visitors to access your site, use the [Allow directive](http://httpd.apache.org/docs/2.2/mod/mod_authz_host.html#allow){:target="_blank"}.
+To enable web site visitors to access your site, use the [Allow directive](http://httpd.apache.org/docs/2.2/mod/mod_authz_host.html#allow){:target="_blank"}.
 
 For example:
 
@@ -211,7 +211,7 @@ For example:
 	
 
 {:.bs-callout .bs-callout-info}
-The preceding values for `Order` might not work in all cases. For more information, see the [Apache documentation](https://httpd.apache.org/docs/2.2/mod/mod_authz_host.html#order){:target="_blank"}.
+The preceding values for `Order` might not work in all cases. For more information, see the [Apache documentation](https://httpd.apache.org/docs/2.2/mod/mod_authz_host.html#order){:target="_blank"}.
 {% endcollapsible %}
 
 #### Related topics:
diff --git a/guides/v2.3/install-gde/prereq/install-rabbitmq.md b/guides/v2.3/install-gde/prereq/install-rabbitmq.md
index 8b3b2bf46cd..387ae048def 100644
--- a/guides/v2.3/install-gde/prereq/install-rabbitmq.md
+++ b/guides/v2.3/install-gde/prereq/install-rabbitmq.md
@@ -37,10 +37,10 @@ This command also installs the required Erlang packages.
 
 If you have an older version of Ubuntu, RabbitMQ recommends installing the package from their {% glossarytooltip a3c8f20f-b067-414e-9781-06378c193155 %}website{% endglossarytooltip %}.
 
-1. Download [rabbitmq-server_3.6.6-1_all.deb](https://www.rabbitmq.com/releases/rabbitmq-server/v3.6.6/rabbitmq-server_3.6.6-1_all.deb){:target="_blank"}.
+1. Download [rabbitmq-server_3.6.6-1_all.deb](https://www.rabbitmq.com/releases/rabbitmq-server/v3.6.6/rabbitmq-server_3.6.6-1_all.deb){:target="_blank"}.
 2. Install the package with `dpkg`.
 
-Refer to [Installing on Debian/Ubuntu](https://www.rabbitmq.com/install-debian.html){:target="_blank"} for more information.
+Refer to [Installing on Debian/Ubuntu](https://www.rabbitmq.com/install-debian.html){:target="_blank"} for more information.
 
 ## Install RabbitMQ on CentOS {#centos-install}
 
@@ -48,7 +48,7 @@ Refer to [Installing on Debian/Ubuntu](https://www.rabbitmq.com/install-debian.h
 
 RabbitMQ was written using the Erlang programming language, which must be installed on the same system as RabbitMQ.
 
-See [Manual installation](https://www.erlang-solutions.com/resources/download.html){:target="_blank"} for more information.
+See [Manual installation](https://www.erlang-solutions.com/resources/download.html){:target="_blank"} for more information.
 
 Run the following commands to install this feature.
 ```bash
@@ -62,7 +62,7 @@ rpm -Uvh erlang-solutions-1.0-1.noarch.rpm
 
 The RabbitMQ server is included on CentOS, but the version is often old. RabbitMQ recommends installing the package from their website.
 
-1. Download [rabbitmq-server-3.5.6-1.noarch.rpm](https://www.rabbitmq.com/releases/rabbitmq-server/v3.5.6/rabbitmq-server-3.5.6-1.noarch.rpm){:target="_blank"}.
+1. Download [rabbitmq-server-3.5.6-1.noarch.rpm](https://www.rabbitmq.com/releases/rabbitmq-server/v3.5.6/rabbitmq-server-3.5.6-1.noarch.rpm){:target="_blank"}.
 2. Run the following commands as a user with root permissions:
 
 ```bash
@@ -72,7 +72,7 @@ rpm --import https://www.rabbitmq.com/rabbitmq-signing-key-public.asc
 yum install rabbitmq-server-3.5.6-1.noarch.rpm
 ```
 
-Refer to [Installing on RPM-based Linux](https://www.rabbitmq.com/install-rpm.html){:target="_blank"} for more information.
+Refer to [Installing on RPM-based Linux](https://www.rabbitmq.com/install-rpm.html){:target="_blank"} for more information.
 
 ## Configure RabbitMQ {#config}
 
diff --git a/guides/v2.3/install-gde/prereq/mysql.md b/guides/v2.3/install-gde/prereq/mysql.md
index 9503769f054..399e511ac65 100644
--- a/guides/v2.3/install-gde/prereq/mysql.md
+++ b/guides/v2.3/install-gde/prereq/mysql.md
@@ -23,9 +23,9 @@ The Magento application requires MySQL 5.6.x. Magento versions 2.1.2 and later a
 
 Magento _strongly_ recommends you observe the following standard when you set up your Magento database:
 
-*	Magento uses [MySQL database triggers](http://dev.mysql.com/doc/refman/5.0/en/triggers.html){:target="_blank"} to improve database access during reindexing. Magento does not support any custom triggers in the Magento database because custom triggers can introduce incompatibilities with future Magento versions.
-*	Familiarize yourself with [these potential MySQL trigger limitations](http://dev.mysql.com/doc/mysql-reslimits-excerpt/5.1/en/stored-program-restrictions.html){:target="_blank"} before you continue.
-*	If you use MySQL database replication, be aware that Magento does _not_ support MySQL statement-based replication. Make sure you use _only_ [row-based replication](http://dev.mysql.com/doc/refman/5.1/en/replication-formats.html){:target="_blank"}.
+*	Magento uses [MySQL database triggers](http://dev.mysql.com/doc/refman/5.0/en/triggers.html){:target="_blank"} to improve database access during reindexing. Magento does not support any custom triggers in the Magento database because custom triggers can introduce incompatibilities with future Magento versions.
+*	Familiarize yourself with [these potential MySQL trigger limitations](http://dev.mysql.com/doc/mysql-reslimits-excerpt/5.1/en/stored-program-restrictions.html){:target="_blank"} before you continue.
+*	If you use MySQL database replication, be aware that Magento does _not_ support MySQL statement-based replication. Make sure you use _only_ [row-based replication](http://dev.mysql.com/doc/refman/5.1/en/replication-formats.html){:target="_blank"}.
 
 {:.bs-callout .bs-callout-info}
 If your web server and database server are on different hosts, perform the tasks discussed in this topic on the database server host then see [Set up a remote MySQL database connection]({{page.baseurl }}/install-gde/prereq/mysql_remote.html).
@@ -79,7 +79,7 @@ To install MySQL 5.7 on Ubuntu 16:
 
 		mysql>
 
-5.	If you expect to import large numbers of products into Magento, you can increase the value for [`max_allowed_packet`](http://dev.mysql.com/doc/refman/5.6/en/program-variables.html){:target="_blank"} that is larger than the default, 16MB.
+5.	If you expect to import large numbers of products into Magento, you can increase the value for [`max_allowed_packet`](http://dev.mysql.com/doc/refman/5.6/en/program-variables.html){:target="_blank"} that is larger than the default, 16MB.
 
 	{% include install/mysql_max-allowed-packet-ubuntu.md %}
 
@@ -121,7 +121,7 @@ To install MySQL 5.6 on Ubuntu 14:
 
 		mysql>
 
-5.	If you expect to import large numbers of products into Magento, you can increase the value for [`max_allowed_packet`](http://dev.mysql.com/doc/refman/5.6/en/program-variables.html){:target="_blank"} that is larger than the default, 16MB.
+5.	If you expect to import large numbers of products into Magento, you can increase the value for [`max_allowed_packet`](http://dev.mysql.com/doc/refman/5.6/en/program-variables.html){:target="_blank"} that is larger than the default, 16MB.
 
 	{% include install/mysql_max-allowed-packet-ubuntu.md %}
 
@@ -129,7 +129,7 @@ To install MySQL 5.6 on Ubuntu 14:
 
 ### Installing MySQL 5.6 on Ubuntu 12 {#instgde-prereq-mysql56ubu12}
 
-To install MySQL 5.6 on Ubuntu 12, use the following instructions from [askubuntu.com](http://askubuntu.com/questions/433014/unable-to-install-mysql-5-6-in-ubuntu-12-04){:target="_blank"}.
+To install MySQL 5.6 on Ubuntu 12, use the following instructions from [askubuntu.com](http://askubuntu.com/questions/433014/unable-to-install-mysql-5-6-in-ubuntu-12-04){:target="_blank"}.
 
 1.	Enter the following commands in the order shown:
 
@@ -166,7 +166,7 @@ To install MySQL 5.6 on Ubuntu 12, use the following instructions from [askubunt
 
 		mysql>
 
-5.	If you expect to import large numbers of products into Magento, you can increase the value for [`max_allowed_packet`](http://dev.mysql.com/doc/refman/5.6/en/program-variables.html){:target="_blank"} that is larger than the default, 16MB.
+5.	If you expect to import large numbers of products into Magento, you can increase the value for [`max_allowed_packet`](http://dev.mysql.com/doc/refman/5.6/en/program-variables.html){:target="_blank"} that is larger than the default, 16MB.
 
 	{% include install/mysql_max-allowed-packet-ubuntu.md %}
 
@@ -181,7 +181,7 @@ The Magento application 2.1.2 and later are compatible with MySQL 5.7.
 
 ### Get MySQL 5.7 for CentOS 7
 
-The following procedure is based on [How to Install Latest MySQL 5.7.9 on RHEL/CentOS 7/6/5 and Fedora 23/22/21](http://www.tecmint.com/install-latest-mysql-on-rhel-centos-and-fedora){:target="_blank"}.
+The following procedure is based on [How to Install Latest MySQL 5.7.9 on RHEL/CentOS 7/6/5 and Fedora 23/22/21](http://www.tecmint.com/install-latest-mysql-on-rhel-centos-and-fedora){:target="_blank"}.
 
 As a user with `root` privileges, enter the following commands in the order shown:
 
@@ -192,7 +192,7 @@ Continue with [Install and configure MySQL 5.7 on CentOS 6 or 7](#mysql57-centos
 
 ### Get MySQL 5.7 for CentOS 6
 
-The following procedure is based on [How to Install Latest MySQL 5.7.9 on RHEL/CentOS 7/6/5 and Fedora 23/22/21](http://www.tecmint.com/install-latest-mysql-on-rhel-centos-and-fedora){:target="_blank"}.
+The following procedure is based on [How to Install Latest MySQL 5.7.9 on RHEL/CentOS 7/6/5 and Fedora 23/22/21](http://www.tecmint.com/install-latest-mysql-on-rhel-centos-and-fedora){:target="_blank"}.
 
 As a user with `root` privileges, enter the following commands in the order shown:
 
@@ -228,7 +228,7 @@ Continue with the next section.
 
 ## Installing and configuring MySQL 5.6 on CentOS {#instgde-prereq-mysql-centos}
 
-The following procedure is based on [Install MySQL Server 5.6 in CentOS 6.x and Red Hat 6.x Linux](http://sharadchhetri.com/2013/12/26/install-mysql-server-5-6-in-centos-6-x-and-red-hat-6-x-linux/){:target="_blank"}.
+The following procedure is based on [Install MySQL Server 5.6 in CentOS 6.x and Red Hat 6.x Linux](http://sharadchhetri.com/2013/12/26/install-mysql-server-5-6-in-centos-6-x-and-red-hat-6-x-linux/){:target="_blank"}.
 
 1.	*CentOS 6* Install the MySQL database:
 
@@ -269,7 +269,7 @@ The following procedure is based on [Install MySQL Server 5.6 in CentOS 6.x and
 
 		Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
 
-5.	If you expect to import large numbers of products into Magento, you can configure MySQL to use the [`max_allowed_packet`](http://dev.mysql.com/doc/refman/5.6/en/program-variables.html){:target="_blank"} parameter. We recommend a value of at least 16MB.
+5.	If you expect to import large numbers of products into Magento, you can configure MySQL to use the [`max_allowed_packet`](http://dev.mysql.com/doc/refman/5.6/en/program-variables.html){:target="_blank"} parameter. We recommend a value of at least 16MB.
 
 	{% include install/mysql_max-allowed-packet-centos.md %}
 
diff --git a/guides/v2.3/install-gde/prereq/nginx.md b/guides/v2.3/install-gde/prereq/nginx.md
index ed907a3a1c5..ef0c283be8c 100644
--- a/guides/v2.3/install-gde/prereq/nginx.md
+++ b/guides/v2.3/install-gde/prereq/nginx.md
@@ -10,7 +10,7 @@ functional_areas:
   - Setup
 ---
 
-Magento supports nginx 1.8 (or the [latest mainline version](http://nginx.org/en/linux_packages.html#mainline){:target="_blank}). You must also install the latest version of `php-fpm`.
+Magento supports nginx 1.8 (or the [latest mainline version](http://nginx.org/en/linux_packages.html#mainline){:target="_blank}). You must also install the latest version of `php-fpm`.
 
 Installation instructions vary based on which operating system you're using. See [PHP](php-centos-ubuntu.html) for instructions to install PHP on CentOS and Ubuntu.
 
diff --git a/guides/v2.3/install-gde/prereq/optional.md b/guides/v2.3/install-gde/prereq/optional.md
index f4fa1625c84..9916bb2274f 100644
--- a/guides/v2.3/install-gde/prereq/optional.md
+++ b/guides/v2.3/install-gde/prereq/optional.md
@@ -18,7 +18,7 @@ We strongly recommend you install NTP because otherwise, cron-related tasks migh
 The other optional utilities discussed in this topic might assist you with your installation; however, they are not required to install or use Magento.
 
 ## Installing and Configuring Network Time Protocol (NTP) {#install-optional-ntp}
-[NTP](http://www.ntp.org){:target="_blank"} enables servers to synchronize their system clocks using [globally available pool servers](http://www.pool.ntp.org/en){:target="_blank"}. Magento recommends you use NTP servers you trust, whether they are dedicated hardware solutions your internal network or external, public servers.
+[NTP](http://www.ntp.org){:target="_blank"} enables servers to synchronize their system clocks using [globally available pool servers](http://www.pool.ntp.org/en){:target="_blank"}. Magento recommends you use NTP servers you trust, whether they are dedicated hardware solutions your internal network or external, public servers.
 
 If you are deploying Magento on multiple hosts, NTP is a simple way to guarantee their clocks are all synchronized, no matter what time zone the servers are in. Also, cron-related tasks (such as indexing and transactional e-mails) depend on the server clock being accurate.
 
@@ -58,7 +58,7 @@ To install and configure NTP:
 
 ### Use NTP pool servers {#install-optional-ntp-servers}
 
-Selecting pool servers is up to you. If you use NTP pool servers, ntp.org recommends you use [pool servers](http://www.pool.ntp.org/en){:target="_blank"} that are close to your servers' time zone as discussed on the [NTP pool project help page](http://www.pool.ntp.org/en/use.html){:target="_blank"}. If you have a private NTP server that is available to all hosts in your Magento deployment, you can use that server instead.
+Selecting pool servers is up to you. If you use NTP pool servers, ntp.org recommends you use [pool servers](http://www.pool.ntp.org/en){:target="_blank"} that are close to your servers' time zone as discussed on the [NTP pool project help page](http://www.pool.ntp.org/en/use.html){:target="_blank"}. If you have a private NTP server that is available to all hosts in your Magento deployment, you can use that server instead.
 
 1.	Open `/etc/ntp.conf` in a text editor.
 
@@ -93,7 +93,7 @@ Selecting pool servers is up to you. If you use NTP pool servers, ntp.org recomm
 	If all else fails, try rebooting the server.
 
 ## Create phpinfo.php {#install-optional-phpinfo}
-[`phpinfo.php`](http://php.net/manual/en/function.phpinfo.php){:target="_blank"} displays a large amount of information about {% glossarytooltip bf703ab1-ca4b-48f9-b2b7-16a81fd46e02 %}PHP{% endglossarytooltip %} and its extensions.
+[`phpinfo.php`](http://php.net/manual/en/function.phpinfo.php){:target="_blank"} displays a large amount of information about {% glossarytooltip bf703ab1-ca4b-48f9-b2b7-16a81fd46e02 %}PHP{% endglossarytooltip %} and its extensions.
 
 {:.bs-callout .bs-callout-info}
 Use `phpinfo.php` in a development system _only_. It can be a security issue in production.
@@ -104,7 +104,7 @@ Add the following code anywhere in your web server's docroot:
 	// Show all information, defaults to INFO_ALL
 	phpinfo();
 
-For more information, see the [phpinfo manual page](http://php.net/manual/en/function.phpinfo.php){:target="_blank"}.
+For more information, see the [phpinfo manual page](http://php.net/manual/en/function.phpinfo.php){:target="_blank"}.
 
 To view the results, enter the following {% glossarytooltip a05c59d3-77b9-47d0-92a1-2cbffe3f8622 %}URL{% endglossarytooltip %} in your browser's location or address field:
 
@@ -117,14 +117,14 @@ If a 404 (Not Found) error displays, check the following:
 
 	[Help for Ubuntu](https://help.ubuntu.com/community/UFW)
 
-	[Help for CentOS](http://wiki.centos.org/HowTos/Network/IPTables){:target="_blank"}
+	[Help for CentOS](http://wiki.centos.org/HowTos/Network/IPTables){:target="_blank"}
 
 ## Install phpmyadmin {#install-optional-phpmyadmin}
 `phpmyadmin` is an easy-to-use, free database administration utility. You can use it to check and manipulate the contents of your database. You must log in to `phpmyadmin` as the MySQL database administrative user.
 
-For more information about `phpmyadmin`, see the [phpmyadmin home page](http://www.phpmyadmin.net/home_page/index.php){:target="_blank"}.
+For more information about `phpmyadmin`, see the [phpmyadmin home page](http://www.phpmyadmin.net/home_page/index.php){:target="_blank"}.
 
-For more detailed information about installation, see the [phpmyadmin installation documentation](http://docs.phpmyadmin.net/en/latest/setup.html#quick-install){:target="_blank"}.
+For more detailed information about installation, see the [phpmyadmin installation documentation](http://docs.phpmyadmin.net/en/latest/setup.html#quick-install){:target="_blank"}.
 
 {:.bs-callout .bs-callout-info}
 Use phpmyadmin in a development system _only_. It can be a security issue in production.
diff --git a/guides/v2.3/install-gde/prereq/php-centos-ubuntu.md b/guides/v2.3/install-gde/prereq/php-centos-ubuntu.md
index 6f678a52266..d42cab9e7bd 100644
--- a/guides/v2.3/install-gde/prereq/php-centos-ubuntu.md
+++ b/guides/v2.3/install-gde/prereq/php-centos-ubuntu.md
@@ -31,7 +31,7 @@ To verify if PHP is installed already, enter `php -v`. If {% glossarytooltip bf7
     Zend Engine v3.1.0, Copyright (c) 1998-2017 Zend Technologies with Zend OPcache v7.1.6, Copyright (c) 1999-2017, by Zend Technologies
 
 {:.bs-callout .bs-callout-info}
-The preceding message confirms that the Zend OPcache is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}.
+The preceding message confirms that the Zend OPcache is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}.
 
 If PHP is installed, continue with the next prerequisite, [MySQL]({{page.baseurl}}/install-gde/prereq/mysql.html).
 
@@ -39,7 +39,7 @@ If PHP is *not* installed, see the [PHP 7.1 on CentOS](#php-centos-71) section.
 
 ### CentOS repositories {#centos-php-repos}
 
-Linux systems provide software like PHP in one or more *repositories*. CentOS, unlike Ubuntu, has a set of [officially recommended repositories](https://wiki.centos.org/AdditionalResources/Repositories){:target="_blank"}. Other repositories are considered less safe for the reasons stated on the CentOS wiki.
+Linux systems provide software like PHP in one or more *repositories*. CentOS, unlike Ubuntu, has a set of [officially recommended repositories](https://wiki.centos.org/AdditionalResources/Repositories){:target="_blank"}. Other repositories are considered less safe for the reasons stated on the CentOS wiki.
 
 We're not aware that you can install PHP 7.1 or 7.2 from a CentOS-recommended repository. Therefore, you must consider the following:
 
@@ -48,9 +48,9 @@ We're not aware that you can install PHP 7.1 or 7.2 from a CentOS-recommended re
 	You should also consider upgrading to a later version of CentOS that has the desired PHP version in a recommended repository.
 *	If you're setting up a development system, you can use any repository you wish.
 
-In this topic, we show how to install PHP using the [Inline with Upstream Stable (IUS)](https://ius.io/GettingStarted){:target="_blank"} repository, which is *not* on the CentOS recommended list. However, packages installed from IUS do not use the same names as CentOS-provided packages, so [no existing system packages are replaced](https://ius.io/Philosophy){:target="_blank"}.
+In this topic, we show how to install PHP using the [Inline with Upstream Stable (IUS)](https://ius.io/GettingStarted){:target="_blank"} repository, which is *not* on the CentOS recommended list. However, packages installed from IUS do not use the same names as CentOS-provided packages, so [no existing system packages are replaced](https://ius.io/Philosophy){:target="_blank"}.
 
-Before you continue, review their [Getting Started topic](https://ius.io/GettingStarted){:target="_blank"}.
+Before you continue, review their [Getting Started topic](https://ius.io/GettingStarted){:target="_blank"}.
 
 {:.bs-callout .bs-callout-warning}
 Magento does not officially recommend using the IUS repository. We discuss it here for example purposes only.
@@ -97,7 +97,7 @@ To install PHP 7.1 on CentOS 6 or 7:
 		Zend Engine v3.1.0, Copyright (c) 1998-2017 Zend Technologies with Zend OPcache v7.1.6, Copyright (c) 1999-2017, by Zend Technologies
 
     {:.bs-callout .bs-callout-info}
-    The preceding message confirms that the Zend OPcache is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the  [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}.
+    The preceding message confirms that the Zend OPcache is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the  [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}.
 
 6.	Verify that all [required PHP extensions]({{ page.baseurl }}/install-gde/system-requirements-tech.html#required-php-extensions) were installed:
 
@@ -170,7 +170,7 @@ To verify if PHP is installed already, enter `php -v`. If PHP is installed, a me
     Zend Engine v3.1.0, Copyright (c) 1998-2017 Zend Technologies with Zend OPcache v7.1.7-1~ubuntu14.04.1+deb.sury.org+1, Copyright (c) 1999-2017, by Zend Technologies
 
 {:.bs-callout .bs-callout-info}
-The preceding message confirms that the Zend OPcache is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with OPcache, see the [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}
+The preceding message confirms that the Zend OPcache is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with OPcache, see the [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}
 
 If PHP is installed, continue with the next prerequisite, [MySQL]({{page.baseurl}}/install-gde/prereq/mysql.html).
 
@@ -202,7 +202,7 @@ To install PHP 7.1 on Ubuntu 14 or 16:
 		Zend Engine v3.1.0, Copyright (c) 1998-2017 Zend Technologies with Zend OPcache v7.1.7-1~ubuntu14.04.1+deb.sury.org+1, Copyright (c) 1999-2017, by Zend Technologies
 
     {:.bs-callout .bs-callout-info}
-    The preceding message confirms that the Zend OPcache is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}.
+    The preceding message confirms that the Zend OPcache is installed. We strongly recommend using the OPcache for performance reasons. If your PHP distribution does not come with the OPcache, see the [PHP OPcache documentation](http://php.net/manual/en/opcache.setup.php){:target="_blank"}.
 
 3.	Verify that all [required PHP extensions]({{ page.baseurl }}/install-gde/system-requirements-tech.html#required-php-extensions) were installed:
 
diff --git a/guides/v2.3/install-gde/prereq/php-settings.md b/guides/v2.3/install-gde/prereq/php-settings.md
index b2d2be76706..64794b5c2e2 100644
--- a/guides/v2.3/install-gde/prereq/php-settings.md
+++ b/guides/v2.3/install-gde/prereq/php-settings.md
@@ -22,14 +22,14 @@ This topic discusses how to set required {% glossarytooltip bf703ab1-ca4b-48f9-b
 	*	Compiling code or deploying static assets, `756M`
     *	Installing and updating Magento components from Magento Marketplace, `2G`
     *	Testing, `~3-4G`
-*	Disable [`asp_tags`](http://php.net/manual/en/ini.core.php#ini.asp-tags){:target="_blank"}
+*	Disable [`asp_tags`](http://php.net/manual/en/ini.core.php#ini.asp-tags){:target="_blank"}
 
 	If `asp_tags are` enabled, errors display when accessing PHTML templates.
 
 	`asp_tags` were removed in PHP 7.
-*	Enable [`opcache.save_comments`](http://php.net/manual/en/opcache.configuration.php#ini.opcache.save_comments){:target="_blank"}, which is required for Magento 2.1 and later.
+*	Enable [`opcache.save_comments`](http://php.net/manual/en/opcache.configuration.php#ini.opcache.save_comments){:target="_blank"}, which is required for Magento 2.1 and later.
 
-	We recommend you enable the [PHP OpCache](http://php.net/manual/en/intro.opcache.php){:target="_blank"} for performance reasons. The OPcache is enabled in many PHP distributions.
+	We recommend you enable the [PHP OpCache](http://php.net/manual/en/intro.opcache.php){:target="_blank"} for performance reasons. The OPcache is enabled in many PHP distributions.
 
 	Magento 2.1 and later use PHP code comments for code generation.
 
@@ -80,7 +80,7 @@ If you have more than one `opcache.ini`, modify all of them.
 To set PHP options:
 
 1.	Open a `php.ini` in a text editor.
-3.	Locate your server's time zone in the available [time zone settings](http://php.net/manual/en/timezones.php){:target="_blank"}
+3.	Locate your server's time zone in the available [time zone settings](http://php.net/manual/en/timezones.php){:target="_blank"}
 4.	Locate the following setting and uncomment it if necessary:
 
 		date.timezone =
diff --git a/guides/v2.3/install-gde/system-requirements-tech.md b/guides/v2.3/install-gde/system-requirements-tech.md
index 38ed9eba475..3b75b007b13 100644
--- a/guides/v2.3/install-gde/system-requirements-tech.md
+++ b/guides/v2.3/install-gde/system-requirements-tech.md
@@ -47,24 +47,24 @@ Magento, with assistance from our community, is implementing PHP 7.2 compatibili
 {:.bs-callout .bs-callout-info}
 The [PHP installation instructions](prereq/php-centos-ubuntu.html) include a step for installing these extensions.
 
-*	[bc-math](http://php.net/manual/en/book.bc.php){:target="_blank"} ({{site.data.var.ee}} only)
-* [ctype](http://php.net/manual/en/book.ctype.php){:target="_blank"}
-*	[curl](http://php.net/manual/en/book.curl.php){:target="_blank"}
-* [dom](http://php.net/manual/en/book.dom.php){:target="_blank"}
-*	[gd](http://php.net/manual/en/book.image.php){:target="_blank"}
-*	[intl](http://php.net/manual/en/book.intl.php){:target="_blank"}
-*	[mbstring](http://php.net/manual/en/book.mbstring.php){:target="_blank"}
-*	[hash](http://php.net/manual/en/book.hash.php){:target="_blank"}
-*	[openssl](http://php.net/manual/en/book.openssl.php){:target="_blank"}
-*	[PDO/MySQL](http://php.net/manual/en/ref.pdo-mysql.php){:target="_blank"}
-*	[SimpleXML](http://php.net/manual/en/book.simplexml.php){:target="_blank"}
-*	[soap](http://php.net/manual/en/book.soap.php){:target="_blank"}
-* [spl](http://php.net/manual/en/book.spl.php){:target="_blank"}
-*	[libxml](http://php.net/manual/en/book.libxml.php){:target="_blank"}
-*	[xsl](http://php.net/manual/en/book.xsl.php){:target="_blank"}
-*	[azip](http://php.net/manual/en/book.zip.php){:target="_blank"}
-*	[json](http://php.net/manual/en/book.json.php){:target="_blank"}
-*	[iconv](http://php.net/manual/en/book.iconv.php){:target="_blank"}
+*	[bc-math](http://php.net/manual/en/book.bc.php){:target="_blank"} ({{site.data.var.ee}} only)
+* [ctype](http://php.net/manual/en/book.ctype.php){:target="_blank"}
+*	[curl](http://php.net/manual/en/book.curl.php){:target="_blank"}
+* [dom](http://php.net/manual/en/book.dom.php){:target="_blank"}
+*	[gd](http://php.net/manual/en/book.image.php){:target="_blank"}
+*	[intl](http://php.net/manual/en/book.intl.php){:target="_blank"}
+*	[mbstring](http://php.net/manual/en/book.mbstring.php){:target="_blank"}
+*	[hash](http://php.net/manual/en/book.hash.php){:target="_blank"}
+*	[openssl](http://php.net/manual/en/book.openssl.php){:target="_blank"}
+*	[PDO/MySQL](http://php.net/manual/en/ref.pdo-mysql.php){:target="_blank"}
+*	[SimpleXML](http://php.net/manual/en/book.simplexml.php){:target="_blank"}
+*	[soap](http://php.net/manual/en/book.soap.php){:target="_blank"}
+* [spl](http://php.net/manual/en/book.spl.php){:target="_blank"}
+*	[libxml](http://php.net/manual/en/book.libxml.php){:target="_blank"}
+*	[xsl](http://php.net/manual/en/book.xsl.php){:target="_blank"}
+*	[azip](http://php.net/manual/en/book.zip.php){:target="_blank"}
+*	[json](http://php.net/manual/en/book.json.php){:target="_blank"}
+*	[iconv](http://php.net/manual/en/book.iconv.php){:target="_blank"}
 
 #### PHP OPcache
 
@@ -101,14 +101,14 @@ Mail Transfer Agent (MTA) or an SMTP server
 
     {{site.data.var.ee}} version 2.3.x supports the following Elasticsearch versions:
 
-    *	Elasticsearch [5.2.x](https://www.elastic.co/downloads/past-releases/elasticsearch-5-2-2){:target="_blank"}
-    *	Elasticsearch [2.x](https://www.elastic.co/downloads/past-releases/elasticsearch-2-4-5){:target="_blank"}
+    *	Elasticsearch [5.2.x](https://www.elastic.co/downloads/past-releases/elasticsearch-5-2-2){:target="_blank"}
+    *	Elasticsearch [2.x](https://www.elastic.co/downloads/past-releases/elasticsearch-2-4-5){:target="_blank"}
 
-    Magento 2.3 uses [Elasticsearch PHP client](https://github.com/elastic/elasticsearch-php){:target="_blank"} version 5.2. (Before version 2.3, Magento used PHP client version 5.1.)
+    Magento 2.3 uses [Elasticsearch PHP client](https://github.com/elastic/elasticsearch-php){:target="_blank"} version 5.2. (Before version 2.3, Magento used PHP client version 5.1.)
 
 *	RabbitMQ 3.7.x (compatible with 2.0 and later)
 
-    [RabbitMQ]({{page.baseurl}}/config-guide/mq/rabbitmq-overview.html){:target="_blank"} can be used to publish messages to queue and to define the consumers that receive the messages asynchronously.
+    [RabbitMQ]({{page.baseurl}}/config-guide/mq/rabbitmq-overview.html){:target="_blank"} can be used to publish messages to queue and to define the consumers that receive the messages asynchronously.
 
 ####	{{site.data.var.ee}} only
 
@@ -118,10 +118,10 @@ Mail Transfer Agent (MTA) or an SMTP server
 
 ### Optional but recommended
 
-*	[php_xdebug 2.5.x](http://xdebug.org/download.php){:target="_blank"} or later (development environments only; can have an adverse effect on performance)
+*	[php_xdebug 2.5.x](http://xdebug.org/download.php){:target="_blank"} or later (development environments only; can have an adverse effect on performance)
 
 {:.bs-callout .bs-callout-info}
 There is a known issue with `xdebug` that can affect Magento installations or access to the storefront or Magento Admin after installation. For details, see [Known issue with xdebug]({{page.baseurl}}/install-gde/trouble/tshoot_install-issues.html#known-devbeta-xdebug).
 
-* [`mcrypt`](http://php.net/manual/en/book.mcrypt.php){:target="_blank"}
+* [`mcrypt`](http://php.net/manual/en/book.mcrypt.php){:target="_blank"}
 *	PHPUnit (as a command-line tool) 6.2.0
diff --git a/guides/v2.3/ui_comp_guide/components/ui-wysiwyg.md b/guides/v2.3/ui_comp_guide/components/ui-wysiwyg.md
index 8cd66e87d7b..f6ada030283 100644
--- a/guides/v2.3/ui_comp_guide/components/ui-wysiwyg.md
+++ b/guides/v2.3/ui_comp_guide/components/ui-wysiwyg.md
@@ -5,12 +5,12 @@ title: WYSIWYG component
 menu_title: WYSIWYG component
 ---
 
-The WYSIWYG component is an {% glossarytooltip edb42858-1ff8-41f9-80a6-edf0d86d7e10 %}adapter{% endglossarytooltip %} for [TinyMCE v4](https://www.tinymce.com/){:target="\_blank"} that integrates an editor instance with the [form component]({{ page.baseurl }}/ui_comp_guide/components/ui-form.html). It expects a complete {% glossarytooltip f0dcf847-ce21-4b88-8b45-83e1cbf08100 %}widget{% endglossarytooltip %} declaration in the `content` option, which should contain both {% glossarytooltip 8f407f13-4350-449b-9dc5-217dcf01bc42 %}markup{% endglossarytooltip %} and the script responsible for creating the editor's instance.
+The WYSIWYG component is an {% glossarytooltip edb42858-1ff8-41f9-80a6-edf0d86d7e10 %}adapter{% endglossarytooltip %} for [TinyMCE v4](https://www.tinymce.com/){:target="_blank"} that integrates an editor instance with the [form component]({{ page.baseurl }}/ui_comp_guide/components/ui-form.html). It expects a complete {% glossarytooltip f0dcf847-ce21-4b88-8b45-83e1cbf08100 %}widget{% endglossarytooltip %} declaration in the `content` option, which should contain both {% glossarytooltip 8f407f13-4350-449b-9dc5-217dcf01bc42 %}markup{% endglossarytooltip %} and the script responsible for creating the editor's instance.
 
 Magento supports all selector, plugin, and toolbar/menu configuration options supported by the TinyMCE v4 `tinymce.init()` method. However, Magento doesn't validate TinyMCE configuration options or flag invalid values before adding the editor to a page.
 
 
        
-Refer to [TinyMCE's documentation](https://www.tinymce.com/docs/){:target="\_blank"} for more information.
+Refer to [TinyMCE's documentation](https://www.tinymce.com/docs/){:target="_blank"} for more information.
 
        
 
 ## Configuration options