You are here:

What are Magento 2.1 backward incompatible changes?

Magento 2.1 release brings multiple improved features and eliminates many backward ones. In this post, we will show you the backward incompatible changes in Magento 2.1 to make you have full view about this version.

API

There are multiple changes in several API classes in order to extend overall API coverage and improve developer experience with new features

Catalog Module API

The new service methods in catalog will improve both options management and products to categories cross liking management

Class: Magento\Catalog\Api\CategoryLinkManagementInterface

Action: Added the service method assignProductToCategories

Description: Assign product to given categories

 

Class: Magento\Catalog\Api\ProductCustomOptionRepositoryInterface

Action: Added the service method getProductOptions

Description: Returns product options

 

Action: Added service method – duplicate

Description: Duplicate product options

 

Class: Catalog\Api\ProductLinkRepositoryInterface

Action: Added service method- getList

Description: Get Product links list

 

CMS module

The CMS module has been updated to allow you to manage meta titles for your CMS pages

Class: Magento\Cms\Api\Data\PageInterface

Action: Added the getter method getMetaTitle

Description: Add meta title field to CMS pages

 

Action: Added the setter method getMetaTitle

Description: Set Meta Title field of CMS pages

 

GiftcardAccount Module (EE Only)

A data interfaces has been changed in the GiftcardAccount module

Class: Magento\Giftcard\Api\Dta\GiftcardAmountInterface

Action: Added the getter method getAtributeId

Description: Remove GiftCard Account entity

 

Action: Added the setter method setAttributeId

Description: Remove GiftCard Account entity

 

UI

A new way to build the Admin UI is provided in Magento 2.1. The forms which is used in previous version is no longer applied, instead, they are rewritten using new UI components. The new UI forms own better flexibility and can be customized using configuration files

The entities below have new forms and design:

  • Product
  • Category
  • CMS Page
  • CMS Block
  • Sales Rule
  • Catalog rules

And there are no longer customizations that were performed with the old forms of entities above

Database Scheme

Staging (EE Only)

Some entities below have database schema changed:

  • Products
  • Categories
  • CMS Pages and Blocks
  • Cart and Catalog Price Rules

These changes just are applied if staging modules are installed. The relations between main entity and extension modules were also changed, which may affect code that manages SQL queries directly

Persistence management

Magento 2.1 is added a new level of persistence management- the EntityManager library component. This new adding allows decoupling from Magento’s persistence infrastructure and supporting more flexibility for development later. At the same time, the entity manager support all Magento model events in backward compatible manner

Data interfaces persistence

In the 2.1 release, we introduce support for the persistence of data interfaces for following entities:

  • Product
  • Category
  • CMS Page
  • CMS Block
  • Sales Rule
  • Catalog Rule

With this change, extensions rely on implicit data of Magento 1 may be affected.

That’s all things we want to introduce you about the backward removed in Magento 2.1. Hope that the information above is useful for you.

Thanks for reading!

Related articles
 

404

Back to Top