
Hi @navneetbhardwaj. Thank you for your report.
To help us process this issue please make sure that you provided the following information:
Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:
@magento give me 2.4-develop instance - upcoming 2.4.x release
For more details, please, review the Magento Contributor Assistant documentation.
@navneetbhardwaj do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?
@magento give me 2.4-develop instance
Hi @navneetbhardwaj. Thank you for your request. I'm working on Magento 2.4-develop instance for you
Hi @navneetbhardwaj, here is your Magento instance.
Admin access: https://i-26040-2-4-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.
@magento give me 2.3.3
@magento give me 2.3.3 instance
Hi @navneetbhardwaj. Thank you for your request. I'm working on Magento 2.3.3 instance for you
Hi @navneetbhardwaj, here is your Magento instance.
Admin access: https://i-26040-2-3-3.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.
@navneetbhardwaj do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?
Yes
over Magento 2.3.3 issue is persist
But Not found 2.4-develop
@magento Yes, I confirmed that I was able to reproduce the issue on vanilla Magento instance version 2.3.3
Hi @shikhamis11. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:
Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.[ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.
[ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
[ ] 4. Verify that the issue is reproducible on 2.4-develop branchDetails
- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
- If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and _stop verification process here_!
[ ] 5. Add label Issue: Confirmed once verification is complete.
[ ] 6. Make sure that automatic system confirms that report has been added to the backlog.
@magento give me 2.4-develop instance
Hi @shikhamis11. Thank you for your request. I'm working on Magento 2.4-develop instance for you
Hi @shikhamis11, here is your Magento instance.
Admin access: https://i-26040-2-4-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.
hi @navneetbhardwaj
thank you for reporting this issue .. it seems this issue is already fixed in 2.4-develop branch.
Hi @shikhamis11,
Could you link us the commit message related to the fix?
Thank you!
I had the same issue one year ago on Magento 2.3.0, which has been patched. Now on Magento 2.3.3 it happens the same. I also checked 2.4-develop and loos like it's patched again.
Anyone has a hotfix of this issue for 2.3.3?
I have exaxtly the same problem with Magento 2.3.3 and PHP 7.2.24
Tried many possible ways but no luck so far. Can anyone address how to resolve this issue?
Hi @tushhan & @flytomek,
I believe this is the file in question: https://github.com/magento/magento2/blob/2.4-develop/app/code/Magento/CatalogImportExport/Model/Import/Uploader.php
I'll be able to confirm at a later date wether this solves the issue. If anyone else wants to confirm the changes to fix the issue for 2.3.X feel free :)
Hi @tushhan & @flytomek,
I believe this is the file in question: https://github.com/magento/magento2/blob/2.4-develop/app/code/Magento/CatalogImportExport/Model/Import/Uploader.phpI'll be able to confirm at a later date wether this solves the issue. If anyone else wants to confirm the changes to fix the issue for 2.3.X feel free :)
Just received word that changing this file alone will not solve the issue. Seems to be an open-source only issue for 2.3.X.
Workaround can be:
Hi @engcom-Delta. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:
Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.[ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.
[ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
[ ] 4. Verify that the issue is reproducible on 2.4-develop branchDetails
- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
- If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and _stop verification process here_!
[ ] 5. Add label Issue: Confirmed once verification is complete.
[ ] 6. Make sure that automatic system confirms that report has been added to the backlog.
Hi @navneetbhardwaj thank you for your report. I am not able to reproduce issue by steps you described on clean 2.4-develop
Csv file is imported succesfully: importImageUrl.csv.txt
If you'd like to update the issue, please reopen it.
Most helpful comment
Hi @shikhamis11,
Could you link us the commit message related to the fix?
Thank you!