FIRST OFF: In my testing I haven't found a problem with this "solution", but that doesn't mean there aren't any, please makes backups and test your site thoroughly if you make adjustments to any files!
I'm posting this "solution" to maybe help some people who, like me, still use an old (v1.3 or v1.4) version of Quick.Cart together with wizzud's Product Attributes plugin, and to get some feedback on it's functioning.
I'm still using version 1.3 of Quick.Cart with Product Attributes, since I need that functionality, but I've always found it annoying that the selection boxes are required. Some customers, no idea how many, but a large enough amount to be noticable, get confused about their functioning, or "their order not going through" because they didn't select anything.
What I've found is that if you change a value in productAttributes.tpl (in your templates folder), it still checks if anything is selected, but it doesn't throw you an error when nothing is selected, which, to me, is ideal. What to change is here, on line 3 in productAttributes.tpl: <option value=''>$aAttributes[group]...</option>
change value='' to value='none'
so that it looks like this: <option value='none'>$aAttributes[group]...</option>
Now, since the value is set to something, it doesn't throw you an error, but since it can't find the value in it's list of options, it doesn't use it either. Any value should work, I just chose 'none' since that's the most obvious, and because a numerical value could in the future be used by another attribute accidentally.
As far as I have tested it, it works fine when you select something, the only difference is that if something isn't selected, that option doesn't show up in the basket or on the receipt, but that should be fine.
Now here is my question about this; this Seems to work well, but does anyone know of a reason why this could be a problem for functioning of any scripts or other store functions?
