question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Errors in checkout stack into multiple orders per submit

See original GitHub issue

Current behavior

The more times you submit an order with invalid data (i.e. only numbers in the name fields) the more times there will be a submit order request sent to the backend. First submit will send only one request, another submit w/o fixing errors will send the order twice, etc.

Expected behavior

Order requests having error are being repeated over and over.

Steps to reproduce the issue

  1. try to place an order with invalid user data (i.e. a few digits in name fields)
  2. hit submit button several times
  3. the more times you hit the button the more requests will be sent to the backend incrementally.

Can you handle fixing this bug by yourself?

  • YES but not anytime soon, feel free to fix it
  • NO

Which Release Cycle state this refers to? Info for developer.

Pick one option.

  • This is a bug report for test version on https://test.storefrontcloud.io - In this case Developer should create branch from develop branch and create Pull Request 2. Feature / Improvement back to develop.
  • This is a bug report for current Release Candidate version on https://next.storefrontcloud.io - In this case Developer should create branch from release branch and create Pull Request 3. Stabilisation fix back to release.
  • This is a bug report for current Stable version on https://demo.storefrontcloud.io and should be placed in next stable version hotfix - In this case Developer should create branch from hotfix or master branch and create Pull Request 4. Hotfix back to hotfix.

Environment details

  • Browser: Chrome 72
  • OS: Ubuntu 18.04
  • Node: 8
  • Code Version: develop

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:9 (4 by maintainers)

github_iconTop GitHub Comments

2reactions
pkarwcommented, Apr 17, 2019

I belive we should do both: changing error statuses inside Vue-storefront-api. Add general workaround - hotifx to not queue orders in case of http error other than 200 (we should use the queue only for network outage / offline mode - in this case there is no http error at all rather there we have a fetch exception)

1reaction
lukeromanowiczcommented, Apr 17, 2019

I believe that #2753 would help a lot in this case.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Errors in checkout stack into multiple orders per submit #2663
The more times you submit an order with invalid data (i.e. only numbers in the name fields) the more times there will be...
Read more >
Two orders being submitted after checkout - Stack Overflow
Most likely (as mentioned in the comments) your client-side code is sending more than one request to create a charge.
Read more >
Single payment to multiple orders won't register or complete ...
The answer was simple in the end: $orderIdsExplode = explode(',',$orderIds); $orders = Mage::getModel('sales/order') ->getCollection() ...
Read more >
Checkout Errors - BigCommerce Support
Checkout errors can be in the form of a failed order, typically shipping or payment related, or a completed order that was processed...
Read more >
IHOP Rewards FAQs
Open your IHOP app or log in to your account at ihop.com/rewards. · Select a reward in the Stack Market, which will place...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found