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.

Sign up for GitHub

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

Jump to bottom

Attribute image exceeded max length in row(s) when importing images from Amazon.com with CSV file #15679

Open
GoogleYY opened this issue Jun 2, 2018 · 2 comments · May be fixed by #30327
Open

Attribute image exceeded max length in row(s) when importing images from Amazon.com with CSV file #15679

GoogleYY opened this issue Jun 2, 2018 · 2 comments · May be fixed by #30327
Labels
Component: CatalogImportExport Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: PR in progress 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 Severity: S2 Major restrictions or short-term circumventions are required until a fix is available. up for grabs
Projects
High Priority Backlog

Comments

@GoogleYY
Copy link

GoogleYY commented Jun 2, 2018

Preconditions

  1. Win 7 / CentOS Linux release 7.4.1708
  2. PHP Version 7.0.28
    3.Magento ver. 2.2.4
    4.Luma blank theme without sample data

Steps to reproduce

  1. Log into backend panel
  2. Go to System->Import
  3. Select products as Entity Type option, select Add/Update as Import Behavior, Select Stop on Error, Allowed Errors Count is 10,Field separator is Comma(,) ,Multiple value separator is Comma(,) , Fields enclosure filed is empty.
    4.Select File to Import
    5.Images File Directory left blank (As the images were going to fetch from Amazon.com)
    6.Click Check Data

Expected result

  1. It should be 0 errors.

Actual result

error

  1. Attribute image exceeded max length in row(s): 1, 3, 4, 6

Further steps to reproduce
I tried changing the data const DB_MAX_VARCHAR_LENGTH from 256 to 512 in MagentoRootFile\vendor\magento\module-import-export\Model\Import\AbstractEntity.php and then run the commands php bin/magento setup:upgrade and php bin/magento cache:flush respectively. The errors still exists

The text content of base_image column is:
https://images-na.ssl-images-amazon.com/images/I/61btlFPdvBL._SL1000_.jpg,https://images-na.ssl-images-amazon.com/images/I/51I%2Bhf88F7L._SL1000_.jpg,https://images-na.ssl-images-amazon.com/images/I/51y0P8C5-2L._SL1000_.jpg,https://images-na.ssl-images-amazon.com/images/I/51uwDQfaHrL._SL1000_.jpg,https://images-na.ssl-images-amazon.com/images/I/61Wh7FkyNYL._SL1000_.jpg
@magento-engcom-team magento-engcom-team added the Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed label Jun 2, 2018
@GoogleYY
Copy link
Author

GoogleYY commented Jun 3, 2018

I've solved this problem by myself. There are two AbstractEntity.php file in magento file. One is in vendor\magento\module-import-export\Model\Import folder the another one is in vendor\magento\module-import-export\Model\Import\Entity\AbstractEntity.php. After I changed the number of DB_MAX_VARCHAR_LENGTH up to 1024 in vendor\magento\module-import-export\Model\Import\Entity\AbstractEntity.php the problem no more occurred.

I know it is not a good behavior to touch the core code. I am very appreciated if some one has better solution to solve this problem.

This was referenced Jun 5, 2018
Closed
Closed
@julienanquetil julienanquetil added the Progress: PR Created Indicates that Pull Request has been created to fix issue label Jun 5, 2018
@ghost ghost self-assigned this Aug 15, 2018
@ghost
Copy link

ghost commented Aug 15, 2018

@GoogleYY, thank you for your report.
We've acknowledged the issue and added to our backlog.

@ghost ghost added Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed 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 Component: CatalogImportExport labels Aug 15, 2018
@ghost ghost removed their assignment Aug 15, 2018
@magento-engcom-team magento-engcom-team added this to Ready for Dev in Community Backlog Mar 24, 2020
@sidolov sidolov added this to Ready for Grooming in Low Priority Backlog Sep 3, 2020
@m2-community-project m2-community-project bot removed Progress: PR Created Indicates that Pull Request has been created to fix issue Progress: ready for dev labels Sep 3, 2020
@sidolov sidolov added this to Ready for Development in Low Priority Backlog Sep 24, 2020
@geryjuhasz geryjuhasz linked a pull request Oct 2, 2020 that will close this issue
Open
4 tasks
@ghost ghost removed this from Ready for Dev in Community Backlog Oct 20, 2020
@ghost ghost removed this from Ready for Development in Low Priority Backlog Oct 20, 2020
@ghost ghost removed Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development labels Oct 20, 2020
@magento-engcom-team magento-engcom-team added the Priority: P2 A defect with this priority could have functionality issues which are not to expectations. label Nov 30, 2020
@magento-engcom-team magento-engcom-team added the Severity: S2 Major restrictions or short-term circumventions are required until a fix is available. label Nov 30, 2020
@m2-community-project m2-community-project bot added this to Pull Request In Progress in High Priority Backlog Nov 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Component: CatalogImportExport Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: PR in progress 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 Severity: S2 Major restrictions or short-term circumventions are required until a fix is available. up for grabs
Projects
High Priority Backlog
  
Pull Request In Progress
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Increase DB_MAX_VARCHAR_LENGTH to 1024 geryjuhasz/magento2
4 participants
@julienanquetil @sdzhepa @GoogleYY @magento-engcom-team