I've installed teacommerce onto a fresh umbraco 7 installation and I'm wondering how I should go about structuring my product catalog. I notice that in the starter kit install there is a 'Product Catalog (Master Products)' node which sits at the root level and then in the actual site itself the product catalog seems to be duplicated with some kind of reference to the root level nodes.
Could someone please explain this structure and if I should go down this path?
Do you need to handle multiple languages or just one language? If just one - then dont have the product catalog. Just have the products as normal Umbraco nodes in your structure.
If you need to handle multiple languages you dont want the editor to enter the product info that is shared multiple times. Like prices, images etc. So that is why the product catalog is there and then the language specific nodes have a contect picker (masterRelation) to the product catalog product. When you use TC.GetPropertyValue it looks at the node and then at the "parent" node from the mater catalog.
TeaCommerce product structure
Hi guys,
I've installed teacommerce onto a fresh umbraco 7 installation and I'm wondering how I should go about structuring my product catalog. I notice that in the starter kit install there is a 'Product Catalog (Master Products)' node which sits at the root level and then in the actual site itself the product catalog seems to be duplicated with some kind of reference to the root level nodes.
Could someone please explain this structure and if I should go down this path?
Do you need to handle multiple languages or just one language? If just one - then dont have the product catalog. Just have the products as normal Umbraco nodes in your structure.
If you need to handle multiple languages you dont want the editor to enter the product info that is shared multiple times. Like prices, images etc. So that is why the product catalog is there and then the language specific nodes have a contect picker (masterRelation) to the product catalog product. When you use TC.GetPropertyValue it looks at the node and then at the "parent" node from the mater catalog.
Kind regards
Anders
is working on a reply...