$conf, $runtime; function_exists('chdir') AND chdir(APP_PATH); $r = 'mysql' == $conf['cache']['type'] ? website_set('runtime', $runtime) : cache_set('runtime', $runtime); } function runtime_truncate() { global $conf; 'mysql' == $conf['cache']['type'] ? website_set('runtime', '') : cache_delete('runtime'); } register_shutdown_function('runtime_save'); ?>posts - What to use: wp_is_post_autosave( $post_id ) or DOING_AUTOSAVE?|Programmer puzzle solving
最新消息:Welcome to the puzzle paradise for programmers! Here, a well-designed puzzle awaits you. From code logic puzzles to algorithmic challenges, each level is closely centered on the programmer's expertise and skills. Whether you're a novice programmer or an experienced tech guru, you'll find your own challenges on this site. In the process of solving puzzles, you can not only exercise your thinking skills, but also deepen your understanding and application of programming knowledge. Come to start this puzzle journey full of wisdom and challenges, with many programmers to compete with each other and show your programming wisdom! Translated with DeepL.com (free version)

posts - What to use: wp_is_post_autosave( $post_id ) or DOING_AUTOSAVE?

matteradmin8PV0评论

I was doing some action on save_post hook, and noticed that there exists

wp_is_post_autosave( $post_id ) 

function.

How does it differ from DOING_AUTOSAVE constant?

If I want my action not to run on autosave should I do both

if ( defined( 'DOING_AUTOSAVE' ) && DOING_AUTOSAVE ) {
  return;
}

and

if ( \wp_is_post_autosave( $post_id ) ) {
  return;
}

Or is one enough?

The DOING_AUTOSAVE constant gets defined in wp-admin/includes/post.php, wp-includes/class-wp-customize-manager.php and wp-includes/rest-api/endpoints/class-wp-rest-autosaves-controller.php, whereas wp_is_post_autosave() checks if the post is revision and has autosave in it's name.

I'm a bit confused what to use, and if it's good idea to use both.

Post a comment

comment list (0)

  1. No comments so far