Magento 2.0.18 is the final 2.0.x release. After March 2018, Magento 2.0.x will no longer receive security patches, quality fixes, or documentation updates.
To maintain your site's performance, security, and PCI compliance, upgrade to the latest version of Magento.

Magento Commerce 2.0.11 Release Notes

We are pleased to present Magento Commerce 2.0.11. This release includes many functional fixes and enhancements.

We republished these Release Notes with clarifications on December 16th, 2016.


Magento 2.0.11 contains more than 70 bug fixes and enhancements, including these highlights:

  • Management of configurable products with many variations in the Admin interface without degrading performance.

  • Upgrade to Magento 2.0.11 without issue when using multiple master databases for checkout, order management, and product data.

  • Successful import or export CSV files with data that contains special symbols (that is, symbols that are not escaped during file processing, such as ,</> or |).

  • The Sales module provides two new web API endpoints that allow you to process refunds from an order or invoice . Previously, these actions could only be performed from Admin. After you install this patch, you can:

    • Create a credit memo (complete or partial) for a particular order or invoice.

    • Add details about refunded items to an order or invoice.

    • Update the status and state of an order or invoice after actions are performed.

    • Notify a customer about refunded items or order or invoice.

    REST integrators can use POST /V1/invoice/{invoiceId}/refund and /V1/order/{orderId}/refund to perform these actions. SOAP integrators can call salesRefundInvoiceV1 and salesRefundOrderV1.

Functional fixes

We address the following functional issues in this release.

Cart and checkout

  • You can now reload a page during checkout without unintentionally changing shipping information.
  • Magento no longer displays the spinning loader widget after you click the Place Order button. Previously, Magento displayed the spinning loader, even after you’d successfully placed an order.
  • Magento now indicates that a product is out-of-stock if you disable it. Previously, Magento did not display the name of an out-of-stock product at all.
  • The number of items in the minicart is now updated correctly when you run Magento in mixed HTTP/HTTPS mode. (GITHUB-6487)
  • Refreshing your browser page while on the Review and Payments page of the checkout process no longer clears information from form fields. Previously, Magento cleared information from the Ship to field if you refreshed your browser page during this process.
  • We’ve resolved an issue that prevented you from adding more than one product from the wishlist to your shopping cart . (GITHUB-5282)
  • Magento now displays the product add validation message (“Product was added to the cart”) only after you’ve successfully added a product to your cart.
  • You can now reload a page during checkout without unintentionally changing shipping information.
  • You can now successfully reorder a product. Previously, if you tried to reorder a product, the checkout page would not load, and Magento would display this error: “Uncaught TypeError: Cannot read property ‘length’ of undefined”.
  • A cart rule with a coupon code no longer overrides a cart rule without a coupon code when multiple cart rules are applied. Previously, when you created two cart rules and applied them to a cart, the rule with a coupon was applied, but the second rule was not. (GITHUB-6294)

Configurable products

  • We’ve improved the performance of the review step to create a configurable product .
  • You can now successfully reorder a configurable product. Previously, if you created an order that includes multiple products, one of which is a reorder, options for these products were confused. (GITHUB-3654), (GITHUB-3820)
  • You can now successfully edit configuration options when creating a configurable product. Previously, the Edit Configuration button did not work as expected.
  • You can now successfully add a simple child product to a configurable product with advanced configurations.
  • We no longer apply one simple product’s special price to another simple product of the same configurable product. Previously, when you set both a regular and a special price for a child product, all products associated with the same configurable product displayed a regular and special price, even when these amounts were the same. (GITHUB-4442), (GITHUB-5097), (GITHUB-6645)
  • Magento no longer displays the as low as price for a configurable product’s simple options if the options are disabled.
  • You can now edit a single product attribute and apply it to multiple configurable products. Previously, when you tried to bulk-edit an attribute on a collection of filtered, configurable products, Magento would complete the process without incorporating your edits, then incorrectly tell you that the products had been edited.
  • A price change to a custom option affects only that option. Previously, changing the price of a custom option also affected the price of related products. (GITHUB-4588)
  • Configurable product option price is displayed correctly per website .
  • You can now successfully disable the lowest price of a configurable product and its associated simple products. Previously, Magento displayed a configurable product’s lowest price even after you disabled that price. (GITHUB-4419)


  • Order emails now specify the amount of the gift card that you’ve purchased.
  • The Send Welcome Email From field now accurately identifies the store that the customer is associated with.
  • The Disable Email Communication option of Store > Configuration > Advanced > System > Email Sending Settings now works as expected. Previously, Magento sent email even if you disabled this feature. (GITHUB-5988)

