Magento Open Source 2.1.9 Release Notes
- Highlights
- Fixed issues
- System requirements
- Install the Magento software
- Upgrade from an earlier version
- Migration toolkits
- Credits
Code released: September 14, 2017
Page updated: September 14, 2017
We are pleased to present Magento Open Source (formerly Community Edition) 2.1.9. This release includes important enhancements to your Magento software.
While there are no confirmed attacks related to these vulnerabilities to date, certain vulnerabilities can potentially be exploited to access customer information or take over administrator sessions. We recommend that you upgrade your existing Magento software to the latest version as soon as possible.
Highlights
Magento 2.1.9 contains almost 40 security fixes and enhancements. Look for the following highlights in this release:
-
enhancements that help close cross-site request forgery (CSRF), unauthorized data leak, and authenticated Admin user remote code execution vulnerabilities. See Magento 2.0.16 and 2.1.9 Security Patches for a comprehensive discussion of these issues.
-
support for changes to the USPS API that USPS implemented on September 1, 2017
-
fixed issue with logging information about exceptions caused by payment failures
-
change to how Magento displays status updates during upgrade.
Fixed issues
- We’ve added support for the change to the USPS API that USPS implemented on September 1, 2017. After installing or upgrading to this release, Magento will display the Domestic rate for USPS, First-Class Mail Parcel as expected. Previously, the USPS First-Class Mail Parcel option was not available after September 1, 2017 on installations running Magento 2.x unless you applied the workaround described here.
- Magento now logs all expected exception information in the
exception.logfile when a payment transaction fails. Previously, Magento did not log all exception information when a payment transaction failed, and this lack of full exception information, undermined debugging attempts. GitHub-6246
- We’ve changed how Magento displays status updates during a product upgrade. Previously, potentially vulnerable information such as full paths and module names were displayed in the product GUI, potentially exposing this information to a malicious user. Magento now restricts this potentially vulnerable information to logs that are available to administrators only.
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 Open Source (formerly Community Edition) 2.1 from Github, Composer, or using a compressed archive.
See one of the following sections for more information:
- Get the Magento Open Source software using Composer
- Get a compressed archive
- Complete the installation
Get the Magento Open Source software using Composer
The Open Source software is available from repo.magento.com. Before getting the Open Source 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 Open Source 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 Open Source software only
- Magento Open Source 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 Open Source software archive:
- Go to http://magento.com/download.
-
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 Open Source software:
- Set file system ownership and permissions.
-
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 Open Source codebase can upgrade manually from the Magento Open Source GitHub repository.
-
Go to the Contributing Developers page.
-
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.
An updated version of this toolkit is typically available several days after the patch release.
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.