apply_filters( ‘auto_core_update_email’, array $email, string $type, object $core_update, mixed $result )

Filters the email sent following an automatic background core update.

Parameters

$emailarray
Array of email arguments that will be passed to wp_mail() .
  • to string
    The email recipient. An array of emails can be returned, as handled by wp_mail() .
  • subject string
    The email’s subject.
  • body string
    The email message body.
  • headers string
    Any email headers, defaults to no headers.
$typestring
The type of email being sent. Can be one of 'success', 'fail', 'manual', 'critical'.
$core_updateobject
The update offer that was attempted.
$resultmixed
The result for the core update. Can be WP_Error.

Source

$email = apply_filters( 'auto_core_update_email', $email, $type, $core_update, $result );

Changelog

VersionDescription
3.7.0Introduced.

User Contributed Notes

  1. Skip to note 2 content

    The apply_filters( 'auto_core_update_email', array $email, string $type, object $core_update, mixed $result ) filter allows developers to customize the content and recipients of the email notification that WordPress sends after a core update.

    Add the following code to your theme’s functions.php file or in a custom plugin.

    add_filter( 'auto_core_update_email', 'wpdocs_auto_core_update_email', 10, 4 );
    
    function wpdocs_auto_core_update_email( $email, $type, $core_update, $result ) {
        // Customize the subject line
        $email['subject'] = sprintf( __( 'WordPress Core Update: %s' ), ucfirst( $type ) );
    
        // Add more information to the email body
        $email['body'] .= "\n\n---\n" . __( 'Additional Information:' ) . "\n";
        $email['body'] .= sprintf( __( 'Version: %s' ) . "\n", $core_update->version );
        $email['body'] .= sprintf( __( 'Update Type: %s' ) . "\n", $type );
        $email['body'] .= sprintf( __( 'Update Status: %s' ) . "\n", $result ? __( 'Success' ) : __( 'Failure' ) );
    
        // Return the modified email
        return $email;
    }

You must log in before being able to contribute a note or feedback.