1
Answers
Product Select attribute first
Within my product display I have various products some with the same title and varying other attributes.
I have found that no matter what I do the additional attributes always display first then if there different products associated then I get the select product option.
What I want to do though is for the customer to be able to select the product first then adjust their choice using the other attributes.
Is this possible and if so how can this be done. I've even tried altering the weight of the attributes using form alter but makes no difference.
Comments
OK but if for example your product has no attributes and your product display contained various products all with different titles you would see a select product option as an attribute. If you then add attributes to these products as well, these are displayed first with the product title option showing depending on what attributes are selected.
I want to be able to select the product by title first then by attributes.
Not sure what you are looking at, Take a look here:
http://www.collaborative.org/events-and-courses/using-visual-representat...
This is a page I have setup for an event. The drop down is the Product that you are choosing, the Are You a Member is the attribute. This attribute is set per product, so if I adjust the product in the drop down, that attribute is being shown for that product only.
Ok so here's a screenshot of my product variations
https://www.dropbox.com/s/tbjwbv2dw9v57pf/Screen%20Shot%202013-11-02%20a...
where quantity and curing method are my 2 attributes and then I have various products, some of which have the same title.
However when you first load the product display I only see the attribute options like this
https://www.dropbox.com/s/soa4411l4xjbt96/Screen%20Shot%202013-11-02%20a...
and the product selection option only appears when there are multiple variations title based on the attributes selected, like this
https://www.dropbox.com/sh/i0h1391dplplcd4/1TyGLaZIfq
The product selection will only appear if you have more than one product variation attached to the product display, if you only have 1 product variation attached, you will only see the attributes since there are no other products to select from. "based on the attributes selected" is a little confusing because there are no conditions that enable a different product if you select another products attribute.
Ok maybe I need to rephrase my original question as if this the default behaviour for DC then I need to find a way to override it as it doesn't work in certain scenarios.
Here's my usage based on product display called Fruit with various bag weights
Apples
--2kg
--5kg
--10kg
Oranges
--5kg
--10kg
Bananas
--5kg
--10kg
In the current setup this would load with just the weight attribute showing as there is only 1 product variation for 2kg Apples, only when you change the weight to 5Kg or 10kg would you see the product option.
From an end user point of view this makes no sense, you'd expect to be able to choose your fruit then the weight.
Yeah see what your saying doesn't make sense to me.
The Product variation is the Apple, the weight is the Attribute. "there is only 1 product variation for 2kg Apples" doesn't make sense since there is no product variations for the weight, the weight is the attribute of the product variation.
So your scenario should work like this:
Yes I know it's probably not the normal way to do it but it's how the people I'm building the site for want it.
Yes you are correct on how my scenario should work.
Well lets get this working for you. I think the confusing part for me is your setup sounds perfect until you get into the use. So can you explain the user flow for what you are looking for?
Such as:
- How does the Product Display work for you? Are you creating nodes called Fruit or nodes called Apples?
- Are the Products setup as individual fruits or are they literally variations of the same Product Display (As in Apples for the Product Display, and each Product Variation is ONLY the weights you are selecting)?
- After answering the above, what is the user path one would take in order to order something from the site?
Ok the fruits was just an example, but it it would be a product display called Fruit and a variation is added for each fruit of each weight
If you want may actual usage I have a product display called chemicals, which contains various type of chemicals (products) with 2 attributes quantity/weight and curing method. Here's and screenshot of the products within the display https://www.dropbox.com/s/tbjwbv2dw9v57pf/Screen%20Shot%202013-11-02%20a...
In terms of the process for the user, I would expect the user to view the product display, select the name of the product that they want, then select any available attributes associated to the selected product.
Sounds like your use case is exactly how I mentioned the setup would be. But because you have completely separate products for each weight, that won't happen. Do you need to have separate SKUs and Products per weight? Or can you have Accelerator G with 3 weights to choose from as a simple attribute? Right now you have 3 separate AGs products with 1 per weight.
If you need it to be that way, you could:
1) Create a Chemicals node called Accelerator G
2) Add the 3 product weight variations, alter their Variation Title so its clear which one you are selecting ("Accelerator G - 4kg")
If you need to have a single node called Chemicals, from the sounds of it thats what you are doing and attaching all products to it, you can do the same thing, just alter the variation title so its clear what they are picking.
If they need to be separate products, then you should just remove the Attribute because that's not how an attribute would be used and having it show up will be confusing for the user. If you still need to report the weight in a separate field, you can, but as a standard text/weight field instead of an attribute.
Thanks for all your advise on this. I ended up finding a solution, whilst probably not the cleanest of solutions, it works. Basically I've added a Taxonmony vocabulary which will hold the product titles, this can then be used as an attribute which then produces the desired result.