Skip to content

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

Closed

Description

@agoeurysky

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.

Activity

  1. veloraven commented on Jun 23, 2016

    @veloraven
    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.

  2. agoeurysky commented on Jun 23, 2016

    @agoeurysky
    Author

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

  3. self-assigned this
    on Sep 14, 2016
  4. BaDos commented on Sep 14, 2016

    @BaDos
    Contributor

    Hi @agoeurysky

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

  5. removed their assignment
    on Sep 14, 2016
  6. 10 remaining items

  7. magento-engcom-team commented on Oct 19, 2017

    @magento-engcom-team
    Contributor

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

  8. self-assigned this
    on Oct 25, 2017
  9. okorshenko commented on Nov 1, 2017

    @okorshenko
    Contributor

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

  10. magento-team commented on Nov 1, 2017

    @magento-team
    Contributor

    Internal ticket to track issue progress: MAGETWO-82956

  11. magento-engcom-team commented on Jan 30, 2018

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

  12. magento-engcom-team commented on Feb 21, 2018

    @magento-engcom-team
    Contributor

    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.

  13. added a commit that references this issue on Nov 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Component: ImportExportFixed in 2.2.xThe issue has been fixed in 2.2 release lineFixed in 2.3.xThe issue has been fixed in 2.3 release lineIssue: ConfirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedIssue: Format is not validGate 1 Failed. Automatic verification of issue format is failedIssue: Ready for WorkGate 4. Acknowledged. Issue is added to backlog and ready for developmentReproduced on 2.1.xThe issue has been reproduced on latest 2.1 releaseReproduced on 2.2.xThe issue has been reproduced on latest 2.2 releaseReproduced on 2.3.xThe issue has been reproduced on latest 2.3 releasebug report

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions