Shipping costs over-stated when weight equals threshold for price change

Hi everyone,

I am running Zen Cart 1.3.0.1 here: http://www.beebasic.co.uk

I'm having a slight problem with the zones shipping module. I have set up the shipping costs as follows:

0.1:1.00,0.3:1.30,0.5:1.80,0.8:2.70,1:4.30,1.5:5.50,2:5.90,4:8.50,6:9.60,8:11.00,10:11.80,20:13.70

If I select an item such as the overall with a hat and zipper, which weighs 2kg, the shipping is correctly calculated at £5.90. All well and good. However, if I order, say, three bee brushes, the total weight being 3 x 0.1kg = 0.3kg, the shipping is incorrectly estimated at £1.80, instead of £1.30 as it ought to be.

I'm guessing the problem involves the fact that the total weight lies on the threshold for shipping charge changes. Can anyone help?

Thanks,

Spinner

Got a funny little bug in 3 of the shipping modules where the math is not evaluating correctly ... :cry:

This is fixed in the upcoming version ...

For now, you can edit the table.php and change the function quote area lines 105-112 to read:

    $table_cost = split("[:,]" , MODULE_SHIPPING_TABLE_COST);
    $size = sizeof($table_cost);
    for ($i=0, $n=$size; $i<$n; $i+=2) {
      if (round($order_total,9) <= $table_cost[$i]) {
        $shipping = $table_cost[$i+1];
        break;
      }
    }

The weird thing is ... were you using 1 3 5 8 vs .1 .3 .5 and .8 it would have worked fine ... :eek:

Go figure? :blink:

Hi Ajeh,

Thanks for your help. I've tried updating table.php with your fix; unfortunately, the problem doesn't seem to have been solved - when selecting three bee brushes, the shipping still shows as being £1.80 instead of £1.30.

Any ideas?

Thanks,

Spinner

have you any tare set to be added to your products?

DrByte:

have you any tare set to be added to your products?

No Tare, no.

If you view the /includes/modules/shipping/table.php ... what is the $ID read on the file?

The current one for v1.3.0.2 is:

• @version $Id: table.php 3308 2006-03-29 08:21:33Z ajeh $

NOTE: if you are still v1.3.0.1 upgrading is a good idea ... a number of fixes are in there ...

NOTE: Be sure to backup your database and site before Upgrading ...