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

Price adjustments set on a product option do not apply if there is no price set for a non-default sku #59

Closed
phillipuniverse opened this issue Jun 5, 2013 · 2 comments
Labels
Milestone

Comments

@phillipuniverse
Copy link
Contributor

Scenario:
ProductOption A is set up with 2 possible values. The first one has no price modification and the second value has +$50.00 as its adjustment.
Product B has defaultSku with price $100.
Product B also has 2 generated skus, neither of which has a price set.
In this case, adding the sku with the price modifier to cart will result in the price being $100, not $150.
This is fixed in 2.3, the change just needs to be backported.

Originally reported by @apazzolini

@bpolster
Copy link
Member

Retest in 3.0, there was some work done in this area.

@phillipuniverse
Copy link
Contributor Author

Retested in 3.0.3, looks to be resolved.

Since this was fixed in 2.3 (from the original comment) then the only action item here would be to backport to 2.1. Will hunt for the commit and backport in response to a specific user request; not many people are using 2.1.

Changed milestone to 2.3.0-GA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants