Magento Open Source 2.1 Release Candidate 1 (RC1) Release Notes

We are pleased to present Magento 2.1 Release Candidate 1 (RC1). This release candidate build is not intended for production purposes. Instead, it provides the development community opportunities to:

  • preview the new features and fixes that Magento 2.1 GA will contain

  • contribute to the Magento 2.1 code base by identifying unresolved issues

  • test your 2.0 extensions against 2.1

We welcome your participation in this process! Please open any Open Source issues or Pull Requests on the Open Source GitHub repository. For more information on how to provide feedback and contribute on GitHub, see Code contributions.

Backward-incompatible changes are documented in Magento 2.0 Backward Incompatible Changes.

Highlights

Magento Open Source 2.1 includes several new features:

  • PayPal in-context checkout helps to increase conversion rates by allowing shoppers to pay with PayPal without leaving the merchant’s site. PayPal saved credit card capabilities allow merchants to securely store credit cards with PayPal so shoppers can make future purchases without re-entering their credit card information.

  • Braintree enhancements enable merchants to qualify for the simplest set of PCI compliance requirements by using Braintree Hosted Fields to collect all sensitive card holder information in checkout. Merchants retain complete control over their checkout style and layout because Braintree uses small, transparent iframes to replace individual payment fields. Merchants can now also access Braintree settlement reports from within the Magento Admin.

  • Improved management interfaces make it faster and easier to search for information in the Admin interface, set up global search synonyms, and create new product, category, and CMS content.

Known issue

Issue: Enabling Varnish causes the category menu to switch from http to https (GITHUB-4540)

Work-around: To use Varnish caching with an HTTP site, add rewrite rules such as the following in Magento’s root .htaccess:

RewriteCond %{HTTPS} on
RewriteCond %{REQUEST_URI} /yellow-fruit.html
RewriteRule (.*) http://%{HTTP_HOST}%{REQUEST_URI} [L]
RewriteCond %{HTTPS} on
RewriteCond %{REQUEST_URI} /red-fruit.html
RewriteRule (.*) http://%{HTTP_HOST}%{REQUEST_URI} [L]

Fixed issues

This release includes fixes for the following GitHub issues:

  • Web APIs no longer allow anonymous access by default. (GITHUB-3786)
  • The OAuth Token exchange expiration period is now calculated correctly. (GITHUB-3449)
  • Shipping Address is now exposed for the Orders API. (GITHUB-2628)
  • A Credit Memo REST API issue with updating attributes has been fixed. Previously, certain attributes (such as Order Status) were not updated when the user took action through the API. However, Magento updates these attributes when the same action is completed in the Admin interface. (GITHUB-4329)
  • Product update operations by either customers or store administrators no longer result in locking queries on catalog category product index. (GITHUB-4342)
  • The Order Repository getList method no longer returns the same shipping address for all orders. (GITHUB-4019)
  • A configurable product’s last attribute with price of zero (0) no longer results in an error. The user can configure the product, and the correct price results. (GITHUB-3912)
  • An error message that users typically received during upgrade has been improved. The message now clearly states when a user must login first to magento.com before continuing the upgrade process. (GITHUB-3059)
  • Magento now displays the correct product prices on the Configurable product page when catalog prices include tax. (GITHUB-2471)
  • The i18n:collect-phrases -m command now works correctly. Previously, this command would not find all important Magento phrases. (GITHUB-2630)
  • Plugins/interceptors now work with early stage single instance objects in Developer mode. (GITHUB-2674)
  • Admin order creation no longer fails when the “Include Tax In Order Total” option is set to yes. (GITHUB-2675)
  • The setup:di:compile script now compiles all files as expected. (GITHUB-2888)
  • Attribute ‘setup_version’ is missing for module error when defined as optional. (GITHUB-1493)

Technology stack

Our technology stack is built on PHP and MySQL. Magento 2.1 RC3 supports:

  • PHP 5.6
  • PHP 7.0.2
  • PHP 7.0.6 + up until 7.1
  • MySQL 5.6.

We do not support PHP 5.5.x or 7.0.5. ## Installation and upgrade instructions You can install Magento Open Source 2.1 Release Candidate 1 (RC1) from either Github or by using Composer. This Release Candidate is for test purposes only. Do not install it in a production environment.

See one of the following sections:

Install from GitHub

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

git clone git@github.com:magento/magento2.git

git checkout tags/2.1.0-rc1 [-b 2.1.0-rc1]

Install using Composer

This Release Candidate is available from repo.magento.com. Before installing this Release Candidate using Composer, familiarize yourself with the Composer metapackage prerequisites, then run

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

Upgrade existing installations

This section discusses how to upgrade to a Release Candidate.

Do not upgrade to a Release Candidate on a production system. Upgrade to a Release Candidate on a development system only.

Upgrade an existing installation from the GitHub repository

Developers who contribute to the Open Source codebase can upgrade manually from the Magento Open Source 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.