Multi-variants not working after update

[ZoBabe]

Joomla: 3.4.8
Virtuemart: 3.0.12

When selecting multi-variant options, nothing happens (or the product URL may just be replaced with /category/"product-name-detail" to /category/"custom-option-label", but this does not refresh the page or retrieve any of the child product information via AJAX).
   Have tried with default template and other plug-ins disabled, it does the same thing but just without updating the URL at all.
   Is anyone else having this issue?
  Z

[GJC Web Design]

after update from what ?

[ZoBabe]

Virtuemart: 3.0.11.4
  I also updated Joomla at the same time from 3.4.6.
  The site I updated doesn't use very many multivariants, which  is why I tried it first. I have several sites, some of which are heavy on the multi-variants, but am getting more and more uneasy about updating as every single update seems to involve hours of bug-fixing, that I don't have time for, and my clients don't want to pay for...
  It is possible that the few products using multi-variants on this particular site stopped functioning after a previous update, and no one noticed. However, any attempt to get them to start functioning again after have failed, and I have another site still on VM: 3.0.11.4 and Joomla 3.4.6 with multivariants working as well as they ever have.
  Is this particular to some other update?
  Z

[Milbo]

I dont remember exact when it happened, but there was a problem, which depended on the product configuration.

Just use the last updated file

http://dev.virtuemart.net/projects/virtuemart/repository/changes/trunk/virtuemart/components/com_virtuemart/sublayouts/customfield.php

If you want an installer, the last release for members has it already http://extensions.virtuemart.net/support/virtuemart-supporter-membership-detail

[maxispin]

Ty Max, that fixes the Bug in 3.0.12

[gtelegadis]

I am working with a gavick template that does not yet support the most recent version of virtuemart (I am currently using vm 3.0.10), so I would rather not try and risk update unless it provides the needed benefit.  I am able to get multi-variants to work properly using 3 ramifications here:  http://www.ahgoobaby.com/Redesign3/index.php/shoes/carry/hunting-camouflage/83/15/kneekers/kneekers-detail but it is not ideal to have vm refresh the sku each time the user makes one of the ramification drop down selections.  As well vm refreshes with a specific sku ahead of the customer finalizing all ramification choices.  In my example there are 24 total skus which require 3 ramifications for the customer to determine the correct single sku desired.  After selecting the first ramification, there are 12 skus that meet that ramification and the page refreshes to the first sku on the list.  This takes valuable time and provides a sku that is most likely not the customer's final choice.  What is necessary is for vm to require the customer to select ALL listed ramifications from the back end before making the selection / page refresh in the front end.  In my example, the parent product has 3 multivariant ramifications, so vm should page refresh only upon a selection being made on the final ramification set in the back end (in my case the 3rd ramification).  Selecting ramification 1 and/or ramification 2 has no result other than setting the drop down selection.  Selecting ramification 3 then refreshes the page.  If for some reason if customer selects ramification 3 first without first selecting 1 and 2, then a notification is shown to the customer, "please complete the remaining variants" or something along that note.  This way, there aren't the current irrelevant and unnecessary page refreshes.

Can someone let me know if the current version of vm has this fix built in?  If not I would appreciate anyone's recommendations on how to make adjustments to the code to allow for the above.  I think it will make for a much better user experience when working with vm multivariants.  I have a very beginner-friendly primer I've been putting together along the way to walk someone through this and will include this answer in an option for those looking for it to share with the community.