Payment gateway bug

I see… I also observed some strange behavior with payments. It does not obey the setup rules.

@miso00 right on! I was trying to figure out the problem but gave up. What you described is exactly what is happening. The default APG shipping payment method become the store wide default for all shipping methods.

Exactly.

I’ve asked Emilio to look into this. He’s going on holidays this week. Hope he sees this before going ??

We’re going to see what happens today, before going on holidays.

As soon as possible, we’ll update the plugin.

?? Good luck!

Fixed, along this morning we’ll publish the update.

Thanks. I even observed checkout process getting slow. I think it is very important how we setup the state/postcode groups.

For example if your store has more light weight products (below 200g or 200kg) then

200|100|P1
200|110|P2
500|200|P1
500|220|P2

maybe more efficient than

200|100|P1
500|200|P1
200|110|P2
500|220|P2

This effect would amplify if you have more groups. I didn’t dig much into the code but this is my intuition.

The plugin get the rate by group (from postal code – P groups – to country – C groups -), not by weights.

When it get an available rate, it’s apply to the shipping cost for calculating the order weight.

Probably, the slowing probably was generated by new WooCommerce core :-(.

Thank you sooooo much. The default APG shipping payment gateway doesn’t affect payment gateways of the other shipping methods already.
But there is still one little problem. If you choose only one payment method for aditional shipping class it shows all enabled payment methods during checkout. So, payment gateways doesn’t work for aditional shipping class.

You’re right. We’re sorry.

Fixed on the version 1.3.6.

You have nothing to be sorry for. Thanks much. You deserve donation from all users.