Since the default option text now uses what is set in POST if it's set, dependent options are not always updated to the correct defaults when moving back and forth across options eg:

I get to the page and here are the options (*=selected)

2006*
2007
2008

Dodge*
GMC

Ram 1500*

Let's say I have a 2007 something or another, so I choose 2007, now we have:

2006
2007*
2008

Chevrolet*
Dodge
GMC

Silverado*

The problem arises when I decide I want to select something back in 2006 instead...I get this:

2006*
2007
2008

Dodge*
GMC

Silverado*

CommentFileSizeAuthor
#3 uc_dependent_attributes-635090_2.patch5.3 KBjantoine
#1 uc_dependent_attributes-635090.patch5.07 KBjantoine

Comments

jantoine’s picture

jantoine commented
Assigned: Unassigned » jantoine
Status: Active » Needs review
StatusFileSize
new uc_dependent_attributes-635090.patch5.07 KB

jpstrikesback,

Try this patch with the latest patch from this uc_aac thread: #629416: Dropdowns revert to default state after selection

Cheers,

Antoine

jpstrikesback’s picture

jpstrikesback commented

Interesting changes:

- The Last Select Doesn't filter until you choose something from it (like if you choose something that shouldn't be in there it updates to the proper default, but not until then)

- The behavior where going back and forth across options doesn't rebuild options that have been set once is still in effect.

- I've also seen something 2 times but I cannot replicate it and that is when you've gone back and forth over options and arrive at something you want and click add to cart - once in a while it will put 2 items in the cart...weird eh, again I can't replicate now, and it may have been hanging around in POST while I patched the module??

jantoine’s picture

jantoine commented
StatusFileSize
new uc_dependent_attributes-635090_2.patch5.3 KB

jpstrikesback,

This was an ordering issue with the attributes when generating all possible combos and then filtering. Attached is a patch that uses the ordering of the attributes from the form, not the ordering in the database table.

Cheers,

Antoine

jpstrikesback’s picture

jpstrikesback commented

Hey Antoine,

Is this patch against the last patch or the original commit?

Cheers,
Jon

jantoine’s picture

jantoine commented

Hey jpstrikesback,

Patches are always against the code in the repository, never against other patches, unless those patches have been committed, in which case they would be in the repository. Hope that makes sense.

Cheers,

Antoine

jantoine’s picture

jantoine commented
Status: Needs review » Fixed

Patch from #3 committed.

Cheers,

Antoine

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.