Use Post ID instead of Post Object in current_user_can #13286
Merged
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.
Changes proposed in this Pull Request:
Similar to #13166,
current_user_canonly accepts object IDs as the optional second param; passing anything else (like an instance of Jetpack_Post like we did) will cause issues.However, #13166 did not fix all wrong implementations so the same issue happens in 2184839-zen, then it was reported in 4206-gh-jpop-issues.
This PR is to correct all wrong implementations. In fact, only changes in
sal/class.json-api-post-base.phpis enough to fix this fatal error. However, I've tried my best, then found out other wrong implementations injson-endpoints/class.wpcom-json-api-post-endpoint.php.Testing instructions:
Proposed changelog entry for your changes: