Changeset 53779 for trunk/src/wp-includes/class-wp-customize-manager.php

Timestamp:

07/25/2022 07:28:29 PM (2 years ago)

Author:

SergeyBiryukov

Message:

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.

File:

• trunk/src/wp-includes/class-wp-customize-manager.php (modified) (1 diff)

trunk/src/wp-includes/class-wp-customize-manager.php

@@ -3428 +3428 @@
      *
      * @param bool    $post_has_changed Whether the post has changed.
-     * @param WP_Post $last_revision    The last revision post object.
+     * @param WP_Post $latest_revision  The latest revision post object.
      * @param WP_Post $post             The post object.
      * @return bool Whether a revision should be made.
      */
-    public function _filter_revision_post_has_changed( $post_has_changed, $last_revision, $post ) {
-        unset( $last_revision );
+    public function _filter_revision_post_has_changed( $post_has_changed, $latest_revision, $post ) {
+        unset( $latest_revision );
         if ( 'customize_changeset' === $post->post_type ) {
             $post_has_changed = $this->store_changeset_revision;