Magento CE 2.1.1 Release Notes

We are pleased to present Magento Community Edition 2.1.1. This release includes several functional fixes and enhancements to the deployment of static assets.

Backward-incompatible changes are documented in Magento 2.1 backward incompatible changes.

Fixed issues

We address the following functional issues in this release.

Installation and upgrade

  • You can now run magento setup:upgrade --keep-generated in production mode. Previously, Magento would throw an error when you ran setup:upgrade after compiling DI. (This significantly curtailed your ability to deploy continuous integration.) (GITHUB-4795)
  • You can now upgrade 2.0.9 with sample data to 2.1.1.

Pricing

  • The Category page now displays current, rather than outdated, product prices.
  • Tier pricing now works correctly with full page cache. (GITHUB-5364)
  • Cart Price rules are now applied as expected to payment method conditions. Previously, discounts set in Cart Price rules were not applied during checkout.

Shopping cart

  • Magento now implements the minicart maximum display recently added item setting to your shopping cart. Previously, Magento displayed all the items in the shopping cart, even when the number of items exceeded this limit. (GITHUB-4750)

Performance

  • You can now quickly generate or preview multiple variations of a configurable product. (Saving these variations to the database can be time-consuming, if you have several thousand product options, and our efforts to improve performance continue.) Previously, Magento threw an Invalid Form key error is thrown while you tried to save a configurable product with variations.
  • We’ve improved the speed of static asset deployment.
  • The setup:static-content:deploy command now provides flags that you can use to exclude or include individual themes, areas, and locales. For more information, see (GITHUB-4294).
  • We’ve improved storefront performance when creating 2500 or more product variants.

Miscellaneous

  • You can now save products using the multiple select attribute value. Previously, you could not save values if using this attribute.
  • Magento now displays configurable products as expected after creation.
  • You can now save a product with images multiple times.
  • You can now log in successfully after creating a custom attribute. Previously, Magento would display an error message, and you could not log in, after first creating a custom attribute, then logging out.
  • You can now successfully place orders when the Enable and Configure Website Payments Standard Payment Action attribute is set to Sale. Previously, under these conditions, Magento would display an error message and not allow you to complete the purchase. (GITHUB-4785)
  • Attributes of the salesInvoiceRepository methods are now more appropriately type cast. (The datatype is now a nullable float.) Previously, due to the use of an incorrect datatype, Magento would produce an error when calling the salesInvoiceRepositoryV1GetList method. (GITHUB-3605)
  • Magento now correctly displays customer address during account creation. Previously, when you selected a default billing address during creation of a new customer account, Magento would not display the address.
  • You can now use Braintree as a payment method when applying reward points or store credit to an order.
  • The category page now shows the current price after Magento runs a scheduled update. Previously, the category page would not update the price after running a scheduled update. (GITHUB-4945)

Known issue

The Sales API does not currently support all the update operations on objects that you can execute from the Admin. (Objects in this context include orders, invoices, shipments, credit memos, and return merchandise authorizations.)   The Sales API

  • supports create, read, delete, and search operations on objects

  • does not support updates to order status or payment status. (Order status includes changes to processing, shipped, processed, and hold, while payment status includes authorized, charged, reject, and refund.)

You can run these operations from the Admin.

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).

Get the Magento CE software from GitHub

If you clone the Magento 2 GitHub repository, you cannot use the Magento software in a production environment. You cannot have a live store that accepts orders and so on.

Before proceeding, please familiarize yourself with these prerequisites, then run

git clone git@github.com:magento/magento2.git
cd magento2
git checkout tags/<version> [-b <version>]

where

<version> is 2.1.0, 2.1.1, and so on

[-b <version>] optionally checks out a new branch.

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.