Magento CE 2.1.6 Release Notes

Release notes updated on April 28, 2017.

Upgrading to this release can cause problems with image resizing. Please see Image Resize Issue with Magento 2.1.6 for an overview of these post-upgrade issues and our suggested workaround.

We are pleased to present Magento Community Edition 2.1.6. This release includes important performance enhancements for your Magento installation, especially for operations that involve the category page as well as image resizing.

Looking for the Magento Enterprise Cloud Edition Release Notes?

Highlights

Magento 2.1.6 contains over 15 significant performance enhancements when compared to 2.1.5. Look for the following highlights in this release:

  • Improved performance of the Category page

    • loading configurable products from the database is now up to 5x faster

    • price calculations are now up to 3-5% faster

    • stock validation is now up to 20% faster

  • Optimized image resizing

    • image resize operations performed from the command line interface now generate images of all sizes. See magento catalog:images:resize for more information.

    • image resize operations from the Admin have been fixed

    • significant decrease in the number of file system operations when processing images on frontend

    • caching of image metadata is up to 50% faster, depending on store size

  • Improved performance of layered navigation

    • layered navigation is now up to 3% faster due to the caching of attribute options
  • Minimized indexing operations after product import

Functional fixes and enhancements

We address the following functional fixes and enhancements in this release.

Catalog

  • Magento no longer locks the category_product_entity table. Unlocking this table reduces the potential of lock-related timeouts that can occur when indexing and checkout operations run in parallel. Previously, Magento locked the category_product_entity table.
  • The storefront now displays images that Magento resizes during product save operations, rather than resizing the product on the storefront. Previously, the image path contained store_id, and during save operations, Magento resized images for images the default store only.

Users have encountered problems displaying images after upgrading their software to Magento 2.1.6. These problems range from incomplete loading to the total inability to load images. Consequently, if you saved a product and didn’t open it on the storefront before upgrading to 2.1.6, you’ll need to apply a workaround.

Workaround: To correct problems with image loading, choose one of these two workarounds:

  • Run php bin/magento catalog:images:resize

or

  • Save (or resave) the product with the associated image in the Admin panel.
  • The \Magento\CatalogInventory\Model\Stock\Status\getStockId() method now returns the correct values.
  • The \Magento\CatalogInventory\Model\Stock\Status\getStockId() method now returns the correct values.

Configurable products

  • The check that Magento runs to confirm a configurable product’s readiness for sale is now faster. (The isSalable method checks that a configurable product can be sold (that is, is in a saleable state)).
  • Magento no longer calculates configurable product special prices on the category page. Previously, Magento calculated special prices on the category page, but did not display them.

Indexers

  • Magento now runs a selective partial re-indexing operation after import if you enabled Update on Schedule. Previously, Magento ran a full reindex no matter which index mode was set.

Import

  • Magento now displays imported product images in this order: first, the base image, then the additional images in the order in which they were listed in the CSV file. Previously, Magento displayed images in this unexpected order: first, an additional image, then the base image, and finally, all remaining additional images.

Miscellaneous

  • Magento now caches attribute options for the layered navigation feature. This reduces the number of queries to the database, and consequently improves performance.
  • Magento no longer performs unnecessary file check operations (for example, file_exists, is_file), which improves the performance of the category and product pages.
  • Magento now caches image metadata, which avoids the time-consuming need to read images for metadata loading.
  • Magento now shows a significant decrease in Redis traffic after upgrading 2.1.2 to 2.1.4.

Swatches

  • Magento no longer creates redundant objects when initializing a configurable product on the Category page.
  • You can now disable swatches for both the Catalog page and search results (quick or advanced). To disable swatches from these requests, disable Stores > Configuration > Catalog > Storefront > Show Swatches in Product List.
  • The logic that Magento uses to validate swatch attributes has been optimized.
  • Magento now caches swatch data in the block cache, which improves the responsiveness of the configurable product pages.

System requirements

Our technology stack is built on PHP and MySQL. For more information, see System Requirements.

Install the Magento software

You can get Magento Community Edition 2.1 from Github, Composer, or using a compressed archive.

See one of the following sections for more information:

Get the Magento CE software using Composer

The CE software is available from repo.magento.com. Before getting the CE software, familiarize yourself with the Composer metapackage prerequisites, then run

composer create-project --repository-url=https://repo.magento.com/ magento/project-community-edition=<version> <installation directory name>

where <version> is 2.1.0, 2.1.1, and so on

For example, to install Magento CE 2.1.1 in the magento2 directory:

composer create-project --repository-url=https://repo.magento.com/ magento/project-community-edition=2.1.1 magento2

Get a compressed archive

The following table discusses where to get the Magento software. We provide the following downloads:

  • Magento CE software only
  • Magento CE software with sample data (designed to help you learn Magento faster)

These packages are easy to get and install. You don’t need to use Composer, all you need to do is to upload a package to your Magento server or hosted platform, unpack it, and run the web-based Setup Wizard.

Archives are available in the following formats: .zip, .tar.bz2, .tar.gz

To get the Magento CE software archive:

  1. Go to http://magento.com/download.
  2. Choose either the software or the software and sample data:

    • Magento-CE-<version>.* (without sample data)
    • Magento-CE-<version>+Samples.* (with sample data)

    <version> is the three-digit release number (for example, 2.0.7, 2.1.0, and so on).

Complete the installation

After you get the CE software:

  1. Set file system ownership and permissions.
  2. Install the software:

Upgrade from an earlier version

See the following sections for more information.

Upgrade an existing installation from the GitHub repository

Developers who contribute to the CE codebase can upgrade manually from the Magento CE GitHub repository.

  1. Go to the Contributing Developers page.

  2. Follow the instructions to pull the updates from the repository and update using Composer.

Other upgrades

Other types of upgrades are discussed in Upgrade to Magento version 2.1 (June 22, 2016).

Migration toolkits

The Data Migration Tool helps transfer existing Magento 1.x store data to Magento 2.x. This command-line interface includes verification, progress tracking, logging, and testing functions. For installation instructions, see Install the Data Migration Tool. Consider exploring or contributing to the Magento Data Migration repository.

The Code Migration Toolkit helps transfer existing Magento 1.x store extensions and customizations to Magento 2.0.x. The command-line interface includes scripts for converting Magento 1.x modules and layouts.

Credits

Dear community members, thank you for your suggestions and bug reports.