WP hooks navigation: Home/browse • Actions index • Filters index
To save our bandwidth, we show only a snippet of code around each occurence of the hook. View complete file in SVN (without highlighting).
The best way to understand what a hook does is to look at where it occurs in the source code.
do_action( "hook_name" )apply_filters( "hook_name", "what_to_filter" ).Remember, this hook may occur in more than one file. Moreover, the hook's context may change from version to version.
| Line | Code |
|---|---|
| 67 | echo '<p class="about-auto-update cool">' . __( 'This site <strong>is</strong> able to apply these updates automatically. Cool!' ). '</p>'; |
| 68 | |
| 69 | // If the updater is disabled entirely, don't show them anything. |
| 70 | } elseif ( ! $updater->is_disabled() ) { |
| 71 | echo '<p class="about-auto-update">'; |
| 72 | // If this is is filtered to false, they won't get emails, so don't claim we will. |
| 73 | // Assumption: If the user can update core, they can see what the admin email is. |
| 74 | |
| 75 | /** This filter is documented in wp-admin/includes/class-wp-upgrader.php */ |
| 76 | if ( apply_filters( 'send_core_update_notification_email', true, $future_minor_update ) ) { |
| 77 | printf( __( 'This site <strong>is not</strong> able to apply these updates automatically. But we’ll email %s when there is a new security release.' ), esc_html( get_site_option( 'admin_email' ) ) ); |
| 78 | } else { |
| 79 | _e( 'This site <strong>is not</strong> able to apply these updates automatically.' ); |
| 80 | } |
| 81 | echo '</p>'; |
| 82 | } |
| 83 | } |
| 84 | ?> |
| 85 | </div> |