-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Order creates an outstanding amount when using single use discount #55
Comments
This is still a serious issue and we have been unable to find the cause despite many developer hours. |
@danaenz So this is for a single use coupon used twice or 2 different single use coupons? Can you replicate on a clean checkout of the latest releases. |
Does this issue occur if you use a different gateway, perhaps just test with the dummy gateway and confirm. If the issue only happens when using DPS as your gateway then it may be caused by the same issue described here (unresolved). Because DPS notifies the site that the payment went through in the background (not part of the user session) any order data in session or requiring session isn't available which affects discounts. |
@christopherbolt this would definitely explain it! We haven't been able to replicate the issue on local test environments reliably. It would explain a lot, actually. I'll keep looking into it. |
@danaenz did you ever make any progress with a fix for this? |
Sorry @beeonlinenz , no progress yet. I'm actually working more with SwipeStripe now so haven't had the chance to try and solve this. |
Please see my related bug report where I have posted a solution to this issue: silvershop/silvershop-core#705 |
I had this issue on a project with unlimited discounts. The problem is, that the order is calculated somehow, but not saved to DB with multistep checkout. I changed the setCoupon method to:
This seems to fix the error. |
@wernerkrauss Did you want to send this as a PR? |
I've used the onPayment hook to update the final order:
|
Silvershop Discounts dev-master
SS version 3.3
I've run into this issue consistently across SilverStripe, SilverShop and Discount versions. It has been notoriously hard to replicate, but the above should work.
The text was updated successfully, but these errors were encountered: