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

[Forwardport] Magento Catalog - fix custom option type text price conversion for mu… #22760

Merged

Conversation

ihor-sviziev
Copy link
Contributor

Original Pull Request

#22016

Description

Previously I already fixed similar issue in the PR #18225, but the fix doesn't cover all the custom option types, e.g. type "Field" still has that issue with price conversion.

It's reproduced on the following Magento setup with multi-currency configuration:

  1. There are 2 websites configured: US and CA (or another one).
  2. Base Currency is configured in the next way: default level - USD; CA - CAD.
  3. And if you try to update product with custom options type "Field" (or another without option values) with non zero price on CA website level.

Fixed Issues (if relevant)

No related issues found.

Manual testing scenarios

Steps to reproduce

  1. Create 2 websites on Magento: US website and CA website.
  2. Set up Base Currency to USD (or any other) on default scope.
  3. Set up Base Currency to CAD on CA website scope.
  4. Create product with custom option type "Field" (or another without option values) and set up non zero price for option.
  5. Save the product.
  6. Change configuration scope on CA website.
  7. Save product.

Expected result
Custom option price is not changed, because no actual changes were done.

Actual result
Custom option price is updated according to USD/CAD currency rate.

Contribution checklist

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds on Travis CI are green)

@m2-assistant
Copy link

m2-assistant bot commented May 7, 2019

Hi @ihor-sviziev. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento-engcom-team give me test instance - deploy test instance based on PR changes
  • @magento-engcom-team give me 2.3-develop instance - deploy vanilla Magento instance

For more details, please, review the Magento Contributor Assistant documentation

@magento-engcom-team
Copy link
Contributor

Hi @rogyar, thank you for the review.
ENGCOM-5085 has been created to process this Pull Request

@Nazar65 Nazar65 force-pushed the 2.3-develop-PR-port-22016 branch from 646ef8e to ccecc7c Compare May 10, 2019 10:36
@soleksii
Copy link

✔️ QA Passed

@m2-assistant
Copy link

m2-assistant bot commented May 24, 2019

Hi @ihor-sviziev, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

@magento-engcom-team magento-engcom-team added this to the Release: 2.3.3 milestone May 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants