Coupon behavior changed between 1.3.8 and 1.5.1?

[daniellek]

I've just upgraded to 1.5.1 and have problem with coupon:
I'd like to give one particular product for free (normal price for this product is 10.5) when total amount on order is 10 or more.

In 1.3.8 i've been setting coupon like this:
Coupon Amount 10.5
Coupon Minimum Order 20.5
and restrictions:
deny for all categories
allow for product that should go free.

In 1.5.1 the same setup doesn't work - I get error "You must spend at least 20.50 to redeem this coupon"

What's interesting, when I add this product 2 times to cart, I can use this coupon:
It looks like "Coupon minimum order" works not for whole order, but just for products which match 'restrictions'.

How can I add such coupon in 1.5.1?

[daniellek]

I'd like to give one particular product for free (normal price for this product is 10.5) when total amount on order is 10 or more.

Just to be clear:
I'd like to give one particular product for free (normal price for this product is 10.5) when total amount on order for other products is 10 or more.

[Ajeh]

You might be able to use the file:
/includes/modules/order_total/ot_coupon.php

from Zen Cart v153 and adapt the changes from the post on:
http://www.zen-cart.com/showthread.p...scount+Coupon*

from post #11 ...

What those changes do it make the minimum amount based on the Order Total rather than the Total of the Qualifying Product(s) ...

That might be the changes that you need for this ...

NOTE: In the up coming v1.6, this will be done on a per coupon basis for the minimum to be based on Order Total or on Qualifying Product(s) Total ...

[daniellek]

I've tried that with v.1.5.1 file and it didn't work as expected.
I'll try to upgrade to 1.5.3 and check it again.
Thx!

[daniellek]

Hi, I'm back :)

I've upgraded to 1.5.3 and made changes to ot_coupon.php.

Now shop says "Congratulations you have redeemed the Discount Coupon", but doesn't substract from order value.
There's something missing to make it work. Any ideas?

UPDATE: it works! I've made changes in one place instead of two - thank you very much!

[Ajeh]

Thanks for the update that this is now working for you ...

[daniellek]

I can work on a patch to get it configurable via admin interface. Interested?

[Ajeh]

It could be handy for others ...

[RodG]

G'day Ajeh,

I realise that this is an old thread, but it appears to be the most current one that pertains to a small issue that has just been brought to my attention.

You might be able to use the file:
/includes/modules/order_total/ot_coupon.php
<snip>
What those changes do it make the minimum amount based on the Order Total rather than the Total of the Qualifying Product(s) ...
<snip>
NOTE: In the up coming v1.6, this will be done on a per coupon basis for the minimum to be based on Order Total or on Qualifying Product(s) Total ...

One of my clients has recently observed that if there are no discount eligible products in the cart (due to category/product restrictions) the 'error' message produced is along the lines of 'You must spend a minimum of $x.xx (often $0,00 if no minimum has been set) to redeem this coupon' and if there are *other* products in the cart this can cause customer confusion (after all, they can easily see that the cart value is more than the '$x.xx' indicated.

After looking at the code I noted that the minimum spend check is the first one performed and if/when it fails the test the customer is redirected back to the checkout page.

What I did to avoid the misleading "You must spend a minimum of $x.xx" message was to re-organise the validity tests so that the order value test is the last check performed. The result being that the customers now see "THIS COUPON CODE IS NOT VALID FOR ANY PRODUCT CURRENTLY IN YOUR CART", which is far less confusing for the customer.

Furthermore (and this is the sole reason for this post) is that with the default code performing the value tests first it means that that this more accurate error (not valid for any product in the cart) response will *never* be invoked, and should therefore be considered a bug.

I've no idea how long this bug has been in existence (not really important IMO). The site in question is currently using V1.5.4.

I'll leave it for you to decide if the problem is 'important' enough to fix in a future update (or not). :)

Cheers
RodG

[Ajeh]

This is fixed in v1.6 ...

I have not tried to backport it to v1.5.4, as it contains numerous other features that would get complicated ...

I will try to look at this when I have some free time ...