Not aware of changes made by Dependent Attributes

jm.federico,

If you do not wan't the Pink + 50ml to be a selectable combination, then you need to visit the products "Adjustments" tab and uncheck the "Enabled" checkbox for this particular combination that the "Dependent Attributes" module adds to the form. If you have done that and are still seeing an issue, please describe in further detail.

Cheers,

Antoine

I have the exact same problem on my setup. For a demo try this:

- go to http://lucbusquin.com/node/7 it's fixed!)
- choose 'Fine Print' with a 'wood frame' option
- go back to 'Value Edition'

The sku and the price are now for an item that is deselected in the 'Adjustments' tab (this shouldn't be). If nevertheless you add the selection to the cart the correct (but different) price and item are added.

Here is another observation: Ubercart Option Images is not affected by this bug and displays the correct image for the selection. This seems to suggest the issue is indeed with uaac and not with Ubercart Dependent Attribute.

As a way to warn visitor of the potential problem, I've use the sku fields in the 'Adjustments' tab of deselected item to display a error message (see http://lucbusquin.com/node/7 it's fixed!)

Please let me know what further info you guys need (the status of this issue is 'postponed (maintener needs more info)').

I recall doing some really messy custom hacking to get uc_aac working with a whole series of modules (price per role, dependent attributes, option images, out of stock) and don't think I'm going to be able to do the uc_aac rewrite in d6 that would accommodate these all in a generic way like a hook system. If someone else has the drive to do that, I'd be glad to start a 3.x branch and give commit access. If not, this probably won't cross my mind again until d7.

For the dependent attribute specific part of this issue, marking as a dup of #715884: Changes in form not being exposed to Ubercart Ajax Attribute Calculations

If anyone wants to open an issue related to any of the other modules mentioned above, feel free to.

I’m way out of my element here, but it seems to me that the compatibility problem may lie with uc_aac.js.
When a click event occurs on the add to cart form, uc_aac will proceed in the following sequence:

• (1) Make a request with POST
• (2) Replace the HTML elements with the new values
• (3) Update the add to cart form

Since (1) and (2) occur before (3), the HTML elements (SKU, diplay price, etc.) will be replaced with value from a combination of attribute options that may have been deselected in adjustments page.

I think (3) should occur before (2), no?

I modified uc_aac.js to execute the following:

1. Make a request with POST
2. Update the add to cart form
3. Make a new request with POST
4. Replace the HTML elements with the new values

It seems to fix the compatibility issue. I've attached the modified uc_aac.js. As I said earlier, I'm way out of my element here and I'm sure there is a prettier to do it.

Changed status to 'needs review'.

Ok, I think I got these modules to work together:

• uc_aac-6.x-2.x-dev
• uc_option_image-6.x-1.4
• uc_dependent_attributes-6.x-1.x-dev

uc_aac.js was modified further from my previous post here to work with uc_option_image.
(I'll post a patch file as soon as learn how make one ;)

Don't use attached files. See post #16.

Here is the patch associated with post #12. (my first patch, let me know if doesn't work)

Don't use attached files. See post #16.

Thanks Cybis, hopefully some people will be able to test this out and give some feedback. I imagine it will be helpful for others in the same scenario.

As far as committing the code into a new release, I'm not fond of the section with:

if (UCOI) {

The modules need to find a nicer way to play together than to make special cases like that. I've talked with others about a hook system to make this all work, but it is outside of what I want to do with the D6 version....so a solution like you've provided will probably be necessary for anyone who wants to combine these modules, but isn't the route I'm hoping to take moving forward.

As far as doing a double request, again I'm glad you found a working solution, but that isn't the route I'd like to take with the module. When a large majority of the scenarios work with 1 request, doubling that to cover an edge case would be a bad idea.

cYu,

I totally understand where you're coming from. The patch I provided is more a hack than a workable solution. I'm working on getting rid of 'if (UCOI)' and making option image work with attached behavior instead. (if(UCOI) was coming from an earlier patch)

As far as the double request, again not pretty, but it's the only way I can think of for uc-aac to work with modules like dependent attributes. I'm curious if the increased load is the only downside to it.

hopefully thinks will look up with D7

Thanks for your great work, cYu!

Ok, got rid of the ugly ‘if(UCOI)..’.

I modified Uc_option_image.js to work on aac’s Ajax delivered content by being called with Drupal.attachBehaviors() in uc_aac.js.

So unmodified aac should now work with this patched UCOI.

The ‘dual requests’ stays in order to enable dependent attribute compatibility.

The attached files are needed only to work with dependent attributes.

Attached is a cleaned up version of the patch #16. Also it works with uc_aac-6.x-2.1.

Thanks for the patch. However, it didn't make any change in the behavior I'm getting that was reported in this bug. It still won't filter out the unselected attribute combinations.

I am also getting the issue where I can't get dependent attributes to filter out the unselected attribute combinations.

I have a select list where it shows all options, but I can't select the unavailable combinations.

It needs to simply get rid of those unwanted options all together out of the select list.

This post may be confusing, it's 5:45am and I haven't slept yet :)

It works for me with Dependent Attributes 6.x-1.x-dev and a patched uc-aac-6.x-2.1.
But, make sure 'Required' is not checked for all your products attributes or it won't work.

xl_cheese and BrisCoder – Any luck since you last posted? I'm having the same issue and am using the same mod versions as cybis in #20. Feels like I've tried everything. Any breakthroughs would be appreciated!

im in the same boat. seems as though it initially works, but after adding a few items, I'm no longer seeing the selects change to reflect the excluded attributes.

update: I've narrowed down where the problem is occurring, at least in my situation.

I'm working on a clothing site, where jeans in certain colors are available only in certain inseam or waist sizes. However, the prices do not change. This lead me to set 'admin/store/settings/attributes' -> option price format "checked" / "Do not display".

This seems to break the select list updating. Once i set the radio button back to "display price adjustment", the unavailable select list items are correctly removed from the lists.

Hope this helps anyone else coming up against something similar.

See this post for a much better solution: #1235202: uc_aac should supply a context to attachBehaviors after modifying the add to cart form.

Hi cybis,

This patch works like magic for me... thank you!

Well, I don't understand jquery. I had tried the patch at http://drupal.org/node/1235202 and could not get it working.

Than I tried this patch and it did work!!

Thank you

@priyankap, patch #17 here works but is clunky and obsolete. I currently use uc_dependent_attributes 6.x-1.x-dev unpatched and uc_aac 6.x-2.1 patched only with #1235202: uc_aac should supply a context to attachBehaviors after modifying the add to cart form with good results.

I've attached those modules as currently sitting in my install.