Fix: Revision REST schema remove protected#11569
Fix: Revision REST schema remove protected#11569DarkMatter-999 wants to merge 4 commits intoWordPress:trunkfrom
protected#11569Conversation
Test using WordPress PlaygroundThe changes in this pull request can previewed and tested using a WordPress Playground instance. WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser. Some things to be aware of
For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation. |
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the Core Committers: Use this line as a base for the props when committing in SVN: To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Trac ticket: https://core.trac.wordpress.org/ticket/53417
The schema provided by the REST API endpoints for revisions at
wp/v2/posts/{id}/revisionsandwp/v2/pages/{id}/revisionsincorrectly states thatcontent.protectedandexcerpt.protectedproperties exist. Revisions do not inherently support password protection in their response payloads, as they belong to the parent post.This PR fixes the issue by removing the
protectedproperty from the revision schema for both thecontentandexcerptfields withinWP_REST_Revisions_Controller::get_item_schema().Use of AI Tools
AI assistance: Yes
Tool(s): Github Copilot (Claude 4.6 Sonnet, Gemini 3.1 Pro)
Used for: Discussing the implementation approach and refining the PHPUnit tests for schema validation. Final code and tests were reviewed and verified locally by me.
This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.