General fixes

  • We fixed an issue where Magento unexpectedly removed categories from a store when an Admin with rights restricted to only one store saves a product.
  • Magento now creates a URL rewrite for the new URL key of a product as expected. Previously, after you saved a change to the URL key of a product by selecting the Create Permanent Redirect for old URL option, Magento did not rewrite the old URL to the new URL.
  • The Product page now displays swatches based on the color swatch attribute. Previously, the Product page did not display swatches.
  • Magento no longer displays a “Wrong request parameters” error when you try to assign products to a category at the store view level. Previously, Magento displayed a levelWrong request parameters error when you assigned products to a category.
  • The Magento Framework now makes its dependencies explicit in the composer.json file. (GITHUB-6442)
  • Magento now decrements stock as expected in a multi-website environment.
  • Magento now correctly manages the maximum number of messages a message queue consumer can process. Previously, the consumer would stop processing messages before reaching the specified maximum number.
  • The catalog category now retrieves prices from the price index update as expected.
  • The search field now works as expected on iOS devices using the Safari browser. Previously on these devices, the search box closed randomly.
  • We’ve removed the duplicate PHP settings from the sample web server configuration files.
  • The Compare Products page now works as expected. Previously, you were erroneously redirected to another page when you removed an item from the Compare Products sidebar .
  • You can now return to the Magento Admin from the Web Setup Wizard (System > Tools > Web Setup Wizard). Previously, you had to log back in to the Magento Admin after you ran the Web Setup Wizard.
  • Magento no longer redirects users to the Checkout page after login. Now, if you set Redirect Customer to Account Dashboard after Logging in value to Yes, users will be redirected to the Account Dashboard page. If you set this value to No, then users will stay on the home page after login.
  • We’ve eliminated difficulties saving product information when logged in as admin. Previously, the Product Save feature worked erratically for some Admin users.
  • Customers can now continue shopping after selecting an unavailable bundle product . Previously, if a customer selected a bundle product that was no longer available, he encountered a fatal error.
  • The Magento storefront now reflects changes in the swatch attribute properties as expected.
  • The Sales Order object can now contain more than one extension_attribute. (GITHUB-3967)
  • We’ve removed the sampassword from the Setup wizard.
  • Customers are now redirected as expected to the destination URL identified in the Redirect to My Account After Log-in setting. Previously, customers were redirected to the My Account page, no matter which URL you identified in this setting.
  • The order of products in a category display no longer changes when you add a new product to the category.
  • Lengthy Order Status tables are now paginated as expected.
  • We’ve fixed an issue with how the Customer Segments report calculates the same customer on two websites.
  • You can now make Return Merchandise Authorization (RMA) comments visible from the storefront by setting Stores > Configuration > Sales > RMA Settings > Enable RMA on Storefront.
  • You can now upload changes to the robots.txt file from the Magento Admin.
  • Users need view permission to the store to which the customers belong in order to see information about those customers. Previously, a user could see information about customers that belonged to websites or stores for which the user did not have explicit permission to view.
  • We’ve fixed an issue with how information in the sales_order_item attribute is handled after upgrade.
  • We’ve fixed an error with an unexpected empty default website during website creation.
  • The Need to Confirm option on Stores > Configuration > Customers > Newsletter now works as expected.

Gift cards

  • You can now complete the purchase of a gift card in environments where you have set the Braintree payment method Payment Action to Authorize and Capture. Previously, any order made under these conditions would remain indefinitely in the processing stage.
  • You can now save a gift message when ordering a gift while logged in as a guest. Previously, Magento would not save this information, and displayed an error. (GITHUB-3804)


  • We’ve added a new way to import images: You can now successfully import images when you set your document root to <your Magento install dir>/pub. Previously, you needed to set document root to /magento to import images. Both ways of importing now work. (GITHUB-5359)
  • You can now preview uploaded images.


  • You can now export a bundle product that contains a custom text attribute. Previously, if you tried to export this type of bundle product, the export failed, and Magento displayed the message, “There is no data for the export”.
  • You can now successfully import multiselect attributes that contain special symbols or delimiters. Previously, when you tried to import attributes that contained delimiters, data validation (and the import) failed.
  • Importing customer data no longer sets the Gender attribute to a blank field.
  • You can now import negative quantities.
  • Magento no longer randomly displays this error during import after a file passes the data check: “Maximum error count has been reached or system error is occurred!”.
  • We’ve fixed an issue with the representation of date and time zones of items in the product catalog during import or export. Previously, Magento converted all data into the default format (UTC-8), including values that you set to be displayed using another standard.

Installation, upgrade, and deployment

  • The Component Manager now shows a list of all available versions of an extension for installation. Previously, the Web Setup component manager showed only the latest version of the extension.
  • During upgrade, we now check directory permissions recursively except for the var/session directory. We skip that directory because the web server usually owns those files.
  • Magento 2.0.x now supports the use of table prefixing during installation. Previously, when you used table prefixing, your Magento installation failed with this error: “Duplicate key on write or update”. (GITHUB-5688)
  • Magento now requires you to log in with your Magento Marketplace account credentials before attempting to upgrade. Previously, it was not clear that you needed to log in first before initiating an upgrade. (GITHUB-3059)


  • You can now reorder an item that is currently invoiced or being shipped. Previously, if you tried to reorder, Magento did not add the item to your shopping cart, and displayed an error. (GITHUB-6278)
  • A user can view orders only on stores to which they’ve been assigned permission. Previously, an Admin user with permissions for only one store could view orders from all stores on the same website.
  • We’ve added PHP interfaces that add the ability to change the status of a shipment . The new Creditmemo interface supports tasks you can already do through the Magento Admin, including the ability to:

    • support returning multiple units of a configurable product. Previously, when you tried to refund an order, you could refund only one unit of a configurable product, not the amount in the original order.

    • return the product to stock

    • change order status after a credit memo has been created.

  • We’ve removed redundancy in the orders comment history display. Previously, Magento would display the time at which the customer entered the comment twice.

