-
Notifications
You must be signed in to change notification settings - Fork 9.4k
On checkout page coupon code validation message break when enter coupon like "test/" #21353
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
Comments
Hi @mageprince. Thank you for your report.
Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:
For more details, please, review the Magento Contributor Assistant documentation. @mageprince do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?
|
Hi @krishprakash. Thank you for working on this issue.
|
@magento-engcom-team give me 2.3-develop instance |
Hi @krishprakash. Thank you for your request. I'm working on Magento 2.3-develop instance for you |
Hi @krishprakash, here is your Magento instance. |
Hi @shikhamis11. Thank you for working on this issue.
|
also at backend it is allowed to create coupon code like test/ . Coupon is being applied from checkout cart page but not from payment step |
✅ Confirmed by @shikhamis11 Issue Available: @shikhamis11, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself. |
@magento-engcom-team give me 2.3-develop instance |
Hi @Shubham-Webkul. Thank you for your request. I'm working on Magento 2.3-develop instance for you |
Hi @Shubham-Webkul, here is your Magento instance. |
@shikhamis11 So, we can create coupons that contain or end in "/" in the backend, but then not apply them in the frontend? Then we should fix the application of code, or completely block creation of such coupons. |
@magento-engcom-team @ihor-sviziev seems the issue is solved on 2.4-develop: |
Hi @shikhamis11 could you confirm that issue is fixed and close the issue? |
@magento-engcom-team give me 2.4-develop instance |
Hi @ihor-sviziev I checked as per explanation of @sdzhepa coupon code with |
@shikhamis11 thank you! @Bartlomiejsz looks like this issue still there |
@ihor-sviziev @shikhamis11 that's weird, you can see on image attached in my previous comment that on my local which is clean fork of 2.4-develop this request was finished successfully and coupon code was added. On github test instance it ends with 404. If I'll be able to I'll try to verify what can be a difference here somewhere in future |
@Bartlomiejsz It might be related to apache vs nginx configuration. I think it might be related to following: |
Definitely looks like it @ihor-sviziev, I'm using nginx locally, so setting AllowEncodedSlashes should fix this for apache I think 👍 |
Hi @slavvka @sidolov @lenaorobei @naydav, @Bartlomiejsz in addition to that I reported issue to describe needed configuration in the devdocs magento/devdocs#6689 |
Hi @ihor-sviziev. Thank you for working on this issue.
|
@magento-engcom-team give me 2.4-develop instance |
Hi @nwmagento. Thank you for your request. I'm working on Magento 2.4-develop instance for you |
Hi @nwmagento, here is your Magento instance. |
Hi @mageprince, |
Preconditions (*)
Steps to reproduce (*)
Create a new Cart Price Rule from Admin > Marketing > Cart Price Rule
Select the next setting and value
-- Coupon = Specific Coupon
-- Coupon Code = test/
Go to Storefront as Guest or Registered user
Add test product to Shopping Cart
Go to Shopping Cart page
Click "Apply Discount Code" and apply coupon "test/" (Discount Code is applied successfully)

Click "Apply Discount Code" again and "Cancel Coupon"
Proceed to Checkout now(without cupon)
Fill all required information for Shipping Address steps and go NEXT
On Payment Method steps, Click "Apply Discount Code" and apply coupon "test/"
Expected result (*)
Actual result (*)
The text was updated successfully, but these errors were encountered: