From 713ef64d693645b6cf2b4b1248212d13079f4d65 Mon Sep 17 00:00:00 2001 From: Peter Westwood Date: Sat, 9 Jan 2010 09:55:41 +0000 Subject: [PATCH] _future_post_hook should not call _deprecated_argument() as it will always get that argument from the action it is hooked to. Fixes #11815 props nacin. git-svn-id: https://develop.svn.wordpress.org/trunk@12679 602fd350-edb4-49c9-b593-d223f7449a82 --- wp-includes/post.php | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/wp-includes/post.php b/wp-includes/post.php index bb0ff0bab0..d4367d29e2 100644 --- a/wp-includes/post.php +++ b/wp-includes/post.php @@ -3581,12 +3581,12 @@ function _transition_post_status($new_status, $old_status, $post) { * @since 2.3.0 * @access private * - * @param int $deprecated Not Used. Can be set to null. + * @param int $deprecated Not used. Can be set to null. Never implemented. + * Not marked as deprecated with _deprecated_argument() as it conflicts with + * wp_transition_post_status() and the default filter for _future_post_hook(). * @param object $post Object type containing the post information */ function _future_post_hook( $deprecated = '', $post ) { - if ( !empty( $deprecated ) ) - _deprecated_argument( __FUNCTION__, '0.0' ); wp_clear_scheduled_hook( 'publish_future_post', array( $post->ID ) ); wp_schedule_single_event( strtotime( $post->post_date_gmt. ' GMT' ), 'publish_future_post', array( $post->ID ) ); }