Prevent order fields from being removed #2728
Merged
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
This way the orders are created with the correct parameters
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 of the Change
Since ElasticPress 4.0.0, password-protected posts have their content removed during the sync process. As stated in #2726, that is a problem for WooCommerce Orders created in the frontend. This PR adjusts that behavior.
Closes #2726
Changelog Entry
Added:
$post_argsand$post_idto theep_pc_skip_post_content_cleanupfilter.Fixed: Sync of WooCommerce Orders fields when WooCommerce and Protected Content features are enabled.
Credits
Props @felipeelia @ecaron