Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Report error csv doesn't work when trying to import a csv file with semicolon delimiter #5015

Closed
agoeurysky opened this issue Jun 14, 2016 · 8 comments
Assignees
Labels
bug report Component: ImportExport Fixed in 2.2.x The issue has been fixed in 2.2 release line Fixed in 2.3.x The issue has been fixed in 2.3 release line Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release

Comments

@agoeurysky
Copy link

agoeurysky commented Jun 14, 2016

Steps to reproduce (Magento 2.1-rc3)

  1. Try to import a catalog_product.csv file in admin interface which contains an error.
  2. Configure the semicolon ; for row delimiter.
  3. Click Check data button, the file is valid for import.
  4. Click Import button.

Expected result

  1. Import is stopped and all errors are printed.
  2. We can download the report error csv file.

Actual result

  1. Import is stopped but only General system exception happened is printed.
  2. 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.

@veloraven
Copy link
Contributor

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
Copy link
Author

@veloraven The problem still appears with the latest version 2.1-rc3.

@vkorotun vkorotun removed the MX label Aug 4, 2016
@BaDos BaDos self-assigned this Sep 14, 2016
@BaDos
Copy link
Contributor

BaDos commented Sep 14, 2016

Hi @agoeurysky

Thank you for reporting.
The internal ticket MAGETWO-58382 was created to resolve this issue.

@BaDos BaDos added Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development 2.1.x labels Sep 14, 2016
@BaDos BaDos removed their assignment Sep 14, 2016
@magento-engcom-team magento-engcom-team added 2.1.x Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development bug report Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed Component: ImportExport labels Sep 11, 2017
@magento-engcom-team magento-engcom-team added 2.2.x Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release labels Oct 19, 2017
@magento-engcom-team
Copy link
Contributor

@agoeurysky, thank you for your report.
We've created internal ticket(s) MAGETWO-58382 to track progress on the issue.

@okorshenko
Copy link
Contributor

The issue has been fixed and delivered to 2.2-develop branch. Will be available with 2.2.2 release

@okorshenko okorshenko added the Fixed in 2.2.x The issue has been fixed in 2.2 release line label Nov 1, 2017
@magento-team
Copy link
Contributor

Internal ticket to track issue progress: MAGETWO-82956

@magento-engcom-team
Copy link
Contributor

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 magento-engcom-team added the Fixed in 2.3.x The issue has been fixed in 2.3 release line label Jan 30, 2018
@magento-engcom-team
Copy link
Contributor

magento-engcom-team commented 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.

magento-engcom-team pushed a commit that referenced this issue Nov 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug report Component: ImportExport Fixed in 2.2.x The issue has been fixed in 2.2 release line Fixed in 2.3.x The issue has been fixed in 2.3 release line Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release
Projects
None yet
Development

No branches or pull requests

10 participants