-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Customer got an error about Virtual Product after setting the shipping address on Cart that contains Downloadable Product only #26107
Comments
The error message originates in This exception is caught in There are two reasons a
I would like to change the exception message to something similar to @lenaorobei Is there an alternative I'm overlooking? |
Hi @TomashKhamlai. 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. @TomashKhamlai do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?
|
✅ Confirmed by @lenaorobei Issue Available: @lenaorobei, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself. |
Hi @sanjay-wagento. Thank you for working on this issue.
|
#MM20IN |
@lenaorobei I have reviewed the issue and it seems this is not related to graphql only. The message is comming from Magento core module. It seems above message is not related to virtula product only but it is for all product that does not contain shipping address. If you think this is valid issue then can you please tell me which type of mesage you want to display through out system for downloadable, virtual and gift card virtula type products? |
Hi @sanjay-wagento! Please have a look at the comment from @pmclain. This is the best option we have now - change the exception message. |
Hi @TomashKhamlai. Thank you for your report.
The fix will be available with the upcoming 2.4.1 release. |
Preconditions (*)
Steps to reproduce (*)
Expected result (*)
Actual result (*)
The text was updated successfully, but these errors were encountered: