VirtueMart + AWO Coupon + Free Item: Doesn't work ...


  • Default avatar
    olf032    
     3 years ago
    0

    Hi there,

    I'm handing out coupons to my customers so they can download MP3 files for free from my VM installation. All files (VM, AIO, AWO) - up to date.

    Now, this always causes an error message, telling the customer there's an invalid PayPal amount. Up until now, there used to be fix where you corrected some lines of code in Plugins / Payment / Paypal.php . I just tried to fix this again after updating to the latest VM files, but now - it doesn't work anymore. The error message still appears, even after flushing the cache. Any suggestion on what I can do?
  • Your avatar
    seyi    
     3 years ago
    0

    Hello,

    Are you using Virtuemart 2.0.24? I believe the problem with payment methods and 0 total has been fixed in this version. They now include the coupon discount.

    So what you should do is create 2 payment methods:
    - Method 1: Paypal, and set minimum amount to 0.01
    - Method 2: Standard Zero Total and set maximum amount to 0.01

    So when your total s 0, only method 2 will appear.
  • Default avatar
    olf032    
     3 years ago
    0

    Hi Seyi!

    Thanks for the feedback. Yes, I'm using the current VM version. The bug still persists.

    I've tried your method, setting up a second payment method (direct transfer) with max amount 0.01, setting Paypals min amount to 0.01. It works well and Zero Pay is the only option showing, but I still get an error message INCORRECT AMOUNT when finalising checkout.

    What can I do about this? I've been able to get Awo Coupon to work with prior VM versions by fixing some of the PHP code as suggested elsewhere, but it doesn't seems to be working anymore that way. So, in a nutshell: AWO Coupon is not working for me with the current VM and transactions totalling to 0 ...
  • Your avatar
    seyi    
     3 years ago
    0

    Hello,

    Sorry to hear it is still giving you problems. Virtuemart and 0 totals in general have been a bug for a long time.

    Exactly what error are you receiving when confirming? Are you using any type of third party checkout?