I have had a closer look now into the way attributes have to be defined and assigned.
And, if I understand that correctly, I must say: this is very, very, very awkward and cumbersome.
Instead of having to [B]type in the value of each product-attribute individually[/B] (which imo is very error prone) there should be a mechanism in place like the one for selection lists…
I.e.: you define [B]all attributes available for one attribute-class[/B] on a shop-wide base, and then add one of these attributes from a dropdown-box to a product.
This would save much unnecessary typing and it would be consistent…
What is even worse is, that these attribute values are now literally stored in the “oxobject2attribute” table for each product.
So if you e.g. want to change the name of one attribute option, you have to go thru alle products with this value and change it for each an any!
If there were shop-wide attribute-lists, you could store the internal attribute option id instead of it’s value, and only change the description once in the list.