-
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
The shipping information was unable to be saved. verify the input data and try again. #23908
Comments
Hi @mehmetuygun. 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. @mehmetuygun do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?
|
Hi @engcom-Bravo. Thank you for working on this issue.
|
@magento give me 2.3.2 instance |
Hi @mehmetuygun. Thank you for your request. I'm working on Magento 2.3.2 instance for you |
Hi @mehmetuygun, here is your Magento instance. |
Hello @mehmetuygun. Thanks for applying. We've been not able to reproduce Your issue on a vanilla magento instance. Please confirm You are able to to so. |
I couldn't reproduce issue on magento instance either. |
@mehmetuygun, if an issue is not reproduced on a fresh magento instance, free from any custom code, third party extensions, etc., then it is not a core magento bug this repository is intended for reporting. Please refer to the Community Forums or the Magento Stack Exchange site for advice or general discussion about this issue. Thus we are supposed to close this issue but please feel free to reopen it if deem necessary. Thanks for applying. |
This issue is related to this issue: #23618 |
I created #23618 and there is a reference to this issue. So I check and the first I see is that this issue is closed here as well. |
We've been seeing this as well on a 2.3.2 install. Our data was imported from a Magento 1.9.x install using the Magento Data Migration Tool. We were originally suspecting something to do with the data migration, but it still happens when you create a new account. At the moment we're disabling our 3rd party modules one by one to see if we can narrow it down, but this behavior seems to have been around since before we added our 3rd party modules. |
I imported the customer data via CSV as I have bad experiences with the data migration tool. |
Disabled all third party modules and still seeing same behavior. Traced things back through the code and found some interesting things happening: exception.log shows the error coming from That's However, $cart->getCustomerIsGuest() is reporting me as a guest, when in fact I'm not. I logged in during checkout, and I'm continuing to refresh the checkout page, so it should be pretty apparent by now that I'm logged in. It is actually showing me all of my addresses, so it clearly thinks I'm logged in. Ultimately, getCustomerIsGuest() pulls the information from the quote table, which I checked and found that for my customer_id, my active quote had customer_is_guest column set to 1. I'm not sure how the quote (merged from my guest cart) ended up with customer_is_guest still set to 1, but after clearing it, the problem vanished (at least for now). The following query helped me find the other quotes in the same situation:
Then I reset them to the proper status:
The only quotes I could find in this state belonged to test accounts. I'll continue with testing with 3rd party modules enabled, and comment back if I find anything else improperly messing with the customer_is_guest field. |
@sbrendtro, this is a good catch! I was not getting this critical message. But I was having the same in the quote table customer_is_guest was 1 with this testing customer. Setting it to 0 fixed things. |
Do you mean
rather than
? |
Yes, thanks for pointing that out. Just edited my comment. |
No, thank you for pointing out the fix for what was turning out to be a massive pain in the backside for a client! |
@onepack I think you should put this solution in your issue too because I believe it will help many people including me. |
This is an issue that effects both Magento 2.2.9 and 2.3.2 It is also pretty disturbing to see Magento team denies that such issue exist. I can also confirm that the issue occurs on a clean installation. Thanks to @sbrendtro we corrected the issue on our shop but denying such important issues on an Enterprise solution is not acceptable on magento teams behalf. |
Dear members of this conversation. Please provide the steps following which we can reproduce the issue on a vanilla Magento installation of 2.3-develop version - the issue will be immediately reopened and confirmed. Dear @onepack, we are not eager to close the issues. We just follow our workflow (please see details to step 4 of this comment above #23908 (comment)). Thank You all for understanding. |
It is really hard to reproduce as this is not an existing issue for everyone. For example when i checked our production instance , we had 85 total user quote that was effected by the issue. We of course corrected the quote issue but a step by step way to reproduce it is extremely hard. One day after correcting the quote's we have this issue back in place. Magento seriously urgently release a patch for this issue as this is effecting many customers incomes and most are not possibly aware of the issue. Just because Magento team choose to close close issues for keeping clean board doesn't mean that us Enterprise customers are going to loose money. In no condition Magento should allow a Logged in customer quote assigned as a Guest customer. But this can happen because of . a weird logic Magento team choose to implement. This shouldn't happen at all. |
@engcom-Bravo We have same problem with magento since the 1st day of launching. The magento team should take a look on how you implement quote validation with |
Here's a temporary workaround at the database level (USE WITH CAUTION). Since no one seems to be able to figure out where this is coming from, I figured I would use a MySQL trigger to prevent
edited: Both triggers were on BEFORE UPDATE, changed the first one to BEFORE INSERT. |
@hostep no problem, let's re-open it and check once again. Thanks! |
Still an issue on newest magento version |
Verified the issue on Magento 2.4-develop branch but cannot able to reproduce the issue due to below issue:; |
Magento 2.4.4 [2022-04-13T12:52:34.090875+00:00] main.CRITICAL: Magento\Framework\Exception\NoSuchEntityException: Id do endereço inválido 10781 in /var/www/html/vendor/magento/module-quote/Model/QuoteAddressValidator.php:79 |
Hi @engcom-Delta. Thank you for working on this issue.
|
Hi @mehmetuygun , Followed steps:
Actual Results: |
We have noticed that this issue has not been updated for a period of more than 14 Days. |
Incredible... |
Still happens on 2.4.5 |
Still happens on 2.4.6-p2 |
@engcom-Delta @magento-engcom-team this is obviously unresolved... could you please reopen? |
Hello maybe this will help. I just got this error while shopping on www.lindt.co.uk. I obviously can't tell you what version they are using but following the error lead me here. This is what I did:
In the end I had to give up with lindt and order as a guest, but maybe the above steps will help to reproduce the issue. Good luck! |
Additional Details
Detailed explanation and result of the investigation #23908 (comment)
Preconditions (*)
Steps to reproduce (*)
2.5. Enable Persistent Shopping Cart (updated Oct 10.2019)
go to the checkout!Impotent: wait until the customer session expires (one hour by default) but no longer than Persistence Lifetime is set to (updated Oct 10.2019)3.5 Reload the page so that somewhere in the upper-right corner You get "Not You?" link next to the welcome message (updated Oct 10.2019)
3.6 Clik on "Not You?" enter the credentials of the customer and log in (updated Oct 10.2019)
3.6 Go to Mini Cart end press Precede to Checkout (updated Oct 10.2019)
Expected result (*)
Actual result (*)
The text was updated successfully, but these errors were encountered: