Skip to content
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

Ordering 'out of stock' products in offline mode - error #2740

Closed
2 of 5 tasks
ArturDivante opened this issue Apr 16, 2019 · 5 comments
Closed
2 of 5 tasks

Ordering 'out of stock' products in offline mode - error #2740

ArturDivante opened this issue Apr 16, 2019 · 5 comments
Assignees
Labels
3: Medium complexity bug Bug reports P3: Normal Priority mark - normal priority QA approved after merge Testers will add this label after positive check on merged changes
Milestone

Comments

@ArturDivante
Copy link
Collaborator

ArturDivante commented Apr 16, 2019

Related issues

#2044

Steps to reproduce the issue

  1. Go to https://demo.storefrontcloud.io/
  2. Open women category
  3. Turn to offline mode
  4. Open https://demo.storefrontcloud.io/p/WT06/chloe-compete-tank/WT06 (example of a product we know is out of stock by default)
  5. Add Product to cart in blue/XS (default) version (example of out-of-stock product version)
  6. Go to checkout and place an order - it will be put on hold until you come back online
  7. Turn to online mode again

Current behavior

  1. Success page is displayed - user is informed, that order was successfully placed
  2. Group of 500 errors is displaye in console
  3. Order is not placed

Offline Order 0
Offline Order 1
Offline Order 2

Expected behavior

Assuming its impossible to check stock status before, we should at least display proper error message on front - currently user is convinced, that he placed an order.

Can you handle fixing this bug by yourself?

  • YES
  • 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: many
  • OS: Win10
@ArturDivante ArturDivante added the bug Bug reports label Apr 16, 2019
@pkarw
Copy link
Collaborator

pkarw commented Apr 16, 2019

As for now we should better handle the ThankYouPage + display the proper error message in that case

@pkarw pkarw added 3: Medium complexity P3: Normal Priority mark - normal priority labels Apr 16, 2019
@lukeromanowicz
Copy link
Contributor

lukeromanowicz commented Apr 16, 2019

@pkarw extracting order synchronization to a visual layer and notifying a user about successful/unsuccessful order placement when he's back online would be a great feature and simplify solutions to a lot of similar issues to this one. Same goes for products that have additional business validation, invalid address fields, expired coupons etc. If you think it's a viable set of features then we should extract that to a separate FR, I believe.

@pkarw
Copy link
Collaborator

pkarw commented Apr 17, 2019

@lukeromanowicz yes, that makes perfect sense to me. We should have this kind of general error handler in here. So I belive you could create such a feature request and maybe close this issue with it

@lukeromanowicz
Copy link
Contributor

@pkarw I elaborated my idea in #2753. If it's similar to what you have in mind

@pkarw pkarw mentioned this issue Apr 23, 2019
5 tasks
@pkarw
Copy link
Collaborator

pkarw commented Apr 25, 2019

As a workaround for currently not having the #2753 implemented we can use the Popup UI from the https://github.com/DivanteLtd/vue-storefront/tree/master/core/modules/offline-order - to just display the details of the order that can't be sent from the queue. In case of any of validation / server error we should just to:

Then we can deal with #2753 and optimize the UX

@lukeromanowicz lukeromanowicz added this to the 1.9.0 milestone Apr 26, 2019
lukeromanowicz added a commit to lukeromanowicz/vue-storefront that referenced this issue Apr 26, 2019
@patzick patzick added the QA - Ready for tests This is notification for testers, that improvement is ready to be tested and verified. label Apr 26, 2019
@patzick patzick closed this as completed Apr 26, 2019
@ArturDivante ArturDivante added QA approved after merge Testers will add this label after positive check on merged changes and removed QA - Ready for tests This is notification for testers, that improvement is ready to be tested and verified. labels May 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3: Medium complexity bug Bug reports P3: Normal Priority mark - normal priority QA approved after merge Testers will add this label after positive check on merged changes
Projects
None yet
Development

No branches or pull requests

4 participants