Hi,
I have an important problem with magento 2 import section.
if i import a product file csv, the page stop loading but the loading icon is always present and magento don't check data.
So this first step is blocked by hours and then i can't import product by csv file.
what is the problem? i haven't error in web console. The server is ok, other functions works correctly.
i have tryed magento setup:upgrade ecc but doesn't work.
What is the problem? Please help me to solve. I must import product!
Thanks
Luca
Hi have this error when i check the file before import:
Fatal error: Uncaught Error: Call to a member function getName() on null in /var/www/vhosts/sito.com/httpdocs/vendor/magento/module-catalog-import-export/Model/Import/Product/CategoryProcessor.php:80
Stack trace:
@lucasound thank you for your feedback.
Please, format this issue according to the Issue reporting guidelines: with steps to reproduce, actual result and expected result.
Please, also identify which version of Magento you are running.
If you are looking for discussion please refer to the Community Forums or the Magento Stack Exchange as GitHub issue tracker is intended for technical issues only.
@lucasound we are closing this issue due to inactivity. If you'd like to update it, please reopen the issue
Issues exists in magento 2.2.2
Issue also in 2.2.3 I would very much like to (re)open this issue.
Preconditions:
Expected result:
Maybe some errors indicating things need to be changed in the CSV file or maybe some message saying it isn't compatible.
Actual result:
An endless rotating "Please wait" icon....
But when opening the console you can see the Internal Sever error:

Some digging around in the logging gives me the following:
[28-Mar-2018 18:53:35 UTC] PHP Fatal error: Uncaught Error: Call to a member function getFrontendInput() on boolean in ....
/vendor/magento/module-catalog-import-export/Model/Import/Product.php:2657
Stack trace:
Deleting the attribute that seems to be the problem (in my case adwords_grouping even though I had created this in store A as well) just gets me onto the next Internal Server Error:
[28-Mar-2018 19:15:47 UTC] PHP Fatal error: Uncaught Error: Call to a member function getFrontendInput() on boolean in /home/scrittu/public_html/vendor/magento/module-catalog-import-export/Model/Import/Product.php:2657
Stack trace:
and another attribute that exists in both stores becomes the problem.
I still need to investigate this further (so far I have created various products and exported and imported these fine in Magento 2.2.x stores and have exported migrated products fine but haven't been able to import these again) but I think Magento 2.2.2/2.2.3 should not throw an Internal Sever error when someone pushes the Check Data button.
I will add further findings.
Same issue on fresh installed 2.3.0 on check data
I receive this issue on 2.3.3 when clicking check data. Can't import products. There's no issues importing customer data though.
Nothing pertinent in exception or system log files. Network monitor shows 500 Internal Server Error on /admin/import/validate/key/_removed_/?form_key=_removed_
Edit: I ended up figuring out that this was caused by the module Magento_Downloadable being disabled. It seems this module became necessary to have enabled in one of the 2.3 updates; as far as importing products goes.
Magento 2.3. trying to do a product csv import.
This is an issue when Fields enclosure box is ticked, which needs to be ticked to get special characters otherwise it stuffs up the encoding and gets scrambled stuff which might push some attributes such as meta_description past their 255 length validation.
Magento_Downloadable is irrelevant, but is enabled.
Most helpful comment
Issue also in 2.2.3 I would very much like to (re)open this issue.
Preconditions:
Expected result:
Maybe some errors indicating things need to be changed in the CSV file or maybe some message saying it isn't compatible.
Actual result:
An endless rotating "Please wait" icon....
But when opening the console you can see the Internal Sever error:
Some digging around in the logging gives me the following:
[28-Mar-2018 18:53:35 UTC] PHP Fatal error: Uncaught Error: Call to a member function getFrontendInput() on boolean in ....
/vendor/magento/module-catalog-import-export/Model/Import/Product.php:2657
Stack trace:
0 .../vendor/magento/module-catalog-import-export/Model/Import/Product.php(2593): MagentoCatalogImportExportModelImportProduct->parseAttributesWithWrappedValues('adwords_groupin...')
1 ../vendor/magento/module-catalog-import-export/Model/Import/Product.php(2573): MagentoCatalogImportExportModelImportProduct->parseAdditionalAttributes('adwords_groupin...')
2 ../vendor/magento/module-catalog-import-export/Model/Import/Product.php(2740): MagentoCatalogImportExportModelImportProduct->_parseAdditionalAttributes(Array)
3 ../vendor/magento/module-catalog-import-export/Model/Import/Product.php(2775): MagentoCatalogImportExportModelImportProduct->_customFieldsMapping(Array)
4 ../vendor/magento/module- in /home/scrittu/public_html/vendor/magento/module-catalog-import-export/Model/Import/Product.php on line 2657
Deleting the attribute that seems to be the problem (in my case adwords_grouping even though I had created this in store A as well) just gets me onto the next Internal Server Error:
[28-Mar-2018 19:15:47 UTC] PHP Fatal error: Uncaught Error: Call to a member function getFrontendInput() on boolean in /home/scrittu/public_html/vendor/magento/module-catalog-import-export/Model/Import/Product.php:2657
Stack trace:
0 ../vendor/magento/module-catalog-import-export/Model/Import/Product.php(2593): MagentoCatalogImportExportModelImportProduct->parseAttributesWithWrappedValues('brand_se="Bomo ...')
and another attribute that exists in both stores becomes the problem.
I still need to investigate this further (so far I have created various products and exported and imported these fine in Magento 2.2.x stores and have exported migrated products fine but haven't been able to import these again) but I think Magento 2.2.2/2.2.3 should not throw an Internal Sever error when someone pushes the Check Data button.
I will add further findings.