Fix upgrading from 4.x with OrderCurrencyValuesAttributeConditionRule in place #3933
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thank you for this, could you provide a stack trace of the error? We are trying to hunt down the origin of what would cause this issue and require the suggested fix. Thanks! |
|
Don't have it anymore but I had an order field layout with an order conditional in 4.x and tried upgrading to 5.x |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
OrderCurrencyValuesAttributeConditionRule exists in 4.x but in 5.x relies on specific 5.x code. When this is in place, upgrading from 4.x to 5.x fails. This PR fixes that.