-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Product Import: Additional data: Invalid URL key #10697
Comments
@Alex-James17 can you attach a sample file please. |
File attached, the comma should be in one of the values rows, not the header as per the attachment. |
Thanks - internal issue is MAGETWO-72101 |
I would like to look into this issue |
@avdb I've sent you an invite to join Magento Team on the GitHub. Please, accept the invite |
@okorshenko done |
@Alex-James17, thank you for your report. The issue is already fixed in 2.2-develop branch (PR: #11049 by @avdb) and will be available in the Magento 2.2.2 release |
Internal ticket to track issue progress: MAGETWO-80229 |
Hi @Alex-James17. Thank you for your report.
The fix will be available with the upcoming 2.3.0 release. |
magento2.3.0 |
Same problem at me too. |
Magento 2.3.1 still buggy :( |
i get same error, exportet from shop, import this error 2.3.1 |
This issue is also happening when there are two slashes in a category.
This is on Magento 2.3.1 |
I am still facing this issue in 2.3.2. Please let me know what is proper fix for this issue. |
do you find the solution or not? it occurs to me |
Any solution to this issue. I am getting the same issue on my Magento 2.3.4 version.? |
Actual Result
When performing a product import with a category field which begins with a comma, a General Exception is raised with a spurious error message and no rows are imported.
Preconditions
Running Magento 2.2 on PHP 5.6.28 with MySQL 5.6.34 on MAMP under MacOS 10.12.6
Steps to reproduce
Expected Result
I would expect the error message to indicate an issue with the clearly invalid category field (column 5 in my file) rather than pointing at the url_key field (column 18 in my file).
The text was updated successfully, but these errors were encountered: