Posted by wjaspers on July 15, 2010 at 4:52pm
5 followers
| Project: | Ubercart Dependent Attributes |
| Version: | 6.x-1.0 |
| Component: | Code |
| Category: | bug report |
| Priority: | major |
| Assigned: | Unassigned |
| Status: | active |
| Issue tags: | attribute fallback, cart errors, cart warnings, invalid combination |
Issue Summary
- Create a product class.
- Create a set of attributes.
- Attach multiple options to each of your attributes.
- Create a product.
- Attach the attributes to the product.
- Go to the Product "Adjustments" tab.
- Turn off a combination or two of options.
- Go to the product's page.
- Choose a combination you know you disabled.
Notice anything funky?
The product is added to the cart using a fallback attribute value for whatever combination is incorrect.
What SHOULD happen, is the cart either
a) warns the user the combination is invalid and returns to the product's configure page
b) each change in attributes triggers an ajax callback to disable/enable the correct combinations
c) both of the above.
In my instance, I tried adding an "invalid combination" to my cart, and the faulty attribute fell back to another option without warning me. Then when I peeked inside my cart, I noticed the attribute wasn't what I had chosen!
Comments
#1
Please see the attached combined screenshot for more information.
#2
Seems to work ok in the 6.x-1.DEV version.
I didn't take into account how slow my test machine can be when I opened this issue report. (I should have looked for XHR/JSON request/responses in Firefox the first time around...)
If no one else can confirm this problem, please "close the issue".
#3
I have seen this happen as well. Later though I could not replicate it.
I have tried to add some user feedback of an invalid combination. I was trying to print a message of the invalid combination. I couldn't get it to work.
#4
The same has happened for my cart. I have all the latest modules (as of Nov 17 2010).
In my case, I have two attributes for tshirts:
1. Style Type (Women's Short Sleeve & Men's Short Sleeve)
2. Size: (S, M, L, XL, 2XL)
I don't sell XL or 2XL Women's Short Sleeve shirts.
On the product page, if I select "Women's Short Sleeve" as the Style Type, XL and 2XL are still available options even though I disabled the combo on the product page. The AJAX, as far as I know, should updated the Sizes to only show S, M, & L.
That's not happening.
#5
And I updated this issue to "major" since the bug is essentially not performing the function of the module.
#6
Have you tried the patch for uc_aac found here? #715878: Not aware of changes made by Dependent Attributes
#7
I tried the patch on post #17 (the "cleaned up" version of #16), and it didn't make a difference :(
#8
Dependent attribute doesn't work when 'required' is selected on the product attribute page. Try deselecting it.
#9
I can confirm that dependent attributes do in fact work just fine when 'Required' is selected on the product attribute page.
The issue I'm having seems to be that several other attributes depend on the setting of one of my attributes.
For example, the available options of Attribute B and Attribute C are dependent on the selected option for Attribute A.
If the first thing I do after the page finished loading is change attribute A, then attribute B's options get updated, but not Attribute C's.
Then, if I change the options of any other attribute (not just A, B, or C) then Attribute C's available options are fixed.
It almost seems like dependent attributes has some kind of limit for how many updates can be made at a time--I've got about 48 total option combination possibilities, and that doesn't seem like it'd be too many to me.