multivariant - page refreshing prior to all variant selections made in front end

[gtelegadis]

Hi - I've been able to correctly get custom fields / multi variant feature to work properly with virtuemart 3.  The problem I have is that with 3 ramifications, the front end user needs to fully complete selecting each of the drop down variants to properly allow vm to determine which sku to refresh to view.  Currently, the screen refreshes to the first listed sku in the list upon EACH ramification selection being made.  Is there a way to get VM to WAIT to page refresh until ALL ramifications have been selected?  The way it currently works, it not only is confusing to the end user but time wasting with each unnecessary page refresh.

See example:  http://www.ahgoobaby.com/Redesign3/index.php/shoes/carry/hunting-camouflage/143/15/kneekers/kneekers-toffee-my-sunshine-lean-leg-detail

[Milbo]

It collides with the idea, that when you change a dropdown that you should see a valid product.

For example, you selected a product. Each ramification depends on the other, so when the user changes the first dropdown, it can happen that the other selected values of the other 2 dropdowns do not exist for the parameter selected in dropdown 1.

I may could add block reloading as long a "select variant" is shown within a variant selection.

[gtelegadis]

Yes, if you mean that you are able to block reloading as long as "select variant" is shown within ANY OTHER ramification, that would be a good solution.  I see your point and agree, but as well it is equally not helpful to reload the page prior to the customer completing ALL of the ramification selections.  So effectively blocking reload as long as "select variant" remains on any of the remaining variants shown would allow the customer to complete selecting ALL of the ramifications prior to the page reloading.  Please let me know how this would be accomplished.

[Milbo]

Yepp, sounds valid, maybe for vm3.0.14. handled with minor priority, you can increase the priority by buying a silver membership http://extensions.virtuemart.net/support/virtuemart-supporter-membership-detail

[gtelegadis]

Is there not a temporary fix for this that can be done to the current code to effectuate the above correction in the interim?  I have numerous extensions and templates that are generally 6-10 months behind the current version of VM (right now they are only supporting up to 3.0.10), so updating vm is generally not going to be something that I can realistically do to keep an overall stable site until around that amount of lead time AFTER the minor priority adjustment is made to 3.0.14.  Right now it is very confusing to customers having the page reload to an incorrect product in the process of selecting each ramification.  A temporary code fix will at least allow supporters of VM to have a temporary fix while they are awaiting the ability to update the more permanent one.  Thanks in advance for your help.

[gtelegadis]

Does anyone know if this fix made it into the most recent version of VM?  If not any help for a temporary fix would be greatly appreciated.