You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the coupon list page, when you click on the number of uses of the coupon, it takes you to a page where all orders of this coupon are shown. This works fine for many web stores when they have just a few coupons or they have distinct name, however it's not very accurate as it's not searching for the exact coupon name.
To be more specific, take the following two coupons for example, Coupon10 offering 10% discount and Coupon100 offering 100% discount. When you click on the coupon usage for Coupon10, you will get all the orders with Coupon10, but also the orders from Coupon100.
This should ideally be updated so the code will search by coupon ID instead.
There is no formal relationship between orders and coupons to do this type of filtering. I've also just noticed this filter is no longer functional in master - running that type of search query on all post meta fields was previously done, but no longer due to the performance issues it causes. The search is a hacky way of doing it.
This link needs to be removed until a relationship is introduced.
EXPLANATION OF THE ISSUE
On the coupon list page, when you click on the number of uses of the coupon, it takes you to a page where all orders of this coupon are shown. This works fine for many web stores when they have just a few coupons or they have distinct name, however it's not very accurate as it's not searching for the exact coupon name.
To be more specific, take the following two coupons for example, Coupon10 offering 10% discount and Coupon100 offering 100% discount. When you click on the coupon usage for Coupon10, you will get all the orders with Coupon10, but also the orders from Coupon100.
This should ideally be updated so the code will search by coupon ID instead.
STEPS TO REPRODUCE THE ISSUE
The text was updated successfully, but these errors were encountered: