zero balance requiring payment method

[llegrand]

This was an issue back in 1.1.7  I think,  but it was fixed previously.  Seems it might be back again there is one payment - authorize.net  installed,  it has been working flawlessly for many months.

In applying a credit to an account thatreduced the order to zero  I am getting 
Error: payment method required.

You can see by the screen shots that system has identified that there is a payment account noted but the previous fix to ignore zero balances seems to be broken.

this is a 1.2.6 Abantecart Version

thanks

[abantecart]

We will get on this issue for upcoming 1.2.7

[abolabo]

what means 10$ flat rate shipping adjustment?

[llegrand]

It is a coupon,  that adjusts shipping charges to $10.   Been in use on the site for months, without conflict.

[Basara]

The issue confirmed. To replicate select payment and on the confirm order page click apply balance.
No matter what payment selected or coupon applied.

[llegrand]

Just for clarity -  in my situation -  there is only one payment method and the shipping is set for that one payment,  so it automatically shows up with the CC info box.

Further -  the Authorize.net is set for .01 minimum in regular operations.   I did try it set to .00, but it still failed.

[abolabo]

issue fixed in 1.2.7.
More details see here https://github.com/abantecart/abantecart-src/commit/99bfad39d7c8a208279683f0921684ec7a5acd02

[llegrand]

thank you,  Will test it in 1.2.6 and let you know the results

[llegrand]

hmmm - I exchanged the file -  but it doesn't work as expected

The coupon code is now showing up a bit differently  AND when acting on behalf of the customer -  I cannot complete the transaction  without logging into the account  -  which was not necessary previously  -  I could apply the credit to the account.

Perhaps a bit more testing on your side is necessary for completing a transaction - both when a customer and as admin working on behalf.

[abolabo]

hmmm..how it related to changes?

[abantecart]

Not sure if this is specific 1.2.6 issue or your set up, but all works as expected on coming up 1.2.7
We just QAed this part.

[llegrand]

I have just finished testing this issue in the 1.2.7 pre-release version available 5/9.

This function now works correctly. 

Thank you for fixing that.

Lee