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 |
|---|---|
| 916 | * |
| 917 | * @since 2.3.0 |
| 918 | * |
| 919 | * @param string $plugin_file Path to the plugin file relative to the plugins directory. |
| 920 | * @param array $plugin_data An array of plugin data. |
| 921 | * @param string $status Status of the plugin. Defaults are 'All', 'Active', |
| 922 | * 'Inactive', 'Recently Activated', 'Upgrade', 'Must-Use', |
| 923 | * 'Drop-ins', 'Search', 'Paused'. |
| 924 | */ |
| 925 | do_action( 'after_plugin_row', $plugin_file, $plugin_data, $status ); |
| 926 | |
| 927 | /** |
| 928 | * Fires after each specific row in the Plugins list table. |
| 929 | * |
| 930 | * The dynamic portion of the hook name, `$plugin_file`, refers to the path |
| 931 | * to the plugin file, relative to the plugins directory. |
| 932 | * |
| 933 | * @since 2.7.0 |
| 934 | * |