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

M 2.2.3 price per website - wrong price at backend by a create order after update #14869

Closed
Webroju opened this issue Apr 26, 2018 · 4 comments
Closed
Assignees
Labels
Fixed in 2.2.x The issue has been fixed in 2.2 release line Fixed in 2.3.x The issue has been fixed in 2.3 release line Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed

Comments

@Webroju
Copy link

Webroju commented Apr 26, 2018

At a shop with 2 websites (and 2 storeviews) and use different prices (price scope: website), if you create an order at the backend for the second website and update this order, e.g. change the quantity then the default price is calculated and not the price of the special website.

Preconditions

  1. Magento 2.2.3.
  2. NGINX,
  3. PHP 7.1.3

Steps to reproduce

  1. Create a second website, create a store and a storeview at this second website
  2. Change the config at Stores > Configuration > Catalog > Catalog> Price >Catalog Price Scope > change from global to website
  3. Create a Product with a price
  4. Change the storeview to the second storeview and and change the price only for this storeview, not the global
  5. At the Backend, create a new order in the second storeview and add the product to the "Items Ordered" (now the price is correct)
  6. change the quantity of the product and click "update items and quantities"

Expected result

  1. the price of the appropriate storeview

Actual result

  1. the default price

screenshot_1
screenshot_2

@magento-engcom-team magento-engcom-team added the Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed label Apr 26, 2018
@phoenix128 phoenix128 self-assigned this Apr 29, 2018
@phoenix128 phoenix128 added Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed labels Apr 29, 2018
@VladimirZaets
Copy link
Contributor

Hi @Webroju. Thank you for your report.
The issue has been fixed in #14904 by @phoenix128 in 2.2-develop branch
Related commit(s):

The fix will be available with the upcoming 2.2.5 release.

@sidolov
Copy link
Contributor

sidolov commented Jul 24, 2018

Hi @Webroju. Thank you for your report.
The issue has been fixed in #16893 by @mage2pratik in 2.3-develop branch
Related commit(s):

The fix will be available with the upcoming 2.3.0 release.

@digikeijs
Copy link

@sidolov issue is not solved yet, See new incident 15846

@ihor-sviziev
Copy link
Contributor

Hi @digikeijs,
I re-checked, this issue was fixed in 2.2.6 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Fixed in 2.2.x The issue has been fixed in 2.2 release line Fixed in 2.3.x The issue has been fixed in 2.3 release line Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed
Projects
None yet
Development

No branches or pull requests

7 participants