Opened 7 years ago
Last modified 6 years ago
#43680 reviewing enhancement
Add new filter to WP_User_Query
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | Future Release | Priority: | normal |
| Severity: | normal | Version: | 3.1 |
| Component: | Users | Keywords: | has-patch needs-testing |
| Focuses: | Cc: |
Description
Add a new filter to filter the value of results returned from the WP_User_Query. This brings the WP_User_Query class inline with other query classes, like WP_Query, which already has posts_results filter. This filter is a powerful one, that will allow for third party code, to hook in and change the results of the query.
Attachments (3)
Change History (11)
#3
@
7 years ago
- Focuses performance removed
- Keywords needs-testing added
- Type changed from defect (bug) to enhancement
Removing the performance focus and converting from bug to enhancement as nothing is technically broken here.
#5
@
6 years ago
- Milestone changed from 5.0 to 4.9.9
- Owner set to SergeyBiryukov
- Status changed from new to reviewing
#6
in reply to:
↑ description
@
6 years ago
Replying to spacedmonkey:
Add a new filter to filter the value of results returned from the WP_User_Query. This brings the WP_User_Query class inline with other query classes, like WP_Query, which already has
posts_resultsfilter.
For consistency with the posts_results filter, which accepts an array of WP_Post objects rather than stdClass objects, I guess I would expect users_results to accept an array of WP_User objects.
What do you think of 43680.3.diff? It runs the filter a bit later, after converting the results to WP_User objects when fields is all or all_with_meta, but before retrieving metadata via cache_users().
Related: #43679