Wednesday, March 13, 2019

KEY MAGENTO 2 DATA MIGRATION ISSUES & THEIR SOLUTION

Movement from Magento 1 to Magento 2 is less of an alternative and to a greater degree a need for the storekeepers. There were a couple of blemishes in the Magento 1.0 which is presently improved in the new Magento 2.0 form. Magento 2 movement can take a lot of time and you can likewise confront a few issues since this strategy is amazingly eccentric and join a few customizations.

Here, in this blog I am posting down the issues that I have looked amid Magento 2 movement administrations.

Adding Grouped sort item to truck

We confronted this issue after we effectively finished the information relocation to Magento 2. Amid the testing stage, we took a stab at adding Grouped sort item to truck and we found that it was just getting added to the shopping basket yet the item subtleties were missing.

The arrangement which we established for this issue was that we built up a custom module which fundamentally used to supersede the shopping basket activity and showed the additional item in the truck.

Checkout catch in Minicart was not working after information relocation

The checkout in Magento 2 is presently determined with JavaScript and KnockoutJS. Therefore, presently you can see improvement in Magento 2 checkout. The Magento 2 checkout has improved general stream now and is outwardly all the more engaging for the guests as well.

The issue which I looked here was that after information movement the checkout catch in Minicart was not working. I was not ready to tap on the checkout catch and accordingly, I was not ready to continue to checkout. In spite of the fact that, I had the capacity to tap the checkout catch on the shopping basket page.

The arrangement we established on this issue was by making a custom module which will supersede the truck activity to make the checkout catch interactive.

Helpless to alter items from Admin after information relocation

Administrator can include/erase items refreshed by the merchants. When we relocated to Magento 2 we found that we were not able alter items from Admin.

The answer for this was we built up a custom module to abrogate the configurable cost.

Classification URLs were not SEO cordial

The URLs you allocate to items and classifications assume a noteworthy job in site design improvement. Magento's change usefulness makes URLs for classes while sparing them. This has caused me innumerable issues throughout the most recent couple of years, principally from a SEO point of view.

So as to determine this issue, we:

Revamp section against the past URL

Built up a custom content to create SEO inviting URLs.

Administrator powerless to make the receipt for Orders

You have to make the receipt for a request as a record of the receipt of the installment. Receipt is to some degree finished request page made when a transitory deals request is affirmed or when dropped. Administrator for the most part produces a receipt with a pressing slip and sending names. Different solicitations can be made for a singular demand, and each can fuse a similar number of or as few of the acquired things that you demonstrate. The issue which I confronted was that Admin was not able make a receipt for requests.

In the wake of doing bunches of research, I found that the tables in charge of Invoice creation is making this issue. Subsequent to adding the fitting segment to the table, I had the capacity to make a receipt for requests from administrator board.

Powerless to alter/refresh classifications

The class can be altered/refreshed or moved to another situation from the index. If there should arise an occurrence of live stock, you should think about how the change may influence any present connects to things in the classification.

In the wake of relocating to Magento 2, we found that altering any classification from Admin was appearing. On investigating I found that the estimations of custom classification property are feeling the loss of that is the reason it was tossing a special case.

This issue was fixed by making a custom module to abrogate the ReadHandler.php Model class

Helpless to alter/refresh index items

We were getting the accompanying mistake when we attempted to include new items in the index subsequent to relocating to Magento 2.

'Class Magento\Catalog\Model\Product\Attribute\Backend\Media does not exist'

The above mistake was coming since Product Attribute media_gallary back-end asset demonstrate class is absent in Magento 2.

To make it work we built up a content which fixes media_gallary property's back-end asset type.

Powerless to submit a request from sub stores

Since the time we moved to Magento 2 the framework was not ready to produce request increase id to make the requests because of which we were not able put in a request from sub-stores and make request solicitations and shipments from the backend.

To comprehend this issue we composed a content to refresh the Magento 2 database and make new grouping tables for sub-stores, which is another idea to create deals request succession Idin Magento 2.

Creator Bio:

Ronak is a sequential business visionary and who has worked with little medium-expansive organizations. He is having a 8+ Years of ability and firmly working with eCommerce adventures since 2009. Ronak Meghani, the Co-Founder of Magneto IT Solutions, a full administrations of magento Development in the USA, UK, UAE, and India. He's eager about wellness, new companies, business, and everything advertising.

No comments:

Post a Comment