[jorgefilipecosta]

Related: #15000

This PR replaces the registered_date field of core/users-query with a registered object, like the core/content-query date fields:

• registered returns { site, gmt }: the registration date in the site's timezone and in GMT. Each is null when the stored date is not a valid date.
• The fields input accepts registered.site and registered.gmt to select a single date.
• Visibility is unchanged: only for the user themselves or users the caller can edit.
• Tests updated, plus coverage for site timezones and offsets, sub-field selection, out-of-range dates and visibility.

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

Testing

Verify unit tests are passing:

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

Or run the ability in the editor console:

wp.apiFetch( { path: wp.url.addQueryArgs( '/wp-abilities/v1/abilities/core/users-query/run', { input: { fields: [ 'id', 'registered' ] } } ) } );

Each item should have a registered object 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]

Let's not keep the history of this removed field, since it didn't become part of the public contract.

[jorgefilipecosta]

Agreed, the registered_date row was removed.

[gziolo]

Thank you, this looks great! The new registered object uses the same { site, gmt } shape and the same field path handling as the date fields in core/content-query. That keeps the two abilities aligned, and clients can handle dates the same way in both.

I also like the improved date handling. user_registered is now always read as UTC, and it no longer depends on the PHP default timezone. The formatter preserves null handling for zero dates and handles timezone conversions that push dates outside the supported four-digit year range. The strict false check also correctly preserves the Unix epoch. The tests for DST, fractional offsets and edge years are very helpful.

The new tests cover the behavior well. I left a few notes on merging some overlapping checks to keep the suite easier to maintain. None of them are blocking.

[jorgefilipecosta]

Thank you for the review @gziolo, all the feedback was applied and I rebased the PR on trunk to pick up the entity actions test fix 😊