bugfix: current_user_can check in Feature/SearchOrdering #2255
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
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.
Requirements
none
Description of the Change
current_user_canshould only be passed simple strings/integer not complete objects.Alternate Designs
Benefits
Possible Drawbacks
Verification Process
Found the Solution here:
https://wordpress.org/support/topic/object-of-class-wp_post-could-not-be-converted-to-string/
Tested in newest ElasticPress und WordPress Version.
Checklist:
Applicable Issues
none
Changelog Entry
Fixed: Creating Custom Results with Feature "Sortable" enabled, could throw an error