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

custom option price value can't be more than 1000 #6116

Closed
ladonenko opened this issue Aug 11, 2016 · 5 comments
Closed

custom option price value can't be more than 1000 #6116

ladonenko opened this issue Aug 11, 2016 · 5 comments
Labels
bug report Component: Catalog Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development

Comments

@ladonenko
Copy link

After saving product with custom option price value more than 1000.00 it is cut to 1.00.
It happens only after second save.

@veloraven
Copy link
Contributor

@ladonenko thank you for your report.
Please, provide the used Magento version and information if it was clear install or update from some previous version.
Please also update description according to template: with steps, expected result and actual result.

@ladonenko
Copy link
Author

magento version 2.1. installed from scratch
Steps for reproduce

  • create configurable product
  • create custom option, type = dropdown
  • add couple values with price more that 1000 euro in my case
  • save product, you will see actual price amount
  • save product again and look at the custom option price value. in my case
    it is different and euqal 1euro
    if i enter original price 4000 it will 4.00

2016-08-15 15:27 GMT+03:00 Olga Moyseyenko [email protected]:

@ladonenko https://github.com/ladonenko thank you for your report.
Please, provide the used Magento version and information if it was clear
install or update from some previous version.
Please also update description according to template: with steps, expected
result and actual result.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#6116 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB03AopHEyT57zDbxbuJY0RuRcsls9GWks5qgFsygaJpZM4JiAQt
.

@katmoon
Copy link
Contributor

katmoon commented Aug 16, 2016

Hi @ladonenko

Thank you for reporting the issue. It is reported as MAGETWO-56866 internally.

Thanks,
Kateryna.

@katmoon katmoon removed their assignment Aug 16, 2016
@katmoon katmoon added the Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development label Aug 16, 2016
mmansoor-magento pushed a commit that referenced this issue Sep 30, 2016
Fixed issues:
- MAGETWO-56866: [GITHUB] Custom option prices unexpectedly change after save #6116 #6342
- MAGETWO-58873: Cannot receive shipping quotes via the admin panel or front end
- MAGETWO-55216: Reference by name to non existing plugin lead to Di compilation failure
- MAGETWO-58958: Fatal error in console in flow for apply new Scheduled Staging Update using CRON
- MAGETWO-55924: [FT] Test fails because of unexpected alert window
- MAGETWO-58664: [GitHub] Free shipping rule with table shipping method breaks checkout #6346
- MAGETWO-58849: [GitHub] Error in product edit page after disable Review module #6704
@sdzhepa
Copy link
Contributor

sdzhepa commented Oct 3, 2016

@ladonenko Fix for this issue was delivered to develop branch. Pls feel free to chech it in develop and reopen if need

  • Fix for Magento 2.1 will be delivered late in scope of internal ticket MAGETWO-58571

@senders
Copy link

senders commented Apr 3, 2017

This patch seems to work fine in magento 2.1.5:

496c24d

But why it isn't still integrated in one of the latest magento versions 2.1.3, 2.1.4 or 2.1.5. ???

okorshenko pushed a commit that referenced this issue Jul 5, 2017
okorshenko pushed a commit that referenced this issue Jul 5, 2017
magento-engcom-team pushed a commit that referenced this issue Sep 10, 2020
[TSG] Fixes for 2.4 (pr83) (2.4-develop)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug report Component: Catalog Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development
Projects
None yet
Development

No branches or pull requests

6 participants