Usage of wp_get_post_revisions in WP_REST_Posts_Controller

[furi3r]

I've come across this line of code:
​https://github.com/WordPress/wordpress-develop/blob/6.0/src/wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php#L2020

We could optimize that query since wp_get_post_revisions accepts arguments, and we are going to use only the last revision, we could use LIMIT, instead of querying all of them.

[TimothyBlynJacobs]

We do also need the revision count.

Trac ticket: #55857

[furi3r]

@TimothyBlynJacobs I've working on it, you can take a look to the PR.

[peterwilsoncc]

There's a few places aside from the rest api that use wp_get_post_revisions() to do a count that could make use of this code.

[furi3r]

@peterwilsoncc I would go first for the rest API usage, since this is introducing a new core function, and the scope here will be more limited. Then we can follow up in another trac for other core occurrences (mainly revision.php)

@spacedmonkey @peterwilsoncc I've added the new round of revisions.

[spacedmonkey]

In 53759:

REST API: Use wp_get_lastest_revision_id_and_total_count function in WP_REST_Posts_Controller class.

Add new function called wp_get_lastest_revision_id_and_total_count, that performs an optimized query to get the last revision and total and use it in WP_REST_Posts_Controller class.

Props Spacedmonkey, timothyblynjacobs, furi3r, peterwilsoncc.
Fixes #55857.

Committed.

[JustinSainton]

Maybe a silly note, but this reads odd to me as wp_get_lastest_revision_id_and_total_count instead of wp_get_latest_revision_id_and_total_count, especially when the docs use the word latest and not lastest (which I'm not certain is a word...but I'm also not certain it's not 🤣)

[SergeyBiryukov]

Replying to JustinSainton:

Maybe a silly note, but this reads odd to me as wp_get_lastest_revision_id_and_total_count instead of wp_get_latest_revision_id_and_total_count, especially when the docs use the word latest and not lastest

Good point. Looking at the tests, they mention "wp_get_last_revision_id_and_total_count()", and the variable name is $last_revision (here and in a few other places in core), so I think this was supposed to be "last".

[SergeyBiryukov]

In 53769:

Revisions: Correct the function name for retrieving the last revision ID and total count.

Includes:

• Renaming the function to wp_get_last_revision_id_and_total_count().
• Making the default value for $post consistent with wp_get_post_revisions().
• Making WP_Error codes more specific and using them in test assertions.
• Adjusting the function description per the documentation standards.

Follow-up to [53759].

Props JustinSainton, SergeyBiryukov.
See #55857.

[SergeyBiryukov]

Follow-up: #56279

[SergeyBiryukov]

Replying to SergeyBiryukov:

Looking at the tests, they mention "wp_get_last_revision_id_and_total_count()", and the variable name is $last_revision (here and in a few other places in core), so I think this was supposed to be "last".

Looks like I missed ​this comment making an argument in favor of "latest" instead of "last". If anyone feels strongly about that, feel free to reopen, but in that case I would also suggest updating the "last revision" wording in other places.

[peterwilsoncc]

My feelings are just strong enough to reopen the ticket. What is the first and last revision seems a little ambiguous to me.

What got me to reopen was that Core refers to latest posts, latest comments, etc fairly consistently based on a basic search for _last_ vs _latest_.

I create a follow up PR.

https://core.trac.wordpress.org/ticket/55857

Looks good to me 👍

I have added a commit with some more instances. Though not directly related to the new function, it aims for more consistency in core, always referring to the latest revision as "latest" instead of "last". This can be committed separately if preferred.

[SergeyBiryukov]

In 53778:

Revisions: Rename the function for retrieving the latest revision ID and total count.

The new name is wp_get_latest_revision_id_and_total_count().

This aims to reduce ambiguity about what exactly is the "first" or "last" revision, and bring more consistency with similar wording elsewhere in core, e.g. latest posts, latest comments, etc.

Follow-up to [53759], [53769].

Props peterwilsoncc.
See #55857.

[SergeyBiryukov]

In 53779:

Revisions: Update the "last revision" wording to "latest revision" in various files.

This aims to reduce ambiguity about what exactly is the "first" or "last" revision, and bring more consistency with similar wording elsewhere in core, e.g. latest posts, latest comments, etc.

This affects:

• wp_save_post_revision()
• wp_prepare_revisions_for_js()
• WP_Customize_Manager::filter_revision_post_has_changed()

Follow-up to [53759], [53769], [53778].

Props peterwilsoncc.
Fixes #55857.

Merged in r53778 and r53779.

[SergeyBiryukov]

In 53841:

Revisions: Use latest_id as the array key for the latest revision ID.

This updates wp_get_latest_revision_id_and_total_count() and its usage to be a bit more descriptive and a bit less repetitive, e.g. $revisions['latest_id'] instead of $revision['revision'].

Includes updating the @return tag to explain when the function returns a WP_Error.

Follow-up to [53759], [53769], [53778], [53779].

See #55857.