Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
Hi,
Is it possible to have two categories with the same name in different categories tree nodes?
Now when I try to add a second Batery category under Vectra B (1995-2002) I get "Name already exists within catalog."
You could different them by the multilingual name (i guess thats the one you display to the users?) :)
Thanks for answer.
However it's not a perfect solution for me. I try to find more suitable solution to add items with same type (like Battery) to different tree nodes.
My new idea is to make ProductType (Enum) and set there "Battery" as an option to choose.
What do you think about this solution?I'm not sure if it would be easy to search for items with "Battery" ProductType in that case.
It sounds to me like you should use a product definition "Battery" for all your battery products.
So for each kind of product you have, you will create a product definition (fx. battery).
So you would be able to fetch all product of the type to display on the page.
This also allow for some pretty neat product filtering later on.
This is it! Thanks.
I have an other problem. It occurs that for each car category I have to add subcategory with engine type.
Could you suggest best solution in that case?
So you want a category with engines ? You could call it VectraB-enginge and modify what to use as the url via. the displayname ?
I think you will create a LOT of duplicate content with that setup.
The Vectra A 1.6 and 1.8 TDI will have a lot of data in common, and maintaining that would be a hell for the editors.
I suggest making a product definitions for cars, with variants with different motorsize / type etc.
Why you don't use ProductRelations to connect products in an engine category with products in the car model categorys?
So you don't have to create multiple categorys with the same name?
Is that an option for your setup?
If not i think the way Nickolaj suggests by using different definitions would be the best approch for that.
is working on a reply...
Write your reply to:
Upload image
Image will be uploaded when post is submitted
Two categories with the same name
Hi,
Is it possible to have two categories with the same name in different categories tree nodes?
Now when I try to add a second Batery category under Vectra B (1995-2002) I get "Name already exists within catalog."
You could different them by the multilingual name (i guess thats the one you display to the users?) :)
Thanks for answer.
However it's not a perfect solution for me. I try to find more suitable solution to add items with same type (like Battery) to different tree nodes.
My new idea is to make ProductType (Enum) and set there "Battery" as an option to choose.
What do you think about this solution?
I'm not sure if it would be easy to search for items with "Battery" ProductType in that case.
It sounds to me like you should use a product definition "Battery" for all your battery products.
So for each kind of product you have, you will create a product definition (fx. battery).
So you would be able to fetch all product of the type to display on the page.
This also allow for some pretty neat product filtering later on.
This is it! Thanks.
I have an other problem. It occurs that for each car category I have to add subcategory with engine type.
Could you suggest best solution in that case?
So you want a category with engines ? You could call it VectraB-enginge and modify what to use as the url via. the displayname ?
I think you will create a LOT of duplicate content with that setup.
The Vectra A 1.6 and 1.8 TDI will have a lot of data in common, and maintaining that would be a hell for the editors.
I suggest making a product definitions for cars, with variants with different motorsize / type etc.
Why you don't use ProductRelations to connect products in an engine category with products in the car model categorys?
So you don't have to create multiple categorys with the same name?
Is that an option for your setup?
If not i think the way Nickolaj suggests by using different definitions would be the best approch for that.
is working on a reply...