Hello,
I have performed a data migration from Magento 1.9.2.1 to Magento 2.3.0.
everything went so smooth and good, however on a deeper review of the data, the product status ( Enabled / Disabled ) was not present on products or the product categories.
Is this a issue with the Magento version compatibility with the tool?
Our setup is: nginx + mariadb
Data migration tool: UBDataMigrationPro-Package_3.1.7
15 answers
Hi there,
however on a deeper review of the data, the product status ( Enabled / Disabled ) was not present on products or the product categories.
That is strange. Do you have see all selected attributes was migrated successfully in step #3 of our migration tool?
If yes, and the issue you mentioned still persists. It seem that, your M1 database has special setting cases on category/product status attributes. Let provide me information about your instance:
+ Admin credentials and URL to back-end
+ SSH credentials and path to M2 folder
I will help to check further and get back you then.
Regards,
Mall.
Hello,
This is the 1st migration that has been performed locally.
In regards to
” Do you have see all selected attributes was migrated successfully in step #3 of our migration tool? ”
Yes everything has been selected.
Hi there,
Yes everything has been selected.
But do you have see all with ‘MIGRATED’ suffix in label of all selected attributes now?
Regards,
Mall.
Hi there,
Yes, all of them are with the migrated suffix
Accessories Migrated
Baby and Todler Migrated
Beavers, Cubs, Scouts Migrated
Blouses Migrated
Dancewear Migrated
Default
Default Migrated
Fleeces Migrated
Jumpers & Knitwear Migrated
Outerwear Migrated
Poloshirts & T-shirts Migrated
Rainbows, Brownies, Guides Options Migrated
School Bags Migrated
Shirts Migrated
Skirts, Pinafores, Dresses Migrated
Sportswear Migrated
However as soon as i save a category, the product category links are visible, but it is a bit too tedious to save 960 categories manually so that the category product links are visible.
but this did not solve any any way the issue with the Product Status ( Enabled / disabled )
Even tried to perform a delta migration and the result is the same
Hello,
I have looked at the database and in the table “catalog_product_entitity_int” it seems that the values for attribute_id = 97 ( which from eav_attribute is status ) is inserted with values 4 and 5
Hi there,
Product Status ( Enabled / disabled )
Even tried to perform a delta migration and the result is the same
The list you quoted are the attribute group/set only. How about on the product’s attributes?
Do you see the product status attribute as in this screenshot: http://i.prntscr.com/xdP07axeQR24kPB9oL7tSQ.png ?
I have looked at the database and in the table “catalog_product_entitity_int” it seems that the values for attribute_id = 97 ( which from eav_attribute is status ) is inserted with values 4 and 5
So, that is strange. The correct value should be either 1 or 2. Do you see any record that has the attribute_id = 97 in the table ‘eav_attribute_option’ in your M1’s database now?
Also, you should move your instance to a live staging server so that I can debug directly and help you out.
Regards,
Mall.
Hello,
Yes the Migrated message appears on the step.
In the m1 database the status attribute has the id of 96 and in the eav_attribute_option there is no record of attribute_id=97
Hi,
I think that i need to mention that we have the following setup:
“PHP 7.1.26-1+ubuntu18.04.1+deb.sury.org+1 (cli) (built: Jan 11 2019 14:13:49) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.1.0, Copyright (c) 1998-2018 Zend Technologies
with Zend OPcache v7.1.26-1+ubuntu18.04.1+deb.sury.org+1, Copyright (c) 1999-2018, by Zend Technologies”
nginx version: nginx/1.14.0 (Ubuntu)
and magento 2.3.0
as for the tool cache is set to ‘class’ => ‘CFileCache’
Hello,
So when i update in the catalog_product_entity_int the value of 5 to 0 ( magento 2 disabled ) and 4 to 1 ( magento 2 enabled ) seems that visibiliti of products is back and working. what remains is to figure out the reason why the categories are not attached to the products.
Hello,
could you please indicate me where is the function for mapping / assigning the values on a product from magento 1 to magento 2 ? so that i can debug this ? every time I perform a delta after updating the catalog_product_entity_int i get the values reverted back
Hello,
After debugging the issue for quite a while i have managed to uncover the following:
from line: 616-619:
else {
//get back new option_id
$model2->value = UBMigrate::getM2EntityId(‘3_attribute_option’, ‘eav_attribute_option’, $model2->value);
}
in the Step5Controller.php
if i comment it out seems that the data is migrated properly ( no issues in regards to product Status / Product Visiblity or Product Categories. Could you please have a look at this please ?
Hi there,
In the m1 database the status attribute has the id of 96 and in the eav_attribute_option there is no record of attribute_id=97
So, do you have see any records which has attribute_id = 96 in table eav_attribute_option in M1 database now? If yes, that is bad data. Because, the options of Product Status and Product Visibility attributes calculates on fly by Magento core function.
And you shouldn’t comment the code lines of our migration tool as you quoted in your reply #11. You should remove the bad records (not needed records) in table eav_attribute_option (the records belong to Product Status and Product Visibility attributes if exists)
Once done, the issue will be solve.
Regards,
Mall.
Hello,
Will try to give it a try and will come back with more feedback.
Hello,
Thank you for your help. it seems that that you were indeed correct. I have removed the bad data and it seems that the categories product link and the product visibility are now migrated back properly. -- I have started a new data migration after I have corrected the database issues that you have pointed out.
Once the migration has finished I will come back with more feedback if everything worked out properly.
Thank you for all of your support during the day
Hi there,
Yes, please move forward with the migration process.
In case you run across any other issue, please pause the process and let us know the details of the issue, we will work closely with you then.
Regards,
Ubertheme team