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 |
|---|---|
| 655 | * @since 4.4.0 |
| 656 | * |
| 657 | * @param array $actions An array of plugin action links. |
| 658 | * @param string $plugin_file Path to the plugin file relative to the plugins directory. |
| 659 | * @param array $plugin_data An array of plugin data. |
| 660 | * @param string $context The plugin context. Defaults are 'All', 'Active', |
| 661 | * 'Inactive', 'Recently Activated', 'Upgrade', |
| 662 | * 'Must-Use', 'Drop-ins', 'Search'. |
| 663 | */ |
| 664 | $actions = apply_filters( 'plugin_action_links', $actions, $plugin_file, $plugin_data, $context ); |
| 665 | |
| 666 | /** |
| 667 | * Filter the list of action links displayed for a specific plugin in the Plugins list table. |
| 668 | * |
| 669 | * The dynamic portion of the hook name, $plugin_file, refers to the path |
| 670 | * to the plugin file, relative to the plugins directory. |
| 671 | * |
| 672 | * @since 2.7.0 As `{$prefix}_plugin_action_links_{$plugin_file}` |
| 673 | * @since 4.4.0 |