Repository navigation
Report error csv doesn't work when trying to import a csv file with semicolon delimiter #5015
Copy link
Copy link
Closed
Labels
Component: ImportExportFixed in 2.2.xThe issue has been fixed in 2.2 release lineThe issue has been fixed in 2.2 release lineFixed in 2.3.xThe issue has been fixed in 2.3 release lineThe issue has been fixed in 2.3 release lineIssue: ConfirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedIssue: Format is not validGate 1 Failed. Automatic verification of issue format is failedGate 1 Failed. Automatic verification of issue format is failedIssue: Ready for WorkGate 4. Acknowledged. Issue is added to backlog and ready for developmentGate 4. Acknowledged. Issue is added to backlog and ready for developmentReproduced on 2.1.xThe issue has been reproduced on latest 2.1 releaseThe issue has been reproduced on latest 2.1 releaseReproduced on 2.2.xThe issue has been reproduced on latest 2.2 releaseThe issue has been reproduced on latest 2.2 releaseReproduced on 2.3.xThe issue has been reproduced on latest 2.3 releaseThe issue has been reproduced on latest 2.3 releasebug report
Description
Steps to reproduce (Magento 2.1-rc3)
- Try to import a catalog_product.csv file in admin interface which contains an error.
- Configure the semicolon
;for row delimiter. - Click
Check databutton, the file is valid for import. - Click
Importbutton.
Expected result
- Import is stopped and all errors are printed.
- We can download the report error csv file.
Actual result
- Import is stopped but only
General system exception happenedis printed. - We cannot download the report error csv file because the link doesn't appear.
Note
The same workflow works with a catalog_product.csv file with the , row delimiter, because this is the default Magento delimiter for a csv source.
See \Magento\ImportExport\Model\Report\Csv::createSourceCsvModel.
Reacted by tarnagas
Metadata
Metadata
Assignees
Labels
Component: ImportExportFixed in 2.2.xThe issue has been fixed in 2.2 release lineThe issue has been fixed in 2.2 release lineFixed in 2.3.xThe issue has been fixed in 2.3 release lineThe issue has been fixed in 2.3 release lineIssue: ConfirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedIssue: Format is not validGate 1 Failed. Automatic verification of issue format is failedGate 1 Failed. Automatic verification of issue format is failedIssue: Ready for WorkGate 4. Acknowledged. Issue is added to backlog and ready for developmentGate 4. Acknowledged. Issue is added to backlog and ready for developmentReproduced on 2.1.xThe issue has been reproduced on latest 2.1 releaseThe issue has been reproduced on latest 2.1 releaseReproduced on 2.2.xThe issue has been reproduced on latest 2.2 releaseThe issue has been reproduced on latest 2.2 releaseReproduced on 2.3.xThe issue has been reproduced on latest 2.3 releaseThe issue has been reproduced on latest 2.3 releasebug report
Activity
veloraven commentedon Jun 23, 2016
Please, provide the used version. If the problem is actual for a specific tag, please, specify it and be sure that the latest update was used.
agoeurysky commentedon Jun 23, 2016
@veloraven The problem still appears with the latest version 2.1-rc3.
BaDos commentedon Sep 14, 2016
Hi @agoeurysky
Thank you for reporting.
The internal ticket MAGETWO-58382 was created to resolve this issue.
10 remaining items
magento-engcom-team commentedon Oct 19, 2017
@agoeurysky, thank you for your report.
We've created internal ticket(s) MAGETWO-58382 to track progress on the issue.
okorshenko commentedon Nov 1, 2017
The issue has been fixed and delivered to 2.2-develop branch. Will be available with 2.2.2 release
magento-team commentedon Nov 1, 2017
Internal ticket to track issue progress: MAGETWO-82956
magento-engcom-team commentedon Jan 30, 2018
Hi @agoeurysky. Thank you for your report.
The issue has been fixed in magento-engcom/magento2ce#1285 by @magento-engcom-team in 2.3-develop branch
Related commit(s):
The fix will be available with the upcoming patch release.
magento-engcom-team commentedon Feb 21, 2018
Hi @agoeurysky. Thank you for your report.
The issue has been fixed in magento-engcom/magento2ce#1203 by @nmalevanec in 2.3-develop branch
Related commit(s):
The fix will be available with the upcoming 2.3.0 release.
Merge pull request #5015 from magento-trigger/honey_tsg
⏫ Forwardport of magento#11732 to 2.3-develop branch
Merge forwardport of magento#11732 to 2.3-develop branch
🔃 [EngCom] Public Pull Requests - 2.3-develop
🔃 [EngCom] Public Pull Requests - 2.3-develop