VirtueMart Forum

VirtueMart 2 + 3 + 4 => Virtuemart Development and bug reports => Topic started by: lindapowers on January 27, 2013, 19:41:02 PM

Title: Use default bill to address does not update shipping rates
Post by: lindapowers on January 27, 2013, 19:41:02 PM
VM 2.018a joomla 2.58

At the checkout process, If you enter a different address from the "bill to" the shipping rates get updated BUT if you then click "use default bill to address" shipping rates don't get updated anymore.

So basicly "use default bill to address" is not updating shipping rates. Happens to everyone or we have a something incorrectly set up? We tested with the default beez template and happens the same.

Regards

Title: Re: Use default bill to address does not update shipping rates
Post by: WebStuff on March 11, 2013, 15:16:25 PM
I too came across this today testing a shipping plugin.
I wanted to try various uk postcodes but as soon as the shipto address is set it sticks and will not change back to billto regardless of pressing the "use billto" checkbox.
VM2.0.18 J2.5.9
Title: Re: Use default bill to address does not update shipping rates
Post by: sohh on February 20, 2014, 05:53:24 AM
Same error! how come no one say anything
Title: Re: Use default bill to address does not update shipping rates
Post by: AH on February 20, 2014, 14:58:27 PM
latest version is 2.02.26d

Try testing this version in your test system, then post a problem if you still have an error.
Title: Re: Use default bill to address does not update shipping rates
Post by: WebStuff on February 20, 2014, 18:40:46 PM
This bug is still present in my version.
J 2.5.18
VM 2.0.26d
I have tried with both the Beez and Atomic templates just to make sure it wasn't an override mucking something up.
The culprit seems to be
<input type="hidden" value="0" name="STsameAsBTjs">
<input id="STsameAsBTjs" type="checkbox" value="1" name="STsameAsBTjs">

The hidden top value never gets set to 1. If I manually change it to a 1 all is well and it uses the BT address instead of the ST address as I would expect.
Not sure if it might be something to do with both input elements having the same name property and something in the javascript is picking up the wrong one.