added button buyer cart choice click code customer database default down dropdown due ejunkie example existing failed input numbers option page paypal phone preference privacy records require requiring select selected selection send setting similar somebody started suitable thread tracking update validation

When somebody fails to select a color preference, it makes for quite an interesting time tracking down the buyer and figuring everything out. As a last resort, I've started requiring phone numbers through paypal - but I'd rather not due to obvious privacy concerns on the part of my clients. So, is there a setting in eJunkie that I can use for this? Or do we know of a line of code I might include somewhere to make this mandatory?

The first option in the dropdown is already selected, so that's the color that will be added in the cart when they click the ADD TO CART button.

But my question is whether there's a way to require a selection, not rely on a default.

If there is something already selected by default, then there is no question of "requiring" a selection as an option is already selected.

I can't make a choice selected by default - that would cause me to send the wrong color to somebody who failed to make a choice. That's why I'm asking if a choice (or change) be make mandatory.

No, it can't be made mandatory by us. You can have some JS validation on your end for that.

Thanks for the update. For those looking for something similar, I was able to find a suitable js example on this page: http://www.elated.com/articles/form-validation-with-javascript/.

Thanks again -

Can I validate the customer input with our existing records from Database before Add Cart?

@zawmn83:
I think I have already answered your question in another thread here:
http://www.e-junkie.com/bb/topic/1718