Closed (outdated)
Project:
Ubercart Dependent Attributes
Version:
6.x-1.0
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
15 Jul 2010 at 16:52 UTC
Updated:
14 Aug 2021 at 09:51 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
wjaspers commentedPlease see the attached combined screenshot for more information.
Comment #2
wjaspers commentedSeems 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".
Comment #3
Anonymous (not verified) commentedI 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.
Comment #4
Doomd commentedThe 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.
Comment #5
Doomd commentedAnd I updated this issue to "major" since the bug is essentially not performing the function of the module.
Comment #6
cybis commentedHave you tried the patch for uc_aac found here? #715878: Not aware of changes made by Dependent Attributes
Comment #7
Doomd commentedI tried the patch on post #17 (the "cleaned up" version of #16), and it didn't make a difference :(
Comment #8
cybis commentedDependent attribute doesn't work when 'required' is selected on the product attribute page. Try deselecting it.
Comment #9
replicaobscuraI 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.
Comment #10
xl_cheese commentedFWIW - I have the same issue. I have required unchecked and I can still see the disabled attribute combinations on the product page. Although, when I try to select them it flips to an attribute that is enabled.
It would be nice if the disabled attribute combinations didn't display to the customer.
Comment #11
avpadernoI am closing this bug report since it has been created for a project version that is now unsupported.
If the bug can be reproduced in a project version compatible with a supported Drupal release, please re-open this issue.
I apologize for bumping this issue.