Payment methods

  • You can now successfully place an order using the Payflow Pro payment method.
  • We’ve fixed an issue with how Magento captures and validates payment information. Previously, after you entered valid credit card information, Magento prompted you to re-enter the information, and displayed this error: “Please enter a valid credit card expiration date”. (GITHUB-4741)
  • Magento now saves credit card information as expected after a customer checks out using a Braintree credit card with Vault.
  • PayPal Payflow Pro now uses the currency you have specified in your store. Previously, under some conditions, PayPal Payflow Pro defaulted to calculating charges in U.S. dollars, no matter which currency you specified.


  • We’ve improved the performance of these tasks:

    • Loading the Configurable Product page.

    • Creating many (2500 - 5000) product variations.

    • Calculating batch sizes while indexing categories.

    • Compiling. (We’ve optimized compiler performance to run faster.)

  • We’ve also streamlined the JavaScript bundling process, which reduces the size of bundled files. (GITHUB-4506)


  • You can now successfully assign products to a category on the store view level. Previously, Magento displayed this error when you tried to assign products to a category: “Wrong request parameters”.
  • A restricted user can now change the attributes (either at the store view or website level) attributes that are defined in his scope. Previously, Admin users with access to only one website could not edit a product, no matter how their scope was set.
  • The scope selector on the Product page now accurately displays all related websites for a restricted user.

* We’ve fixed an issue with the scope selector on the Catalog page. Previously, Magento did not display the scope selector when using Mass Actions, but now you can specify the scope of the action that will be applied to the products when using Mass Actions.

Static file processing

  • Versioning of static files (including CSS, JavaScript, fonts, and images) is now enabled by default.

Web APIs

  • The Swagger documentation erroneously indicated that search queries can return detailed information about multiple objects. The description of these APIs now state which API to use to return detailed information about a single object.

Known issues

  • Issue: When editing a product, you cannot edit customizable options on the store view level. That is, a change to one option affects products on all stores. Also, the ‘Use Default Value’ checkbox for the option title does not work. Unchecking this box and then changing the title affects all store views.
  • Issue: When you add a new product and re-index using Varnish, Magento does not display the product on the frontend, even after you purge the cache and re-index. Workaround: Purge the Varnish cache using the Varnish admin CLI.

  • Issue: A Paypal SSL CURL communication error can occur if your Magento installation is not running the minimal required TLS version. Older versions of Magento might not run the minimal version, which is TLS 1.2. If it isn’t, then Magento displays this error: curl: (35) Cannot communicate securely with peer: no common encryption algorithm(s). Workaround: Upgrade your version of CURL to the latest possible version that will enable the use of TLS 1.2 by default.

  • Issue: Mass actions can be slow and consume excessive memory unless you increase the default PHP settings for your installation. These default settings for your Magento installation typically support the processing of about 1,000 variables. If you try a mass action that involves 1000 or more variables, the mass action might fail. Workaround: You can reduce processing time and performance by increasing your default PHP memory settings to 1 GB.

  • Issue: Gallery doesn’t show all images added to configurable options.

  • Issue: The Add Products Manually link is not available after removing all variations. Workaround: Retain at least one variation or use the Choose a different product option option.

  • Issue: When you log in to run a system upgrade, Magento displays this error: Encountered end of file. Workaround: Upgrade your SSL protocol to a minimum of TLS 1.0.

System requirements

Our technology stack is built on PHP and MySQL. See System Requirements.

Install the Magento software

See one of the following sections:

Get Magento Commerce using Composer

This software is available from Before installing the Magento Commerce software using Composer, familiarize yourself with these prerequisites, then run:

composer create-project --repository-url= magento/project-enterprise-edition=<version> <installation directory name>

where <version> matches the version you want (for example, 2.0.10)

For example, to install 2.0.10 in the magento2 directory:

composer create-project --repository-url= magento/project-enterprise-edition=2.0.10 magento2

Get Magento Commerce using a compressed archive

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

  • Magento Commerce software only
  • Magento Commerce 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 Commerce archive:

  1. Go to your account on
  2. Log in with your Magento username and password.
  3. In the left navigation bar, click Downloads.
  4. In the right pane, click Magento Commerce 2.X > Full Release or Magento Commerce 2.X > Full Release + Sample Data for the software.
  5. Follow the instructions on your screen to complete the Magento Commerce download:

    • Magento-EE-<version>.* (without sample data)
    • Magento-EE-<version>+Samples.* (with sample data)
  6. Transfer the installation package to your development system.

Complete the installation

After you get the Commerce software:

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

Upgrade from an earlier version

To upgrade to version 2.0.x from an earlier version:

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.


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