Hook wp_smush_should_skip_parse deprecated

  • Resolved Gust

    (@gustavonardi10)


    1 month, 2 weeks ago

    Hi!

    I am encountering the following error every time a page is loaded on my site, despite having the latest updates:

    Deprecated: The hook wp_smush_should_skip_parse has been deprecated since version 3.16.1! Use wp_smush_should_skip_lazy_load instead. in /home/mysite/wp-includes/functions.php on line 6085

    Deprecated: The hook wp_smush_should_skip_parse has been deprecated since version 3.16.1! Use wp_smush_should_skip_lazy_load instead. in /home/mysite/wp-includes/functions.php on line 6085

    I noticed that on line 6085 (and nearby lines) there is the following code:

    do_action( ‘wp_trigger_error_run’, $function_name, $message, $error_level );

    if ( ! empty( $function_name ) ) {
    $message = sprintf( '%s(): %s', $function_name, $message );
}

$message = wp_kses(
    $message,
    array(
        'a'      => array( 'href' => true ),
        'br'     => array(),
        'code'   => array(),
        'em'     => array(),
        'strong' => array(),
    ),
    array( 'http', 'https' )
);

trigger_error( $message, $error_level );

    }

    Could you please advise on how to resolve this issue?

    Thank you!

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Adam – WPMU DEV Support

    (@wpmudev-support8)

    Hi @gustavonardi10

    I hope you’re well today!

    With version 3.16.1 the “wp_smush_should_skip_parse” filter hook was replaced by the “wp_smush_should_skip_lazy_load” one but:

    if you are not using any custom code that would use this hook (and your theme or other plugins are not using it – so there’s no built-in integration for Smush in theme or other 3rd-party plugins) – you do not need to do anything about it and it doesn’t require fix.

    “Deprecated” means it is still there and still working but will eventually be removed in future. In plugin that filter hook is called using WordPress core “apply_filters_deprecated()” function instead of standard “apply_filters()” and the sole reason for that is to issue that deprecation message – so developers who use that hook would be informed and had time to update their code. Other than this, it works the same way.

    If you don’t have any such custom code, you can completely ignore it as it does nothing else than just issuing message. With one of future releases (though I don’t have information which one exactly yet), this hook will be completely removed and that notice will stop.

    Until then, it doesn’t cause any issues, it’s expected notice and should simply be ignored.

    Kind regards,
    Adam

    Plugin Support Laura – WPMU DEV Support

    (@wpmudevsupport3)

    Hi @gustavonardi10,

    We haven’t heard from you in a while, I’ll go and mark this thread as resolved. Note that you can still reply on this topic.

    If you have any additional questions or require further help, please let us know!

    Best regards,
    Laura

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.