2006-06-19 22:03:24 -04:00
|
|
|
<?php
|
2007-10-19 13:45:08 -04:00
|
|
|
/**
|
|
|
|
* The plugin API is located in this file, which allows for creating actions
|
|
|
|
* and filters and hooking functions, and methods. The functions or methods will
|
|
|
|
* then be run when the action or filter is called.
|
|
|
|
*
|
|
|
|
* The API callback examples reference functions, but can be methods of classes.
|
|
|
|
* To hook methods, you'll need to pass an array one of two ways.
|
|
|
|
*
|
|
|
|
* Any of the syntaxes explained in the PHP documentation for the
|
2020-01-19 22:14:06 -05:00
|
|
|
* {@link https://www.php.net/manual/en/language.pseudo-types.php#language.types.callback 'callback'}
|
2007-12-06 00:56:38 -05:00
|
|
|
* type are valid.
|
2007-10-19 13:45:08 -04:00
|
|
|
*
|
2019-07-25 18:45:57 -04:00
|
|
|
* Also see the {@link https://developer.wordpress.org/plugins/ Plugin API} for
|
2008-08-30 17:23:43 -04:00
|
|
|
* more information and examples on how to use a lot of these functions.
|
2007-10-19 13:45:08 -04:00
|
|
|
*
|
2016-08-19 00:10:30 -04:00
|
|
|
* This file should have no external dependencies.
|
|
|
|
*
|
2007-10-19 13:45:08 -04:00
|
|
|
* @package WordPress
|
|
|
|
* @subpackage Plugin
|
2013-12-24 13:57:12 -05:00
|
|
|
* @since 1.5.0
|
2007-10-19 13:45:08 -04:00
|
|
|
*/
|
2006-06-19 22:03:24 -04:00
|
|
|
|
2013-09-24 15:05:10 -04:00
|
|
|
// Initialize the filter globals.
|
2020-02-06 01:33:11 -05:00
|
|
|
require __DIR__ . '/class-wp-hook.php';
|
2013-09-24 15:05:10 -04:00
|
|
|
|
Hooks: Add the new class `WP_Hook`, and modify hook handling to make use of it.
Filters and actions have been the basis of WordPress' plugin functionality since time immemorial, they've always been a reliable method for acting upon the current state of WordPress, and will continue to be so.
Over the years, however, edge cases have cropped up. Particularly when it comes to recursively executing hooks, or a hook adding and removing itself, the existing implementation struggled to keep up with more complex use cases.
And so, we introduce `WP_Hook`. By changing `$wp_filter` from an array of arrays, to an array of objects, we reduce the complexity of the hook handling code, as the processing code (see `::apply_filters()`) only needs to be aware of itself, rather than the state of all hooks. At the same time, we're able te handle more complex use cases, as the object can more easily keep track of its own state than an array ever could.
Props jbrinley for the original architecture and design of this patch.
Props SergeyBiryukov, cheeserolls, Denis-de-Bernardy, leewillis77, wonderboymusic, nacin, jorbin, DrewAPicture, ocean90, dougwollison, khag7, pento, noplanman and aaroncampbell for their testing, suggestions, contributions, patch maintenance, cajoling and patience as we got through this.
Fixes #17817.
Built from https://develop.svn.wordpress.org/trunk@38571
git-svn-id: http://core.svn.wordpress.org/trunk@38514 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-09-07 23:55:31 -04:00
|
|
|
/** @var WP_Hook[] $wp_filter */
|
|
|
|
global $wp_filter, $wp_actions, $wp_current_filter;
|
|
|
|
|
|
|
|
if ( $wp_filter ) {
|
|
|
|
$wp_filter = WP_Hook::build_preinitialized_hooks( $wp_filter );
|
|
|
|
} else {
|
2013-09-24 15:05:10 -04:00
|
|
|
$wp_filter = array();
|
Hooks: Add the new class `WP_Hook`, and modify hook handling to make use of it.
Filters and actions have been the basis of WordPress' plugin functionality since time immemorial, they've always been a reliable method for acting upon the current state of WordPress, and will continue to be so.
Over the years, however, edge cases have cropped up. Particularly when it comes to recursively executing hooks, or a hook adding and removing itself, the existing implementation struggled to keep up with more complex use cases.
And so, we introduce `WP_Hook`. By changing `$wp_filter` from an array of arrays, to an array of objects, we reduce the complexity of the hook handling code, as the processing code (see `::apply_filters()`) only needs to be aware of itself, rather than the state of all hooks. At the same time, we're able te handle more complex use cases, as the object can more easily keep track of its own state than an array ever could.
Props jbrinley for the original architecture and design of this patch.
Props SergeyBiryukov, cheeserolls, Denis-de-Bernardy, leewillis77, wonderboymusic, nacin, jorbin, DrewAPicture, ocean90, dougwollison, khag7, pento, noplanman and aaroncampbell for their testing, suggestions, contributions, patch maintenance, cajoling and patience as we got through this.
Fixes #17817.
Built from https://develop.svn.wordpress.org/trunk@38571
git-svn-id: http://core.svn.wordpress.org/trunk@38514 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-09-07 23:55:31 -04:00
|
|
|
}
|
2013-09-24 15:05:10 -04:00
|
|
|
|
2017-11-30 18:11:00 -05:00
|
|
|
if ( ! isset( $wp_actions ) ) {
|
2013-09-24 15:05:10 -04:00
|
|
|
$wp_actions = array();
|
2017-11-30 18:11:00 -05:00
|
|
|
}
|
2013-09-24 15:05:10 -04:00
|
|
|
|
2017-11-30 18:11:00 -05:00
|
|
|
if ( ! isset( $wp_current_filter ) ) {
|
2013-09-24 15:05:10 -04:00
|
|
|
$wp_current_filter = array();
|
2017-11-30 18:11:00 -05:00
|
|
|
}
|
2013-09-24 15:05:10 -04:00
|
|
|
|
2007-03-28 22:45:34 -04:00
|
|
|
/**
|
2014-06-29 05:19:15 -04:00
|
|
|
* Hook a function or method to a specific filter action.
|
2007-09-03 19:32:58 -04:00
|
|
|
*
|
2013-09-18 03:48:10 -04:00
|
|
|
* WordPress offers filter hooks to allow plugins to modify
|
|
|
|
* various types of internal data at runtime.
|
2007-10-19 13:45:08 -04:00
|
|
|
*
|
2013-09-18 03:48:10 -04:00
|
|
|
* A plugin can modify data by binding a callback to a filter hook. When the filter
|
|
|
|
* is later applied, each bound callback is run in order of priority, and given
|
|
|
|
* the opportunity to modify a value by returning a new value.
|
|
|
|
*
|
|
|
|
* The following example shows how a callback function is bound to a filter hook.
|
2008-08-30 17:23:43 -04:00
|
|
|
*
|
2014-11-24 01:05:23 -05:00
|
|
|
* Note that `$example` is passed to the callback, (maybe) modified, then returned:
|
|
|
|
*
|
|
|
|
* function example_callback( $example ) {
|
|
|
|
* // Maybe modify $example in some way.
|
2016-01-25 13:58:27 -05:00
|
|
|
* return $example;
|
2014-11-24 01:05:23 -05:00
|
|
|
* }
|
|
|
|
* add_filter( 'example_filter', 'example_callback' );
|
2007-10-19 13:45:08 -04:00
|
|
|
*
|
2015-09-18 10:53:28 -04:00
|
|
|
* Bound callbacks can accept from none to the total number of arguments passed as parameters
|
|
|
|
* in the corresponding apply_filters() call.
|
2007-10-19 13:45:08 -04:00
|
|
|
*
|
2015-09-18 10:53:28 -04:00
|
|
|
* In other words, if an apply_filters() call passes four total arguments, callbacks bound to
|
|
|
|
* it can accept none (the same as 1) of the arguments or up to four. The important part is that
|
|
|
|
* the `$accepted_args` value must reflect the number of arguments the bound callback *actually*
|
|
|
|
* opted to accept. If no arguments were accepted by the callback that is considered to be the
|
|
|
|
* same as accepting 1 argument. For example:
|
|
|
|
*
|
|
|
|
* // Filter call.
|
|
|
|
* $value = apply_filters( 'hook', $value, $arg2, $arg3 );
|
|
|
|
*
|
|
|
|
* // Accepting zero/one arguments.
|
|
|
|
* function example_callback() {
|
|
|
|
* ...
|
|
|
|
* return 'some value';
|
|
|
|
* }
|
|
|
|
* add_filter( 'hook', 'example_callback' ); // Where $priority is default 10, $accepted_args is default 1.
|
|
|
|
*
|
|
|
|
* // Accepting two arguments (three possible).
|
|
|
|
* function example_callback( $value, $arg2 ) {
|
|
|
|
* ...
|
|
|
|
* return $maybe_modified_value;
|
|
|
|
* }
|
|
|
|
* add_filter( 'hook', 'example_callback', 10, 2 ); // Where $priority is 10, $accepted_args is 2.
|
|
|
|
*
|
|
|
|
* *Note:* The function will return true whether or not the callback is valid.
|
|
|
|
* It is up to you to take care. This is done for optimization purposes, so
|
|
|
|
* everything is as quick as possible.
|
2007-10-19 13:45:08 -04:00
|
|
|
*
|
2013-09-18 03:48:10 -04:00
|
|
|
* @since 0.71
|
|
|
|
*
|
2019-11-29 16:42:01 -05:00
|
|
|
* @global array $wp_filter A multidimensional array of all hooks and the callbacks hooked to them.
|
2014-06-29 05:19:15 -04:00
|
|
|
*
|
2013-09-18 03:48:10 -04:00
|
|
|
* @param string $tag The name of the filter to hook the $function_to_add callback to.
|
2015-09-25 19:58:25 -04:00
|
|
|
* @param callable $function_to_add The callback to be run when the filter is applied.
|
2014-06-29 04:42:16 -04:00
|
|
|
* @param int $priority Optional. Used to specify the order in which the functions
|
2019-11-29 16:42:01 -05:00
|
|
|
* associated with a particular action are executed.
|
2014-06-29 04:42:16 -04:00
|
|
|
* Lower numbers correspond with earlier execution,
|
|
|
|
* and functions with the same priority are executed
|
2019-11-29 16:42:01 -05:00
|
|
|
* in the order in which they were added to the action. Default 10.
|
2014-06-29 04:42:16 -04:00
|
|
|
* @param int $accepted_args Optional. The number of arguments the function accepts. Default 1.
|
2015-05-27 11:56:26 -04:00
|
|
|
* @return true
|
2007-03-28 22:45:34 -04:00
|
|
|
*/
|
2013-09-18 03:48:10 -04:00
|
|
|
function add_filter( $tag, $function_to_add, $priority = 10, $accepted_args = 1 ) {
|
Hooks: Add the new class `WP_Hook`, and modify hook handling to make use of it.
Filters and actions have been the basis of WordPress' plugin functionality since time immemorial, they've always been a reliable method for acting upon the current state of WordPress, and will continue to be so.
Over the years, however, edge cases have cropped up. Particularly when it comes to recursively executing hooks, or a hook adding and removing itself, the existing implementation struggled to keep up with more complex use cases.
And so, we introduce `WP_Hook`. By changing `$wp_filter` from an array of arrays, to an array of objects, we reduce the complexity of the hook handling code, as the processing code (see `::apply_filters()`) only needs to be aware of itself, rather than the state of all hooks. At the same time, we're able te handle more complex use cases, as the object can more easily keep track of its own state than an array ever could.
Props jbrinley for the original architecture and design of this patch.
Props SergeyBiryukov, cheeserolls, Denis-de-Bernardy, leewillis77, wonderboymusic, nacin, jorbin, DrewAPicture, ocean90, dougwollison, khag7, pento, noplanman and aaroncampbell for their testing, suggestions, contributions, patch maintenance, cajoling and patience as we got through this.
Fixes #17817.
Built from https://develop.svn.wordpress.org/trunk@38571
git-svn-id: http://core.svn.wordpress.org/trunk@38514 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-09-07 23:55:31 -04:00
|
|
|
global $wp_filter;
|
|
|
|
if ( ! isset( $wp_filter[ $tag ] ) ) {
|
|
|
|
$wp_filter[ $tag ] = new WP_Hook();
|
|
|
|
}
|
|
|
|
$wp_filter[ $tag ]->add_filter( $tag, $function_to_add, $priority, $accepted_args );
|
2006-06-19 22:03:24 -04:00
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
2007-11-06 23:30:11 -05:00
|
|
|
/**
|
2008-08-07 19:39:27 -04:00
|
|
|
* Check if any filter has been registered for a hook.
|
2007-12-06 00:56:38 -05:00
|
|
|
*
|
2013-12-24 13:57:12 -05:00
|
|
|
* @since 2.5.0
|
|
|
|
*
|
2019-11-29 16:42:01 -05:00
|
|
|
* @global array $wp_filter Stores all of the filters and actions.
|
2007-11-06 23:30:11 -05:00
|
|
|
*
|
2014-06-29 04:42:16 -04:00
|
|
|
* @param string $tag The name of the filter hook.
|
2015-09-25 19:58:25 -04:00
|
|
|
* @param callable|bool $function_to_check Optional. The callback to check for. Default false.
|
2015-05-27 11:56:26 -04:00
|
|
|
* @return false|int If $function_to_check is omitted, returns boolean for whether the hook has
|
|
|
|
* anything registered. When checking a specific function, the priority of that
|
|
|
|
* hook is returned, or false if the function is not attached. When using the
|
|
|
|
* $function_to_check argument, this function may return a non-boolean value
|
|
|
|
* that evaluates to false (e.g.) 0, so use the === operator for testing the
|
|
|
|
* return value.
|
2007-11-06 23:30:11 -05:00
|
|
|
*/
|
2017-11-30 18:11:00 -05:00
|
|
|
function has_filter( $tag, $function_to_check = false ) {
|
Hooks: Add the new class `WP_Hook`, and modify hook handling to make use of it.
Filters and actions have been the basis of WordPress' plugin functionality since time immemorial, they've always been a reliable method for acting upon the current state of WordPress, and will continue to be so.
Over the years, however, edge cases have cropped up. Particularly when it comes to recursively executing hooks, or a hook adding and removing itself, the existing implementation struggled to keep up with more complex use cases.
And so, we introduce `WP_Hook`. By changing `$wp_filter` from an array of arrays, to an array of objects, we reduce the complexity of the hook handling code, as the processing code (see `::apply_filters()`) only needs to be aware of itself, rather than the state of all hooks. At the same time, we're able te handle more complex use cases, as the object can more easily keep track of its own state than an array ever could.
Props jbrinley for the original architecture and design of this patch.
Props SergeyBiryukov, cheeserolls, Denis-de-Bernardy, leewillis77, wonderboymusic, nacin, jorbin, DrewAPicture, ocean90, dougwollison, khag7, pento, noplanman and aaroncampbell for their testing, suggestions, contributions, patch maintenance, cajoling and patience as we got through this.
Fixes #17817.
Built from https://develop.svn.wordpress.org/trunk@38571
git-svn-id: http://core.svn.wordpress.org/trunk@38514 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-09-07 23:55:31 -04:00
|
|
|
global $wp_filter;
|
2007-11-06 23:30:11 -05:00
|
|
|
|
Hooks: Add the new class `WP_Hook`, and modify hook handling to make use of it.
Filters and actions have been the basis of WordPress' plugin functionality since time immemorial, they've always been a reliable method for acting upon the current state of WordPress, and will continue to be so.
Over the years, however, edge cases have cropped up. Particularly when it comes to recursively executing hooks, or a hook adding and removing itself, the existing implementation struggled to keep up with more complex use cases.
And so, we introduce `WP_Hook`. By changing `$wp_filter` from an array of arrays, to an array of objects, we reduce the complexity of the hook handling code, as the processing code (see `::apply_filters()`) only needs to be aware of itself, rather than the state of all hooks. At the same time, we're able te handle more complex use cases, as the object can more easily keep track of its own state than an array ever could.
Props jbrinley for the original architecture and design of this patch.
Props SergeyBiryukov, cheeserolls, Denis-de-Bernardy, leewillis77, wonderboymusic, nacin, jorbin, DrewAPicture, ocean90, dougwollison, khag7, pento, noplanman and aaroncampbell for their testing, suggestions, contributions, patch maintenance, cajoling and patience as we got through this.
Fixes #17817.
Built from https://develop.svn.wordpress.org/trunk@38571
git-svn-id: http://core.svn.wordpress.org/trunk@38514 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-09-07 23:55:31 -04:00
|
|
|
if ( ! isset( $wp_filter[ $tag ] ) ) {
|
2007-11-06 23:30:11 -05:00
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
Hooks: Add the new class `WP_Hook`, and modify hook handling to make use of it.
Filters and actions have been the basis of WordPress' plugin functionality since time immemorial, they've always been a reliable method for acting upon the current state of WordPress, and will continue to be so.
Over the years, however, edge cases have cropped up. Particularly when it comes to recursively executing hooks, or a hook adding and removing itself, the existing implementation struggled to keep up with more complex use cases.
And so, we introduce `WP_Hook`. By changing `$wp_filter` from an array of arrays, to an array of objects, we reduce the complexity of the hook handling code, as the processing code (see `::apply_filters()`) only needs to be aware of itself, rather than the state of all hooks. At the same time, we're able te handle more complex use cases, as the object can more easily keep track of its own state than an array ever could.
Props jbrinley for the original architecture and design of this patch.
Props SergeyBiryukov, cheeserolls, Denis-de-Bernardy, leewillis77, wonderboymusic, nacin, jorbin, DrewAPicture, ocean90, dougwollison, khag7, pento, noplanman and aaroncampbell for their testing, suggestions, contributions, patch maintenance, cajoling and patience as we got through this.
Fixes #17817.
Built from https://develop.svn.wordpress.org/trunk@38571
git-svn-id: http://core.svn.wordpress.org/trunk@38514 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-09-07 23:55:31 -04:00
|
|
|
return $wp_filter[ $tag ]->has_filter( $tag, $function_to_check );
|
2007-11-06 23:30:11 -05:00
|
|
|
}
|
|
|
|
|
2007-03-28 22:45:34 -04:00
|
|
|
/**
|
2019-05-25 18:52:54 -04:00
|
|
|
* Calls the callback functions that have been added to a filter hook.
|
2007-09-03 19:32:58 -04:00
|
|
|
*
|
2019-05-25 18:52:54 -04:00
|
|
|
* The callback functions attached to the filter hook are invoked by calling
|
2008-08-30 17:23:43 -04:00
|
|
|
* this function. This function can be used to create a new filter hook by
|
|
|
|
* simply calling this function with the name of the new hook specified using
|
2019-05-25 18:52:54 -04:00
|
|
|
* the `$tag` parameter.
|
2007-10-19 13:45:08 -04:00
|
|
|
*
|
2019-05-25 18:52:54 -04:00
|
|
|
* The function also allows for multiple additional arguments to be passed to hooks.
|
2014-11-24 01:05:23 -05:00
|
|
|
*
|
2019-05-25 18:52:54 -04:00
|
|
|
* Example usage:
|
|
|
|
*
|
2020-01-28 19:45:18 -05:00
|
|
|
* // The filter callback function.
|
2014-11-24 01:05:23 -05:00
|
|
|
* function example_callback( $string, $arg1, $arg2 ) {
|
2020-01-28 19:45:18 -05:00
|
|
|
* // (maybe) modify $string.
|
2014-11-24 01:05:23 -05:00
|
|
|
* return $string;
|
|
|
|
* }
|
|
|
|
* add_filter( 'example_filter', 'example_callback', 10, 3 );
|
|
|
|
*
|
|
|
|
* /*
|
2020-01-28 19:45:18 -05:00
|
|
|
* * Apply the filters by calling the 'example_callback()' function
|
|
|
|
* * that's hooked onto `example_filter` above.
|
2019-05-25 18:52:54 -04:00
|
|
|
* *
|
2020-01-28 19:45:18 -05:00
|
|
|
* * - 'example_filter' is the filter hook.
|
|
|
|
* * - 'filter me' is the value being filtered.
|
2014-11-24 01:05:23 -05:00
|
|
|
* * - $arg1 and $arg2 are the additional arguments passed to the callback.
|
|
|
|
* $value = apply_filters( 'example_filter', 'filter me', $arg1, $arg2 );
|
2007-10-19 13:45:08 -04:00
|
|
|
*
|
2014-06-29 05:19:15 -04:00
|
|
|
* @since 0.71
|
|
|
|
*
|
2019-11-29 16:42:01 -05:00
|
|
|
* @global array $wp_filter Stores all of the filters and actions.
|
2014-06-29 04:42:16 -04:00
|
|
|
* @global array $wp_current_filter Stores the list of current filters with the current one last.
|
2007-10-19 13:45:08 -04:00
|
|
|
*
|
2019-05-25 18:52:54 -04:00
|
|
|
* @param string $tag The name of the filter hook.
|
|
|
|
* @param mixed $value The value to filter.
|
|
|
|
* @param mixed ...$args Additional parameters to pass to the callback functions.
|
2007-12-06 00:56:38 -05:00
|
|
|
* @return mixed The filtered value after all hooked functions are applied to it.
|
2007-03-28 22:45:34 -04:00
|
|
|
*/
|
2013-09-18 03:48:10 -04:00
|
|
|
function apply_filters( $tag, $value ) {
|
Hooks: Add the new class `WP_Hook`, and modify hook handling to make use of it.
Filters and actions have been the basis of WordPress' plugin functionality since time immemorial, they've always been a reliable method for acting upon the current state of WordPress, and will continue to be so.
Over the years, however, edge cases have cropped up. Particularly when it comes to recursively executing hooks, or a hook adding and removing itself, the existing implementation struggled to keep up with more complex use cases.
And so, we introduce `WP_Hook`. By changing `$wp_filter` from an array of arrays, to an array of objects, we reduce the complexity of the hook handling code, as the processing code (see `::apply_filters()`) only needs to be aware of itself, rather than the state of all hooks. At the same time, we're able te handle more complex use cases, as the object can more easily keep track of its own state than an array ever could.
Props jbrinley for the original architecture and design of this patch.
Props SergeyBiryukov, cheeserolls, Denis-de-Bernardy, leewillis77, wonderboymusic, nacin, jorbin, DrewAPicture, ocean90, dougwollison, khag7, pento, noplanman and aaroncampbell for their testing, suggestions, contributions, patch maintenance, cajoling and patience as we got through this.
Fixes #17817.
Built from https://develop.svn.wordpress.org/trunk@38571
git-svn-id: http://core.svn.wordpress.org/trunk@38514 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-09-07 23:55:31 -04:00
|
|
|
global $wp_filter, $wp_current_filter;
|
2007-11-06 16:38:04 -05:00
|
|
|
|
2019-09-15 08:04:55 -04:00
|
|
|
$args = func_get_args();
|
2006-06-19 22:03:24 -04:00
|
|
|
|
2014-06-29 05:19:15 -04:00
|
|
|
// Do 'all' actions first.
|
2017-11-30 18:11:00 -05:00
|
|
|
if ( isset( $wp_filter['all'] ) ) {
|
2011-04-14 14:05:30 -04:00
|
|
|
$wp_current_filter[] = $tag;
|
2017-11-30 18:11:00 -05:00
|
|
|
_wp_call_all_hook( $args );
|
2007-11-06 13:31:43 -05:00
|
|
|
}
|
2006-06-19 22:03:24 -04:00
|
|
|
|
2017-11-30 18:11:00 -05:00
|
|
|
if ( ! isset( $wp_filter[ $tag ] ) ) {
|
|
|
|
if ( isset( $wp_filter['all'] ) ) {
|
|
|
|
array_pop( $wp_current_filter );
|
|
|
|
}
|
2007-10-19 13:45:08 -04:00
|
|
|
return $value;
|
2007-11-06 16:38:04 -05:00
|
|
|
}
|
2006-06-19 22:03:24 -04:00
|
|
|
|
2017-11-30 18:11:00 -05:00
|
|
|
if ( ! isset( $wp_filter['all'] ) ) {
|
2011-04-14 14:05:30 -04:00
|
|
|
$wp_current_filter[] = $tag;
|
2017-11-30 18:11:00 -05:00
|
|
|
}
|
2011-04-14 14:05:30 -04:00
|
|
|
|
2019-09-15 08:04:55 -04:00
|
|
|
// Don't pass the tag name to WP_Hook.
|
Hooks: Add the new class `WP_Hook`, and modify hook handling to make use of it.
Filters and actions have been the basis of WordPress' plugin functionality since time immemorial, they've always been a reliable method for acting upon the current state of WordPress, and will continue to be so.
Over the years, however, edge cases have cropped up. Particularly when it comes to recursively executing hooks, or a hook adding and removing itself, the existing implementation struggled to keep up with more complex use cases.
And so, we introduce `WP_Hook`. By changing `$wp_filter` from an array of arrays, to an array of objects, we reduce the complexity of the hook handling code, as the processing code (see `::apply_filters()`) only needs to be aware of itself, rather than the state of all hooks. At the same time, we're able te handle more complex use cases, as the object can more easily keep track of its own state than an array ever could.
Props jbrinley for the original architecture and design of this patch.
Props SergeyBiryukov, cheeserolls, Denis-de-Bernardy, leewillis77, wonderboymusic, nacin, jorbin, DrewAPicture, ocean90, dougwollison, khag7, pento, noplanman and aaroncampbell for their testing, suggestions, contributions, patch maintenance, cajoling and patience as we got through this.
Fixes #17817.
Built from https://develop.svn.wordpress.org/trunk@38571
git-svn-id: http://core.svn.wordpress.org/trunk@38514 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-09-07 23:55:31 -04:00
|
|
|
array_shift( $args );
|
2012-07-21 16:24:21 -04:00
|
|
|
|
Hooks: Add the new class `WP_Hook`, and modify hook handling to make use of it.
Filters and actions have been the basis of WordPress' plugin functionality since time immemorial, they've always been a reliable method for acting upon the current state of WordPress, and will continue to be so.
Over the years, however, edge cases have cropped up. Particularly when it comes to recursively executing hooks, or a hook adding and removing itself, the existing implementation struggled to keep up with more complex use cases.
And so, we introduce `WP_Hook`. By changing `$wp_filter` from an array of arrays, to an array of objects, we reduce the complexity of the hook handling code, as the processing code (see `::apply_filters()`) only needs to be aware of itself, rather than the state of all hooks. At the same time, we're able te handle more complex use cases, as the object can more easily keep track of its own state than an array ever could.
Props jbrinley for the original architecture and design of this patch.
Props SergeyBiryukov, cheeserolls, Denis-de-Bernardy, leewillis77, wonderboymusic, nacin, jorbin, DrewAPicture, ocean90, dougwollison, khag7, pento, noplanman and aaroncampbell for their testing, suggestions, contributions, patch maintenance, cajoling and patience as we got through this.
Fixes #17817.
Built from https://develop.svn.wordpress.org/trunk@38571
git-svn-id: http://core.svn.wordpress.org/trunk@38514 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-09-07 23:55:31 -04:00
|
|
|
$filtered = $wp_filter[ $tag ]->apply_filters( $value, $args );
|
2008-02-05 01:47:27 -05:00
|
|
|
|
2007-11-06 16:38:04 -05:00
|
|
|
array_pop( $wp_current_filter );
|
2010-03-18 17:24:07 -04:00
|
|
|
|
Hooks: Add the new class `WP_Hook`, and modify hook handling to make use of it.
Filters and actions have been the basis of WordPress' plugin functionality since time immemorial, they've always been a reliable method for acting upon the current state of WordPress, and will continue to be so.
Over the years, however, edge cases have cropped up. Particularly when it comes to recursively executing hooks, or a hook adding and removing itself, the existing implementation struggled to keep up with more complex use cases.
And so, we introduce `WP_Hook`. By changing `$wp_filter` from an array of arrays, to an array of objects, we reduce the complexity of the hook handling code, as the processing code (see `::apply_filters()`) only needs to be aware of itself, rather than the state of all hooks. At the same time, we're able te handle more complex use cases, as the object can more easily keep track of its own state than an array ever could.
Props jbrinley for the original architecture and design of this patch.
Props SergeyBiryukov, cheeserolls, Denis-de-Bernardy, leewillis77, wonderboymusic, nacin, jorbin, DrewAPicture, ocean90, dougwollison, khag7, pento, noplanman and aaroncampbell for their testing, suggestions, contributions, patch maintenance, cajoling and patience as we got through this.
Fixes #17817.
Built from https://develop.svn.wordpress.org/trunk@38571
git-svn-id: http://core.svn.wordpress.org/trunk@38514 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-09-07 23:55:31 -04:00
|
|
|
return $filtered;
|
2010-03-18 17:24:07 -04:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
2019-05-25 18:52:54 -04:00
|
|
|
* Calls the callback functions that have been added to a filter hook, specifying arguments in an array.
|
2010-03-18 17:24:07 -04:00
|
|
|
*
|
2015-12-23 02:13:26 -05:00
|
|
|
* @since 3.0.0
|
2010-03-18 17:24:07 -04:00
|
|
|
*
|
2014-11-24 01:05:23 -05:00
|
|
|
* @see apply_filters() This function is identical, but the arguments passed to the
|
|
|
|
* functions hooked to `$tag` are supplied using an array.
|
2014-06-29 05:19:15 -04:00
|
|
|
*
|
2019-11-29 16:42:01 -05:00
|
|
|
* @global array $wp_filter Stores all of the filters and actions.
|
|
|
|
* @global array $wp_current_filter Stores the list of current filters with the current one last.
|
2010-03-18 17:24:07 -04:00
|
|
|
*
|
2014-06-29 04:42:16 -04:00
|
|
|
* @param string $tag The name of the filter hook.
|
2014-06-29 05:19:15 -04:00
|
|
|
* @param array $args The arguments supplied to the functions hooked to $tag.
|
2010-03-18 17:24:07 -04:00
|
|
|
* @return mixed The filtered value after all hooked functions are applied to it.
|
|
|
|
*/
|
2017-11-30 18:11:00 -05:00
|
|
|
function apply_filters_ref_array( $tag, $args ) {
|
Hooks: Add the new class `WP_Hook`, and modify hook handling to make use of it.
Filters and actions have been the basis of WordPress' plugin functionality since time immemorial, they've always been a reliable method for acting upon the current state of WordPress, and will continue to be so.
Over the years, however, edge cases have cropped up. Particularly when it comes to recursively executing hooks, or a hook adding and removing itself, the existing implementation struggled to keep up with more complex use cases.
And so, we introduce `WP_Hook`. By changing `$wp_filter` from an array of arrays, to an array of objects, we reduce the complexity of the hook handling code, as the processing code (see `::apply_filters()`) only needs to be aware of itself, rather than the state of all hooks. At the same time, we're able te handle more complex use cases, as the object can more easily keep track of its own state than an array ever could.
Props jbrinley for the original architecture and design of this patch.
Props SergeyBiryukov, cheeserolls, Denis-de-Bernardy, leewillis77, wonderboymusic, nacin, jorbin, DrewAPicture, ocean90, dougwollison, khag7, pento, noplanman and aaroncampbell for their testing, suggestions, contributions, patch maintenance, cajoling and patience as we got through this.
Fixes #17817.
Built from https://develop.svn.wordpress.org/trunk@38571
git-svn-id: http://core.svn.wordpress.org/trunk@38514 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-09-07 23:55:31 -04:00
|
|
|
global $wp_filter, $wp_current_filter;
|
2010-03-18 17:24:07 -04:00
|
|
|
|
2020-01-28 19:45:18 -05:00
|
|
|
// Do 'all' actions first.
|
2017-11-30 18:11:00 -05:00
|
|
|
if ( isset( $wp_filter['all'] ) ) {
|
2011-04-14 14:05:30 -04:00
|
|
|
$wp_current_filter[] = $tag;
|
2020-06-03 13:40:12 -04:00
|
|
|
$all_args = func_get_args(); // phpcs:ignore PHPCompatibility.FunctionUse.ArgumentFunctionsReportCurrentValue.NeedsInspection
|
2017-11-30 18:11:00 -05:00
|
|
|
_wp_call_all_hook( $all_args );
|
2010-03-18 17:24:07 -04:00
|
|
|
}
|
|
|
|
|
2017-11-30 18:11:00 -05:00
|
|
|
if ( ! isset( $wp_filter[ $tag ] ) ) {
|
|
|
|
if ( isset( $wp_filter['all'] ) ) {
|
|
|
|
array_pop( $wp_current_filter );
|
|
|
|
}
|
2010-03-31 17:39:18 -04:00
|
|
|
return $args[0];
|
2010-03-18 17:24:07 -04:00
|
|
|
}
|
|
|
|
|
2017-11-30 18:11:00 -05:00
|
|
|
if ( ! isset( $wp_filter['all'] ) ) {
|
2011-04-14 14:05:30 -04:00
|
|
|
$wp_current_filter[] = $tag;
|
2017-11-30 18:11:00 -05:00
|
|
|
}
|
2011-04-14 14:05:30 -04:00
|
|
|
|
Hooks: Add the new class `WP_Hook`, and modify hook handling to make use of it.
Filters and actions have been the basis of WordPress' plugin functionality since time immemorial, they've always been a reliable method for acting upon the current state of WordPress, and will continue to be so.
Over the years, however, edge cases have cropped up. Particularly when it comes to recursively executing hooks, or a hook adding and removing itself, the existing implementation struggled to keep up with more complex use cases.
And so, we introduce `WP_Hook`. By changing `$wp_filter` from an array of arrays, to an array of objects, we reduce the complexity of the hook handling code, as the processing code (see `::apply_filters()`) only needs to be aware of itself, rather than the state of all hooks. At the same time, we're able te handle more complex use cases, as the object can more easily keep track of its own state than an array ever could.
Props jbrinley for the original architecture and design of this patch.
Props SergeyBiryukov, cheeserolls, Denis-de-Bernardy, leewillis77, wonderboymusic, nacin, jorbin, DrewAPicture, ocean90, dougwollison, khag7, pento, noplanman and aaroncampbell for their testing, suggestions, contributions, patch maintenance, cajoling and patience as we got through this.
Fixes #17817.
Built from https://develop.svn.wordpress.org/trunk@38571
git-svn-id: http://core.svn.wordpress.org/trunk@38514 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-09-07 23:55:31 -04:00
|
|
|
$filtered = $wp_filter[ $tag ]->apply_filters( $args[0], $args );
|
2010-03-18 17:24:07 -04:00
|
|
|
|
|
|
|
array_pop( $wp_current_filter );
|
2007-02-27 20:09:20 -05:00
|
|
|
|
Hooks: Add the new class `WP_Hook`, and modify hook handling to make use of it.
Filters and actions have been the basis of WordPress' plugin functionality since time immemorial, they've always been a reliable method for acting upon the current state of WordPress, and will continue to be so.
Over the years, however, edge cases have cropped up. Particularly when it comes to recursively executing hooks, or a hook adding and removing itself, the existing implementation struggled to keep up with more complex use cases.
And so, we introduce `WP_Hook`. By changing `$wp_filter` from an array of arrays, to an array of objects, we reduce the complexity of the hook handling code, as the processing code (see `::apply_filters()`) only needs to be aware of itself, rather than the state of all hooks. At the same time, we're able te handle more complex use cases, as the object can more easily keep track of its own state than an array ever could.
Props jbrinley for the original architecture and design of this patch.
Props SergeyBiryukov, cheeserolls, Denis-de-Bernardy, leewillis77, wonderboymusic, nacin, jorbin, DrewAPicture, ocean90, dougwollison, khag7, pento, noplanman and aaroncampbell for their testing, suggestions, contributions, patch maintenance, cajoling and patience as we got through this.
Fixes #17817.
Built from https://develop.svn.wordpress.org/trunk@38571
git-svn-id: http://core.svn.wordpress.org/trunk@38514 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-09-07 23:55:31 -04:00
|
|
|
return $filtered;
|
2006-06-19 22:03:24 -04:00
|
|
|
}
|
|
|
|
|
2007-03-28 22:45:34 -04:00
|
|
|
/**
|
2008-08-07 19:39:27 -04:00
|
|
|
* Removes a function from a specified filter hook.
|
2007-09-03 19:32:58 -04:00
|
|
|
*
|
|
|
|
* This function removes a function attached to a specified filter hook. This
|
|
|
|
* method can be used to remove default functions attached to a specific filter
|
2007-03-28 22:45:34 -04:00
|
|
|
* hook and possibly replace them with a substitute.
|
2007-10-19 13:45:08 -04:00
|
|
|
*
|
2008-08-07 19:39:27 -04:00
|
|
|
* To remove a hook, the $function_to_remove and $priority arguments must match
|
|
|
|
* when the hook was added. This goes for both filters and actions. No warning
|
2007-10-19 13:45:08 -04:00
|
|
|
* will be given on removal failure.
|
|
|
|
*
|
2013-12-24 13:57:12 -05:00
|
|
|
* @since 1.2.0
|
2007-10-19 13:45:08 -04:00
|
|
|
*
|
2019-11-29 16:42:01 -05:00
|
|
|
* @global array $wp_filter Stores all of the filters and actions.
|
2015-05-27 11:56:26 -04:00
|
|
|
*
|
2014-06-29 04:42:16 -04:00
|
|
|
* @param string $tag The filter hook to which the function to be removed is hooked.
|
2015-09-25 19:58:25 -04:00
|
|
|
* @param callable $function_to_remove The name of the function which should be removed.
|
2014-06-29 04:42:16 -04:00
|
|
|
* @param int $priority Optional. The priority of the function. Default 10.
|
2015-05-27 11:56:26 -04:00
|
|
|
* @return bool Whether the function existed before it was removed.
|
2007-03-28 22:45:34 -04:00
|
|
|
*/
|
2012-07-20 09:54:42 -04:00
|
|
|
function remove_filter( $tag, $function_to_remove, $priority = 10 ) {
|
Hooks: Add the new class `WP_Hook`, and modify hook handling to make use of it.
Filters and actions have been the basis of WordPress' plugin functionality since time immemorial, they've always been a reliable method for acting upon the current state of WordPress, and will continue to be so.
Over the years, however, edge cases have cropped up. Particularly when it comes to recursively executing hooks, or a hook adding and removing itself, the existing implementation struggled to keep up with more complex use cases.
And so, we introduce `WP_Hook`. By changing `$wp_filter` from an array of arrays, to an array of objects, we reduce the complexity of the hook handling code, as the processing code (see `::apply_filters()`) only needs to be aware of itself, rather than the state of all hooks. At the same time, we're able te handle more complex use cases, as the object can more easily keep track of its own state than an array ever could.
Props jbrinley for the original architecture and design of this patch.
Props SergeyBiryukov, cheeserolls, Denis-de-Bernardy, leewillis77, wonderboymusic, nacin, jorbin, DrewAPicture, ocean90, dougwollison, khag7, pento, noplanman and aaroncampbell for their testing, suggestions, contributions, patch maintenance, cajoling and patience as we got through this.
Fixes #17817.
Built from https://develop.svn.wordpress.org/trunk@38571
git-svn-id: http://core.svn.wordpress.org/trunk@38514 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-09-07 23:55:31 -04:00
|
|
|
global $wp_filter;
|
2007-02-27 20:09:20 -05:00
|
|
|
|
Hooks: Add the new class `WP_Hook`, and modify hook handling to make use of it.
Filters and actions have been the basis of WordPress' plugin functionality since time immemorial, they've always been a reliable method for acting upon the current state of WordPress, and will continue to be so.
Over the years, however, edge cases have cropped up. Particularly when it comes to recursively executing hooks, or a hook adding and removing itself, the existing implementation struggled to keep up with more complex use cases.
And so, we introduce `WP_Hook`. By changing `$wp_filter` from an array of arrays, to an array of objects, we reduce the complexity of the hook handling code, as the processing code (see `::apply_filters()`) only needs to be aware of itself, rather than the state of all hooks. At the same time, we're able te handle more complex use cases, as the object can more easily keep track of its own state than an array ever could.
Props jbrinley for the original architecture and design of this patch.
Props SergeyBiryukov, cheeserolls, Denis-de-Bernardy, leewillis77, wonderboymusic, nacin, jorbin, DrewAPicture, ocean90, dougwollison, khag7, pento, noplanman and aaroncampbell for their testing, suggestions, contributions, patch maintenance, cajoling and patience as we got through this.
Fixes #17817.
Built from https://develop.svn.wordpress.org/trunk@38571
git-svn-id: http://core.svn.wordpress.org/trunk@38514 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-09-07 23:55:31 -04:00
|
|
|
$r = false;
|
|
|
|
if ( isset( $wp_filter[ $tag ] ) ) {
|
|
|
|
$r = $wp_filter[ $tag ]->remove_filter( $tag, $function_to_remove, $priority );
|
|
|
|
if ( ! $wp_filter[ $tag ]->callbacks ) {
|
|
|
|
unset( $wp_filter[ $tag ] );
|
2014-06-28 00:38:15 -04:00
|
|
|
}
|
2007-11-06 13:31:43 -05:00
|
|
|
}
|
2007-05-04 19:27:12 -04:00
|
|
|
|
|
|
|
return $r;
|
2006-06-19 22:03:24 -04:00
|
|
|
}
|
|
|
|
|
2008-08-17 07:15:38 -04:00
|
|
|
/**
|
|
|
|
* Remove all of the hooks from a filter.
|
|
|
|
*
|
2013-12-24 13:57:12 -05:00
|
|
|
* @since 2.7.0
|
2008-08-17 07:15:38 -04:00
|
|
|
*
|
2019-11-29 16:42:01 -05:00
|
|
|
* @global array $wp_filter Stores all of the filters and actions.
|
2015-05-27 11:56:26 -04:00
|
|
|
*
|
2014-06-29 04:42:16 -04:00
|
|
|
* @param string $tag The filter to remove hooks from.
|
2014-06-29 04:47:14 -04:00
|
|
|
* @param int|bool $priority Optional. The priority number to remove. Default false.
|
2015-05-27 11:56:26 -04:00
|
|
|
* @return true True when finished.
|
2008-08-17 07:15:38 -04:00
|
|
|
*/
|
2014-06-28 00:27:15 -04:00
|
|
|
function remove_all_filters( $tag, $priority = false ) {
|
Hooks: Add the new class `WP_Hook`, and modify hook handling to make use of it.
Filters and actions have been the basis of WordPress' plugin functionality since time immemorial, they've always been a reliable method for acting upon the current state of WordPress, and will continue to be so.
Over the years, however, edge cases have cropped up. Particularly when it comes to recursively executing hooks, or a hook adding and removing itself, the existing implementation struggled to keep up with more complex use cases.
And so, we introduce `WP_Hook`. By changing `$wp_filter` from an array of arrays, to an array of objects, we reduce the complexity of the hook handling code, as the processing code (see `::apply_filters()`) only needs to be aware of itself, rather than the state of all hooks. At the same time, we're able te handle more complex use cases, as the object can more easily keep track of its own state than an array ever could.
Props jbrinley for the original architecture and design of this patch.
Props SergeyBiryukov, cheeserolls, Denis-de-Bernardy, leewillis77, wonderboymusic, nacin, jorbin, DrewAPicture, ocean90, dougwollison, khag7, pento, noplanman and aaroncampbell for their testing, suggestions, contributions, patch maintenance, cajoling and patience as we got through this.
Fixes #17817.
Built from https://develop.svn.wordpress.org/trunk@38571
git-svn-id: http://core.svn.wordpress.org/trunk@38514 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-09-07 23:55:31 -04:00
|
|
|
global $wp_filter;
|
2008-08-17 07:15:38 -04:00
|
|
|
|
2017-11-30 18:11:00 -05:00
|
|
|
if ( isset( $wp_filter[ $tag ] ) ) {
|
Hooks: Add the new class `WP_Hook`, and modify hook handling to make use of it.
Filters and actions have been the basis of WordPress' plugin functionality since time immemorial, they've always been a reliable method for acting upon the current state of WordPress, and will continue to be so.
Over the years, however, edge cases have cropped up. Particularly when it comes to recursively executing hooks, or a hook adding and removing itself, the existing implementation struggled to keep up with more complex use cases.
And so, we introduce `WP_Hook`. By changing `$wp_filter` from an array of arrays, to an array of objects, we reduce the complexity of the hook handling code, as the processing code (see `::apply_filters()`) only needs to be aware of itself, rather than the state of all hooks. At the same time, we're able te handle more complex use cases, as the object can more easily keep track of its own state than an array ever could.
Props jbrinley for the original architecture and design of this patch.
Props SergeyBiryukov, cheeserolls, Denis-de-Bernardy, leewillis77, wonderboymusic, nacin, jorbin, DrewAPicture, ocean90, dougwollison, khag7, pento, noplanman and aaroncampbell for their testing, suggestions, contributions, patch maintenance, cajoling and patience as we got through this.
Fixes #17817.
Built from https://develop.svn.wordpress.org/trunk@38571
git-svn-id: http://core.svn.wordpress.org/trunk@38514 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-09-07 23:55:31 -04:00
|
|
|
$wp_filter[ $tag ]->remove_all_filters( $priority );
|
|
|
|
if ( ! $wp_filter[ $tag ]->has_filters() ) {
|
|
|
|
unset( $wp_filter[ $tag ] );
|
2014-06-28 00:27:15 -04:00
|
|
|
}
|
2008-08-17 07:15:38 -04:00
|
|
|
}
|
|
|
|
|
|
|
|
return true;
|
|
|
|
}
|
2007-11-06 13:31:43 -05:00
|
|
|
|
2007-11-06 16:38:04 -05:00
|
|
|
/**
|
2008-08-30 17:23:43 -04:00
|
|
|
* Retrieve the name of the current filter or action.
|
2007-12-06 00:56:38 -05:00
|
|
|
*
|
2013-12-24 13:57:12 -05:00
|
|
|
* @since 2.5.0
|
2007-12-06 00:56:38 -05:00
|
|
|
*
|
2015-05-27 11:56:26 -04:00
|
|
|
* @global array $wp_current_filter Stores the list of current filters with the current one last
|
|
|
|
*
|
2007-12-06 00:56:38 -05:00
|
|
|
* @return string Hook name of the current filter or action.
|
2007-11-06 16:38:04 -05:00
|
|
|
*/
|
|
|
|
function current_filter() {
|
|
|
|
global $wp_current_filter;
|
|
|
|
return end( $wp_current_filter );
|
|
|
|
}
|
|
|
|
|
2014-02-26 13:44:14 -05:00
|
|
|
/**
|
|
|
|
* Retrieve the name of the current action.
|
|
|
|
*
|
|
|
|
* @since 3.9.0
|
2014-04-07 17:30:14 -04:00
|
|
|
*
|
2014-02-26 13:44:14 -05:00
|
|
|
* @return string Hook name of the current action.
|
|
|
|
*/
|
|
|
|
function current_action() {
|
|
|
|
return current_filter();
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* Retrieve the name of a filter currently being processed.
|
|
|
|
*
|
|
|
|
* The function current_filter() only returns the most recent filter or action
|
2014-04-07 17:30:14 -04:00
|
|
|
* being executed. did_action() returns true once the action is initially
|
2014-06-29 05:19:15 -04:00
|
|
|
* processed.
|
|
|
|
*
|
|
|
|
* This function allows detection for any filter currently being
|
2014-02-26 13:44:14 -05:00
|
|
|
* executed (despite not being the most recent filter to fire, in the case of
|
|
|
|
* hooks called from hook callbacks) to be verified.
|
|
|
|
*
|
|
|
|
* @since 3.9.0
|
2014-04-07 17:30:14 -04:00
|
|
|
*
|
2014-02-26 13:44:14 -05:00
|
|
|
* @see current_filter()
|
|
|
|
* @see did_action()
|
2014-04-07 17:30:14 -04:00
|
|
|
* @global array $wp_current_filter Current filter.
|
2014-02-26 13:44:14 -05:00
|
|
|
*
|
2014-04-07 17:30:14 -04:00
|
|
|
* @param null|string $filter Optional. Filter to check. Defaults to null, which
|
|
|
|
* checks if any filter is currently being run.
|
2014-06-29 05:19:15 -04:00
|
|
|
* @return bool Whether the filter is currently in the stack.
|
2014-02-26 13:44:14 -05:00
|
|
|
*/
|
|
|
|
function doing_filter( $filter = null ) {
|
|
|
|
global $wp_current_filter;
|
|
|
|
|
|
|
|
if ( null === $filter ) {
|
|
|
|
return ! empty( $wp_current_filter );
|
|
|
|
}
|
|
|
|
|
2020-04-04 23:02:11 -04:00
|
|
|
return in_array( $filter, $wp_current_filter, true );
|
2014-02-26 13:44:14 -05:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
2017-10-04 16:25:49 -04:00
|
|
|
* Retrieve the name of an action currently being processed.
|
2014-02-26 13:44:14 -05:00
|
|
|
*
|
|
|
|
* @since 3.9.0
|
|
|
|
*
|
2014-04-07 17:30:14 -04:00
|
|
|
* @param string|null $action Optional. Action to check. Defaults to null, which checks
|
|
|
|
* if any action is currently being run.
|
2014-02-26 13:44:14 -05:00
|
|
|
* @return bool Whether the action is currently in the stack.
|
|
|
|
*/
|
|
|
|
function doing_action( $action = null ) {
|
|
|
|
return doing_filter( $action );
|
|
|
|
}
|
|
|
|
|
2007-03-28 22:45:34 -04:00
|
|
|
/**
|
2008-08-07 19:39:27 -04:00
|
|
|
* Hooks a function on to a specific action.
|
2007-09-03 19:32:58 -04:00
|
|
|
*
|
|
|
|
* Actions are the hooks that the WordPress core launches at specific points
|
2007-03-28 22:45:34 -04:00
|
|
|
* during execution, or when specific events occur. Plugins can specify that
|
2007-09-03 19:32:58 -04:00
|
|
|
* one or more of its PHP functions are executed at these points, using the
|
2007-03-28 22:45:34 -04:00
|
|
|
* Action API.
|
2007-09-03 19:32:58 -04:00
|
|
|
*
|
2013-12-24 13:57:12 -05:00
|
|
|
* @since 1.2.0
|
2007-10-19 13:45:08 -04:00
|
|
|
*
|
2014-06-29 04:42:16 -04:00
|
|
|
* @param string $tag The name of the action to which the $function_to_add is hooked.
|
2015-09-25 19:58:25 -04:00
|
|
|
* @param callable $function_to_add The name of the function you wish to be called.
|
2014-06-29 04:42:16 -04:00
|
|
|
* @param int $priority Optional. Used to specify the order in which the functions
|
|
|
|
* associated with a particular action are executed. Default 10.
|
|
|
|
* Lower numbers correspond with earlier execution,
|
|
|
|
* and functions with the same priority are executed
|
|
|
|
* in the order in which they were added to the action.
|
2015-06-18 04:37:25 -04:00
|
|
|
* @param int $accepted_args Optional. The number of arguments the function accepts. Default 1.
|
2015-05-27 11:56:26 -04:00
|
|
|
* @return true Will always return true.
|
2007-03-28 22:45:34 -04:00
|
|
|
*/
|
2017-11-30 18:11:00 -05:00
|
|
|
function add_action( $tag, $function_to_add, $priority = 10, $accepted_args = 1 ) {
|
|
|
|
return add_filter( $tag, $function_to_add, $priority, $accepted_args );
|
2006-06-19 22:03:24 -04:00
|
|
|
}
|
|
|
|
|
2007-03-28 22:45:34 -04:00
|
|
|
/**
|
2008-08-07 19:39:27 -04:00
|
|
|
* Execute functions hooked on a specific action hook.
|
2007-09-03 19:32:58 -04:00
|
|
|
*
|
2014-11-24 01:05:23 -05:00
|
|
|
* This function invokes all functions attached to action hook `$tag`. It is
|
2008-08-30 17:23:43 -04:00
|
|
|
* possible to create new action hooks by simply calling this function,
|
2014-11-24 01:05:23 -05:00
|
|
|
* specifying the name of the new hook using the `$tag` parameter.
|
2007-10-19 13:45:08 -04:00
|
|
|
*
|
2019-05-25 18:52:54 -04:00
|
|
|
* You can pass extra arguments to the hooks, much like you can with `apply_filters()`.
|
|
|
|
*
|
|
|
|
* Example usage:
|
|
|
|
*
|
2020-01-28 19:45:18 -05:00
|
|
|
* // The action callback function.
|
2019-05-25 18:52:54 -04:00
|
|
|
* function example_callback( $arg1, $arg2 ) {
|
2020-01-28 19:45:18 -05:00
|
|
|
* // (maybe) do something with the args.
|
2019-05-25 18:52:54 -04:00
|
|
|
* }
|
|
|
|
* add_action( 'example_action', 'example_callback', 10, 2 );
|
|
|
|
*
|
|
|
|
* /*
|
2020-01-28 19:45:18 -05:00
|
|
|
* * Trigger the actions by calling the 'example_callback()' function
|
|
|
|
* * that's hooked onto `example_action` above.
|
2019-05-25 18:52:54 -04:00
|
|
|
* *
|
2020-01-28 19:45:18 -05:00
|
|
|
* * - 'example_action' is the action hook.
|
2019-05-25 18:52:54 -04:00
|
|
|
* * - $arg1 and $arg2 are the additional arguments passed to the callback.
|
2019-05-25 18:53:51 -04:00
|
|
|
* $value = do_action( 'example_action', $arg1, $arg2 );
|
2007-10-19 13:45:08 -04:00
|
|
|
*
|
2013-12-24 13:57:12 -05:00
|
|
|
* @since 1.2.0
|
2019-10-09 00:28:02 -04:00
|
|
|
* @since 5.3.0 Formalized the existing and already documented `...$arg` parameter
|
|
|
|
* by adding it to the function signature.
|
2013-12-24 13:57:12 -05:00
|
|
|
*
|
2019-11-29 16:42:01 -05:00
|
|
|
* @global array $wp_filter Stores all of the filters and actions.
|
2015-05-27 11:56:26 -04:00
|
|
|
* @global array $wp_actions Increments the amount of times action was triggered.
|
2019-11-29 16:42:01 -05:00
|
|
|
* @global array $wp_current_filter Stores the list of current filters with the current one last.
|
2007-10-19 13:45:08 -04:00
|
|
|
*
|
2019-05-25 17:59:51 -04:00
|
|
|
* @param string $tag The name of the action to be executed.
|
|
|
|
* @param mixed ...$arg Optional. Additional arguments which are passed on to the
|
|
|
|
* functions hooked to the action. Default empty.
|
2007-03-28 22:45:34 -04:00
|
|
|
*/
|
2019-09-26 09:53:58 -04:00
|
|
|
function do_action( $tag, ...$arg ) {
|
Hooks: Add the new class `WP_Hook`, and modify hook handling to make use of it.
Filters and actions have been the basis of WordPress' plugin functionality since time immemorial, they've always been a reliable method for acting upon the current state of WordPress, and will continue to be so.
Over the years, however, edge cases have cropped up. Particularly when it comes to recursively executing hooks, or a hook adding and removing itself, the existing implementation struggled to keep up with more complex use cases.
And so, we introduce `WP_Hook`. By changing `$wp_filter` from an array of arrays, to an array of objects, we reduce the complexity of the hook handling code, as the processing code (see `::apply_filters()`) only needs to be aware of itself, rather than the state of all hooks. At the same time, we're able te handle more complex use cases, as the object can more easily keep track of its own state than an array ever could.
Props jbrinley for the original architecture and design of this patch.
Props SergeyBiryukov, cheeserolls, Denis-de-Bernardy, leewillis77, wonderboymusic, nacin, jorbin, DrewAPicture, ocean90, dougwollison, khag7, pento, noplanman and aaroncampbell for their testing, suggestions, contributions, patch maintenance, cajoling and patience as we got through this.
Fixes #17817.
Built from https://develop.svn.wordpress.org/trunk@38571
git-svn-id: http://core.svn.wordpress.org/trunk@38514 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-09-07 23:55:31 -04:00
|
|
|
global $wp_filter, $wp_actions, $wp_current_filter;
|
2006-12-07 22:45:34 -05:00
|
|
|
|
2017-11-30 18:11:00 -05:00
|
|
|
if ( ! isset( $wp_actions[ $tag ] ) ) {
|
|
|
|
$wp_actions[ $tag ] = 1;
|
|
|
|
} else {
|
|
|
|
++$wp_actions[ $tag ];
|
|
|
|
}
|
2007-05-07 19:22:50 -04:00
|
|
|
|
2020-01-28 19:45:18 -05:00
|
|
|
// Do 'all' actions first.
|
2017-11-30 18:11:00 -05:00
|
|
|
if ( isset( $wp_filter['all'] ) ) {
|
2011-04-14 14:05:30 -04:00
|
|
|
$wp_current_filter[] = $tag;
|
2020-06-03 13:40:12 -04:00
|
|
|
$all_args = func_get_args(); // phpcs:ignore PHPCompatibility.FunctionUse.ArgumentFunctionsReportCurrentValue.NeedsInspection
|
2017-11-30 18:11:00 -05:00
|
|
|
_wp_call_all_hook( $all_args );
|
2007-11-06 13:31:43 -05:00
|
|
|
}
|
|
|
|
|
2017-11-30 18:11:00 -05:00
|
|
|
if ( ! isset( $wp_filter[ $tag ] ) ) {
|
|
|
|
if ( isset( $wp_filter['all'] ) ) {
|
|
|
|
array_pop( $wp_current_filter );
|
|
|
|
}
|
2006-06-19 22:03:24 -04:00
|
|
|
return;
|
2007-11-06 16:38:04 -05:00
|
|
|
}
|
2007-11-07 20:05:43 -05:00
|
|
|
|
2017-11-30 18:11:00 -05:00
|
|
|
if ( ! isset( $wp_filter['all'] ) ) {
|
2011-04-14 14:05:30 -04:00
|
|
|
$wp_current_filter[] = $tag;
|
2017-11-30 18:11:00 -05:00
|
|
|
}
|
2011-04-14 14:05:30 -04:00
|
|
|
|
2019-09-26 09:53:58 -04:00
|
|
|
if ( empty( $arg ) ) {
|
|
|
|
$arg[] = '';
|
2019-10-21 20:11:03 -04:00
|
|
|
} elseif ( is_array( $arg[0] ) && 1 === count( $arg[0] ) && isset( $arg[0][0] ) && is_object( $arg[0][0] ) ) {
|
|
|
|
// Backward compatibility for PHP4-style passing of `array( &$this )` as action `$arg`.
|
|
|
|
$arg[0] = $arg[0][0];
|
2017-11-30 18:11:00 -05:00
|
|
|
}
|
2007-11-07 20:05:43 -05:00
|
|
|
|
2019-09-26 09:53:58 -04:00
|
|
|
$wp_filter[ $tag ]->do_action( $arg );
|
2006-12-07 22:45:34 -05:00
|
|
|
|
2017-11-30 18:11:00 -05:00
|
|
|
array_pop( $wp_current_filter );
|
2006-12-07 22:45:34 -05:00
|
|
|
}
|
|
|
|
|
2007-03-28 22:45:34 -04:00
|
|
|
/**
|
2011-08-04 12:03:53 -04:00
|
|
|
* Retrieve the number of times an action is fired.
|
2007-10-19 13:45:08 -04:00
|
|
|
*
|
2013-12-24 13:57:12 -05:00
|
|
|
* @since 2.1.0
|
|
|
|
*
|
2007-10-19 13:45:08 -04:00
|
|
|
* @global array $wp_actions Increments the amount of times action was triggered.
|
|
|
|
*
|
2007-03-28 22:45:34 -04:00
|
|
|
* @param string $tag The name of the action hook.
|
2014-06-29 05:19:15 -04:00
|
|
|
* @return int The number of times action hook $tag is fired.
|
2007-03-28 22:45:34 -04:00
|
|
|
*/
|
2017-11-30 18:11:00 -05:00
|
|
|
function did_action( $tag ) {
|
2006-12-07 22:45:34 -05:00
|
|
|
global $wp_actions;
|
|
|
|
|
2017-11-30 18:11:00 -05:00
|
|
|
if ( ! isset( $wp_actions[ $tag ] ) ) {
|
2007-05-08 13:59:52 -04:00
|
|
|
return 0;
|
2017-11-30 18:11:00 -05:00
|
|
|
}
|
2007-05-08 13:59:52 -04:00
|
|
|
|
2017-11-30 18:11:00 -05:00
|
|
|
return $wp_actions[ $tag ];
|
2006-09-12 13:45:23 -04:00
|
|
|
}
|
|
|
|
|
2007-03-28 22:45:34 -04:00
|
|
|
/**
|
2019-05-25 18:52:54 -04:00
|
|
|
* Calls the callback functions that have been added to an action hook, specifying arguments in an array.
|
2007-09-03 19:32:58 -04:00
|
|
|
*
|
2013-12-24 13:57:12 -05:00
|
|
|
* @since 2.1.0
|
|
|
|
*
|
2014-06-29 05:19:15 -04:00
|
|
|
* @see do_action() This function is identical, but the arguments passed to the
|
2019-05-25 18:52:54 -04:00
|
|
|
* functions hooked to `$tag` are supplied using an array.
|
2019-11-29 16:42:01 -05:00
|
|
|
* @global array $wp_filter Stores all of the filters and actions.
|
2015-05-27 11:56:26 -04:00
|
|
|
* @global array $wp_actions Increments the amount of times action was triggered.
|
2019-11-29 16:42:01 -05:00
|
|
|
* @global array $wp_current_filter Stores the list of current filters with the current one last.
|
2007-10-19 13:45:08 -04:00
|
|
|
*
|
2014-06-29 04:42:16 -04:00
|
|
|
* @param string $tag The name of the action to be executed.
|
2014-11-24 01:05:23 -05:00
|
|
|
* @param array $args The arguments supplied to the functions hooked to `$tag`.
|
2007-03-28 22:45:34 -04:00
|
|
|
*/
|
2017-11-30 18:11:00 -05:00
|
|
|
function do_action_ref_array( $tag, $args ) {
|
Hooks: Add the new class `WP_Hook`, and modify hook handling to make use of it.
Filters and actions have been the basis of WordPress' plugin functionality since time immemorial, they've always been a reliable method for acting upon the current state of WordPress, and will continue to be so.
Over the years, however, edge cases have cropped up. Particularly when it comes to recursively executing hooks, or a hook adding and removing itself, the existing implementation struggled to keep up with more complex use cases.
And so, we introduce `WP_Hook`. By changing `$wp_filter` from an array of arrays, to an array of objects, we reduce the complexity of the hook handling code, as the processing code (see `::apply_filters()`) only needs to be aware of itself, rather than the state of all hooks. At the same time, we're able te handle more complex use cases, as the object can more easily keep track of its own state than an array ever could.
Props jbrinley for the original architecture and design of this patch.
Props SergeyBiryukov, cheeserolls, Denis-de-Bernardy, leewillis77, wonderboymusic, nacin, jorbin, DrewAPicture, ocean90, dougwollison, khag7, pento, noplanman and aaroncampbell for their testing, suggestions, contributions, patch maintenance, cajoling and patience as we got through this.
Fixes #17817.
Built from https://develop.svn.wordpress.org/trunk@38571
git-svn-id: http://core.svn.wordpress.org/trunk@38514 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-09-07 23:55:31 -04:00
|
|
|
global $wp_filter, $wp_actions, $wp_current_filter;
|
2006-12-07 22:45:34 -05:00
|
|
|
|
2017-11-30 18:11:00 -05:00
|
|
|
if ( ! isset( $wp_actions[ $tag ] ) ) {
|
|
|
|
$wp_actions[ $tag ] = 1;
|
|
|
|
} else {
|
|
|
|
++$wp_actions[ $tag ];
|
|
|
|
}
|
2006-09-12 13:45:23 -04:00
|
|
|
|
2020-01-28 19:45:18 -05:00
|
|
|
// Do 'all' actions first.
|
2017-11-30 18:11:00 -05:00
|
|
|
if ( isset( $wp_filter['all'] ) ) {
|
2011-04-14 14:05:30 -04:00
|
|
|
$wp_current_filter[] = $tag;
|
2020-06-03 13:40:12 -04:00
|
|
|
$all_args = func_get_args(); // phpcs:ignore PHPCompatibility.FunctionUse.ArgumentFunctionsReportCurrentValue.NeedsInspection
|
2017-11-30 18:11:00 -05:00
|
|
|
_wp_call_all_hook( $all_args );
|
2007-11-06 13:31:43 -05:00
|
|
|
}
|
|
|
|
|
2017-11-30 18:11:00 -05:00
|
|
|
if ( ! isset( $wp_filter[ $tag ] ) ) {
|
|
|
|
if ( isset( $wp_filter['all'] ) ) {
|
|
|
|
array_pop( $wp_current_filter );
|
|
|
|
}
|
2006-09-12 13:45:23 -04:00
|
|
|
return;
|
2007-12-06 00:56:38 -05:00
|
|
|
}
|
2006-09-12 13:45:23 -04:00
|
|
|
|
2017-11-30 18:11:00 -05:00
|
|
|
if ( ! isset( $wp_filter['all'] ) ) {
|
2011-04-14 14:05:30 -04:00
|
|
|
$wp_current_filter[] = $tag;
|
2017-11-30 18:11:00 -05:00
|
|
|
}
|
2011-04-14 14:05:30 -04:00
|
|
|
|
Hooks: Add the new class `WP_Hook`, and modify hook handling to make use of it.
Filters and actions have been the basis of WordPress' plugin functionality since time immemorial, they've always been a reliable method for acting upon the current state of WordPress, and will continue to be so.
Over the years, however, edge cases have cropped up. Particularly when it comes to recursively executing hooks, or a hook adding and removing itself, the existing implementation struggled to keep up with more complex use cases.
And so, we introduce `WP_Hook`. By changing `$wp_filter` from an array of arrays, to an array of objects, we reduce the complexity of the hook handling code, as the processing code (see `::apply_filters()`) only needs to be aware of itself, rather than the state of all hooks. At the same time, we're able te handle more complex use cases, as the object can more easily keep track of its own state than an array ever could.
Props jbrinley for the original architecture and design of this patch.
Props SergeyBiryukov, cheeserolls, Denis-de-Bernardy, leewillis77, wonderboymusic, nacin, jorbin, DrewAPicture, ocean90, dougwollison, khag7, pento, noplanman and aaroncampbell for their testing, suggestions, contributions, patch maintenance, cajoling and patience as we got through this.
Fixes #17817.
Built from https://develop.svn.wordpress.org/trunk@38571
git-svn-id: http://core.svn.wordpress.org/trunk@38514 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-09-07 23:55:31 -04:00
|
|
|
$wp_filter[ $tag ]->do_action( $args );
|
2007-02-27 20:09:20 -05:00
|
|
|
|
2017-11-30 18:11:00 -05:00
|
|
|
array_pop( $wp_current_filter );
|
2006-06-19 22:03:24 -04:00
|
|
|
}
|
|
|
|
|
2007-11-06 23:30:11 -05:00
|
|
|
/**
|
2008-08-07 19:39:27 -04:00
|
|
|
* Check if any action has been registered for a hook.
|
2007-12-06 00:56:38 -05:00
|
|
|
*
|
2013-12-24 13:57:12 -05:00
|
|
|
* @since 2.5.0
|
|
|
|
*
|
2007-12-06 00:56:38 -05:00
|
|
|
* @see has_filter() has_action() is an alias of has_filter().
|
2007-11-06 23:30:11 -05:00
|
|
|
*
|
2014-06-29 04:42:16 -04:00
|
|
|
* @param string $tag The name of the action hook.
|
2015-09-25 19:58:25 -04:00
|
|
|
* @param callable|bool $function_to_check Optional. The callback to check for. Default false.
|
2014-06-29 05:19:15 -04:00
|
|
|
* @return bool|int If $function_to_check is omitted, returns boolean for whether the hook has
|
|
|
|
* anything registered. When checking a specific function, the priority of that
|
|
|
|
* hook is returned, or false if the function is not attached. When using the
|
|
|
|
* $function_to_check argument, this function may return a non-boolean value
|
|
|
|
* that evaluates to false (e.g.) 0, so use the === operator for testing the
|
|
|
|
* return value.
|
2007-11-06 23:30:11 -05:00
|
|
|
*/
|
2017-11-30 18:11:00 -05:00
|
|
|
function has_action( $tag, $function_to_check = false ) {
|
|
|
|
return has_filter( $tag, $function_to_check );
|
2007-11-06 23:30:11 -05:00
|
|
|
}
|
|
|
|
|
2007-03-28 22:45:34 -04:00
|
|
|
/**
|
2008-08-07 19:39:27 -04:00
|
|
|
* Removes a function from a specified action hook.
|
2007-09-03 19:32:58 -04:00
|
|
|
*
|
|
|
|
* This function removes a function attached to a specified action hook. This
|
|
|
|
* method can be used to remove default functions attached to a specific filter
|
2007-03-28 22:45:34 -04:00
|
|
|
* hook and possibly replace them with a substitute.
|
2007-10-19 13:45:08 -04:00
|
|
|
*
|
2013-12-24 13:57:12 -05:00
|
|
|
* @since 1.2.0
|
2007-10-19 13:45:08 -04:00
|
|
|
*
|
2014-06-29 04:42:16 -04:00
|
|
|
* @param string $tag The action hook to which the function to be removed is hooked.
|
2015-09-25 19:58:25 -04:00
|
|
|
* @param callable $function_to_remove The name of the function which should be removed.
|
2014-06-29 04:42:16 -04:00
|
|
|
* @param int $priority Optional. The priority of the function. Default 10.
|
2015-06-26 21:03:25 -04:00
|
|
|
* @return bool Whether the function is removed.
|
2007-03-28 22:45:34 -04:00
|
|
|
*/
|
2012-07-20 09:54:42 -04:00
|
|
|
function remove_action( $tag, $function_to_remove, $priority = 10 ) {
|
|
|
|
return remove_filter( $tag, $function_to_remove, $priority );
|
2006-06-19 22:03:24 -04:00
|
|
|
}
|
|
|
|
|
2008-08-17 07:15:38 -04:00
|
|
|
/**
|
|
|
|
* Remove all of the hooks from an action.
|
|
|
|
*
|
2013-12-24 13:57:12 -05:00
|
|
|
* @since 2.7.0
|
2008-08-17 07:15:38 -04:00
|
|
|
*
|
2014-06-29 04:42:16 -04:00
|
|
|
* @param string $tag The action to remove hooks from.
|
2014-06-29 04:47:14 -04:00
|
|
|
* @param int|bool $priority The priority number to remove them from. Default false.
|
2015-05-27 11:56:26 -04:00
|
|
|
* @return true True when finished.
|
2008-08-17 07:15:38 -04:00
|
|
|
*/
|
2017-11-30 18:11:00 -05:00
|
|
|
function remove_all_actions( $tag, $priority = false ) {
|
|
|
|
return remove_all_filters( $tag, $priority );
|
2008-08-17 07:15:38 -04:00
|
|
|
}
|
|
|
|
|
2016-06-26 10:26:29 -04:00
|
|
|
/**
|
|
|
|
* Fires functions attached to a deprecated filter hook.
|
|
|
|
*
|
|
|
|
* When a filter hook is deprecated, the apply_filters() call is replaced with
|
|
|
|
* apply_filters_deprecated(), which triggers a deprecation notice and then fires
|
|
|
|
* the original filter hook.
|
|
|
|
*
|
2017-08-23 11:52:46 -04:00
|
|
|
* Note: the value and extra arguments passed to the original apply_filters() call
|
|
|
|
* must be passed here to `$args` as an array. For example:
|
|
|
|
*
|
|
|
|
* // Old filter.
|
|
|
|
* return apply_filters( 'wpdocs_filter', $value, $extra_arg );
|
|
|
|
*
|
|
|
|
* // Deprecated.
|
2019-11-09 08:57:03 -05:00
|
|
|
* return apply_filters_deprecated( 'wpdocs_filter', array( $value, $extra_arg ), '4.9.0', 'wpdocs_new_filter' );
|
2017-08-23 11:52:46 -04:00
|
|
|
*
|
2016-06-26 10:26:29 -04:00
|
|
|
* @since 4.6.0
|
|
|
|
*
|
|
|
|
* @see _deprecated_hook()
|
|
|
|
*
|
|
|
|
* @param string $tag The name of the filter hook.
|
|
|
|
* @param array $args Array of additional function arguments to be passed to apply_filters().
|
|
|
|
* @param string $version The version of WordPress that deprecated the hook.
|
2019-11-27 18:55:01 -05:00
|
|
|
* @param string $replacement Optional. The hook that should have been used. Default null.
|
2016-07-20 15:33:30 -04:00
|
|
|
* @param string $message Optional. A message regarding the change. Default null.
|
2016-06-26 10:26:29 -04:00
|
|
|
*/
|
2019-11-27 18:55:01 -05:00
|
|
|
function apply_filters_deprecated( $tag, $args, $version, $replacement = null, $message = null ) {
|
2016-06-26 10:26:29 -04:00
|
|
|
if ( ! has_filter( $tag ) ) {
|
2016-06-29 09:22:27 -04:00
|
|
|
return $args[0];
|
2016-06-26 10:26:29 -04:00
|
|
|
}
|
|
|
|
|
|
|
|
_deprecated_hook( $tag, $version, $replacement, $message );
|
|
|
|
|
|
|
|
return apply_filters_ref_array( $tag, $args );
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* Fires functions attached to a deprecated action hook.
|
|
|
|
*
|
|
|
|
* When an action hook is deprecated, the do_action() call is replaced with
|
|
|
|
* do_action_deprecated(), which triggers a deprecation notice and then fires
|
|
|
|
* the original hook.
|
|
|
|
*
|
|
|
|
* @since 4.6.0
|
|
|
|
*
|
|
|
|
* @see _deprecated_hook()
|
|
|
|
*
|
|
|
|
* @param string $tag The name of the action hook.
|
|
|
|
* @param array $args Array of additional function arguments to be passed to do_action().
|
|
|
|
* @param string $version The version of WordPress that deprecated the hook.
|
2019-11-27 18:55:01 -05:00
|
|
|
* @param string $replacement Optional. The hook that should have been used. Default null.
|
|
|
|
* @param string $message Optional. A message regarding the change. Default null.
|
2016-06-26 10:26:29 -04:00
|
|
|
*/
|
2019-11-27 18:55:01 -05:00
|
|
|
function do_action_deprecated( $tag, $args, $version, $replacement = null, $message = null ) {
|
2016-06-26 10:26:29 -04:00
|
|
|
if ( ! has_action( $tag ) ) {
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
_deprecated_hook( $tag, $version, $replacement, $message );
|
|
|
|
|
|
|
|
do_action_ref_array( $tag, $args );
|
|
|
|
}
|
|
|
|
|
2006-06-19 22:03:24 -04:00
|
|
|
//
|
|
|
|
// Functions for handling plugins.
|
|
|
|
//
|
|
|
|
|
2007-03-28 22:45:34 -04:00
|
|
|
/**
|
2008-08-07 19:39:27 -04:00
|
|
|
* Gets the basename of a plugin.
|
2007-09-03 19:32:58 -04:00
|
|
|
*
|
2008-05-27 13:55:24 -04:00
|
|
|
* This method extracts the name of a plugin from its filename.
|
2007-10-19 13:45:08 -04:00
|
|
|
*
|
2013-12-24 13:57:12 -05:00
|
|
|
* @since 1.5.0
|
2007-10-19 13:45:08 -04:00
|
|
|
*
|
2015-05-27 11:56:26 -04:00
|
|
|
* @global array $wp_plugin_paths
|
|
|
|
*
|
2007-03-28 22:45:34 -04:00
|
|
|
* @param string $file The filename of plugin.
|
|
|
|
* @return string The name of a plugin.
|
|
|
|
*/
|
2014-02-10 18:00:15 -05:00
|
|
|
function plugin_basename( $file ) {
|
|
|
|
global $wp_plugin_paths;
|
|
|
|
|
2016-04-30 11:09:27 -04:00
|
|
|
// $wp_plugin_paths contains normalized paths.
|
|
|
|
$file = wp_normalize_path( $file );
|
|
|
|
|
2016-07-06 05:45:27 -04:00
|
|
|
arsort( $wp_plugin_paths );
|
2014-02-10 18:00:15 -05:00
|
|
|
foreach ( $wp_plugin_paths as $dir => $realdir ) {
|
|
|
|
if ( strpos( $file, $realdir ) === 0 ) {
|
|
|
|
$file = $dir . substr( $file, strlen( $realdir ) );
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2017-11-30 18:11:00 -05:00
|
|
|
$plugin_dir = wp_normalize_path( WP_PLUGIN_DIR );
|
2014-02-10 18:00:15 -05:00
|
|
|
$mu_plugin_dir = wp_normalize_path( WPMU_PLUGIN_DIR );
|
|
|
|
|
2020-01-28 19:45:18 -05:00
|
|
|
// Get relative path from plugins directory.
|
|
|
|
$file = preg_replace( '#^' . preg_quote( $plugin_dir, '#' ) . '/|^' . preg_quote( $mu_plugin_dir, '#' ) . '/#', '', $file );
|
2017-11-30 18:11:00 -05:00
|
|
|
$file = trim( $file, '/' );
|
2010-11-24 15:25:26 -05:00
|
|
|
return $file;
|
2006-06-19 22:03:24 -04:00
|
|
|
}
|
|
|
|
|
2014-02-10 18:00:15 -05:00
|
|
|
/**
|
|
|
|
* Register a plugin's real path.
|
|
|
|
*
|
2014-04-07 17:34:14 -04:00
|
|
|
* This is used in plugin_basename() to resolve symlinked paths.
|
|
|
|
*
|
|
|
|
* @since 3.9.0
|
|
|
|
*
|
2016-07-13 15:22:28 -04:00
|
|
|
* @see wp_normalize_path()
|
2014-02-10 18:00:15 -05:00
|
|
|
*
|
2015-05-27 11:56:26 -04:00
|
|
|
* @global array $wp_plugin_paths
|
|
|
|
*
|
2014-02-10 18:00:15 -05:00
|
|
|
* @param string $file Known path to the file.
|
2014-04-07 16:15:15 -04:00
|
|
|
* @return bool Whether the path was able to be registered.
|
2014-02-10 18:00:15 -05:00
|
|
|
*/
|
|
|
|
function wp_register_plugin_realpath( $file ) {
|
|
|
|
global $wp_plugin_paths;
|
|
|
|
|
2020-01-28 19:45:18 -05:00
|
|
|
// Normalize, but store as static to avoid recalculation of a constant value.
|
2015-05-29 11:43:29 -04:00
|
|
|
static $wp_plugin_path = null, $wpmu_plugin_path = null;
|
2014-04-07 16:15:15 -04:00
|
|
|
if ( ! isset( $wp_plugin_path ) ) {
|
2017-11-30 18:11:00 -05:00
|
|
|
$wp_plugin_path = wp_normalize_path( WP_PLUGIN_DIR );
|
2014-04-07 16:15:15 -04:00
|
|
|
$wpmu_plugin_path = wp_normalize_path( WPMU_PLUGIN_DIR );
|
|
|
|
}
|
|
|
|
|
2017-11-30 18:11:00 -05:00
|
|
|
$plugin_path = wp_normalize_path( dirname( $file ) );
|
2014-02-10 18:00:15 -05:00
|
|
|
$plugin_realpath = wp_normalize_path( dirname( realpath( $file ) ) );
|
|
|
|
|
2014-04-07 16:15:15 -04:00
|
|
|
if ( $plugin_path === $wp_plugin_path || $plugin_path === $wpmu_plugin_path ) {
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
2014-02-10 18:00:15 -05:00
|
|
|
if ( $plugin_path !== $plugin_realpath ) {
|
|
|
|
$wp_plugin_paths[ $plugin_path ] = $plugin_realpath;
|
|
|
|
}
|
2014-04-07 16:15:15 -04:00
|
|
|
|
|
|
|
return true;
|
2014-02-10 18:00:15 -05:00
|
|
|
}
|
|
|
|
|
2009-03-10 15:50:55 -04:00
|
|
|
/**
|
2014-06-29 05:19:15 -04:00
|
|
|
* Get the filesystem directory path (with trailing slash) for the plugin __FILE__ passed in.
|
2014-02-25 12:14:14 -05:00
|
|
|
*
|
2013-12-24 13:57:12 -05:00
|
|
|
* @since 2.8.0
|
2009-03-10 15:50:55 -04:00
|
|
|
*
|
2014-06-29 05:19:15 -04:00
|
|
|
* @param string $file The filename of the plugin (__FILE__).
|
|
|
|
* @return string the filesystem path of the directory that contains the plugin.
|
2009-03-10 15:50:55 -04:00
|
|
|
*/
|
|
|
|
function plugin_dir_path( $file ) {
|
|
|
|
return trailingslashit( dirname( $file ) );
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
2014-06-29 05:19:15 -04:00
|
|
|
* Get the URL directory path (with trailing slash) for the plugin __FILE__ passed in.
|
2014-02-25 12:14:14 -05:00
|
|
|
*
|
2013-12-24 13:57:12 -05:00
|
|
|
* @since 2.8.0
|
2009-03-10 15:50:55 -04:00
|
|
|
*
|
2014-06-29 05:19:15 -04:00
|
|
|
* @param string $file The filename of the plugin (__FILE__).
|
|
|
|
* @return string the URL path of the directory that contains the plugin.
|
2009-03-10 15:50:55 -04:00
|
|
|
*/
|
|
|
|
function plugin_dir_url( $file ) {
|
|
|
|
return trailingslashit( plugins_url( '', $file ) );
|
|
|
|
}
|
|
|
|
|
2007-03-28 22:45:34 -04:00
|
|
|
/**
|
2008-08-07 19:39:27 -04:00
|
|
|
* Set the activation hook for a plugin.
|
2007-09-03 19:32:58 -04:00
|
|
|
*
|
2007-03-28 22:45:34 -04:00
|
|
|
* When a plugin is activated, the action 'activate_PLUGINNAME' hook is
|
2013-04-16 05:53:02 -04:00
|
|
|
* called. In the name of this hook, PLUGINNAME is replaced with the name
|
|
|
|
* of the plugin, including the optional subdirectory. For example, when the
|
|
|
|
* plugin is located in wp-content/plugins/sampleplugin/sample.php, then
|
|
|
|
* the name of this hook will become 'activate_sampleplugin/sample.php'.
|
|
|
|
*
|
|
|
|
* When the plugin consists of only one file and is (as by default) located at
|
2012-12-20 10:49:55 -05:00
|
|
|
* wp-content/plugins/sample.php the name of this hook will be
|
2007-03-28 22:45:34 -04:00
|
|
|
* 'activate_sample.php'.
|
2007-10-19 13:45:08 -04:00
|
|
|
*
|
2013-12-24 13:57:12 -05:00
|
|
|
* @since 2.0.0
|
2007-10-19 13:45:08 -04:00
|
|
|
*
|
2014-06-29 05:19:15 -04:00
|
|
|
* @param string $file The filename of the plugin including the path.
|
2015-09-25 19:58:25 -04:00
|
|
|
* @param callable $function The function hooked to the 'activate_PLUGIN' action.
|
2007-03-28 22:45:34 -04:00
|
|
|
*/
|
2017-11-30 18:11:00 -05:00
|
|
|
function register_activation_hook( $file, $function ) {
|
|
|
|
$file = plugin_basename( $file );
|
|
|
|
add_action( 'activate_' . $file, $function );
|
2006-06-19 22:03:24 -04:00
|
|
|
}
|
|
|
|
|
2007-03-28 22:45:34 -04:00
|
|
|
/**
|
2008-08-07 19:39:27 -04:00
|
|
|
* Set the deactivation hook for a plugin.
|
2007-09-03 19:32:58 -04:00
|
|
|
*
|
2007-03-28 22:45:34 -04:00
|
|
|
* When a plugin is deactivated, the action 'deactivate_PLUGINNAME' hook is
|
2013-04-16 05:53:02 -04:00
|
|
|
* called. In the name of this hook, PLUGINNAME is replaced with the name
|
2008-08-07 19:39:27 -04:00
|
|
|
* of the plugin, including the optional subdirectory. For example, when the
|
2012-12-20 10:49:55 -05:00
|
|
|
* plugin is located in wp-content/plugins/sampleplugin/sample.php, then
|
2013-04-16 05:53:02 -04:00
|
|
|
* the name of this hook will become 'deactivate_sampleplugin/sample.php'.
|
2008-08-07 19:39:27 -04:00
|
|
|
*
|
2007-09-03 19:32:58 -04:00
|
|
|
* When the plugin consists of only one file and is (as by default) located at
|
2012-12-20 10:49:55 -05:00
|
|
|
* wp-content/plugins/sample.php the name of this hook will be
|
2013-04-16 05:53:02 -04:00
|
|
|
* 'deactivate_sample.php'.
|
2007-10-19 13:45:08 -04:00
|
|
|
*
|
2013-12-24 13:57:12 -05:00
|
|
|
* @since 2.0.0
|
2007-10-19 13:45:08 -04:00
|
|
|
*
|
2014-06-29 05:19:15 -04:00
|
|
|
* @param string $file The filename of the plugin including the path.
|
2015-09-25 19:58:25 -04:00
|
|
|
* @param callable $function The function hooked to the 'deactivate_PLUGIN' action.
|
2007-03-28 22:45:34 -04:00
|
|
|
*/
|
2017-11-30 18:11:00 -05:00
|
|
|
function register_deactivation_hook( $file, $function ) {
|
|
|
|
$file = plugin_basename( $file );
|
|
|
|
add_action( 'deactivate_' . $file, $function );
|
2006-06-19 22:03:24 -04:00
|
|
|
}
|
|
|
|
|
2008-02-05 01:47:27 -05:00
|
|
|
/**
|
2008-08-07 19:39:27 -04:00
|
|
|
* Set the uninstallation hook for a plugin.
|
|
|
|
*
|
|
|
|
* Registers the uninstall hook that will be called when the user clicks on the
|
|
|
|
* uninstall link that calls for the plugin to uninstall itself. The link won't
|
|
|
|
* be active unless the plugin hooks into the action.
|
|
|
|
*
|
|
|
|
* The plugin should not run arbitrary code outside of functions, when
|
|
|
|
* registering the uninstall hook. In order to run using the hook, the plugin
|
|
|
|
* will have to be included, which means that any code laying outside of a
|
2017-08-22 07:52:48 -04:00
|
|
|
* function will be run during the uninstallation process. The plugin should not
|
|
|
|
* hinder the uninstallation process.
|
2008-08-07 19:39:27 -04:00
|
|
|
*
|
|
|
|
* If the plugin can not be written without running code within the plugin, then
|
|
|
|
* the plugin should create a file named 'uninstall.php' in the base plugin
|
2017-08-22 07:52:48 -04:00
|
|
|
* folder. This file will be called, if it exists, during the uninstallation process
|
2008-08-07 19:39:27 -04:00
|
|
|
* bypassing the uninstall hook. The plugin, when using the 'uninstall.php'
|
2008-11-11 07:43:04 -05:00
|
|
|
* should always check for the 'WP_UNINSTALL_PLUGIN' constant, before
|
2008-08-07 19:39:27 -04:00
|
|
|
* executing.
|
|
|
|
*
|
2013-12-24 13:57:12 -05:00
|
|
|
* @since 2.7.0
|
2008-08-08 00:15:03 -04:00
|
|
|
*
|
2014-06-29 05:19:15 -04:00
|
|
|
* @param string $file Plugin file.
|
2015-09-25 19:58:25 -04:00
|
|
|
* @param callable $callback The callback to run when the hook is called. Must be
|
2014-06-29 05:19:15 -04:00
|
|
|
* a static method or function.
|
2008-08-07 19:39:27 -04:00
|
|
|
*/
|
2010-11-13 04:45:57 -05:00
|
|
|
function register_uninstall_hook( $file, $callback ) {
|
|
|
|
if ( is_array( $callback ) && is_object( $callback[0] ) ) {
|
2016-07-06 08:40:29 -04:00
|
|
|
_doing_it_wrong( __FUNCTION__, __( 'Only a static class method or function can be used in an uninstall hook.' ), '3.1.0' );
|
2010-11-13 04:45:57 -05:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2014-06-29 05:19:15 -04:00
|
|
|
/*
|
|
|
|
* The option should not be autoloaded, because it is not needed in most
|
|
|
|
* cases. Emphasis should be put on using the 'uninstall.php' way of
|
|
|
|
* uninstalling the plugin.
|
|
|
|
*/
|
2019-09-26 18:08:57 -04:00
|
|
|
$uninstallable_plugins = (array) get_option( 'uninstall_plugins' );
|
|
|
|
$plugin_basename = plugin_basename( $file );
|
|
|
|
if ( ! isset( $uninstallable_plugins[ $plugin_basename ] ) || $uninstallable_plugins[ $plugin_basename ] !== $callback ) {
|
|
|
|
$uninstallable_plugins[ $plugin_basename ] = $callback;
|
|
|
|
update_option( 'uninstall_plugins', $uninstallable_plugins );
|
|
|
|
}
|
2008-08-07 19:39:27 -04:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
2014-06-29 05:19:15 -04:00
|
|
|
* Call the 'all' hook, which will process the functions hooked into it.
|
2007-12-06 00:56:38 -05:00
|
|
|
*
|
2008-08-07 19:39:27 -04:00
|
|
|
* The 'all' hook passes all of the arguments or parameters that were used for
|
|
|
|
* the hook, which this function was called for.
|
2007-12-06 00:56:38 -05:00
|
|
|
*
|
2008-08-07 19:39:27 -04:00
|
|
|
* This function is used internally for apply_filters(), do_action(), and
|
|
|
|
* do_action_ref_array() and is not meant to be used from outside those
|
|
|
|
* functions. This function does not check for the existence of the all hook, so
|
|
|
|
* it will fail unless the all hook exists prior to this function call.
|
2007-12-06 00:56:38 -05:00
|
|
|
*
|
2013-12-24 13:57:12 -05:00
|
|
|
* @since 2.5.0
|
2007-12-06 00:56:38 -05:00
|
|
|
* @access private
|
|
|
|
*
|
2019-11-29 16:42:01 -05:00
|
|
|
* @global array $wp_filter Stores all of the filters and actions.
|
2015-05-27 11:56:26 -04:00
|
|
|
*
|
2007-12-06 00:56:38 -05:00
|
|
|
* @param array $args The collected parameters from the hook that was called.
|
2008-02-05 01:47:27 -05:00
|
|
|
*/
|
2017-11-30 18:11:00 -05:00
|
|
|
function _wp_call_all_hook( $args ) {
|
2008-02-05 01:47:27 -05:00
|
|
|
global $wp_filter;
|
2007-12-06 00:56:38 -05:00
|
|
|
|
Hooks: Add the new class `WP_Hook`, and modify hook handling to make use of it.
Filters and actions have been the basis of WordPress' plugin functionality since time immemorial, they've always been a reliable method for acting upon the current state of WordPress, and will continue to be so.
Over the years, however, edge cases have cropped up. Particularly when it comes to recursively executing hooks, or a hook adding and removing itself, the existing implementation struggled to keep up with more complex use cases.
And so, we introduce `WP_Hook`. By changing `$wp_filter` from an array of arrays, to an array of objects, we reduce the complexity of the hook handling code, as the processing code (see `::apply_filters()`) only needs to be aware of itself, rather than the state of all hooks. At the same time, we're able te handle more complex use cases, as the object can more easily keep track of its own state than an array ever could.
Props jbrinley for the original architecture and design of this patch.
Props SergeyBiryukov, cheeserolls, Denis-de-Bernardy, leewillis77, wonderboymusic, nacin, jorbin, DrewAPicture, ocean90, dougwollison, khag7, pento, noplanman and aaroncampbell for their testing, suggestions, contributions, patch maintenance, cajoling and patience as we got through this.
Fixes #17817.
Built from https://develop.svn.wordpress.org/trunk@38571
git-svn-id: http://core.svn.wordpress.org/trunk@38514 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-09-07 23:55:31 -04:00
|
|
|
$wp_filter['all']->do_all_hook( $args );
|
2007-12-06 00:56:38 -05:00
|
|
|
}
|
|
|
|
|
2007-10-07 03:31:14 -04:00
|
|
|
/**
|
2008-08-07 19:39:27 -04:00
|
|
|
* Build Unique ID for storage and retrieval.
|
2007-10-19 13:45:08 -04:00
|
|
|
*
|
|
|
|
* The old way to serialize the callback caused issues and this function is the
|
2015-03-22 18:56:27 -04:00
|
|
|
* solution. It works by checking for objects and creating a new property in
|
2007-10-19 13:45:08 -04:00
|
|
|
* the class to keep track of the object and new objects of the same class that
|
|
|
|
* need to be added.
|
|
|
|
*
|
|
|
|
* It also allows for the removal of actions and filters for objects after they
|
|
|
|
* change class properties. It is possible to include the property $wp_filter_id
|
2008-08-07 19:39:27 -04:00
|
|
|
* in your class and set it to "null" or a number to bypass the workaround.
|
|
|
|
* However this will prevent you from adding new classes and any new classes
|
|
|
|
* will overwrite the previous hook by the same class.
|
2007-10-07 03:31:14 -04:00
|
|
|
*
|
2008-08-07 19:39:27 -04:00
|
|
|
* Functions and static method callbacks are just returned as strings and
|
|
|
|
* shouldn't have any speed penalty.
|
2007-10-07 03:31:14 -04:00
|
|
|
*
|
2014-09-29 09:37:16 -04:00
|
|
|
* @link https://core.trac.wordpress.org/ticket/3875
|
2007-10-07 03:31:14 -04:00
|
|
|
*
|
2014-06-29 05:19:15 -04:00
|
|
|
* @since 2.2.3
|
2019-11-29 16:42:01 -05:00
|
|
|
* @since 5.3.0 Removed workarounds for spl_object_hash().
|
|
|
|
* `$tag` and `$priority` are no longer used,
|
|
|
|
* and the function always returns a string.
|
2014-06-29 05:19:15 -04:00
|
|
|
* @access private
|
|
|
|
*
|
2019-11-29 16:42:01 -05:00
|
|
|
* @param string $tag Unused. The name of the filter to build ID for.
|
|
|
|
* @param callable $function The function to generate ID for.
|
2019-11-29 17:14:01 -05:00
|
|
|
* @param int $priority Unused. The order in which the functions
|
|
|
|
* associated with a particular action are executed.
|
|
|
|
* @return string Unique function ID for usage as array key.
|
2007-10-07 03:31:14 -04:00
|
|
|
*/
|
2017-11-30 18:11:00 -05:00
|
|
|
function _wp_filter_build_unique_id( $tag, $function, $priority ) {
|
|
|
|
if ( is_string( $function ) ) {
|
2007-08-24 10:18:08 -04:00
|
|
|
return $function;
|
2017-11-30 18:11:00 -05:00
|
|
|
}
|
2010-01-07 03:27:02 -05:00
|
|
|
|
2017-11-30 18:11:00 -05:00
|
|
|
if ( is_object( $function ) ) {
|
2019-11-29 16:42:01 -05:00
|
|
|
// Closures are currently implemented as objects.
|
2010-05-16 09:41:02 -04:00
|
|
|
$function = array( $function, '' );
|
2010-05-16 04:10:39 -04:00
|
|
|
} else {
|
|
|
|
$function = (array) $function;
|
|
|
|
}
|
2010-05-25 22:42:15 -04:00
|
|
|
|
2017-11-30 18:11:00 -05:00
|
|
|
if ( is_object( $function[0] ) ) {
|
2019-11-29 16:42:01 -05:00
|
|
|
// Object class calling.
|
2019-09-20 18:34:57 -04:00
|
|
|
return spl_object_hash( $function[0] ) . $function[1];
|
2015-01-08 02:05:25 -05:00
|
|
|
} elseif ( is_string( $function[0] ) ) {
|
2019-11-29 16:42:01 -05:00
|
|
|
// Static calling.
|
2013-05-14 11:55:21 -04:00
|
|
|
return $function[0] . '::' . $function[1];
|
2009-10-22 15:33:11 -04:00
|
|
|
}
|
2007-08-24 10:18:08 -04:00
|
|
|
}
|