-
Notifications
You must be signed in to change notification settings - Fork 170
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
[4.x]: Coupon Code cannot be used in conjunction with a custom order adjustment "discount" #3321
Comments
Is it possible that the conditions for the coupon and adjuster (or their calculations) conflict or are mutually exclusive? Adjusters are applied in a consistent order (based on how they're registered), and may depend on previous adjustments at the time they're evaluated against the order. Are you able to share the full adjuster class, and your |
Hi August, Thanks for looking into it. I cant see anything that would cause a conflict except the adjuster is a "discount" one.
|
Ill attempt to reproduce using your example. Thanks. |
Thanks for looking into this. Could you try via the admin panel? Sorry I should have mentioned that we are only applying coupon codes via admin panel. I did just test frontend and I can get it working like you but not via admin panel. |
@philipboomy just tried to reproduce this and found that the discount is being removed because it is a positive number discount. If you switch your discount to |
What happened?
Description
Not sure if its classed as a bug but here goes.
In some cases the client need to be able to use a coupon code on orders where there is a custom adjustment "discount".
Whenever he enters the coupon code it removes the custom adjuster making it impossible to have both. Please see attached screenshots.
Is it possible to have both somehow?
Craft CMS version
4.5.9
Craft Commerce version
4.3.1
PHP version
No response
Operating system and version
No response
Database type and version
No response
Image driver and version
No response
Installed plugins and versions
The text was updated successfully, but these errors were encountered: