REST API: Expose the privacy policy page in the settings endpoint

[oandregal]

Backport of WordPress/gutenberg#82422.
Trac ticket https://core.trac.wordpress.org/ticket/66045#ticket

The page assigned in Settings > Privacy is stored in the wp_page_for_privacy_policy option, but the option is not registered with show_in_rest, so the /wp/v2/settings endpoint cannot report it. This registers it as page_for_privacy_policy, alongside page_on_front and page_for_posts, so the editor can show a "Privacy Policy Page" badge next to that page, as the classic pages list does.

Changes:

• register_initial_settings(): register wp_page_for_privacy_policy with the REST name page_for_privacy_policy.
• rest_restrict_privacy_policy_page_setting_update(): ignore updates from users without manage_privacy_options. The settings endpoint only checks manage_options, and on multisite manage_privacy_options maps to manage_network, so a site administrator could otherwise change the page over REST but not in Settings > Privacy.
• Settings controller tests: expect the new key, and cover updating the setting with and without the capability.
• REST fixture: add the new setting to the schema and the settings response.

Trac ticket:

Use of AI Tools

AI assistance: Yes
Tool(s): Claude Code
Model(s): Claude Fable 5.1
Used for: Drafting the change and the tests; reviewed and tested 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.

[github-actions]

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 props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props oandregal, ntsekouras.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[Copilot]

🟢 Approval recommended

The change is small and consistent with existing settings registration patterns, and it includes corresponding test and fixture updates.

Pull request overview

Exposes the site’s configured Privacy Policy page through the REST API settings endpoint (/wp/v2/settings) by registering the underlying wp_page_for_privacy_policy option with a REST-facing name, enabling clients (e.g., the editor) to reliably read it alongside other reading-related page settings.

Changes:

• Register wp_page_for_privacy_policy in register_initial_settings() with show_in_rest name page_for_privacy_policy.
• Extend the REST settings controller PHPUnit test to expect the new settings key.
• Update the QUnit REST API fixture schema and mocked settings payload to include page_for_privacy_policy.

File summaries

File	Description
src/wp-includes/option.php	Registers wp_page_for_privacy_policy for REST exposure as page_for_privacy_policy.
tests/phpunit/tests/rest-api/rest-settings-controller.php	Adds page_for_privacy_policy to the expected /wp/v2/settings response keys.
tests/qunit/fixtures/wp-api-generated.js	Extends the fixture schema and mocked settings response with page_for_privacy_policy.

Review details

• Files reviewed: 3/3 changed files
• Comments generated: 1
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[oandregal]

Reworded in ad178e6 to say the option was registered and exposed as page_for_privacy_policy.

[github-actions]

Test using WordPress Playground

The 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

• All changes will be lost when closing a tab with a Playground instance.
• All changes will be lost when refreshing the page.
• A fresh instance is created each time the link below is clicked.
• Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
  it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

[ntsekouras]

Let's also include (if needed) this change in tests for multisite.