Menu Adam R Brown

WP hooks navigation: Home/browseActions indexFilters index

Source View: wp_creating_autosave

To save our bandwidth, we show only a snippet of code around each occurence of the hook. View complete file in SVN (without highlighting).

Understanding Source Code

The best way to understand what a hook does is to look at where it occurs in the source code.

Remember, this hook may occur in more than one file. Moreover, the hook's context may change from version to version.

Source View

This hook occurs 2 times in this file.

Line Code
2000           /**
2001            * Fires before an autosave is stored.
2002            *
2003            * @since 4.1.0
2004            * @since 6.4.0 The `$is_update` parameter was added to indicate if the autosave is being updated or was newly created.
2005            *
2006            * @param array $new_autosave Post array - the autosave that is about to be saved.
2007            * @param bool  $is_update    Whether this is an existing autosave.
2008            */
2009           do_action( 'wp_creating_autosave', $new_autosave, true );
2010           return wp_update_post( $new_autosave );
2011      }
2012
2013      // _wp_put_post_revision() expects unescaped.
2014      $post_data = wp_unslash( $post_data );
2015
2016      // Otherwise create the new autosave as a special post revision.
2017      $revision = _wp_put_post_revision( $post_data, true );
2018
2019      if ( ! is_wp_error( $revision ) && 0 !== $revision ) {
2020
2021           /** This action is documented in wp-admin/includes/post.php */
2022           do_action( 'wp_creating_autosave', get_post( $revision, ARRAY_A ), false );
2023      }
2024
2025      return $revision;
2026 }
2027
2028 /**
2029  * Autosaves the revisioned meta fields.
2030  *
2031  * Iterates through the revisioned meta fields and checks each to see if they are set,