I am trying to build a plugin that would allow me to route a customer to a specific product page when a discount code is used.
User would go to https://store.com?discountcoupon=abc123 (default coupon route)
The discount would be applied to the cart, as it is now, but then (if the discount has been assigned to a product or category) the user would be routed to the product/category that the coupon is related to.
However, upon looking into how i could do this, all of the MVC filter classes are sealed, and cannot be overridden, which is what I would prefer to do, so as to keep the standard nop functionality.
Was this done intentionally to prevent 3rd party plugins from overriding core nop functionalities?? Anyone know why this is designed like this?
I could just make a plugin route that applies the discount and also handles the routing, but I always try to implement a plugin using the tools already available rather than building the same thing from scratch that requires independent maintenance.
Thanks!
Please, no solicitation.