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 |
|---|---|
| 227 | 'banners_rtl' => array(), |
| 228 | 'tested' => '', |
| 229 | 'requires_php' => '', |
| 230 | 'compatibility' => new stdClass(), |
| 231 | ); |
| 232 | $filter_payload = (object) array_merge( $filter_payload, array_intersect_key( $plugin_data, $filter_payload ) ); |
| 233 | |
| 234 | $type = 'plugin'; |
| 235 | /** This filter is documented in wp-admin/includes/class-wp-automatic-updater.php */ |
| 236 | $auto_update_forced = apply_filters( "auto_update_{$type}", null, $filter_payload ); |
| 237 | |
| 238 | if ( ! is_null( $auto_update_forced ) ) { |
| 239 | $plugin_data['auto-update-forced'] = $auto_update_forced; |
| 240 | } |
| 241 | |
| 242 | $plugins['all'][ $plugin_file ] = $plugin_data; |
| 243 | // Make sure that $plugins['upgrade'] also receives the extra info since it is used on ?plugin_status=upgrade. |
| 244 | if ( isset( $plugins['upgrade'][ $plugin_file ] ) ) { |
| 245 | $plugins['upgrade'][ $plugin_file ] = $plugin_data; |