Are Sub Attributes possible?

[ktomas]

That is what I said. What I've decided to do is to have 11 options, and simply group them together with the design rather than trying to have 4 options with dependent variables (obviously, because this is impossible). For instance, I'll have:

Center Stone
_Crystal
_Pearl

Stone Color
_Brass
_Green
_Bronze
_etc

Stone Shape
_Round
_Square

And so on.

The only problem with this, is that the customer may not want to have a center stone, and would chose "none," but they are still able to chose stone color and shape...etc, which become void since they said "no" to a stone in the first place. I've seen this done before, it just doesn't seem as professional to me.

Is there a way to "turn off" subsequent options if a preceding one is not checked? They could still be visible, just not active? I'm pretty sure I've seen this before.

[kobra]

Is there a way to "turn off" subsequent options if a preceding one is not checked?

This again croses into the "dependant variable" arena

[kuroi]

Attributes are one of the more complex areas of Zen Cart. Even as they are now, people find them difficult to understand and work with. Dependant attributes is just one of several ways that they could be further extended, but the challenge each time is to find a generic solution that works in all circumstances and which remains usable for Zen Cart users.

The requirements that you describe above are of the sort that are often easier to build for a specific situation. And that's the beauty of open source software, you're allowed, even encouraged, to do so.