Include billing and shipping address conditions in Gateway edit form#4259
Merged
Conversation
lukeholder
added a commit
that referenced
this pull request
Mar 25, 2026
Member
|
Thankyou, we have included a fix like this this in the next release. To get the fix early, change your "require": {
"craftcms/commerce": "5.x-dev#15ddcbde0e333d0b79bba0178bb8425275afbaca as 5.6.0",
"...": "..."
}Then run We will update this PR once the release is out. |
Member
|
Commerce 5.6.1 is now out with this! |
This file contains hidden or 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
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
We have a need to include gateways on orders by address. The billing and shipping address conditions already exist on the Gateway class, they're just not being rendered in the edit form, or included in the save action.
This PR updates the edit form to show both condition inputs, and updates the save action so that they can be persisted correctly.
Related issues