The problem with pure multidimensional variants is the following:lets assume you sell goods in different colors and sizes.While size does not matter for you (same price, same photos, same ...), the color does matter (e.g. different photo).If you now have 5 sizes and five colors, and each color gets a distinct photo, you will have to upload 25 pictures.This was the reason for me to use both techniques at the same time. Because now i will only have to maintain 5 variants instead of 25.I admit that this way is not working under all conditions (e.g. different prices for different sizes) and there might be an existing way to achieve the same results, that I have overlooked.What I did not see for example was a possibility to create tree-like md-variants.e.g.:A has variants B and CB has variants D and EC has variants F and GThis would also make it possible to maintain 5 colors, while the sizes inherit all their attributes from the colors. However, this seems to be a more deep change.Jan-----Ursprüngliche Nachricht-----
Von: "Linas Kukulskis" <[email protected]> Gesendet: 21.03.2011 09:10:40 An: "[email protected]" <[email protected]> Betreff: Re: [oxid-dev-general] Submission for SelectLists Hello, From your letter it's not clear why you are using variants and selection-lists at the same time. Our advice would be use selection-list where it is enough (feature gives you functionality you needed), where it is not enough use variants or even multi dimensional variants. Linas Kukulskis Developer ________________________________________ From: [email protected] [[email protected]] on behalf of Jan Sandbrink [[email protected]] Sent: Friday, March 18, 2011 10:20 PM To: [email protected] Subject: [oxid-dev-general] Submission for SelectLists Hello, I've noticed that using variants and selection-lists at the same time can be quite irritating in some cases. If the article has different variants it will not be buyable directly (because you can only buy its variants). For that reason i added an additional check to the detail.tpl, that prevents a select-list from being displayed in that case (the dropdown would not be usable anyway, but can irritate the user). In the product.tpl I basically added the select-list code from detail.tpl, to enable the user to add an article to his shopping cart with a selected value from a select-list (previous behavior was, that the first selectable value was set). I hope I was not unclear about my intentions. I would appreciate any feedback. Jan Sandbrink _______________________________________________ dev-general mailing list [email protected] http://dir.gmane.org/gmane.comp.php.oxid.general ___________________________________________________________ NEU: FreePhone - kostenlos mobil telefonieren und surfen! Jetzt informieren: http://produkte.web.de/go/webdefreephone _______________________________________________ dev-general mailing list [email protected] http://dir.gmane.org/gmane.comp.php.oxid.general
