Magento 2.0.7-9 Updates

Since our last post there were 3 updates for Magento for version 2.0. The recently released Magento 2.1 update will be described in another article.

Magento 2.0.7

This update brings just one fix for a compatibility problem with PHP 7.0.3 at the checkout page.

Magento 2.0.8

Magento 2.0.8 was released and contains functional fixes.

The fixes are:

  • Solved a problem with the installation on environments with PHP 7.0.5
  • Magento no longer duplicates URL keys during the product creation
  • Magento shows always the error messages on the page where the error occurred
  • Magento now sends email using a store’s specific email address when an admin sends email.
  • Magento now shows correctly the customer address on the storefront. Previously, there was a problem by new customer accounts.
  • You can now successfully reset the product attributes mass update admin form.

Magento 2.0.9

The latest Magento 2.0.9 update with functional fixes was released in August.

The fixes are:

  • Magento no longer displays an incorrect price in the shopping cart when using multiple shipping addresses.
  • The Minicart Maximum Display Recently Added Item setting now works as expected.
  • Better performance if you use many variations of a configurable product.
  • Cart Price Rules are now applied as expected to Payment method conditions.
  • You can now save a product without a Swatch attribute value when this attribute is not required.
  • The Tier Price option on the Advanced Pricing tab was renamed to Customer Group Price option.
  • Tier pricing now works correctly with full page cache.

For more information about the security fixes visit the Magento Security Center. The release notes you can find here.

Depending on how you installed Magento 2, the upgrade process will vary. Obviously, the best approach to upgrade is in a test environment on the same server or on a local development environment. If you feel lucky and your store does not have lots of traffic, you might want to upgrade in production, but you still should do a full backup of all your files and your database.

Kommentar verfassen

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert