How to use --url-key-strategy.

[IvoJongmans]

How to use --url-key-strategy.

[IvoJongmans]

Hi,

Using <generate_url_key>1</generate_url_key> on global and storeview levels solved my problems. Thanks for the quick replies.

[patrick-bigbridge]

Hello Ivo, thank you!

I just did a quick check if this actually still works, and I was happy to find that it does. I used doc/example/a-basic-product.xml and duplicated the product into a second one, while only changing the sku.

The sku is only added if necessary. It won't be added for the first product, but it will be added for the second and further products.

Your command line options are correct. What exactly happens? Did you get an error? Which one?

Can you share the xml with two of the conflicting products? You can obfuscate product names if you like.

[IvoJongmans]

Hi Patrick,

Thanks for the quick response. I've added my .xml file that I use for the product import. Change .txt extension to .xml.

exportProducts.txt (Can't upload XML's here)

I've also added a screenshot with the error I get on my CLI.

[patrick-bigbridge]

Thanks, yes it's clear to me now.

The importer works like this: you can either specify a url_key explicitly, or have the importer generate one for you. If you specify one yourself, you are responsible for making sure that it's unique.

Only if you tell the importer to generate a url key, based on the name of the product, you can tell it what to do if the generated url key already exists.

A url key is generated if you remove the <url_key> attribute and add

<generate_url_key>1</generate_url_key>

I wanted to respond to you quickly, and that means I haven't taken the time yet to think if the use case you present is acceptable. I will get back to you on this.