[jorgefilipecosta]

Follow up to https://core.trac.wordpress.org/changeset/64388.

This PR renames the local sub-field of the core/content-query date fields to site:

• date and modified now return { site, gmt } instead of { local, gmt }. The values are unchanged.
• The fields input accepts date.site and modified.site; date.local and modified.local are rejected as unknown fields.
• Tests updated, plus coverage for the site, gmt order.

Trac ticket: https://core.trac.wordpress.org/ticket/66268

Testing

Verify unit tests are passing:

vendor/bin/phpunit tests/phpunit/tests/abilities-api/wpRegisterCoreContentAbility.php

Or run the ability in the editor console:

wp.apiFetch( { path: wp.url.addQueryArgs( '/wp-abilities/v1/abilities/core/content-query/run', { input: { where: { type: 'post' }, fields: [ 'id', 'date', 'modified' ] } } ) } );

Each item should have date and modified objects with site and gmt keys.

AI disclosure: the change and tests were drafted with AI assistance (Claude Code) and reviewed by me.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs.

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

Props jorgefilipecosta, gziolo.

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

---

Props Bot commands

You can trigger Props Bot actions by commenting on this PR:

• @propsbot add <username> to give props to a GitHub user. Requires write access.
• @propsbot remove <username> to leave a user out of the props. Requires write access.
• @propsbot refresh to refresh this list. Adding the props-bot label works too.

[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.

[gziolo]

Thanks for this, the rename looks good! One small suggestion: I would drop the date.local and modified.local cases from data_unknown_field_paths(). These names never shipped in a release, and the bogus_field case already covers the same validation. Keeping the original single test is simpler, and it doesn't keep the old name around in the tests.

[jorgefilipecosta]

Hi @gziolo, thank you for the review! The suggestion was applied, the unknown field test is back to the single bogus_field case.