Welcome, visitor! Log in
 

Source View: {$prefix}plugin_action_links

To save our bandwidth, we show only a snippet of code around each occurence of the hook. View complete file in SVN (without highlighting).

Understanding Source Code

The best way to understand what a hook does is to look at where it occurs in the source code.

  • Action hooks look like this: do_action( "hook_name" )
  • Filter hooks look like this: 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.

Source View

Line Code
439            * @since 2.5.0
440            *
441            * @param array  $actions     An array of plugin action links.
442            * @param string $plugin_file Path to the plugin file.
443            * @param array  $plugin_data An array of plugin data.
444            * @param string $context     The plugin context. Defaults are 'All', 'Active',
445            *                            'Inactive', 'Recently Activated', 'Upgrade',
446            *                            'Must-Use', 'Drop-ins', 'Search'.
447            */
448           $actions = apply_filters( $prefix . 'plugin_action_links', array_filter( $actions ), $plugin_file, $plugin_data, $context );
449
450           /**
451            * Filter the list of action links displayed for a specific plugin.
452            *
453            * The first dynamic portion of the hook name, $prefix, refers to the context
454            * the action links are displayed in. The 'network_admin_' prefix is used if the
455            * current screen is the Network plugins list table. The prefix is empty ('')
456            * if the current screen is the site plugins list table.
457            *