Product attribute displays every option value

[NJTackle]

When I add a new product to my catalog with a product attribute, it displays every option value entered even though I've selected a specific option name. With the ability to add option values to option names, why wouldn't it filter out and only display the values associated with the option name?

 

Almost seems like the database lost its relationships between tables.

 

Any help would be appricated...thanks!

[NJTackle]

No body else is having this problem???

[Guest]

Yep same problem here!

[Zeme]

Just to make sure I'm on the same page as you, I'm going to restate your problem in my own terms.

 

So, I arrive on the admin's products_attributes.php page, and I see the "Product Options" there, I decide to add a new Product Option "theproductoption". I click "insert". <point A>

 

Next, I see the "Option Values" section, and I decide to add some Option Values to my new product option. So, I add "theoptionvalA" and "theoptionvalB". <point B>

 

Now, I can start adding these new options to some existing products, so I look at the "Products Attributes" section. I click on the "Product Name" select box, and I see all my products listed (alphabetically), I choose "A Bug's Life", then I click on the "Option Name" select box, and I see all my "Product Options" (including "theproductoption"), so I pick "theproductoption".

 

Now, at this point, I click on the "Option Values" select box, and I expect to see only the "theoptionvalA" and "theoptionvalB" options available, and yet I see ALL my Option Values, no matter which Product Option they are associated with.

 

 

Is this an accurate description of the problem you're encountering?

 

I too have recently noticed this (I just started using osc on a test system), and as far as I can tell, this is "by design" a little (at least, there is no code trying to prevent this specifically). A big part of the reason that the Option Value list is not filtered the way you would expect is that there is no php-call after the Option Name is selected. Without a php-call (a form-submit or button click of sorts), the filtering code has to be written in JavaScript (many ppl don't like using Javascript).

 

I am planning on looking at this exact problem myself (when I have time) to see if I can get a workable solution running. There is at least 1 problem I know about, and that is the fact that the Attribute Option Type contribution relies on the fact that this relationship is not enforced (for Text inputs).

 

Mainly, I'm just using this post to inform you of how things are, and that you are essentially just seeing a "missing feature" (or "feature" depending on how you look at it).

 

When I add a new product to my catalog with a product attribute, it displays every option value entered even though I've selected a specific option name.  With the ability to add option values to option names, why wouldn't it filter out and only display the values associated with the option name?

 

Almost seems like the database lost its relationships between tables.

 

Any help would be appricated...thanks!

<{POST_SNAPBACK}>

[Guest]

Hi,

 

I'm having the exact same problem, Has any one found a solution yet?..

 

Any suggestions on how to fix this is greatly appreciated.

[Guest]

Just to make sure I'm on the same page as you, I'm going to restate your problem in my own terms.

 

That's exactly my problem, although with the site I am currently building it is actually quite beneficial. I have several different product options which require the more or less the same same option values i.e seats colour: red blue green etc, and logo colour red, blue green etc.. So even though the drop down lists are getting very long I am saving time by not having to repeat the colour values for the different product options.

 

So for this site at least I don't need to change the way it works.

 

Does that make sense to anyone?