REST API: Introduce baby API to the world.
Baby API was born at 2.8KLOC on October 8th at 2:30 UTC. API has lots
of growing to do, so wish it the best of luck.
Thanks to everyone who helped along the way:
Props rmccue, rachelbaker, danielbachhuber, joehoyle, drewapicture,
adamsilverstein, netweb, tlovett1, shelob9, kadamwhite, pento,
westonruter, nikv, tobych, redsweater, alecuf, pollyplummer, hurtige,
bpetty, oso96_2000, ericlewis, wonderboymusic, joshkadis, mordauk,
jdgrimes, johnbillion, jeremyfelt, thiago-negri, jdolan, pkevan,
iseulde, thenbrent, maxcutler, kwight, markoheijnen, phh, natewr,
jjeaton, shprink, mattheu, quasel, jmusal, codebykat, hubdotcom,
tapsboy, QWp6t, pushred, jaredcobb, justinsainton, japh, matrixik,
jorbin, frozzare, codfish, michael-arestad, kellbot, ironpaperweight,
simonlampen, alisspers, eliorivero, davidbhayes, JohnDittmar, dimadin,
traversal, cmmarslender, Toddses, kokarn, welcher, and ericpedia.
Fixes #33982.
Built from https://develop.svn.wordpress.org/trunk@34928
git-svn-id: http://core.svn.wordpress.org/trunk@34893 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-10-07 22:31:25 -04:00
< ? php
/**
* REST API functions .
*
* @ package WordPress
* @ subpackage REST_API
2015-11-20 02:24:30 -05:00
* @ since 4.4 . 0
REST API: Introduce baby API to the world.
Baby API was born at 2.8KLOC on October 8th at 2:30 UTC. API has lots
of growing to do, so wish it the best of luck.
Thanks to everyone who helped along the way:
Props rmccue, rachelbaker, danielbachhuber, joehoyle, drewapicture,
adamsilverstein, netweb, tlovett1, shelob9, kadamwhite, pento,
westonruter, nikv, tobych, redsweater, alecuf, pollyplummer, hurtige,
bpetty, oso96_2000, ericlewis, wonderboymusic, joshkadis, mordauk,
jdgrimes, johnbillion, jeremyfelt, thiago-negri, jdolan, pkevan,
iseulde, thenbrent, maxcutler, kwight, markoheijnen, phh, natewr,
jjeaton, shprink, mattheu, quasel, jmusal, codebykat, hubdotcom,
tapsboy, QWp6t, pushred, jaredcobb, justinsainton, japh, matrixik,
jorbin, frozzare, codfish, michael-arestad, kellbot, ironpaperweight,
simonlampen, alisspers, eliorivero, davidbhayes, JohnDittmar, dimadin,
traversal, cmmarslender, Toddses, kokarn, welcher, and ericpedia.
Fixes #33982.
Built from https://develop.svn.wordpress.org/trunk@34928
git-svn-id: http://core.svn.wordpress.org/trunk@34893 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-10-07 22:31:25 -04:00
*/
/**
* Version number for our API .
*
* @ var string
*/
define ( 'REST_API_VERSION' , '2.0' );
2015-11-20 02:24:30 -05:00
/**
* Registers a REST API route .
*
2019-01-11 13:19:49 -05:00
* Note : Do not use before the { @ see 'rest_api_init' } hook .
*
2015-11-20 02:24:30 -05:00
* @ since 4.4 . 0
2020-08-19 08:31:08 -04:00
* @ since 5.1 . 0 Added a `_doing_it_wrong()` notice when not called on or after the `rest_api_init` hook .
* @ since 5.5 . 0 Added a `_doing_it_wrong()` notice when the required `permission_callback` argument is not set .
2015-11-20 02:24:30 -05:00
*
Code Modernization: Rename parameters that use reserved keywords in `wp-includes/rest-api.php`.
While using reserved PHP keywords as parameter name labels is allowed, in the context of function calls using named parameters in PHP 8.0+, this will easily lead to confusion. To avoid that, it is recommended not to use reserved keywords as function parameter names.
This commit:
* Renames the `$namespace` parameter to `$route_namespace` in `register_rest_route()`.
* Renames the `$function` parameter to `$function_name` in:
* `rest_handle_deprecated_function()`
* `rest_handle_deprecated_argument()`
* `rest_handle_doing_it_wrong()`
* Renames the `$array` parameter to `$input_array` in `rest_validate_array_contains_unique_items()`.
Follow-up to [52946], [52996], [52997], [52998], [53003], [53014], [53029], [53039], [53116], [53117], [53137], [53174], [53184], [53185], [53192], [53193], [53198], [53203], [53207], [53215], [53216], [53220], [53230], [53232], [53236], [53239], [53240], [53242], [53243], [53245], [53246], [53257], [53269], [53270], [53271], [53272], [53273], [53274], [53275], [53276], [53277], [53281], [53283], [53284], [53285], [53287], [53364], [53365], [54927], [54929], [54930], [54931], [54932], [54933], [54938], [54943], [54944], [54945], [54946], [54947], [54948], [54950], [54951], [54952], [54956], [54959], [54960], [54961], [54962].
Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
See #56788.
Built from https://develop.svn.wordpress.org/trunk@54964
git-svn-id: http://core.svn.wordpress.org/trunk@54516 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2022-12-13 13:28:11 -05:00
* @ param string $route_namespace The first URL segment after core prefix . Should be unique to your package / plugin .
* @ param string $route The base URL for route you are adding .
* @ param array $args Optional . Either an array of options for the endpoint , or an array of arrays for
* multiple methods . Default empty array .
* @ param bool $override Optional . If the route already exists , should we override it ? True overrides ,
* false merges ( with newer overriding if duplicate keys exist ) . Default false .
2015-11-20 02:24:30 -05:00
* @ return bool True on success , false on error .
*/
Code Modernization: Rename parameters that use reserved keywords in `wp-includes/rest-api.php`.
While using reserved PHP keywords as parameter name labels is allowed, in the context of function calls using named parameters in PHP 8.0+, this will easily lead to confusion. To avoid that, it is recommended not to use reserved keywords as function parameter names.
This commit:
* Renames the `$namespace` parameter to `$route_namespace` in `register_rest_route()`.
* Renames the `$function` parameter to `$function_name` in:
* `rest_handle_deprecated_function()`
* `rest_handle_deprecated_argument()`
* `rest_handle_doing_it_wrong()`
* Renames the `$array` parameter to `$input_array` in `rest_validate_array_contains_unique_items()`.
Follow-up to [52946], [52996], [52997], [52998], [53003], [53014], [53029], [53039], [53116], [53117], [53137], [53174], [53184], [53185], [53192], [53193], [53198], [53203], [53207], [53215], [53216], [53220], [53230], [53232], [53236], [53239], [53240], [53242], [53243], [53245], [53246], [53257], [53269], [53270], [53271], [53272], [53273], [53274], [53275], [53276], [53277], [53281], [53283], [53284], [53285], [53287], [53364], [53365], [54927], [54929], [54930], [54931], [54932], [54933], [54938], [54943], [54944], [54945], [54946], [54947], [54948], [54950], [54951], [54952], [54956], [54959], [54960], [54961], [54962].
Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
See #56788.
Built from https://develop.svn.wordpress.org/trunk@54964
git-svn-id: http://core.svn.wordpress.org/trunk@54516 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2022-12-13 13:28:11 -05:00
function register_rest_route ( $route_namespace , $route , $args = array (), $override = false ) {
if ( empty ( $route_namespace ) ) {
2015-11-20 02:24:30 -05:00
/*
* Non - namespaced routes are not allowed , with the exception of the main
* and namespace indexes . If you really need to register a
* non - namespaced route , call `WP_REST_Server::register_route` directly .
*/
2024-08-25 18:51:14 -04:00
_doing_it_wrong (
__FUNCTION__ ,
sprintf (
/* translators: 1: string value of the namespace, 2: string value of the route. */
__ ( 'Routes must be namespaced with plugin or theme name and version. Instead there seems to be an empty namespace \'%1$s\' for route \'%2$s\'.' ),
'<code>' . $route_namespace . '</code>' ,
'<code>' . $route . '</code>'
),
'4.4.0'
);
2015-11-20 02:24:30 -05:00
return false ;
2017-11-30 18:11:00 -05:00
} elseif ( empty ( $route ) ) {
2024-08-25 18:51:14 -04:00
_doing_it_wrong (
__FUNCTION__ ,
sprintf (
/* translators: 1: string value of the namespace, 2: string value of the route. */
__ ( 'Route must be specified. Instead within the namespace \'%1$s\', there seems to be an empty route \'%2$s\'.' ),
'<code>' . $route_namespace . '</code>' ,
'<code>' . $route . '</code>'
),
'4.4.0'
);
2015-11-20 02:24:30 -05:00
return false ;
}
Code Modernization: Rename parameters that use reserved keywords in `wp-includes/rest-api.php`.
While using reserved PHP keywords as parameter name labels is allowed, in the context of function calls using named parameters in PHP 8.0+, this will easily lead to confusion. To avoid that, it is recommended not to use reserved keywords as function parameter names.
This commit:
* Renames the `$namespace` parameter to `$route_namespace` in `register_rest_route()`.
* Renames the `$function` parameter to `$function_name` in:
* `rest_handle_deprecated_function()`
* `rest_handle_deprecated_argument()`
* `rest_handle_doing_it_wrong()`
* Renames the `$array` parameter to `$input_array` in `rest_validate_array_contains_unique_items()`.
Follow-up to [52946], [52996], [52997], [52998], [53003], [53014], [53029], [53039], [53116], [53117], [53137], [53174], [53184], [53185], [53192], [53193], [53198], [53203], [53207], [53215], [53216], [53220], [53230], [53232], [53236], [53239], [53240], [53242], [53243], [53245], [53246], [53257], [53269], [53270], [53271], [53272], [53273], [53274], [53275], [53276], [53277], [53281], [53283], [53284], [53285], [53287], [53364], [53365], [54927], [54929], [54930], [54931], [54932], [54933], [54938], [54943], [54944], [54945], [54946], [54947], [54948], [54950], [54951], [54952], [54956], [54959], [54960], [54961], [54962].
Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
See #56788.
Built from https://develop.svn.wordpress.org/trunk@54964
git-svn-id: http://core.svn.wordpress.org/trunk@54516 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2022-12-13 13:28:11 -05:00
$clean_namespace = trim ( $route_namespace , '/' );
2020-05-22 16:48:08 -04:00
Code Modernization: Rename parameters that use reserved keywords in `wp-includes/rest-api.php`.
While using reserved PHP keywords as parameter name labels is allowed, in the context of function calls using named parameters in PHP 8.0+, this will easily lead to confusion. To avoid that, it is recommended not to use reserved keywords as function parameter names.
This commit:
* Renames the `$namespace` parameter to `$route_namespace` in `register_rest_route()`.
* Renames the `$function` parameter to `$function_name` in:
* `rest_handle_deprecated_function()`
* `rest_handle_deprecated_argument()`
* `rest_handle_doing_it_wrong()`
* Renames the `$array` parameter to `$input_array` in `rest_validate_array_contains_unique_items()`.
Follow-up to [52946], [52996], [52997], [52998], [53003], [53014], [53029], [53039], [53116], [53117], [53137], [53174], [53184], [53185], [53192], [53193], [53198], [53203], [53207], [53215], [53216], [53220], [53230], [53232], [53236], [53239], [53240], [53242], [53243], [53245], [53246], [53257], [53269], [53270], [53271], [53272], [53273], [53274], [53275], [53276], [53277], [53281], [53283], [53284], [53285], [53287], [53364], [53365], [54927], [54929], [54930], [54931], [54932], [54933], [54938], [54943], [54944], [54945], [54946], [54947], [54948], [54950], [54951], [54952], [54956], [54959], [54960], [54961], [54962].
Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
See #56788.
Built from https://develop.svn.wordpress.org/trunk@54964
git-svn-id: http://core.svn.wordpress.org/trunk@54516 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2022-12-13 13:28:11 -05:00
if ( $clean_namespace !== $route_namespace ) {
2024-08-25 18:51:14 -04:00
_doing_it_wrong (
__FUNCTION__ ,
sprintf (
/* translators: 1: string value of the namespace, 2: string value of the route. */
__ ( 'Namespace must not start or end with a slash. Instead namespace \'%1$s\' for route \'%2$s\' seems to contain a slash.' ),
'<code>' . $route_namespace . '</code>' ,
'<code>' . $route . '</code>'
),
'5.4.2'
);
2020-05-22 16:48:08 -04:00
}
2019-01-11 13:19:49 -05:00
if ( ! did_action ( 'rest_api_init' ) ) {
2019-01-26 07:29:54 -05:00
_doing_it_wrong (
2024-08-25 18:51:14 -04:00
__FUNCTION__ ,
2019-01-26 07:29:54 -05:00
sprintf (
2024-08-25 18:51:14 -04:00
/* translators: 1: rest_api_init, 2: string value of the route, 3: string value of the namespace. */
__ ( 'REST API routes must be registered on the %1$s action. Instead route \'%2$s\' with namespace \'%3$s\' was not registered on this action.' ),
'<code>rest_api_init</code>' ,
'<code>' . $route . '</code>' ,
'<code>' . $route_namespace . '</code>'
2019-01-26 07:29:54 -05:00
),
'5.1.0'
);
2019-01-11 13:19:49 -05:00
}
2017-01-26 08:39:41 -05:00
if ( isset ( $args [ 'args' ] ) ) {
$common_args = $args [ 'args' ];
unset ( $args [ 'args' ] );
} else {
$common_args = array ();
}
2015-11-20 02:24:30 -05:00
if ( isset ( $args [ 'callback' ] ) ) {
// Upgrade a single set to multiple.
$args = array ( $args );
}
$defaults = array (
2017-11-30 18:11:00 -05:00
'methods' => 'GET' ,
'callback' => null ,
'args' => array (),
2015-11-20 02:24:30 -05:00
);
2020-01-28 19:45:18 -05:00
2015-11-20 02:24:30 -05:00
foreach ( $args as $key => & $arg_group ) {
2017-01-26 08:39:41 -05:00
if ( ! is_numeric ( $key ) ) {
2015-11-20 02:24:30 -05:00
// Route option, skip here.
continue ;
}
2017-11-30 18:11:00 -05:00
$arg_group = array_merge ( $defaults , $arg_group );
2017-01-26 08:39:41 -05:00
$arg_group [ 'args' ] = array_merge ( $common_args , $arg_group [ 'args' ] );
2020-07-21 08:03:05 -04:00
if ( ! isset ( $arg_group [ 'permission_callback' ] ) ) {
_doing_it_wrong (
__FUNCTION__ ,
sprintf (
2020-08-08 21:46:07 -04:00
/* translators: 1: The REST API route being registered, 2: The argument name, 3: The suggested function name. */
2020-07-22 18:31:04 -04:00
__ ( 'The REST API route definition for %1$s is missing the required %2$s argument. For REST API routes that are intended to be public, use %3$s as the permission callback.' ),
2020-07-21 08:03:05 -04:00
'<code>' . $clean_namespace . '/' . trim ( $route , '/' ) . '</code>' ,
'<code>permission_callback</code>' ,
'<code>__return_true</code>'
),
'5.5.0'
);
}
REST API: Ensure `args` is an array of arrays in `register_rest_route()`.
When calling `register_rest_route()`, the `args` parameter for a route should be an array of arrays. However, some plugins/themes have passed an array of strings or key-value pairs which produces a PHP warning when `array_intersect_key` is used to filter the array keys based on an allowed list of schema keywords.
This change adds a check of the `args` parameter to ensure it's an array of arrays, presenting a `_doing_it_wrong` if any element of `args` is not an array and restructuring to an array of arrays. This change also adds a unit test for the incorrect usage described above, expecting that a `_doing_it_wrong` is produced.
Props slaFFik, desrosj, apermo, AndrewNZ, aristath, poena, dovyp, timothyblynjacobs, Hinjiriyo, johnmark8080, nateallen.
Fixes #51986.
Built from https://develop.svn.wordpress.org/trunk@54339
git-svn-id: http://core.svn.wordpress.org/trunk@53898 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2022-09-27 16:13:13 -04:00
2022-10-14 11:55:11 -04:00
foreach ( $arg_group [ 'args' ] as $arg ) {
if ( ! is_array ( $arg ) ) {
_doing_it_wrong (
__FUNCTION__ ,
sprintf (
/* translators: 1: $args, 2: The REST API route being registered. */
__ ( 'REST API %1$s should be an array of arrays. Non-array value detected for %2$s.' ),
'<code>$args</code>' ,
'<code>' . $clean_namespace . '/' . trim ( $route , '/' ) . '</code>'
),
'6.1.0'
);
break ; // Leave the foreach loop once a non-array argument was found.
}
REST API: Ensure `args` is an array of arrays in `register_rest_route()`.
When calling `register_rest_route()`, the `args` parameter for a route should be an array of arrays. However, some plugins/themes have passed an array of strings or key-value pairs which produces a PHP warning when `array_intersect_key` is used to filter the array keys based on an allowed list of schema keywords.
This change adds a check of the `args` parameter to ensure it's an array of arrays, presenting a `_doing_it_wrong` if any element of `args` is not an array and restructuring to an array of arrays. This change also adds a unit test for the incorrect usage described above, expecting that a `_doing_it_wrong` is produced.
Props slaFFik, desrosj, apermo, AndrewNZ, aristath, poena, dovyp, timothyblynjacobs, Hinjiriyo, johnmark8080, nateallen.
Fixes #51986.
Built from https://develop.svn.wordpress.org/trunk@54339
git-svn-id: http://core.svn.wordpress.org/trunk@53898 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2022-09-27 16:13:13 -04:00
}
2015-11-20 02:24:30 -05:00
}
2020-05-22 16:48:08 -04:00
$full_route = '/' . $clean_namespace . '/' . trim ( $route , '/' );
rest_get_server () -> register_route ( $clean_namespace , $full_route , $args , $override );
2015-11-20 02:24:30 -05:00
return true ;
}
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
/**
* Registers a new field on an existing WordPress object type .
*
* @ since 4.7 . 0
*
* @ global array $wp_rest_additional_fields Holds registered fields , organized
* by object type .
*
2021-06-30 08:34:56 -04:00
* @ param string | array $object_type Object ( s ) the field is being registered to ,
* " post " | " term " | " comment " etc .
2020-07-23 17:11:05 -04:00
* @ param string $attribute The attribute name .
* @ param array $args {
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
* Optional . An array of arguments used to handle the registered field .
*
2019-08-15 16:04:55 -04:00
* @ type callable | null $get_callback Optional . The callback function used to retrieve the field value . Default is
* 'null' , the field will not be returned in the response . The function will
* be passed the prepared object data .
* @ type callable | null $update_callback Optional . The callback function used to set and update the field value . Default
* is 'null' , the value cannot be set or updated . The function will be passed
* the model object , like WP_Post .
2020-11-16 06:04:12 -05:00
* @ type array | null $schema Optional . The schema for this field .
2019-08-15 16:04:55 -04:00
* Default is 'null' , no schema entry will be returned .
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
* }
*/
function register_rest_field ( $object_type , $attribute , $args = array () ) {
2021-06-30 08:34:56 -04:00
global $wp_rest_additional_fields ;
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
$defaults = array (
'get_callback' => null ,
'update_callback' => null ,
'schema' => null ,
);
$args = wp_parse_args ( $args , $defaults );
$object_types = ( array ) $object_type ;
foreach ( $object_types as $object_type ) {
$wp_rest_additional_fields [ $object_type ][ $attribute ] = $args ;
}
}
2015-11-20 02:24:30 -05:00
/**
2020-11-16 06:04:12 -05:00
* Registers rewrite rules for the REST API .
2015-11-20 02:24:30 -05:00
*
* @ since 4.4 . 0
*
* @ see rest_api_register_rewrites ()
* @ global WP $wp Current WordPress environment instance .
*/
function rest_api_init () {
rest_api_register_rewrites ();
global $wp ;
$wp -> add_query_var ( 'rest_route' );
}
/**
* Adds REST rewrite rules .
*
* @ since 4.4 . 0
*
* @ see add_rewrite_rule ()
2019-08-03 21:19:56 -04:00
* @ global WP_Rewrite $wp_rewrite WordPress rewrite component .
2015-11-20 02:24:30 -05:00
*/
function rest_api_register_rewrites () {
2016-10-14 15:30:29 -04:00
global $wp_rewrite ;
2017-11-30 18:11:00 -05:00
add_rewrite_rule ( '^' . rest_get_url_prefix () . '/?$' , 'index.php?rest_route=/' , 'top' );
add_rewrite_rule ( '^' . rest_get_url_prefix () . '/(.*)?' , 'index.php?rest_route=/$matches[1]' , 'top' );
add_rewrite_rule ( '^' . $wp_rewrite -> index . '/' . rest_get_url_prefix () . '/?$' , 'index.php?rest_route=/' , 'top' );
add_rewrite_rule ( '^' . $wp_rewrite -> index . '/' . rest_get_url_prefix () . '/(.*)?' , 'index.php?rest_route=/$matches[1]' , 'top' );
2015-11-20 02:24:30 -05:00
}
/**
* Registers the default REST API filters .
*
* Attached to the { @ see 'rest_api_init' } action
* to make testing and disabling these filters easier .
*
* @ since 4.4 . 0
*/
function rest_api_default_filters () {
Bootstrap/Load: Introduce functions to check whether WordPress is serving a REST API request.
This changeset introduces two functions:
* `wp_is_serving_rest_request()` returns a boolean for whether WordPress is serving an actual REST API request.
* `wp_is_rest_endpoint()` returns a boolean for whether a WordPress REST API endpoint is currently being used. While this is always the case if `wp_is_serving_rest_request()` returns `true`, the function additionally covers the scenario of internal REST API requests, i.e. where WordPress calls a REST API endpoint within the same request.
Both functions should only be used after the `parse_request` action.
All relevant manual checks have been adjusted to use one of the new functions, depending on the use-case. They were all using the same constant check so far, while in fact some of them were intending to check for an actual REST API request while others were intending to check for REST endpoint usage.
A new filter `wp_is_rest_endpoint` can be used to alter the return value of the `wp_is_rest_endpoint()` function.
Props lots.0.logs, TimothyBlynJacobs, flixos90, joehoyle, peterwilsoncc, swissspidy, SergeyBiryukov, pento, mikejolley, iandunn, hellofromTonya, Cybr, petitphp.
Fixes #42061.
Built from https://develop.svn.wordpress.org/trunk@57312
git-svn-id: http://core.svn.wordpress.org/trunk@56818 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2024-01-19 12:40:09 -05:00
if ( wp_is_serving_rest_request () ) {
2020-06-23 19:04:07 -04:00
// Deprecated reporting.
add_action ( 'deprecated_function_run' , 'rest_handle_deprecated_function' , 10 , 3 );
add_filter ( 'deprecated_function_trigger_error' , '__return_false' );
add_action ( 'deprecated_argument_run' , 'rest_handle_deprecated_argument' , 10 , 3 );
add_filter ( 'deprecated_argument_trigger_error' , '__return_false' );
2020-07-07 01:01:07 -04:00
add_action ( 'doing_it_wrong_run' , 'rest_handle_doing_it_wrong' , 10 , 3 );
add_filter ( 'doing_it_wrong_trigger_error' , '__return_false' );
2020-06-23 19:04:07 -04:00
}
2015-11-20 02:24:30 -05:00
// Default serving.
add_filter ( 'rest_pre_serve_request' , 'rest_send_cors_headers' );
add_filter ( 'rest_post_dispatch' , 'rest_send_allow_header' , 10 , 3 );
2017-10-04 14:46:38 -04:00
add_filter ( 'rest_post_dispatch' , 'rest_filter_response_fields' , 10 , 3 );
2015-11-20 02:24:30 -05:00
add_filter ( 'rest_pre_dispatch' , 'rest_handle_options_request' , 10 , 3 );
REST API: Introduce Application Passwords for API authentication.
In WordPress 4.4 the REST API was first introduced. A few releases later in WordPress 4.7, the Content API endpoints were added, paving the way for Gutenberg and countless in-site experiences. In the intervening years, numerous plugins have built on top of the REST API. Many developers shared a common frustration, the lack of external authentication to the REST API.
This commit introduces Application Passwords to allow users to connect to external applications to their WordPress website. Users can generate individual passwords for each application, allowing for easy revocation and activity monitoring. An authorization flow is introduced to make the connection flow simple for users and application developers.
Application Passwords uses Basic Authentication, and by default is only available over an SSL connection.
Props georgestephanis, kasparsd, timothyblynjacobs, afercia, akkspro, andraganescu, arippberger, aristath, austyfrosty, ayesh, batmoo, bradyvercher, brianhenryie, helen, ipstenu, jeffmatson, jeffpaul, joostdevalk, joshlevinson, kadamwhite, kjbenk, koke, michael-arestad, Otto42, pekz0r, salzano, spacedmonkey, valendesigns.
Fixes #42790.
Built from https://develop.svn.wordpress.org/trunk@49109
git-svn-id: http://core.svn.wordpress.org/trunk@48871 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-10-08 18:14:06 -04:00
add_filter ( 'rest_index' , 'rest_add_application_passwords_to_index' );
2015-11-20 02:24:30 -05:00
}
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
/**
* Registers default REST API routes .
*
* @ since 4.7 . 0
*/
function create_initial_rest_routes () {
foreach ( get_post_types ( array ( 'show_in_rest' => true ), 'objects' ) as $post_type ) {
2019-09-23 16:25:57 -04:00
$controller = $post_type -> get_rest_controller ();
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
2019-09-23 16:25:57 -04:00
if ( ! $controller ) {
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
continue ;
}
REST API: Fix issue with Template and Template Part Revision/Autosave REST API controllers.
The Template and Template Part REST API controllers have unique characteristics compared to other post type REST API controllers. They do not rely on integer IDs to reference objects; instead, they use a combination of the theme name and slug of the template, like 'twentytwentyfour//home.' Consequently, when the post types template and template part were introduced in [52062], it led to the registration of REST API endpoints for autosaves and revisions with invalid URL structures.
In this commit, we introduce new functionality to enable custom autosave and revisions endpoints to be registered at the post type level. Similar to the 'rest_controller_class' parameter, developers can now define 'revisions_rest_controller' and 'autosave_rest_controller.' This empowers developers to create custom controllers for these functionalities. Additionally, we introduce a 'late_route_registration' parameter, which proves helpful when dealing with custom URL patterns and regex pattern matching issues.
This commit registers new classes for template and template part autosave and revisions controllers, differentiating them from standard controllers in the following ways:
* The response shape now matches that of the template controller.
* Permission checks align with the template controller.
* A custom URL pattern is introduced to support slug-based identification of templates.
Furthermore, we've updated the utility function '_build_block_template_result_from_post' to support passing revision post objects. This enhancement ensures compatibility with the custom revisions controller.
Props spacedmonkey, revgeorge, andraganescu, hellofromTonya, antonvlasenko, kadamwhite, ironprogrammer, costdev, mukesh27, timothyblynjacobs, adamsilverstein.
Fixes 56922.
Built from https://develop.svn.wordpress.org/trunk@56819
git-svn-id: http://core.svn.wordpress.org/trunk@56331 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2023-10-10 10:05:21 -04:00
if ( ! $post_type -> late_route_registration ) {
$controller -> register_routes ();
}
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
REST API: Fix issue with Template and Template Part Revision/Autosave REST API controllers.
The Template and Template Part REST API controllers have unique characteristics compared to other post type REST API controllers. They do not rely on integer IDs to reference objects; instead, they use a combination of the theme name and slug of the template, like 'twentytwentyfour//home.' Consequently, when the post types template and template part were introduced in [52062], it led to the registration of REST API endpoints for autosaves and revisions with invalid URL structures.
In this commit, we introduce new functionality to enable custom autosave and revisions endpoints to be registered at the post type level. Similar to the 'rest_controller_class' parameter, developers can now define 'revisions_rest_controller' and 'autosave_rest_controller.' This empowers developers to create custom controllers for these functionalities. Additionally, we introduce a 'late_route_registration' parameter, which proves helpful when dealing with custom URL patterns and regex pattern matching issues.
This commit registers new classes for template and template part autosave and revisions controllers, differentiating them from standard controllers in the following ways:
* The response shape now matches that of the template controller.
* Permission checks align with the template controller.
* A custom URL pattern is introduced to support slug-based identification of templates.
Furthermore, we've updated the utility function '_build_block_template_result_from_post' to support passing revision post objects. This enhancement ensures compatibility with the custom revisions controller.
Props spacedmonkey, revgeorge, andraganescu, hellofromTonya, antonvlasenko, kadamwhite, ironprogrammer, costdev, mukesh27, timothyblynjacobs, adamsilverstein.
Fixes 56922.
Built from https://develop.svn.wordpress.org/trunk@56819
git-svn-id: http://core.svn.wordpress.org/trunk@56331 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2023-10-10 10:05:21 -04:00
$revisions_controller = $post_type -> get_revisions_rest_controller ();
if ( $revisions_controller ) {
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
$revisions_controller -> register_routes ();
}
REST API: Introduce Autosaves controller and endpoint.
- Adds `WP_REST_Autosaves_Controller` which extends `WP_REST_Revisions_Controller`.
- Autosaves endpoint is registered for all post types except attachment because even post types without revisions enabled are expected to autosave.
- Because setting the `DOING_AUTOSAVE` constant pollutes the test suite, autosaves tests are run last. We may want to improve upon this later.
Also, use a truly impossibly high number in User Controller tests. The number `100`, (or `7777` in `trunk`), could be valid in certain test run configurations. The `REST_TESTS_IMPOSSIBLY_HIGH_NUMBER` constant is impossibly high for this very reason.
Finally, Skip Autosaves controller test for multisite. There's a PHP 5.2 edge case where paths calculated differently, possibly caused by differing version of PHPUnit.
Props adamsilverstein, aduth, azaozz, danielbachhuber, rmccue, danielbachhuber.
Merges [43767], [43768], [43769] to trunk.
See #45132, #45131.
Fixes #45128, #43316.
Built from https://develop.svn.wordpress.org/trunk@44126
git-svn-id: http://core.svn.wordpress.org/trunk@43956 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2018-12-13 17:42:38 -05:00
REST API: Fix issue with Template and Template Part Revision/Autosave REST API controllers.
The Template and Template Part REST API controllers have unique characteristics compared to other post type REST API controllers. They do not rely on integer IDs to reference objects; instead, they use a combination of the theme name and slug of the template, like 'twentytwentyfour//home.' Consequently, when the post types template and template part were introduced in [52062], it led to the registration of REST API endpoints for autosaves and revisions with invalid URL structures.
In this commit, we introduce new functionality to enable custom autosave and revisions endpoints to be registered at the post type level. Similar to the 'rest_controller_class' parameter, developers can now define 'revisions_rest_controller' and 'autosave_rest_controller.' This empowers developers to create custom controllers for these functionalities. Additionally, we introduce a 'late_route_registration' parameter, which proves helpful when dealing with custom URL patterns and regex pattern matching issues.
This commit registers new classes for template and template part autosave and revisions controllers, differentiating them from standard controllers in the following ways:
* The response shape now matches that of the template controller.
* Permission checks align with the template controller.
* A custom URL pattern is introduced to support slug-based identification of templates.
Furthermore, we've updated the utility function '_build_block_template_result_from_post' to support passing revision post objects. This enhancement ensures compatibility with the custom revisions controller.
Props spacedmonkey, revgeorge, andraganescu, hellofromTonya, antonvlasenko, kadamwhite, ironprogrammer, costdev, mukesh27, timothyblynjacobs, adamsilverstein.
Fixes 56922.
Built from https://develop.svn.wordpress.org/trunk@56819
git-svn-id: http://core.svn.wordpress.org/trunk@56331 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2023-10-10 10:05:21 -04:00
$autosaves_controller = $post_type -> get_autosave_rest_controller ();
if ( $autosaves_controller ) {
REST API: Introduce Autosaves controller and endpoint.
- Adds `WP_REST_Autosaves_Controller` which extends `WP_REST_Revisions_Controller`.
- Autosaves endpoint is registered for all post types except attachment because even post types without revisions enabled are expected to autosave.
- Because setting the `DOING_AUTOSAVE` constant pollutes the test suite, autosaves tests are run last. We may want to improve upon this later.
Also, use a truly impossibly high number in User Controller tests. The number `100`, (or `7777` in `trunk`), could be valid in certain test run configurations. The `REST_TESTS_IMPOSSIBLY_HIGH_NUMBER` constant is impossibly high for this very reason.
Finally, Skip Autosaves controller test for multisite. There's a PHP 5.2 edge case where paths calculated differently, possibly caused by differing version of PHPUnit.
Props adamsilverstein, aduth, azaozz, danielbachhuber, rmccue, danielbachhuber.
Merges [43767], [43768], [43769] to trunk.
See #45132, #45131.
Fixes #45128, #43316.
Built from https://develop.svn.wordpress.org/trunk@44126
git-svn-id: http://core.svn.wordpress.org/trunk@43956 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2018-12-13 17:42:38 -05:00
$autosaves_controller -> register_routes ();
}
REST API: Fix issue with Template and Template Part Revision/Autosave REST API controllers.
The Template and Template Part REST API controllers have unique characteristics compared to other post type REST API controllers. They do not rely on integer IDs to reference objects; instead, they use a combination of the theme name and slug of the template, like 'twentytwentyfour//home.' Consequently, when the post types template and template part were introduced in [52062], it led to the registration of REST API endpoints for autosaves and revisions with invalid URL structures.
In this commit, we introduce new functionality to enable custom autosave and revisions endpoints to be registered at the post type level. Similar to the 'rest_controller_class' parameter, developers can now define 'revisions_rest_controller' and 'autosave_rest_controller.' This empowers developers to create custom controllers for these functionalities. Additionally, we introduce a 'late_route_registration' parameter, which proves helpful when dealing with custom URL patterns and regex pattern matching issues.
This commit registers new classes for template and template part autosave and revisions controllers, differentiating them from standard controllers in the following ways:
* The response shape now matches that of the template controller.
* Permission checks align with the template controller.
* A custom URL pattern is introduced to support slug-based identification of templates.
Furthermore, we've updated the utility function '_build_block_template_result_from_post' to support passing revision post objects. This enhancement ensures compatibility with the custom revisions controller.
Props spacedmonkey, revgeorge, andraganescu, hellofromTonya, antonvlasenko, kadamwhite, ironprogrammer, costdev, mukesh27, timothyblynjacobs, adamsilverstein.
Fixes 56922.
Built from https://develop.svn.wordpress.org/trunk@56819
git-svn-id: http://core.svn.wordpress.org/trunk@56331 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2023-10-10 10:05:21 -04:00
if ( $post_type -> late_route_registration ) {
$controller -> register_routes ();
}
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
}
// Post types.
2022-11-29 10:51:14 -05:00
$controller = new WP_REST_Post_Types_Controller ();
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
$controller -> register_routes ();
// Post statuses.
2022-11-29 10:51:14 -05:00
$controller = new WP_REST_Post_Statuses_Controller ();
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
$controller -> register_routes ();
// Taxonomies.
2022-11-29 10:51:14 -05:00
$controller = new WP_REST_Taxonomies_Controller ();
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
$controller -> register_routes ();
// Terms.
foreach ( get_taxonomies ( array ( 'show_in_rest' => true ), 'object' ) as $taxonomy ) {
2020-07-02 01:57:01 -04:00
$controller = $taxonomy -> get_rest_controller ();
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
2020-07-02 01:57:01 -04:00
if ( ! $controller ) {
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
continue ;
}
$controller -> register_routes ();
}
// Users.
2022-11-29 10:51:14 -05:00
$controller = new WP_REST_Users_Controller ();
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
$controller -> register_routes ();
REST API: Introduce Application Passwords for API authentication.
In WordPress 4.4 the REST API was first introduced. A few releases later in WordPress 4.7, the Content API endpoints were added, paving the way for Gutenberg and countless in-site experiences. In the intervening years, numerous plugins have built on top of the REST API. Many developers shared a common frustration, the lack of external authentication to the REST API.
This commit introduces Application Passwords to allow users to connect to external applications to their WordPress website. Users can generate individual passwords for each application, allowing for easy revocation and activity monitoring. An authorization flow is introduced to make the connection flow simple for users and application developers.
Application Passwords uses Basic Authentication, and by default is only available over an SSL connection.
Props georgestephanis, kasparsd, timothyblynjacobs, afercia, akkspro, andraganescu, arippberger, aristath, austyfrosty, ayesh, batmoo, bradyvercher, brianhenryie, helen, ipstenu, jeffmatson, jeffpaul, joostdevalk, joshlevinson, kadamwhite, kjbenk, koke, michael-arestad, Otto42, pekz0r, salzano, spacedmonkey, valendesigns.
Fixes #42790.
Built from https://develop.svn.wordpress.org/trunk@49109
git-svn-id: http://core.svn.wordpress.org/trunk@48871 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-10-08 18:14:06 -04:00
// Application Passwords
$controller = new WP_REST_Application_Passwords_Controller ();
$controller -> register_routes ();
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
// Comments.
2022-11-29 10:51:14 -05:00
$controller = new WP_REST_Comments_Controller ();
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
$controller -> register_routes ();
2020-10-07 21:32:05 -04:00
$search_handlers = array (
new WP_REST_Post_Search_Handler (),
new WP_REST_Term_Search_Handler (),
2020-10-12 15:54:05 -04:00
new WP_REST_Post_Format_Search_Handler (),
2020-10-07 21:32:05 -04:00
);
2018-12-13 04:38:25 -05:00
/**
* Filters the search handlers to use in the REST search controller .
*
* @ since 5.0 . 0
*
* @ param array $search_handlers List of search handlers to use in the controller . Each search
* handler instance must extend the `WP_REST_Search_Handler` class .
* Default is only a handler for posts .
*/
2020-10-07 21:32:05 -04:00
$search_handlers = apply_filters ( 'wp_rest_search_handlers' , $search_handlers );
2018-12-13 04:38:25 -05:00
$controller = new WP_REST_Search_Controller ( $search_handlers );
$controller -> register_routes ();
2018-12-13 21:35:38 -05:00
// Block Renderer.
2021-11-10 14:56:00 -05:00
$controller = new WP_REST_Block_Renderer_Controller ();
2018-12-13 21:35:38 -05:00
$controller -> register_routes ();
2020-06-25 20:46:07 -04:00
// Block Types.
$controller = new WP_REST_Block_Types_Controller ();
$controller -> register_routes ();
2021-11-08 16:00:07 -05:00
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
// Settings.
2022-11-29 10:51:14 -05:00
$controller = new WP_REST_Settings_Controller ();
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
$controller -> register_routes ();
2018-12-11 22:33:24 -05:00
// Themes.
2022-11-29 10:51:14 -05:00
$controller = new WP_REST_Themes_Controller ();
2018-12-11 22:33:24 -05:00
$controller -> register_routes ();
2018-12-13 21:35:38 -05:00
REST API: Introduce plugin management and block directory endpoints.
These endpoints facilitate the Block Directory Inserter feature in Gutenberg. Users can now install, activate, deactivate, and delete plugins over the REST API. The block directoryendpoint allows searching for available blocks from the WordPress.org block directory.
Props cklee, talldanwp, noisysocks, joen, soean, youknowriad, dufresnesteven, gziolo, dd32, tellyworth, ryelle, spacedmonkey, TimothyBlynJacobs.
Fixes #50321.
Built from https://develop.svn.wordpress.org/trunk@48242
git-svn-id: http://core.svn.wordpress.org/trunk@48011 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-07-01 00:24:03 -04:00
// Plugins.
$controller = new WP_REST_Plugins_Controller ();
$controller -> register_routes ();
2021-05-25 04:27:57 -04:00
// Sidebars.
$controller = new WP_REST_Sidebars_Controller ();
$controller -> register_routes ();
// Widget Types.
$controller = new WP_REST_Widget_Types_Controller ();
$controller -> register_routes ();
// Widgets.
$controller = new WP_REST_Widgets_Controller ();
$controller -> register_routes ();
REST API: Introduce plugin management and block directory endpoints.
These endpoints facilitate the Block Directory Inserter feature in Gutenberg. Users can now install, activate, deactivate, and delete plugins over the REST API. The block directoryendpoint allows searching for available blocks from the WordPress.org block directory.
Props cklee, talldanwp, noisysocks, joen, soean, youknowriad, dufresnesteven, gziolo, dd32, tellyworth, ryelle, spacedmonkey, TimothyBlynJacobs.
Fixes #50321.
Built from https://develop.svn.wordpress.org/trunk@48242
git-svn-id: http://core.svn.wordpress.org/trunk@48011 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-07-01 00:24:03 -04:00
// Block Directory.
$controller = new WP_REST_Block_Directory_Controller ();
$controller -> register_routes ();
2020-10-14 22:00:08 -04:00
2021-05-25 21:11:59 -04:00
// Pattern Directory.
$controller = new WP_REST_Pattern_Directory_Controller ();
$controller -> register_routes ();
2022-04-12 05:26:16 -04:00
// Block Patterns.
$controller = new WP_REST_Block_Patterns_Controller ();
$controller -> register_routes ();
// Block Pattern Categories.
$controller = new WP_REST_Block_Pattern_Categories_Controller ();
$controller -> register_routes ();
2020-11-16 11:48:12 -05:00
// Site Health.
2020-10-14 22:00:08 -04:00
$site_health = WP_Site_Health :: get_instance ();
2020-10-20 09:29:08 -04:00
$controller = new WP_REST_Site_Health_Controller ( $site_health );
2020-10-14 22:00:08 -04:00
$controller -> register_routes ();
REST API: Add URL Details endpoint.
Adds a new REST API endpoint (`/wp-block-editor/v1/url-details`) for retrieving information from an external URL.
Information retrieved:
* Title: content of the `<title>` element
* Icon: favicon image link
* Description: content of the `description` or `og:description` meta element
* Image: OG image link
This endpoint is used by the block editor for link previews.
Props get_dave, aduth, andraganescu, beaulebens, hellofromTonya, kevin940726, mamaduka, marekhrabe, mnelson4, noisysocks, obenland, ocean90, retrofox, shaunandrews, spacedmonkey, swissspidy, timothyblynjacobs, xknown, youknowriad.
Fixes #54358.
Built from https://develop.svn.wordpress.org/trunk@51973
git-svn-id: http://core.svn.wordpress.org/trunk@51562 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2021-11-02 08:48:00 -04:00
// URL Details.
$controller = new WP_REST_URL_Details_Controller ();
$controller -> register_routes ();
REST API: Introduce Menu management endpoints.
This commit introduces the `/wp/v2/menus`, `/wp/v2/menu-items` and `/wp/v2/menu-locations` REST API endpoints. These endpoints are fully available to users with the `edit_theme_options` capability, but can be read by any user who can edit a REST API available post type.
The `nav_menu` taxonomy and `nav_menu_item` post type now map their capabilities to the `edit_theme_options` primitive capability. This allows developers to provide more fine-grained access control. However, if a developer is currently dynamically removing the `edit_theme_options` capability using `map_meta_cap`, they should use the `user_has_cap` filter instead.
The `wp_update_nav_menu_item()` function has been adjusted to return an error if saving the menu item post or assigning the menu item to a menu generate an error.
Lastly, a new menu item type is introduced, `block`, that can be used to store a Block as a menu item.
Props andraganescu, antonvlasenko, dingo_d, dlh, isabel_brison, kadamwhite, Mamaduka, NateWr, noisysocks, peterwilsoncc, ryelle, schlessera, soean, Spacedmonkey, talldanwp, TimothyBlynJacobs, tobifjellner, westonruter, wpscholar, zieladam.
Fixes #40878.
Built from https://develop.svn.wordpress.org/trunk@52079
git-svn-id: http://core.svn.wordpress.org/trunk@51671 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2021-11-09 14:00:01 -05:00
// Menu Locations.
$controller = new WP_REST_Menu_Locations_Controller ();
$controller -> register_routes ();
2021-11-30 12:32:02 -05:00
// Site Editor Export.
$controller = new WP_REST_Edit_Site_Export_Controller ();
$controller -> register_routes ();
2023-06-27 01:54:19 -04:00
// Navigation Fallback.
$controller = new WP_REST_Navigation_Fallback_Controller ();
$controller -> register_routes ();
2024-02-07 04:20:08 -05:00
// Font Collections.
$font_collections_controller = new WP_REST_Font_Collections_Controller ();
$font_collections_controller -> register_routes ();
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
}
2015-11-20 02:24:30 -05:00
/**
* Loads the REST API .
*
* @ since 4.4 . 0
*
2019-08-03 21:28:55 -04:00
* @ global WP $wp Current WordPress environment instance .
2015-11-20 02:24:30 -05:00
*/
function rest_api_loaded () {
if ( empty ( $GLOBALS [ 'wp' ] -> query_vars [ 'rest_route' ] ) ) {
return ;
}
/**
* Whether this is a REST Request .
*
* @ since 4.4 . 0
* @ var bool
*/
define ( 'REST_REQUEST' , true );
2016-02-15 20:12:26 -05:00
// Initialize the server.
$server = rest_get_server ();
2015-11-20 02:24:30 -05:00
// Fire off the request.
2017-01-17 00:40:40 -05:00
$route = untrailingslashit ( $GLOBALS [ 'wp' ] -> query_vars [ 'rest_route' ] );
if ( empty ( $route ) ) {
$route = '/' ;
}
$server -> serve_request ( $route );
2015-11-20 02:24:30 -05:00
// We're done.
die ();
}
/**
* Retrieves the URL prefix for any API resource .
*
* @ since 4.4 . 0
*
* @ return string Prefix .
*/
function rest_get_url_prefix () {
/**
2016-05-22 14:50:28 -04:00
* Filters the REST URL prefix .
2015-11-20 02:24:30 -05:00
*
* @ since 4.4 . 0
*
* @ param string $prefix URL prefix . Default 'wp-json' .
*/
return apply_filters ( 'rest_url_prefix' , 'wp-json' );
}
/**
* Retrieves the URL to a REST endpoint on a site .
*
* Note : The returned URL is NOT escaped .
*
* @ since 4.4 . 0
*
* @ todo Check if this is even necessary
2019-08-03 21:19:56 -04:00
* @ global WP_Rewrite $wp_rewrite WordPress rewrite component .
2015-11-20 02:24:30 -05:00
*
2021-02-13 10:16:08 -05:00
* @ param int | null $blog_id Optional . Blog ID . Default of null returns URL for current blog .
* @ param string $path Optional . REST route . Default '/' .
* @ param string $scheme Optional . Sanitization scheme . Default 'rest' .
2015-11-20 02:24:30 -05:00
* @ return string Full URL to the endpoint .
*/
function get_rest_url ( $blog_id = null , $path = '/' , $scheme = 'rest' ) {
if ( empty ( $path ) ) {
$path = '/' ;
}
2017-11-28 02:10:46 -05:00
$path = '/' . ltrim ( $path , '/' );
2015-11-20 02:24:30 -05:00
if ( is_multisite () && get_blog_option ( $blog_id , 'permalink_structure' ) || get_option ( 'permalink_structure' ) ) {
2016-10-14 15:30:29 -04:00
global $wp_rewrite ;
if ( $wp_rewrite -> using_index_permalinks () ) {
$url = get_home_url ( $blog_id , $wp_rewrite -> index . '/' . rest_get_url_prefix (), $scheme );
} else {
$url = get_home_url ( $blog_id , rest_get_url_prefix (), $scheme );
}
2017-11-28 02:10:46 -05:00
$url .= $path ;
2015-11-20 02:24:30 -05:00
} else {
$url = trailingslashit ( get_home_url ( $blog_id , '' , $scheme ) );
2023-07-10 18:48:22 -04:00
/*
* nginx only allows HTTP / 1.0 methods when redirecting from / to / index . php .
* To work around this , we manually add index . php to the URL , avoiding the redirect .
*/
2023-06-24 05:52:19 -04:00
if ( ! str_ends_with ( $url , 'index.php' ) ) {
2017-07-24 20:50:43 -04:00
$url .= 'index.php' ;
}
2015-11-20 02:24:30 -05:00
$url = add_query_arg ( 'rest_route' , $path , $url );
}
2019-08-08 16:20:55 -04:00
if ( is_ssl () && isset ( $_SERVER [ 'SERVER_NAME' ] ) ) {
2015-11-20 02:24:30 -05:00
// If the current host is the same as the REST URL host, force the REST URL scheme to HTTPS.
2020-02-09 11:55:09 -05:00
if ( parse_url ( get_home_url ( $blog_id ), PHP_URL_HOST ) === $_SERVER [ 'SERVER_NAME' ] ) {
2015-11-20 02:24:30 -05:00
$url = set_url_scheme ( $url , 'https' );
}
}
2017-05-25 14:02:41 -04:00
if ( is_admin () && force_ssl_admin () ) {
2020-01-28 19:45:18 -05:00
/*
* In this situation the home URL may be http : , and `is_ssl()` may be false ,
* but the admin is served over https : ( one way or another ), so REST API usage
* will be blocked by browsers unless it is also served over HTTPS .
*/
2017-05-25 14:02:41 -04:00
$url = set_url_scheme ( $url , 'https' );
}
2015-11-20 02:24:30 -05:00
/**
2016-05-22 14:50:28 -04:00
* Filters the REST URL .
2015-11-20 02:24:30 -05:00
*
2016-05-23 15:02:28 -04:00
* Use this filter to adjust the url returned by the get_rest_url () function .
2015-11-20 02:24:30 -05:00
*
* @ since 4.4 . 0
*
2021-02-13 10:16:08 -05:00
* @ param string $url REST URL .
* @ param string $path REST route .
* @ param int | null $blog_id Blog ID .
* @ param string $scheme Sanitization scheme .
2015-11-20 02:24:30 -05:00
*/
return apply_filters ( 'rest_url' , $url , $path , $blog_id , $scheme );
}
/**
* Retrieves the URL to a REST endpoint .
*
* Note : The returned URL is NOT escaped .
*
* @ since 4.4 . 0
*
* @ param string $path Optional . REST route . Default empty .
2019-09-22 15:15:57 -04:00
* @ param string $scheme Optional . Sanitization scheme . Default 'rest' .
2015-11-20 02:24:30 -05:00
* @ return string Full URL to the endpoint .
*/
2019-09-22 15:15:57 -04:00
function rest_url ( $path = '' , $scheme = 'rest' ) {
2015-11-20 02:24:30 -05:00
return get_rest_url ( null , $path , $scheme );
}
/**
* Do a REST request .
*
* Used primarily to route internal requests through WP_REST_Server .
*
* @ since 4.4 . 0
*
* @ param WP_REST_Request | string $request Request .
* @ return WP_REST_Response REST response .
*/
function rest_do_request ( $request ) {
$request = rest_ensure_request ( $request );
2016-02-15 20:12:26 -05:00
return rest_get_server () -> dispatch ( $request );
}
/**
2016-03-10 13:49:26 -05:00
* Retrieves the current REST server instance .
2016-02-15 20:12:26 -05:00
*
* Instantiates a new instance if none exists already .
*
* @ since 4.5 . 0
*
* @ global WP_REST_Server $wp_rest_server REST server instance .
*
2016-03-10 13:49:26 -05:00
* @ return WP_REST_Server REST server instance .
2016-02-15 20:12:26 -05:00
*/
function rest_get_server () {
/* @var WP_REST_Server $wp_rest_server */
global $wp_rest_server ;
if ( empty ( $wp_rest_server ) ) {
/**
2016-05-22 14:50:28 -04:00
* Filters the REST Server Class .
2016-02-15 20:12:26 -05:00
*
2020-11-16 06:04:12 -05:00
* This filter allows you to adjust the server class used by the REST API , using a
2016-02-15 20:12:26 -05:00
* different class to handle requests .
*
* @ since 4.4 . 0
*
* @ param string $class_name The name of the server class . Default 'WP_REST_Server' .
*/
$wp_rest_server_class = apply_filters ( 'wp_rest_server_class' , 'WP_REST_Server' );
2022-11-29 10:51:14 -05:00
$wp_rest_server = new $wp_rest_server_class ();
2016-02-15 20:12:26 -05:00
/**
2020-11-16 06:04:12 -05:00
* Fires when preparing to serve a REST API request .
2016-02-15 20:12:26 -05:00
*
* Endpoint objects should be created and register their hooks on this action rather
* than another action to ensure they ' re only loaded when needed .
*
* @ since 4.4 . 0
*
* @ param WP_REST_Server $wp_rest_server Server object .
*/
do_action ( 'rest_api_init' , $wp_rest_server );
}
return $wp_rest_server ;
2015-11-20 02:24:30 -05:00
}
/**
* Ensures request arguments are a request object ( for consistency ) .
*
* @ since 4.4 . 0
2019-09-12 17:47:57 -04:00
* @ since 5.3 . 0 Accept string argument for the request path .
2015-11-20 02:24:30 -05:00
*
2019-09-12 17:47:57 -04:00
* @ param array | string | WP_REST_Request $request Request to check .
2015-11-20 02:24:30 -05:00
* @ return WP_REST_Request REST request instance .
*/
function rest_ensure_request ( $request ) {
if ( $request instanceof WP_REST_Request ) {
return $request ;
}
2019-09-12 17:47:57 -04:00
if ( is_string ( $request ) ) {
return new WP_REST_Request ( 'GET' , $request );
}
2015-11-20 02:24:30 -05:00
return new WP_REST_Request ( 'GET' , '' , $request );
}
/**
* Ensures a REST response is a response object ( for consistency ) .
*
2020-05-23 10:36:09 -04:00
* This implements WP_REST_Response , allowing usage of `set_status` / `header` / etc
2015-11-20 02:24:30 -05:00
* without needing to double - check the object . Will also allow WP_Error to indicate error
* responses , so users should immediately check for this value .
*
* @ since 4.4 . 0
*
2020-05-23 10:36:09 -04:00
* @ param WP_REST_Response | WP_Error | WP_HTTP_Response | mixed $response Response to check .
* @ return WP_REST_Response | WP_Error If response generated an error , WP_Error , if response
* is already an instance , WP_REST_Response , otherwise
* returns a new WP_REST_Response instance .
2015-11-20 02:24:30 -05:00
*/
function rest_ensure_response ( $response ) {
if ( is_wp_error ( $response ) ) {
return $response ;
}
2020-05-23 10:36:09 -04:00
if ( $response instanceof WP_REST_Response ) {
2015-11-20 02:24:30 -05:00
return $response ;
}
2023-07-10 18:48:22 -04:00
/*
* While WP_HTTP_Response is the base class of WP_REST_Response , it doesn ' t provide
* all the required methods used in WP_REST_Server :: dispatch () .
*/
2020-05-23 10:36:09 -04:00
if ( $response instanceof WP_HTTP_Response ) {
return new WP_REST_Response (
$response -> get_data (),
$response -> get_status (),
$response -> get_headers ()
);
}
2015-11-20 02:24:30 -05:00
return new WP_REST_Response ( $response );
}
/**
* Handles _deprecated_function () errors .
*
* @ since 4.4 . 0
*
Code Modernization: Rename parameters that use reserved keywords in `wp-includes/rest-api.php`.
While using reserved PHP keywords as parameter name labels is allowed, in the context of function calls using named parameters in PHP 8.0+, this will easily lead to confusion. To avoid that, it is recommended not to use reserved keywords as function parameter names.
This commit:
* Renames the `$namespace` parameter to `$route_namespace` in `register_rest_route()`.
* Renames the `$function` parameter to `$function_name` in:
* `rest_handle_deprecated_function()`
* `rest_handle_deprecated_argument()`
* `rest_handle_doing_it_wrong()`
* Renames the `$array` parameter to `$input_array` in `rest_validate_array_contains_unique_items()`.
Follow-up to [52946], [52996], [52997], [52998], [53003], [53014], [53029], [53039], [53116], [53117], [53137], [53174], [53184], [53185], [53192], [53193], [53198], [53203], [53207], [53215], [53216], [53220], [53230], [53232], [53236], [53239], [53240], [53242], [53243], [53245], [53246], [53257], [53269], [53270], [53271], [53272], [53273], [53274], [53275], [53276], [53277], [53281], [53283], [53284], [53285], [53287], [53364], [53365], [54927], [54929], [54930], [54931], [54932], [54933], [54938], [54943], [54944], [54945], [54946], [54947], [54948], [54950], [54951], [54952], [54956], [54959], [54960], [54961], [54962].
Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
See #56788.
Built from https://develop.svn.wordpress.org/trunk@54964
git-svn-id: http://core.svn.wordpress.org/trunk@54516 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2022-12-13 13:28:11 -05:00
* @ param string $function_name The function that was called .
* @ param string $replacement The function that should have been called .
* @ param string $version Version .
2015-11-20 02:24:30 -05:00
*/
Code Modernization: Rename parameters that use reserved keywords in `wp-includes/rest-api.php`.
While using reserved PHP keywords as parameter name labels is allowed, in the context of function calls using named parameters in PHP 8.0+, this will easily lead to confusion. To avoid that, it is recommended not to use reserved keywords as function parameter names.
This commit:
* Renames the `$namespace` parameter to `$route_namespace` in `register_rest_route()`.
* Renames the `$function` parameter to `$function_name` in:
* `rest_handle_deprecated_function()`
* `rest_handle_deprecated_argument()`
* `rest_handle_doing_it_wrong()`
* Renames the `$array` parameter to `$input_array` in `rest_validate_array_contains_unique_items()`.
Follow-up to [52946], [52996], [52997], [52998], [53003], [53014], [53029], [53039], [53116], [53117], [53137], [53174], [53184], [53185], [53192], [53193], [53198], [53203], [53207], [53215], [53216], [53220], [53230], [53232], [53236], [53239], [53240], [53242], [53243], [53245], [53246], [53257], [53269], [53270], [53271], [53272], [53273], [53274], [53275], [53276], [53277], [53281], [53283], [53284], [53285], [53287], [53364], [53365], [54927], [54929], [54930], [54931], [54932], [54933], [54938], [54943], [54944], [54945], [54946], [54947], [54948], [54950], [54951], [54952], [54956], [54959], [54960], [54961], [54962].
Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
See #56788.
Built from https://develop.svn.wordpress.org/trunk@54964
git-svn-id: http://core.svn.wordpress.org/trunk@54516 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2022-12-13 13:28:11 -05:00
function rest_handle_deprecated_function ( $function_name , $replacement , $version ) {
2017-05-18 13:49:42 -04:00
if ( ! WP_DEBUG || headers_sent () ) {
return ;
}
2015-11-20 02:24:30 -05:00
if ( ! empty ( $replacement ) ) {
2019-09-02 20:41:05 -04:00
/* translators: 1: Function name, 2: WordPress version number, 3: New function name. */
Code Modernization: Rename parameters that use reserved keywords in `wp-includes/rest-api.php`.
While using reserved PHP keywords as parameter name labels is allowed, in the context of function calls using named parameters in PHP 8.0+, this will easily lead to confusion. To avoid that, it is recommended not to use reserved keywords as function parameter names.
This commit:
* Renames the `$namespace` parameter to `$route_namespace` in `register_rest_route()`.
* Renames the `$function` parameter to `$function_name` in:
* `rest_handle_deprecated_function()`
* `rest_handle_deprecated_argument()`
* `rest_handle_doing_it_wrong()`
* Renames the `$array` parameter to `$input_array` in `rest_validate_array_contains_unique_items()`.
Follow-up to [52946], [52996], [52997], [52998], [53003], [53014], [53029], [53039], [53116], [53117], [53137], [53174], [53184], [53185], [53192], [53193], [53198], [53203], [53207], [53215], [53216], [53220], [53230], [53232], [53236], [53239], [53240], [53242], [53243], [53245], [53246], [53257], [53269], [53270], [53271], [53272], [53273], [53274], [53275], [53276], [53277], [53281], [53283], [53284], [53285], [53287], [53364], [53365], [54927], [54929], [54930], [54931], [54932], [54933], [54938], [54943], [54944], [54945], [54946], [54947], [54948], [54950], [54951], [54952], [54956], [54959], [54960], [54961], [54962].
Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
See #56788.
Built from https://develop.svn.wordpress.org/trunk@54964
git-svn-id: http://core.svn.wordpress.org/trunk@54516 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2022-12-13 13:28:11 -05:00
$string = sprintf ( __ ( '%1$s (since %2$s; use %3$s instead)' ), $function_name , $version , $replacement );
2015-11-20 02:24:30 -05:00
} else {
2019-09-02 20:41:05 -04:00
/* translators: 1: Function name, 2: WordPress version number. */
Code Modernization: Rename parameters that use reserved keywords in `wp-includes/rest-api.php`.
While using reserved PHP keywords as parameter name labels is allowed, in the context of function calls using named parameters in PHP 8.0+, this will easily lead to confusion. To avoid that, it is recommended not to use reserved keywords as function parameter names.
This commit:
* Renames the `$namespace` parameter to `$route_namespace` in `register_rest_route()`.
* Renames the `$function` parameter to `$function_name` in:
* `rest_handle_deprecated_function()`
* `rest_handle_deprecated_argument()`
* `rest_handle_doing_it_wrong()`
* Renames the `$array` parameter to `$input_array` in `rest_validate_array_contains_unique_items()`.
Follow-up to [52946], [52996], [52997], [52998], [53003], [53014], [53029], [53039], [53116], [53117], [53137], [53174], [53184], [53185], [53192], [53193], [53198], [53203], [53207], [53215], [53216], [53220], [53230], [53232], [53236], [53239], [53240], [53242], [53243], [53245], [53246], [53257], [53269], [53270], [53271], [53272], [53273], [53274], [53275], [53276], [53277], [53281], [53283], [53284], [53285], [53287], [53364], [53365], [54927], [54929], [54930], [54931], [54932], [54933], [54938], [54943], [54944], [54945], [54946], [54947], [54948], [54950], [54951], [54952], [54956], [54959], [54960], [54961], [54962].
Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
See #56788.
Built from https://develop.svn.wordpress.org/trunk@54964
git-svn-id: http://core.svn.wordpress.org/trunk@54516 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2022-12-13 13:28:11 -05:00
$string = sprintf ( __ ( '%1$s (since %2$s; no alternative available)' ), $function_name , $version );
2015-11-20 02:24:30 -05:00
}
header ( sprintf ( 'X-WP-DeprecatedFunction: %s' , $string ) );
}
/**
* Handles _deprecated_argument () errors .
*
* @ since 4.4 . 0
*
Code Modernization: Rename parameters that use reserved keywords in `wp-includes/rest-api.php`.
While using reserved PHP keywords as parameter name labels is allowed, in the context of function calls using named parameters in PHP 8.0+, this will easily lead to confusion. To avoid that, it is recommended not to use reserved keywords as function parameter names.
This commit:
* Renames the `$namespace` parameter to `$route_namespace` in `register_rest_route()`.
* Renames the `$function` parameter to `$function_name` in:
* `rest_handle_deprecated_function()`
* `rest_handle_deprecated_argument()`
* `rest_handle_doing_it_wrong()`
* Renames the `$array` parameter to `$input_array` in `rest_validate_array_contains_unique_items()`.
Follow-up to [52946], [52996], [52997], [52998], [53003], [53014], [53029], [53039], [53116], [53117], [53137], [53174], [53184], [53185], [53192], [53193], [53198], [53203], [53207], [53215], [53216], [53220], [53230], [53232], [53236], [53239], [53240], [53242], [53243], [53245], [53246], [53257], [53269], [53270], [53271], [53272], [53273], [53274], [53275], [53276], [53277], [53281], [53283], [53284], [53285], [53287], [53364], [53365], [54927], [54929], [54930], [54931], [54932], [54933], [54938], [54943], [54944], [54945], [54946], [54947], [54948], [54950], [54951], [54952], [54956], [54959], [54960], [54961], [54962].
Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
See #56788.
Built from https://develop.svn.wordpress.org/trunk@54964
git-svn-id: http://core.svn.wordpress.org/trunk@54516 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2022-12-13 13:28:11 -05:00
* @ param string $function_name The function that was called .
* @ param string $message A message regarding the change .
* @ param string $version Version .
2015-11-20 02:24:30 -05:00
*/
Code Modernization: Rename parameters that use reserved keywords in `wp-includes/rest-api.php`.
While using reserved PHP keywords as parameter name labels is allowed, in the context of function calls using named parameters in PHP 8.0+, this will easily lead to confusion. To avoid that, it is recommended not to use reserved keywords as function parameter names.
This commit:
* Renames the `$namespace` parameter to `$route_namespace` in `register_rest_route()`.
* Renames the `$function` parameter to `$function_name` in:
* `rest_handle_deprecated_function()`
* `rest_handle_deprecated_argument()`
* `rest_handle_doing_it_wrong()`
* Renames the `$array` parameter to `$input_array` in `rest_validate_array_contains_unique_items()`.
Follow-up to [52946], [52996], [52997], [52998], [53003], [53014], [53029], [53039], [53116], [53117], [53137], [53174], [53184], [53185], [53192], [53193], [53198], [53203], [53207], [53215], [53216], [53220], [53230], [53232], [53236], [53239], [53240], [53242], [53243], [53245], [53246], [53257], [53269], [53270], [53271], [53272], [53273], [53274], [53275], [53276], [53277], [53281], [53283], [53284], [53285], [53287], [53364], [53365], [54927], [54929], [54930], [54931], [54932], [54933], [54938], [54943], [54944], [54945], [54946], [54947], [54948], [54950], [54951], [54952], [54956], [54959], [54960], [54961], [54962].
Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
See #56788.
Built from https://develop.svn.wordpress.org/trunk@54964
git-svn-id: http://core.svn.wordpress.org/trunk@54516 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2022-12-13 13:28:11 -05:00
function rest_handle_deprecated_argument ( $function_name , $message , $version ) {
2017-05-18 13:49:42 -04:00
if ( ! WP_DEBUG || headers_sent () ) {
return ;
}
2020-07-07 05:56:02 -04:00
if ( $message ) {
2019-09-02 20:41:05 -04:00
/* translators: 1: Function name, 2: WordPress version number, 3: Error message. */
Code Modernization: Rename parameters that use reserved keywords in `wp-includes/rest-api.php`.
While using reserved PHP keywords as parameter name labels is allowed, in the context of function calls using named parameters in PHP 8.0+, this will easily lead to confusion. To avoid that, it is recommended not to use reserved keywords as function parameter names.
This commit:
* Renames the `$namespace` parameter to `$route_namespace` in `register_rest_route()`.
* Renames the `$function` parameter to `$function_name` in:
* `rest_handle_deprecated_function()`
* `rest_handle_deprecated_argument()`
* `rest_handle_doing_it_wrong()`
* Renames the `$array` parameter to `$input_array` in `rest_validate_array_contains_unique_items()`.
Follow-up to [52946], [52996], [52997], [52998], [53003], [53014], [53029], [53039], [53116], [53117], [53137], [53174], [53184], [53185], [53192], [53193], [53198], [53203], [53207], [53215], [53216], [53220], [53230], [53232], [53236], [53239], [53240], [53242], [53243], [53245], [53246], [53257], [53269], [53270], [53271], [53272], [53273], [53274], [53275], [53276], [53277], [53281], [53283], [53284], [53285], [53287], [53364], [53365], [54927], [54929], [54930], [54931], [54932], [54933], [54938], [54943], [54944], [54945], [54946], [54947], [54948], [54950], [54951], [54952], [54956], [54959], [54960], [54961], [54962].
Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
See #56788.
Built from https://develop.svn.wordpress.org/trunk@54964
git-svn-id: http://core.svn.wordpress.org/trunk@54516 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2022-12-13 13:28:11 -05:00
$string = sprintf ( __ ( '%1$s (since %2$s; %3$s)' ), $function_name , $version , $message );
2015-11-20 02:24:30 -05:00
} else {
2019-09-02 20:41:05 -04:00
/* translators: 1: Function name, 2: WordPress version number. */
Code Modernization: Rename parameters that use reserved keywords in `wp-includes/rest-api.php`.
While using reserved PHP keywords as parameter name labels is allowed, in the context of function calls using named parameters in PHP 8.0+, this will easily lead to confusion. To avoid that, it is recommended not to use reserved keywords as function parameter names.
This commit:
* Renames the `$namespace` parameter to `$route_namespace` in `register_rest_route()`.
* Renames the `$function` parameter to `$function_name` in:
* `rest_handle_deprecated_function()`
* `rest_handle_deprecated_argument()`
* `rest_handle_doing_it_wrong()`
* Renames the `$array` parameter to `$input_array` in `rest_validate_array_contains_unique_items()`.
Follow-up to [52946], [52996], [52997], [52998], [53003], [53014], [53029], [53039], [53116], [53117], [53137], [53174], [53184], [53185], [53192], [53193], [53198], [53203], [53207], [53215], [53216], [53220], [53230], [53232], [53236], [53239], [53240], [53242], [53243], [53245], [53246], [53257], [53269], [53270], [53271], [53272], [53273], [53274], [53275], [53276], [53277], [53281], [53283], [53284], [53285], [53287], [53364], [53365], [54927], [54929], [54930], [54931], [54932], [54933], [54938], [54943], [54944], [54945], [54946], [54947], [54948], [54950], [54951], [54952], [54956], [54959], [54960], [54961], [54962].
Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
See #56788.
Built from https://develop.svn.wordpress.org/trunk@54964
git-svn-id: http://core.svn.wordpress.org/trunk@54516 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2022-12-13 13:28:11 -05:00
$string = sprintf ( __ ( '%1$s (since %2$s; no alternative available)' ), $function_name , $version );
2015-11-20 02:24:30 -05:00
}
header ( sprintf ( 'X-WP-DeprecatedParam: %s' , $string ) );
}
2020-07-07 01:01:07 -04:00
/**
* Handles _doing_it_wrong errors .
*
* @ since 5.5 . 0
*
Code Modernization: Rename parameters that use reserved keywords in `wp-includes/rest-api.php`.
While using reserved PHP keywords as parameter name labels is allowed, in the context of function calls using named parameters in PHP 8.0+, this will easily lead to confusion. To avoid that, it is recommended not to use reserved keywords as function parameter names.
This commit:
* Renames the `$namespace` parameter to `$route_namespace` in `register_rest_route()`.
* Renames the `$function` parameter to `$function_name` in:
* `rest_handle_deprecated_function()`
* `rest_handle_deprecated_argument()`
* `rest_handle_doing_it_wrong()`
* Renames the `$array` parameter to `$input_array` in `rest_validate_array_contains_unique_items()`.
Follow-up to [52946], [52996], [52997], [52998], [53003], [53014], [53029], [53039], [53116], [53117], [53137], [53174], [53184], [53185], [53192], [53193], [53198], [53203], [53207], [53215], [53216], [53220], [53230], [53232], [53236], [53239], [53240], [53242], [53243], [53245], [53246], [53257], [53269], [53270], [53271], [53272], [53273], [53274], [53275], [53276], [53277], [53281], [53283], [53284], [53285], [53287], [53364], [53365], [54927], [54929], [54930], [54931], [54932], [54933], [54938], [54943], [54944], [54945], [54946], [54947], [54948], [54950], [54951], [54952], [54956], [54959], [54960], [54961], [54962].
Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
See #56788.
Built from https://develop.svn.wordpress.org/trunk@54964
git-svn-id: http://core.svn.wordpress.org/trunk@54516 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2022-12-13 13:28:11 -05:00
* @ param string $function_name The function that was called .
* @ param string $message A message explaining what has been done incorrectly .
* @ param string | null $version The version of WordPress where the message was added .
2020-07-07 01:01:07 -04:00
*/
Code Modernization: Rename parameters that use reserved keywords in `wp-includes/rest-api.php`.
While using reserved PHP keywords as parameter name labels is allowed, in the context of function calls using named parameters in PHP 8.0+, this will easily lead to confusion. To avoid that, it is recommended not to use reserved keywords as function parameter names.
This commit:
* Renames the `$namespace` parameter to `$route_namespace` in `register_rest_route()`.
* Renames the `$function` parameter to `$function_name` in:
* `rest_handle_deprecated_function()`
* `rest_handle_deprecated_argument()`
* `rest_handle_doing_it_wrong()`
* Renames the `$array` parameter to `$input_array` in `rest_validate_array_contains_unique_items()`.
Follow-up to [52946], [52996], [52997], [52998], [53003], [53014], [53029], [53039], [53116], [53117], [53137], [53174], [53184], [53185], [53192], [53193], [53198], [53203], [53207], [53215], [53216], [53220], [53230], [53232], [53236], [53239], [53240], [53242], [53243], [53245], [53246], [53257], [53269], [53270], [53271], [53272], [53273], [53274], [53275], [53276], [53277], [53281], [53283], [53284], [53285], [53287], [53364], [53365], [54927], [54929], [54930], [54931], [54932], [54933], [54938], [54943], [54944], [54945], [54946], [54947], [54948], [54950], [54951], [54952], [54956], [54959], [54960], [54961], [54962].
Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
See #56788.
Built from https://develop.svn.wordpress.org/trunk@54964
git-svn-id: http://core.svn.wordpress.org/trunk@54516 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2022-12-13 13:28:11 -05:00
function rest_handle_doing_it_wrong ( $function_name , $message , $version ) {
2020-07-07 01:01:07 -04:00
if ( ! WP_DEBUG || headers_sent () ) {
return ;
}
2020-07-07 05:56:02 -04:00
if ( $version ) {
/* translators: Developer debugging message. 1: PHP function name, 2: WordPress version number, 3: Explanatory message. */
2020-07-07 01:01:07 -04:00
$string = __ ( '%1$s (since %2$s; %3$s)' );
Code Modernization: Rename parameters that use reserved keywords in `wp-includes/rest-api.php`.
While using reserved PHP keywords as parameter name labels is allowed, in the context of function calls using named parameters in PHP 8.0+, this will easily lead to confusion. To avoid that, it is recommended not to use reserved keywords as function parameter names.
This commit:
* Renames the `$namespace` parameter to `$route_namespace` in `register_rest_route()`.
* Renames the `$function` parameter to `$function_name` in:
* `rest_handle_deprecated_function()`
* `rest_handle_deprecated_argument()`
* `rest_handle_doing_it_wrong()`
* Renames the `$array` parameter to `$input_array` in `rest_validate_array_contains_unique_items()`.
Follow-up to [52946], [52996], [52997], [52998], [53003], [53014], [53029], [53039], [53116], [53117], [53137], [53174], [53184], [53185], [53192], [53193], [53198], [53203], [53207], [53215], [53216], [53220], [53230], [53232], [53236], [53239], [53240], [53242], [53243], [53245], [53246], [53257], [53269], [53270], [53271], [53272], [53273], [53274], [53275], [53276], [53277], [53281], [53283], [53284], [53285], [53287], [53364], [53365], [54927], [54929], [54930], [54931], [54932], [54933], [54938], [54943], [54944], [54945], [54946], [54947], [54948], [54950], [54951], [54952], [54956], [54959], [54960], [54961], [54962].
Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
See #56788.
Built from https://develop.svn.wordpress.org/trunk@54964
git-svn-id: http://core.svn.wordpress.org/trunk@54516 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2022-12-13 13:28:11 -05:00
$string = sprintf ( $string , $function_name , $version , $message );
2020-07-07 05:56:02 -04:00
} else {
/* translators: Developer debugging message. 1: PHP function name, 2: Explanatory message. */
$string = __ ( '%1$s (%2$s)' );
Code Modernization: Rename parameters that use reserved keywords in `wp-includes/rest-api.php`.
While using reserved PHP keywords as parameter name labels is allowed, in the context of function calls using named parameters in PHP 8.0+, this will easily lead to confusion. To avoid that, it is recommended not to use reserved keywords as function parameter names.
This commit:
* Renames the `$namespace` parameter to `$route_namespace` in `register_rest_route()`.
* Renames the `$function` parameter to `$function_name` in:
* `rest_handle_deprecated_function()`
* `rest_handle_deprecated_argument()`
* `rest_handle_doing_it_wrong()`
* Renames the `$array` parameter to `$input_array` in `rest_validate_array_contains_unique_items()`.
Follow-up to [52946], [52996], [52997], [52998], [53003], [53014], [53029], [53039], [53116], [53117], [53137], [53174], [53184], [53185], [53192], [53193], [53198], [53203], [53207], [53215], [53216], [53220], [53230], [53232], [53236], [53239], [53240], [53242], [53243], [53245], [53246], [53257], [53269], [53270], [53271], [53272], [53273], [53274], [53275], [53276], [53277], [53281], [53283], [53284], [53285], [53287], [53364], [53365], [54927], [54929], [54930], [54931], [54932], [54933], [54938], [54943], [54944], [54945], [54946], [54947], [54948], [54950], [54951], [54952], [54956], [54959], [54960], [54961], [54962].
Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
See #56788.
Built from https://develop.svn.wordpress.org/trunk@54964
git-svn-id: http://core.svn.wordpress.org/trunk@54516 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2022-12-13 13:28:11 -05:00
$string = sprintf ( $string , $function_name , $message );
2020-07-07 01:01:07 -04:00
}
header ( sprintf ( 'X-WP-DoingItWrong: %s' , $string ) );
}
2015-11-20 02:24:30 -05:00
/**
* Sends Cross - Origin Resource Sharing headers with API requests .
*
* @ since 4.4 . 0
*
* @ param mixed $value Response data .
* @ return mixed Response data .
*/
function rest_send_cors_headers ( $value ) {
$origin = get_http_origin ();
if ( $origin ) {
2020-01-28 19:45:18 -05:00
// Requests from file:// and data: URLs send "Origin: null".
2017-05-10 00:22:43 -04:00
if ( 'null' !== $origin ) {
2022-06-01 14:14:10 -04:00
$origin = sanitize_url ( $origin );
2017-05-10 00:22:43 -04:00
}
header ( 'Access-Control-Allow-Origin: ' . $origin );
2016-10-30 20:19:30 -04:00
header ( 'Access-Control-Allow-Methods: OPTIONS, GET, POST, PUT, PATCH, DELETE' );
2015-11-20 02:24:30 -05:00
header ( 'Access-Control-Allow-Credentials: true' );
2019-10-15 11:47:03 -04:00
header ( 'Vary: Origin' , false );
2019-10-14 12:25:04 -04:00
} elseif ( ! headers_sent () && 'GET' === $_SERVER [ 'REQUEST_METHOD' ] && ! is_user_logged_in () ) {
2019-10-15 11:47:03 -04:00
header ( 'Vary: Origin' , false );
2015-11-20 02:24:30 -05:00
}
return $value ;
}
/**
* Handles OPTIONS requests for the server .
*
* This is handled outside of the server code , as it doesn ' t obey normal route
* mapping .
*
* @ since 4.4 . 0
*
* @ param mixed $response Current response , either response or `null` to indicate pass - through .
* @ param WP_REST_Server $handler ResponseHandler instance ( usually WP_REST_Server ) .
* @ param WP_REST_Request $request The request that was used to make current response .
* @ return WP_REST_Response Modified response , either response or `null` to indicate pass - through .
*/
function rest_handle_options_request ( $response , $handler , $request ) {
if ( ! empty ( $response ) || $request -> get_method () !== 'OPTIONS' ) {
return $response ;
}
$response = new WP_REST_Response ();
2017-11-30 18:11:00 -05:00
$data = array ();
2015-11-20 02:24:30 -05:00
foreach ( $handler -> get_routes () as $route => $endpoints ) {
2019-03-18 23:22:51 -04:00
$match = preg_match ( '@^' . $route . '$@i' , $request -> get_route (), $matches );
2015-11-20 02:24:30 -05:00
if ( ! $match ) {
continue ;
}
2019-03-18 23:22:51 -04:00
$args = array ();
foreach ( $matches as $param => $value ) {
if ( ! is_int ( $param ) ) {
$args [ $param ] = $value ;
}
}
foreach ( $endpoints as $endpoint ) {
$request -> set_url_params ( $args );
$request -> set_attributes ( $endpoint );
}
2015-11-20 02:24:30 -05:00
$data = $handler -> get_data_for_route ( $route , $endpoints , 'help' );
2016-03-03 04:55:26 -05:00
$response -> set_matched_route ( $route );
2015-11-20 02:24:30 -05:00
break ;
}
$response -> set_data ( $data );
return $response ;
}
/**
* Sends the " Allow " header to state all methods that can be sent to the current route .
*
* @ since 4.4 . 0
*
* @ param WP_REST_Response $response Current response being served .
* @ param WP_REST_Server $server ResponseHandler instance ( usually WP_REST_Server ) .
* @ param WP_REST_Request $request The request that was used to make current response .
* @ return WP_REST_Response Response to be served , with " Allow " header if route has allowed methods .
*/
function rest_send_allow_header ( $response , $server , $request ) {
$matched_route = $response -> get_matched_route ();
if ( ! $matched_route ) {
return $response ;
}
$routes = $server -> get_routes ();
$allowed_methods = array ();
// Get the allowed methods across the routes.
foreach ( $routes [ $matched_route ] as $_handler ) {
foreach ( $_handler [ 'methods' ] as $handler_method => $value ) {
if ( ! empty ( $_handler [ 'permission_callback' ] ) ) {
$permission = call_user_func ( $_handler [ 'permission_callback' ], $request );
$allowed_methods [ $handler_method ] = true === $permission ;
} else {
$allowed_methods [ $handler_method ] = true ;
}
}
}
// Strip out all the methods that are not allowed (false values).
$allowed_methods = array_filter ( $allowed_methods );
if ( $allowed_methods ) {
$response -> header ( 'Allow' , implode ( ', ' , array_map ( 'strtoupper' , array_keys ( $allowed_methods ) ) ) );
}
return $response ;
}
2019-09-19 10:05:55 -04:00
/**
* Recursively computes the intersection of arrays using keys for comparison .
*
2020-06-20 07:18:09 -04:00
* @ since 5.3 . 0
*
2020-06-20 08:58:10 -04:00
* @ param array $array1 The array with master keys to check .
* @ param array $array2 An array to compare keys against .
2020-06-20 07:18:09 -04:00
* @ return array An associative array containing all the entries of array1 which have keys
* that are present in all arguments .
2019-09-19 10:05:55 -04:00
*/
function _rest_array_intersect_key_recursive ( $array1 , $array2 ) {
$array1 = array_intersect_key ( $array1 , $array2 );
foreach ( $array1 as $key => $value ) {
if ( is_array ( $value ) && is_array ( $array2 [ $key ] ) ) {
$array1 [ $key ] = _rest_array_intersect_key_recursive ( $value , $array2 [ $key ] );
}
}
return $array1 ;
}
2017-10-04 14:46:38 -04:00
/**
2024-02-22 04:54:08 -05:00
* Filters the REST API response to include only an allow - listed set of response object fields .
2017-10-04 14:46:38 -04:00
*
* @ since 4.8 . 0
*
* @ param WP_REST_Response $response Current response being served .
* @ param WP_REST_Server $server ResponseHandler instance ( usually WP_REST_Server ) .
* @ param WP_REST_Request $request The request that was used to make current response .
* @ return WP_REST_Response Response to be served , trimmed down to contain a subset of fields .
*/
function rest_filter_response_fields ( $response , $server , $request ) {
if ( ! isset ( $request [ '_fields' ] ) || $response -> is_error () ) {
return $response ;
}
$data = $response -> get_data ();
2019-01-10 16:06:49 -05:00
$fields = wp_parse_list ( $request [ '_fields' ] );
2017-10-04 14:46:38 -04:00
if ( 0 === count ( $fields ) ) {
return $response ;
}
// Trim off outside whitespace from the comma delimited list.
$fields = array_map ( 'trim' , $fields );
2019-09-19 10:05:55 -04:00
// Create nested array of accepted field hierarchy.
$fields_as_keyed = array ();
foreach ( $fields as $field ) {
$parts = explode ( '.' , $field );
$ref = & $fields_as_keyed ;
while ( count ( $parts ) > 1 ) {
2019-10-10 13:18:03 -04:00
$next = array_shift ( $parts );
if ( isset ( $ref [ $next ] ) && true === $ref [ $next ] ) {
// Skip any sub-properties if their parent prop is already marked for inclusion.
break 2 ;
}
$ref [ $next ] = isset ( $ref [ $next ] ) ? $ref [ $next ] : array ();
2019-09-19 10:05:55 -04:00
$ref = & $ref [ $next ];
}
$last = array_shift ( $parts );
$ref [ $last ] = true ;
}
2017-10-04 14:46:38 -04:00
if ( wp_is_numeric_array ( $data ) ) {
$new_data = array ();
foreach ( $data as $item ) {
2019-09-19 10:05:55 -04:00
$new_data [] = _rest_array_intersect_key_recursive ( $item , $fields_as_keyed );
2017-10-04 14:46:38 -04:00
}
} else {
2019-09-19 10:05:55 -04:00
$new_data = _rest_array_intersect_key_recursive ( $data , $fields_as_keyed );
2017-10-04 14:46:38 -04:00
}
$response -> set_data ( $new_data );
return $response ;
}
2019-09-19 10:05:55 -04:00
/**
* Given an array of fields to include in a response , some of which may be
* `nested.fields` , determine whether the provided field should be included
* in the response body .
*
* If a parent field is passed in , the presence of any nested field within
* that parent will cause the method to return `true` . For example " title "
* will return true if any of `title` , `title.raw` or `title.rendered` is
* provided .
*
* @ since 5.3 . 0
*
* @ param string $field A field to test for inclusion in the response body .
* @ param array $fields An array of string fields supported by the endpoint .
* @ return bool Whether to include the field or not .
*/
function rest_is_field_included ( $field , $fields ) {
if ( in_array ( $field , $fields , true ) ) {
return true ;
}
2020-01-28 19:45:18 -05:00
2019-09-19 10:05:55 -04:00
foreach ( $fields as $accepted_field ) {
2023-07-10 18:48:22 -04:00
/*
* Check to see if $field is the parent of any item in $fields .
* A field " parent " should be accepted if " parent.child " is accepted .
*/
Code Modernization: Replace usage of `strpos()` with `str_starts_with()`.
`str_starts_with()` was introduced in PHP 8.0 to perform a case-sensitive check indicating if the string to search in (haystack) begins with the given substring (needle).
WordPress core includes a polyfill for `str_starts_with()` on PHP < 8.0 as of WordPress 5.9.
This commit replaces `0 === strpos( ... )` with `str_starts_with()` in core files, making the code more readable and consistent, as well as improving performance.
While `strpos()` is slightly faster than the polyfill on PHP < 8.0, `str_starts_with()` is noticeably faster on PHP 8.0+, as it is optimized to avoid unnecessarily searching along the whole haystack if it does not find the needle.
Follow-up to [52039], [52040], [52326].
Props spacedmonkey, costdev, sabernhardt, mukesh27, desrosj, jorbin, TobiasBg, ayeshrajans, lgadzhev, SergeyBiryukov.
Fixes #58012.
Built from https://develop.svn.wordpress.org/trunk@55703
git-svn-id: http://core.svn.wordpress.org/trunk@55215 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2023-05-02 11:45:22 -04:00
if ( str_starts_with ( $accepted_field , " $field . " ) ) {
2019-09-19 10:05:55 -04:00
return true ;
}
2023-07-10 18:48:22 -04:00
/*
* Conversely , if " parent " is accepted , all " parent.child " fields
* should also be accepted .
*/
Code Modernization: Replace usage of `strpos()` with `str_starts_with()`.
`str_starts_with()` was introduced in PHP 8.0 to perform a case-sensitive check indicating if the string to search in (haystack) begins with the given substring (needle).
WordPress core includes a polyfill for `str_starts_with()` on PHP < 8.0 as of WordPress 5.9.
This commit replaces `0 === strpos( ... )` with `str_starts_with()` in core files, making the code more readable and consistent, as well as improving performance.
While `strpos()` is slightly faster than the polyfill on PHP < 8.0, `str_starts_with()` is noticeably faster on PHP 8.0+, as it is optimized to avoid unnecessarily searching along the whole haystack if it does not find the needle.
Follow-up to [52039], [52040], [52326].
Props spacedmonkey, costdev, sabernhardt, mukesh27, desrosj, jorbin, TobiasBg, ayeshrajans, lgadzhev, SergeyBiryukov.
Fixes #58012.
Built from https://develop.svn.wordpress.org/trunk@55703
git-svn-id: http://core.svn.wordpress.org/trunk@55215 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2023-05-02 11:45:22 -04:00
if ( str_starts_with ( $field , " $accepted_field . " ) ) {
2019-09-19 10:05:55 -04:00
return true ;
}
}
2020-01-28 19:45:18 -05:00
2019-09-19 10:05:55 -04:00
return false ;
}
2015-11-20 02:24:30 -05:00
/**
* Adds the REST API URL to the WP RSD endpoint .
*
* @ since 4.4 . 0
*
* @ see get_rest_url ()
*/
function rest_output_rsd () {
$api_root = get_rest_url ();
if ( empty ( $api_root ) ) {
return ;
}
?>
< api name = " WP-API " blogID = " 1 " preferred = " false " apiLink = " <?php echo esc_url( $api_root ); ?> " />
< ? php
}
/**
* Outputs the REST API link tag into page header .
*
* @ since 4.4 . 0
*
* @ see get_rest_url ()
*/
function rest_output_link_wp_head () {
$api_root = get_rest_url ();
if ( empty ( $api_root ) ) {
return ;
}
2020-07-02 01:57:01 -04:00
printf ( '<link rel="https://api.w.org/" href="%s" />' , esc_url ( $api_root ) );
$resource = rest_get_queried_resource_route ();
if ( $resource ) {
2024-06-02 18:02:16 -04:00
printf (
'<link rel="alternate" title="%1$s" type="application/json" href="%2$s" />' ,
_x ( 'JSON' , 'REST API resource link name' ),
esc_url ( rest_url ( $resource ) )
);
2020-07-02 01:57:01 -04:00
}
2015-11-20 02:24:30 -05:00
}
/**
* Sends a Link header for the REST API .
*
* @ since 4.4 . 0
*/
function rest_output_link_header () {
if ( headers_sent () ) {
return ;
}
$api_root = get_rest_url ();
if ( empty ( $api_root ) ) {
return ;
}
2022-06-01 14:14:10 -04:00
header ( sprintf ( 'Link: <%s>; rel="https://api.w.org/"' , sanitize_url ( $api_root ) ), false );
2020-07-02 01:57:01 -04:00
$resource = rest_get_queried_resource_route ();
if ( $resource ) {
2024-06-02 18:02:16 -04:00
header (
sprintf (
'Link: <%1$s>; rel="alternate"; title="%2$s"; type="application/json"' ,
sanitize_url ( rest_url ( $resource ) ),
_x ( 'JSON' , 'REST API resource link name' )
),
false
);
2020-07-02 01:57:01 -04:00
}
2015-11-20 02:24:30 -05:00
}
/**
* Checks for errors when using cookie - based authentication .
*
* WordPress ' built - in cookie authentication is always active
* for logged in users . However , the API has to check nonces
* for each request to ensure users are not vulnerable to CSRF .
*
* @ since 4.4 . 0
*
2016-06-28 23:02:07 -04:00
* @ global mixed $wp_rest_auth_cookie
2015-11-20 02:24:30 -05:00
*
2016-06-28 23:02:07 -04:00
* @ param WP_Error | mixed $result Error from another authentication handler ,
2019-11-10 21:43:03 -05:00
* null if we should handle it , or another value if not .
2015-11-20 02:24:30 -05:00
* @ return WP_Error | mixed | bool WP_Error if the cookie is invalid , the $result , otherwise true .
*/
function rest_cookie_check_errors ( $result ) {
if ( ! empty ( $result ) ) {
return $result ;
}
2017-08-09 21:38:43 -04:00
global $wp_rest_auth_cookie ;
2015-11-20 02:24:30 -05:00
/*
* Is cookie authentication being used ? ( If we get an auth
* error , but we ' re still logged in , another authentication
* must have been used ) .
*/
if ( true !== $wp_rest_auth_cookie && is_user_logged_in () ) {
return $result ;
}
// Determine if there is a nonce.
$nonce = null ;
if ( isset ( $_REQUEST [ '_wpnonce' ] ) ) {
$nonce = $_REQUEST [ '_wpnonce' ];
} elseif ( isset ( $_SERVER [ 'HTTP_X_WP_NONCE' ] ) ) {
$nonce = $_SERVER [ 'HTTP_X_WP_NONCE' ];
}
if ( null === $nonce ) {
// No nonce at all, so act as if it's an unauthenticated request.
wp_set_current_user ( 0 );
return true ;
}
// Check the nonce.
$result = wp_verify_nonce ( $nonce , 'wp_rest' );
if ( ! $result ) {
2023-10-12 08:32:32 -04:00
add_filter ( 'rest_send_nocache_headers' , '__return_true' , 20 );
2021-05-21 06:49:57 -04:00
return new WP_Error ( 'rest_cookie_invalid_nonce' , __ ( 'Cookie check failed' ), array ( 'status' => 403 ) );
2015-11-20 02:24:30 -05:00
}
2016-06-28 23:02:07 -04:00
// Send a refreshed nonce in header.
2017-08-09 21:38:43 -04:00
rest_get_server () -> send_header ( 'X-WP-Nonce' , wp_create_nonce ( 'wp_rest' ) );
2016-06-28 23:02:07 -04:00
2015-11-20 02:24:30 -05:00
return true ;
}
/**
* Collects cookie authentication status .
*
* Collects errors from wp_validate_auth_cookie for use by rest_cookie_check_errors .
*
* @ since 4.4 . 0
*
* @ see current_action ()
* @ global mixed $wp_rest_auth_cookie
*/
function rest_cookie_collect_status () {
global $wp_rest_auth_cookie ;
$status_type = current_action ();
if ( 'auth_cookie_valid' !== $status_type ) {
$wp_rest_auth_cookie = substr ( $status_type , 12 );
return ;
}
$wp_rest_auth_cookie = true ;
}
REST API: Introduce Application Passwords for API authentication.
In WordPress 4.4 the REST API was first introduced. A few releases later in WordPress 4.7, the Content API endpoints were added, paving the way for Gutenberg and countless in-site experiences. In the intervening years, numerous plugins have built on top of the REST API. Many developers shared a common frustration, the lack of external authentication to the REST API.
This commit introduces Application Passwords to allow users to connect to external applications to their WordPress website. Users can generate individual passwords for each application, allowing for easy revocation and activity monitoring. An authorization flow is introduced to make the connection flow simple for users and application developers.
Application Passwords uses Basic Authentication, and by default is only available over an SSL connection.
Props georgestephanis, kasparsd, timothyblynjacobs, afercia, akkspro, andraganescu, arippberger, aristath, austyfrosty, ayesh, batmoo, bradyvercher, brianhenryie, helen, ipstenu, jeffmatson, jeffpaul, joostdevalk, joshlevinson, kadamwhite, kjbenk, koke, michael-arestad, Otto42, pekz0r, salzano, spacedmonkey, valendesigns.
Fixes #42790.
Built from https://develop.svn.wordpress.org/trunk@49109
git-svn-id: http://core.svn.wordpress.org/trunk@48871 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-10-08 18:14:06 -04:00
/**
* Collects the status of authenticating with an application password .
*
* @ since 5.6 . 0
2021-01-28 19:07:02 -05:00
* @ since 5.7 . 0 Added the `$app_password` parameter .
REST API: Introduce Application Passwords for API authentication.
In WordPress 4.4 the REST API was first introduced. A few releases later in WordPress 4.7, the Content API endpoints were added, paving the way for Gutenberg and countless in-site experiences. In the intervening years, numerous plugins have built on top of the REST API. Many developers shared a common frustration, the lack of external authentication to the REST API.
This commit introduces Application Passwords to allow users to connect to external applications to their WordPress website. Users can generate individual passwords for each application, allowing for easy revocation and activity monitoring. An authorization flow is introduced to make the connection flow simple for users and application developers.
Application Passwords uses Basic Authentication, and by default is only available over an SSL connection.
Props georgestephanis, kasparsd, timothyblynjacobs, afercia, akkspro, andraganescu, arippberger, aristath, austyfrosty, ayesh, batmoo, bradyvercher, brianhenryie, helen, ipstenu, jeffmatson, jeffpaul, joostdevalk, joshlevinson, kadamwhite, kjbenk, koke, michael-arestad, Otto42, pekz0r, salzano, spacedmonkey, valendesigns.
Fixes #42790.
Built from https://develop.svn.wordpress.org/trunk@49109
git-svn-id: http://core.svn.wordpress.org/trunk@48871 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-10-08 18:14:06 -04:00
*
* @ global WP_User | WP_Error | null $wp_rest_application_password_status
2021-01-28 19:07:02 -05:00
* @ global string | null $wp_rest_application_password_uuid
REST API: Introduce Application Passwords for API authentication.
In WordPress 4.4 the REST API was first introduced. A few releases later in WordPress 4.7, the Content API endpoints were added, paving the way for Gutenberg and countless in-site experiences. In the intervening years, numerous plugins have built on top of the REST API. Many developers shared a common frustration, the lack of external authentication to the REST API.
This commit introduces Application Passwords to allow users to connect to external applications to their WordPress website. Users can generate individual passwords for each application, allowing for easy revocation and activity monitoring. An authorization flow is introduced to make the connection flow simple for users and application developers.
Application Passwords uses Basic Authentication, and by default is only available over an SSL connection.
Props georgestephanis, kasparsd, timothyblynjacobs, afercia, akkspro, andraganescu, arippberger, aristath, austyfrosty, ayesh, batmoo, bradyvercher, brianhenryie, helen, ipstenu, jeffmatson, jeffpaul, joostdevalk, joshlevinson, kadamwhite, kjbenk, koke, michael-arestad, Otto42, pekz0r, salzano, spacedmonkey, valendesigns.
Fixes #42790.
Built from https://develop.svn.wordpress.org/trunk@49109
git-svn-id: http://core.svn.wordpress.org/trunk@48871 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-10-08 18:14:06 -04:00
*
* @ param WP_Error $user_or_error The authenticated user or error instance .
2021-01-28 19:07:02 -05:00
* @ param array $app_password The Application Password used to authenticate .
REST API: Introduce Application Passwords for API authentication.
In WordPress 4.4 the REST API was first introduced. A few releases later in WordPress 4.7, the Content API endpoints were added, paving the way for Gutenberg and countless in-site experiences. In the intervening years, numerous plugins have built on top of the REST API. Many developers shared a common frustration, the lack of external authentication to the REST API.
This commit introduces Application Passwords to allow users to connect to external applications to their WordPress website. Users can generate individual passwords for each application, allowing for easy revocation and activity monitoring. An authorization flow is introduced to make the connection flow simple for users and application developers.
Application Passwords uses Basic Authentication, and by default is only available over an SSL connection.
Props georgestephanis, kasparsd, timothyblynjacobs, afercia, akkspro, andraganescu, arippberger, aristath, austyfrosty, ayesh, batmoo, bradyvercher, brianhenryie, helen, ipstenu, jeffmatson, jeffpaul, joostdevalk, joshlevinson, kadamwhite, kjbenk, koke, michael-arestad, Otto42, pekz0r, salzano, spacedmonkey, valendesigns.
Fixes #42790.
Built from https://develop.svn.wordpress.org/trunk@49109
git-svn-id: http://core.svn.wordpress.org/trunk@48871 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-10-08 18:14:06 -04:00
*/
2021-01-28 19:07:02 -05:00
function rest_application_password_collect_status ( $user_or_error , $app_password = array () ) {
global $wp_rest_application_password_status , $wp_rest_application_password_uuid ;
REST API: Introduce Application Passwords for API authentication.
In WordPress 4.4 the REST API was first introduced. A few releases later in WordPress 4.7, the Content API endpoints were added, paving the way for Gutenberg and countless in-site experiences. In the intervening years, numerous plugins have built on top of the REST API. Many developers shared a common frustration, the lack of external authentication to the REST API.
This commit introduces Application Passwords to allow users to connect to external applications to their WordPress website. Users can generate individual passwords for each application, allowing for easy revocation and activity monitoring. An authorization flow is introduced to make the connection flow simple for users and application developers.
Application Passwords uses Basic Authentication, and by default is only available over an SSL connection.
Props georgestephanis, kasparsd, timothyblynjacobs, afercia, akkspro, andraganescu, arippberger, aristath, austyfrosty, ayesh, batmoo, bradyvercher, brianhenryie, helen, ipstenu, jeffmatson, jeffpaul, joostdevalk, joshlevinson, kadamwhite, kjbenk, koke, michael-arestad, Otto42, pekz0r, salzano, spacedmonkey, valendesigns.
Fixes #42790.
Built from https://develop.svn.wordpress.org/trunk@49109
git-svn-id: http://core.svn.wordpress.org/trunk@48871 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-10-08 18:14:06 -04:00
$wp_rest_application_password_status = $user_or_error ;
2021-01-28 19:07:02 -05:00
if ( empty ( $app_password [ 'uuid' ] ) ) {
$wp_rest_application_password_uuid = null ;
} else {
$wp_rest_application_password_uuid = $app_password [ 'uuid' ];
}
}
/**
* Gets the Application Password used for authenticating the request .
*
* @ since 5.7 . 0
*
* @ global string | null $wp_rest_application_password_uuid
*
2021-10-30 16:26:59 -04:00
* @ return string | null The Application Password UUID , or null if Application Passwords was not used .
2021-01-28 19:07:02 -05:00
*/
function rest_get_authenticated_app_password () {
global $wp_rest_application_password_uuid ;
return $wp_rest_application_password_uuid ;
REST API: Introduce Application Passwords for API authentication.
In WordPress 4.4 the REST API was first introduced. A few releases later in WordPress 4.7, the Content API endpoints were added, paving the way for Gutenberg and countless in-site experiences. In the intervening years, numerous plugins have built on top of the REST API. Many developers shared a common frustration, the lack of external authentication to the REST API.
This commit introduces Application Passwords to allow users to connect to external applications to their WordPress website. Users can generate individual passwords for each application, allowing for easy revocation and activity monitoring. An authorization flow is introduced to make the connection flow simple for users and application developers.
Application Passwords uses Basic Authentication, and by default is only available over an SSL connection.
Props georgestephanis, kasparsd, timothyblynjacobs, afercia, akkspro, andraganescu, arippberger, aristath, austyfrosty, ayesh, batmoo, bradyvercher, brianhenryie, helen, ipstenu, jeffmatson, jeffpaul, joostdevalk, joshlevinson, kadamwhite, kjbenk, koke, michael-arestad, Otto42, pekz0r, salzano, spacedmonkey, valendesigns.
Fixes #42790.
Built from https://develop.svn.wordpress.org/trunk@49109
git-svn-id: http://core.svn.wordpress.org/trunk@48871 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-10-08 18:14:06 -04:00
}
/**
* Checks for errors when using application password - based authentication .
*
* @ since 5.6 . 0
*
* @ global WP_User | WP_Error | null $wp_rest_application_password_status
*
* @ param WP_Error | null | true $result Error from another authentication handler ,
* null if we should handle it , or another value if not .
* @ return WP_Error | null | true WP_Error if the application password is invalid , the $result , otherwise true .
*/
function rest_application_password_check_errors ( $result ) {
global $wp_rest_application_password_status ;
if ( ! empty ( $result ) ) {
return $result ;
}
if ( is_wp_error ( $wp_rest_application_password_status ) ) {
$data = $wp_rest_application_password_status -> get_error_data ();
if ( ! isset ( $data [ 'status' ] ) ) {
$data [ 'status' ] = 401 ;
}
$wp_rest_application_password_status -> add_data ( $data );
return $wp_rest_application_password_status ;
}
if ( $wp_rest_application_password_status instanceof WP_User ) {
return true ;
}
return $result ;
}
/**
* Adds Application Passwords info to the REST API index .
*
* @ since 5.6 . 0
*
* @ param WP_REST_Response $response The index response object .
* @ return WP_REST_Response
*/
function rest_add_application_passwords_to_index ( $response ) {
if ( ! wp_is_application_passwords_available () ) {
return $response ;
}
$response -> data [ 'authentication' ][ 'application-passwords' ] = array (
'endpoints' => array (
'authorization' => admin_url ( 'authorize-application.php' ),
),
);
return $response ;
}
2020-07-04 20:15:05 -04:00
/**
2023-10-03 12:15:19 -04:00
* Retrieves the avatar URLs in various sizes .
2020-07-04 20:15:05 -04:00
*
* @ since 4.7 . 0
*
* @ see get_avatar_url ()
*
2023-10-03 12:15:19 -04:00
* @ param mixed $id_or_email The avatar to retrieve a URL for . Accepts a user ID , Gravatar MD5 hash ,
2020-07-04 20:15:05 -04:00
* user email , WP_User object , WP_Post object , or WP_Comment object .
2022-08-11 10:03:09 -04:00
* @ return ( string | false )[] Avatar URLs keyed by size . Each value can be a URL string or boolean false .
2020-07-04 20:15:05 -04:00
*/
function rest_get_avatar_urls ( $id_or_email ) {
$avatar_sizes = rest_get_avatar_sizes ();
$urls = array ();
foreach ( $avatar_sizes as $size ) {
$urls [ $size ] = get_avatar_url ( $id_or_email , array ( 'size' => $size ) );
}
return $urls ;
}
/**
* Retrieves the pixel sizes for avatars .
*
* @ since 4.7 . 0
*
* @ return int [] List of pixel sizes for avatars . Default `[ 24, 48, 96 ]` .
*/
function rest_get_avatar_sizes () {
/**
* Filters the REST avatar sizes .
*
* Use this filter to adjust the array of sizes returned by the
* `rest_get_avatar_sizes` function .
*
* @ since 4.4 . 0
*
* @ param int [] $sizes An array of int values that are the pixel sizes for avatars .
* Default `[ 24, 48, 96 ]` .
*/
return apply_filters ( 'rest_avatar_sizes' , array ( 24 , 48 , 96 ) );
}
2015-11-20 02:24:30 -05:00
/**
2015-12-25 15:41:26 -05:00
* Parses an RFC3339 time into a Unix timestamp .
2015-11-20 02:24:30 -05:00
*
2024-09-17 19:24:12 -04:00
* Explicitly check for `false` to detect failure , as zero is a valid return
* value on success .
*
2015-11-20 02:24:30 -05:00
* @ since 4.4 . 0
*
* @ param string $date RFC3339 timestamp .
* @ param bool $force_utc Optional . Whether to force UTC timezone instead of using
* the timestamp ' s timezone . Default false .
2024-05-31 06:35:14 -04:00
* @ return int | false Unix timestamp on success , false on failure .
2015-11-20 02:24:30 -05:00
*/
function rest_parse_date ( $date , $force_utc = false ) {
if ( $force_utc ) {
$date = preg_replace ( '/[+-]\d+:?\d+$/' , '+00:00' , $date );
}
$regex = '#^\d{4}-\d{2}-\d{2}[Tt ]\d{2}:\d{2}:\d{2}(?:\.\d+)?(?:Z|[+-]\d{2}(?::\d{2})?)?$#' ;
if ( ! preg_match ( $regex , $date , $matches ) ) {
return false ;
}
return strtotime ( $date );
}
2020-03-11 22:42:08 -04:00
/**
* Parses a 3 or 6 digit hex color ( with #).
*
* @ since 5.4 . 0
*
* @ param string $color 3 or 6 digit hex color ( with #).
2024-05-31 06:35:14 -04:00
* @ return string | false Color value on success , false on failure .
2020-03-11 22:42:08 -04:00
*/
function rest_parse_hex_color ( $color ) {
$regex = '|^#([A-Fa-f0-9]{3}){1,2}$|' ;
if ( ! preg_match ( $regex , $color , $matches ) ) {
return false ;
}
return $color ;
}
2015-11-20 02:24:30 -05:00
/**
2017-02-21 13:18:45 -05:00
* Parses a date into both its local and UTC equivalent , in MySQL datetime format .
2015-11-20 02:24:30 -05:00
*
* @ since 4.4 . 0
*
* @ see rest_parse_date ()
*
2017-02-21 13:18:45 -05:00
* @ param string $date RFC3339 timestamp .
* @ param bool $is_utc Whether the provided date should be interpreted as UTC . Default false .
2023-02-07 16:21:18 -05:00
* @ return array | null {
* Local and UTC datetime strings , in MySQL datetime format ( Y - m - d H : i : s ),
* null on failure .
*
* @ type string $ 0 Local datetime string .
* @ type string $ 1 UTC datetime string .
* }
2015-11-20 02:24:30 -05:00
*/
2017-02-21 13:18:45 -05:00
function rest_get_date_with_gmt ( $date , $is_utc = false ) {
2020-01-28 19:45:18 -05:00
/*
* Whether or not the original date actually has a timezone string
* changes the way we need to do timezone conversion .
* Store this info before parsing the date , and use it later .
*/
2017-02-21 13:18:45 -05:00
$has_timezone = preg_match ( '#(Z|[+-]\d{2}(:\d{2})?)$#' , $date );
$date = rest_parse_date ( $date );
REST API: Introduce baby API to the world.
Baby API was born at 2.8KLOC on October 8th at 2:30 UTC. API has lots
of growing to do, so wish it the best of luck.
Thanks to everyone who helped along the way:
Props rmccue, rachelbaker, danielbachhuber, joehoyle, drewapicture,
adamsilverstein, netweb, tlovett1, shelob9, kadamwhite, pento,
westonruter, nikv, tobych, redsweater, alecuf, pollyplummer, hurtige,
bpetty, oso96_2000, ericlewis, wonderboymusic, joshkadis, mordauk,
jdgrimes, johnbillion, jeremyfelt, thiago-negri, jdolan, pkevan,
iseulde, thenbrent, maxcutler, kwight, markoheijnen, phh, natewr,
jjeaton, shprink, mattheu, quasel, jmusal, codebykat, hubdotcom,
tapsboy, QWp6t, pushred, jaredcobb, justinsainton, japh, matrixik,
jorbin, frozzare, codfish, michael-arestad, kellbot, ironpaperweight,
simonlampen, alisspers, eliorivero, davidbhayes, JohnDittmar, dimadin,
traversal, cmmarslender, Toddses, kokarn, welcher, and ericpedia.
Fixes #33982.
Built from https://develop.svn.wordpress.org/trunk@34928
git-svn-id: http://core.svn.wordpress.org/trunk@34893 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-10-07 22:31:25 -04:00
2024-09-17 19:24:12 -04:00
if ( false === $date ) {
2015-11-20 02:24:30 -05:00
return null ;
}
REST API: Introduce baby API to the world.
Baby API was born at 2.8KLOC on October 8th at 2:30 UTC. API has lots
of growing to do, so wish it the best of luck.
Thanks to everyone who helped along the way:
Props rmccue, rachelbaker, danielbachhuber, joehoyle, drewapicture,
adamsilverstein, netweb, tlovett1, shelob9, kadamwhite, pento,
westonruter, nikv, tobych, redsweater, alecuf, pollyplummer, hurtige,
bpetty, oso96_2000, ericlewis, wonderboymusic, joshkadis, mordauk,
jdgrimes, johnbillion, jeremyfelt, thiago-negri, jdolan, pkevan,
iseulde, thenbrent, maxcutler, kwight, markoheijnen, phh, natewr,
jjeaton, shprink, mattheu, quasel, jmusal, codebykat, hubdotcom,
tapsboy, QWp6t, pushred, jaredcobb, justinsainton, japh, matrixik,
jorbin, frozzare, codfish, michael-arestad, kellbot, ironpaperweight,
simonlampen, alisspers, eliorivero, davidbhayes, JohnDittmar, dimadin,
traversal, cmmarslender, Toddses, kokarn, welcher, and ericpedia.
Fixes #33982.
Built from https://develop.svn.wordpress.org/trunk@34928
git-svn-id: http://core.svn.wordpress.org/trunk@34893 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-10-07 22:31:25 -04:00
2020-01-28 19:45:18 -05:00
/*
* At this point $date could either be a local date ( if we were passed
* a * local * date without a timezone offset ) or a UTC date ( otherwise ) .
* Timezone conversion needs to be handled differently between these two cases .
*/
2017-02-21 13:18:45 -05:00
if ( ! $is_utc && ! $has_timezone ) {
2019-05-25 20:12:54 -04:00
$local = gmdate ( 'Y-m-d H:i:s' , $date );
2017-11-30 18:11:00 -05:00
$utc = get_gmt_from_date ( $local );
2017-02-21 13:18:45 -05:00
} else {
2019-05-25 20:12:54 -04:00
$utc = gmdate ( 'Y-m-d H:i:s' , $date );
2017-02-21 13:18:45 -05:00
$local = get_date_from_gmt ( $utc );
}
REST API: Introduce baby API to the world.
Baby API was born at 2.8KLOC on October 8th at 2:30 UTC. API has lots
of growing to do, so wish it the best of luck.
Thanks to everyone who helped along the way:
Props rmccue, rachelbaker, danielbachhuber, joehoyle, drewapicture,
adamsilverstein, netweb, tlovett1, shelob9, kadamwhite, pento,
westonruter, nikv, tobych, redsweater, alecuf, pollyplummer, hurtige,
bpetty, oso96_2000, ericlewis, wonderboymusic, joshkadis, mordauk,
jdgrimes, johnbillion, jeremyfelt, thiago-negri, jdolan, pkevan,
iseulde, thenbrent, maxcutler, kwight, markoheijnen, phh, natewr,
jjeaton, shprink, mattheu, quasel, jmusal, codebykat, hubdotcom,
tapsboy, QWp6t, pushred, jaredcobb, justinsainton, japh, matrixik,
jorbin, frozzare, codfish, michael-arestad, kellbot, ironpaperweight,
simonlampen, alisspers, eliorivero, davidbhayes, JohnDittmar, dimadin,
traversal, cmmarslender, Toddses, kokarn, welcher, and ericpedia.
Fixes #33982.
Built from https://develop.svn.wordpress.org/trunk@34928
git-svn-id: http://core.svn.wordpress.org/trunk@34893 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-10-07 22:31:25 -04:00
2015-11-20 02:24:30 -05:00
return array ( $local , $utc );
}
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
/**
* Returns a contextual HTTP error code for authorization failure .
*
* @ since 4.7 . 0
*
2020-10-10 16:02:05 -04:00
* @ return int 401 if the user is not logged in , 403 if the user is logged in .
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
*/
function rest_authorization_required_code () {
return is_user_logged_in () ? 403 : 401 ;
}
/**
* Validate a request argument based on details registered to the route .
*
* @ since 4.7 . 0
*
2020-06-20 08:58:10 -04:00
* @ param mixed $value
* @ param WP_REST_Request $request
* @ param string $param
2019-11-10 21:43:03 -05:00
* @ return true | WP_Error
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
*/
function rest_validate_request_arg ( $value , $request , $param ) {
$attributes = $request -> get_attributes ();
if ( ! isset ( $attributes [ 'args' ][ $param ] ) || ! is_array ( $attributes [ 'args' ][ $param ] ) ) {
return true ;
}
$args = $attributes [ 'args' ][ $param ];
2016-10-30 21:48:41 -04:00
return rest_validate_value_from_schema ( $value , $args , $param );
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
}
/**
* Sanitize a request argument based on details registered to the route .
*
* @ since 4.7 . 0
*
2020-06-20 08:58:10 -04:00
* @ param mixed $value
* @ param WP_REST_Request $request
* @ param string $param
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
* @ return mixed
*/
function rest_sanitize_request_arg ( $value , $request , $param ) {
$attributes = $request -> get_attributes ();
if ( ! isset ( $attributes [ 'args' ][ $param ] ) || ! is_array ( $attributes [ 'args' ][ $param ] ) ) {
return $value ;
}
$args = $attributes [ 'args' ][ $param ];
2020-07-04 20:15:05 -04:00
return rest_sanitize_value_from_schema ( $value , $args , $param );
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
}
/**
* Parse a request argument based on details registered to the route .
*
* Runs a validation check and sanitizes the value , primarily to be used via
* the `sanitize_callback` arguments in the endpoint args registration .
*
* @ since 4.7 . 0
*
2020-06-20 08:58:10 -04:00
* @ param mixed $value
* @ param WP_REST_Request $request
* @ param string $param
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
* @ return mixed
*/
function rest_parse_request_arg ( $value , $request , $param ) {
$is_valid = rest_validate_request_arg ( $value , $request , $param );
if ( is_wp_error ( $is_valid ) ) {
return $is_valid ;
}
$value = rest_sanitize_request_arg ( $value , $request , $param );
return $value ;
}
/**
2016-11-18 14:33:31 -05:00
* Determines if an IP address is valid .
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
*
2016-11-18 14:33:31 -05:00
* Handles both IPv4 and IPv6 addresses .
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
*
* @ since 4.7 . 0
*
2020-06-20 08:58:10 -04:00
* @ param string $ip IP address .
2016-11-18 14:33:31 -05:00
* @ return string | false The valid IP address , otherwise false .
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
*/
2016-11-18 14:33:31 -05:00
function rest_is_ip_address ( $ip ) {
$ipv4_pattern = '/^(?:(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.){3}(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)$/' ;
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
External Libraries: Update Requests library to version 2.0.0.
This is a major release and contains breaking changes.
Most important changes to be aware of for this release:
* All code is now namespaced. Though there is a full backward compatibility layer available and the old class names are still supported, using them will generate a deprecation notice (which can be silenced by plugins if they'd need to support multiple WP versions). See the [https://requests.ryanmccue.info/docs/upgrading.html upgrade guide] for more details.
* A lot of classes have been marked `final`. This should generally not affect userland code as care has been taken to not apply the `final` keyword to classes which are known to be extended in userland code.
* Extensive input validation has been added to Requests. When Requests is used as documented though, this will be unnoticable.
* A new `WpOrg\Requests\Requests::has_capabilities()` method has been introduced which can be used to address #37708.
* A new `WpOrg\Requests\Response::decode_body()` method has been introduced which may be usable to simplify some of the WP native wrapper code.
* Remaining PHP 8.0 compatibility fixed (support for named parameters).
* PHP 8.1 compatibility.
Release notes: https://github.com/WordPress/Requests/releases/tag/v2.0.0
For a full list of changes in this update, see the Requests GitHub:
https://github.com/WordPress/Requests/compare/v1.8.1...v2.0.0
This commit also resolves 2 blocking issues which previously caused the revert of [52244]:
* New Requests files are loaded into `wp-includes/Requests/src/`, matching the location of the library. In doing so, filesystems that are case-insensitive are not impacted (see #54582).
* Preload: During a Core update, the old Requests files are preloaded into memory before the update deletes the files. Preloading avoids fatal errors noted in #54562.
Follow-up to [50842], [51078], [52244], [52315], [52327], [52328].
Props jrf, schlessera, datagutten, wojsmol, dustinrue, soulseekah, szepeviktor. costdev, sergeybiryukov, peterwilsoncc, ironprogrammer, antonvlasenko, hellofromTonya, swissspidy, dd32, azaozz, TobiasBg, audrasjb.
Fixes #54504.
See #54582, #54562.
Built from https://develop.svn.wordpress.org/trunk@54997
git-svn-id: http://core.svn.wordpress.org/trunk@54530 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2022-12-15 16:32:17 -05:00
if ( ! preg_match ( $ipv4_pattern , $ip ) && ! WpOrg\Requests\Ipv6 :: check_ipv6 ( $ip ) ) {
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
return false ;
}
2016-11-18 14:33:31 -05:00
return $ip ;
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
}
/**
* Changes a boolean - like value into the proper boolean value .
*
* @ since 4.7 . 0
*
* @ param bool | string | int $value The value being evaluated .
2020-10-10 16:02:05 -04:00
* @ return bool Returns the proper associated boolean value .
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
*/
function rest_sanitize_boolean ( $value ) {
// String values are translated to `true`; make sure 'false' is false.
2017-11-30 18:11:00 -05:00
if ( is_string ( $value ) ) {
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
$value = strtolower ( $value );
if ( in_array ( $value , array ( 'false' , '0' ), true ) ) {
$value = false ;
}
}
// Everything else will map nicely to boolean.
2018-12-11 17:30:24 -05:00
return ( bool ) $value ;
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
}
/**
* Determines if a given value is boolean - like .
*
* @ since 4.7 . 0
*
* @ param bool | string $maybe_bool The value being evaluated .
2020-10-10 16:02:05 -04:00
* @ return bool True if a boolean , otherwise false .
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
*/
function rest_is_boolean ( $maybe_bool ) {
if ( is_bool ( $maybe_bool ) ) {
return true ;
}
if ( is_string ( $maybe_bool ) ) {
$maybe_bool = strtolower ( $maybe_bool );
$valid_boolean_values = array (
'false' ,
'true' ,
'0' ,
'1' ,
);
return in_array ( $maybe_bool , $valid_boolean_values , true );
}
if ( is_int ( $maybe_bool ) ) {
return in_array ( $maybe_bool , array ( 0 , 1 ), true );
}
return false ;
}
/**
2020-07-04 20:15:05 -04:00
* Determines if a given value is integer - like .
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
*
2020-07-04 20:15:05 -04:00
* @ since 5.5 . 0
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
*
2020-07-04 20:15:05 -04:00
* @ param mixed $maybe_integer The value being evaluated .
* @ return bool True if an integer , otherwise false .
*/
function rest_is_integer ( $maybe_integer ) {
2020-10-08 17:15:13 -04:00
return is_numeric ( $maybe_integer ) && round ( ( float ) $maybe_integer ) === ( float ) $maybe_integer ;
2020-07-04 20:15:05 -04:00
}
/**
* Determines if a given value is array - like .
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
*
2020-07-04 20:15:05 -04:00
* @ since 5.5 . 0
*
* @ param mixed $maybe_array The value being evaluated .
* @ return bool
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
*/
2020-07-04 20:15:05 -04:00
function rest_is_array ( $maybe_array ) {
if ( is_scalar ( $maybe_array ) ) {
$maybe_array = wp_parse_list ( $maybe_array );
}
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
2020-07-04 20:15:05 -04:00
return wp_is_numeric_array ( $maybe_array );
}
/**
* Converts an array - like value to an array .
*
* @ since 5.5 . 0
*
* @ param mixed $maybe_array The value being evaluated .
* @ return array Returns the array extracted from the value .
*/
function rest_sanitize_array ( $maybe_array ) {
if ( is_scalar ( $maybe_array ) ) {
return wp_parse_list ( $maybe_array );
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
}
2020-07-04 20:15:05 -04:00
if ( ! is_array ( $maybe_array ) ) {
return array ();
}
// Normalize to numeric array so nothing unexpected is in the keys.
return array_values ( $maybe_array );
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
}
/**
2020-07-04 20:15:05 -04:00
* Determines if a given value is object - like .
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
*
2020-07-04 20:15:05 -04:00
* @ since 5.5 . 0
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
*
2020-07-04 20:15:05 -04:00
* @ param mixed $maybe_object The value being evaluated .
* @ return bool True if object like , otherwise false .
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
*/
2020-07-04 20:15:05 -04:00
function rest_is_object ( $maybe_object ) {
if ( '' === $maybe_object ) {
return true ;
}
if ( $maybe_object instanceof stdClass ) {
return true ;
}
if ( $maybe_object instanceof JsonSerializable ) {
$maybe_object = $maybe_object -> jsonSerialize ();
}
return is_array ( $maybe_object );
}
/**
2023-02-07 16:21:18 -05:00
* Converts an object - like value to an array .
2020-07-04 20:15:05 -04:00
*
* @ since 5.5 . 0
*
* @ param mixed $maybe_object The value being evaluated .
2023-02-07 16:21:18 -05:00
* @ return array Returns the object extracted from the value as an associative array .
2020-07-04 20:15:05 -04:00
*/
function rest_sanitize_object ( $maybe_object ) {
if ( '' === $maybe_object ) {
return array ();
}
if ( $maybe_object instanceof stdClass ) {
return ( array ) $maybe_object ;
}
if ( $maybe_object instanceof JsonSerializable ) {
$maybe_object = $maybe_object -> jsonSerialize ();
}
if ( ! is_array ( $maybe_object ) ) {
return array ();
}
return $maybe_object ;
}
/**
* Gets the best type for a value .
*
* @ since 5.5 . 0
*
2023-02-07 16:21:18 -05:00
* @ param mixed $value The value to check .
* @ param string [] $types The list of possible types .
2020-07-04 20:15:05 -04:00
* @ return string The best matching type , an empty string if no types match .
*/
function rest_get_best_type_for_value ( $value , $types ) {
static $checks = array (
'array' => 'rest_is_array' ,
'object' => 'rest_is_object' ,
'integer' => 'rest_is_integer' ,
'number' => 'is_numeric' ,
'boolean' => 'rest_is_boolean' ,
'string' => 'is_string' ,
'null' => 'is_null' ,
);
2023-07-10 18:48:22 -04:00
/*
* Both arrays and objects allow empty strings to be converted to their types .
* But the best answer for this type is a string .
*/
2020-07-04 20:15:05 -04:00
if ( '' === $value && in_array ( 'string' , $types , true ) ) {
return 'string' ;
}
foreach ( $types as $type ) {
if ( isset ( $checks [ $type ] ) && $checks [ $type ]( $value ) ) {
return $type ;
}
}
return '' ;
}
/**
* Handles getting the best type for a multi - type schema .
*
* This is a wrapper for { @ see rest_get_best_type_for_value ()} that handles
* backward compatibility for schemas that use invalid types .
*
* @ since 5.5 . 0
*
* @ param mixed $value The value to check .
* @ param array $args The schema array to use .
* @ param string $param The parameter name , used in error messages .
* @ return string
*/
function rest_handle_multi_type_schema ( $value , $args , $param = '' ) {
$allowed_types = array ( 'array' , 'object' , 'string' , 'number' , 'integer' , 'boolean' , 'null' );
$invalid_types = array_diff ( $args [ 'type' ], $allowed_types );
if ( $invalid_types ) {
_doing_it_wrong (
__FUNCTION__ ,
2020-08-08 21:46:07 -04:00
/* translators: 1: Parameter, 2: List of allowed types. */
2020-07-04 20:15:05 -04:00
wp_sprintf ( __ ( 'The "type" schema keyword for %1$s can only contain the built-in types: %2$l.' ), $param , $allowed_types ),
'5.5.0'
);
}
$best_type = rest_get_best_type_for_value ( $value , $args [ 'type' ] );
if ( ! $best_type ) {
if ( ! $invalid_types ) {
return '' ;
}
// Backward compatibility for previous behavior which allowed the value if there was an invalid type used.
$best_type = reset ( $invalid_types );
}
return $best_type ;
REST API: Introduce the Content API endpoints.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
- Posts: Read and write access to all post data, for all types of post-based data, including pages and media.
- Comments: Read and write access to all comment data. This includes pingbacks and trackbacks.
- Terms: Read and write access to all term data.
- Users: Read and write access to all user data. This includes public access to some data for post authors.
- Meta: Read and write access to metadata for posts, comments, terms, and users, on an opt-in basis from plugins.
- Settings: Read and write access to settings, on an opt-in basis from plugins and core. This enables API management of key site content values that are technically stored in options, such as site title and byline.
Love your REST API, WordPress! The infrastructure says, "Let's do lunch!" but the content API endpoints say, "You're paying!"
Props rmccue, rachelbaker, danielbachhuber, joehoyle, adamsilverstein, afurculita, ahmadawais, airesvsg, alisspers, antisilent, apokalyptik, artoliukkonen, attitude, boonebgorges, bradyvercher, brianhogg, caseypatrickdriscoll, chopinbach, chredd, christianesperar, chrisvanpatten, claudiolabarbera, claudiosmweb, cmmarslender, codebykat, coderkevin, codfish, codonnell822, daggerhart, danielpunkass, davidbhayes, delphinus, desrosj, dimadin, dotancohen, DrewAPicture, Dudo1985, duncanjbrown, eherman24, eivhyl, eliorivero, elyobo, en-alis, ericandrewlewis, ericpedia, evansobkowicz, fjarrett, frozzare, georgestephanis, greatislander, guavaworks, hideokamoto, hkdobrev, hubdotcom, hurtige, iandunn, ircrash, ironpaperweight, iseulde, Japh, jaredcobb, JDGrimes, jdolan, jdoubleu, jeremyfelt, jimt, jjeaton, jmusal, jnylen0, johanmynhardt, johnbillion, jonathanbardo, jorbin, joshkadis, JPry, jshreve, jtsternberg, JustinSainton, kacperszurek, kadamwhite, kalenjohnson, kellbot, kjbenk, kokarn, krogsgard, kuchenundkakao, kuldipem, kwight, lgedeon, lukepettway, mantismamita, markoheijnen, matrixik, mattheu, mauteri, maxcutler, mayukojpn, michael-arestad, miyauchi, mjbanks, modemlooper, mrbobbybryant, NateWr, nathanrice, netweb, NikV, nullvariable, oskosk, oso96_2000, oxymoron, pcfreak30, pento, peterwilsoncc, Pezzab, phh, pippinsplugins, pjgalbraith, pkevan, pollyplummer, pushred, quasel, QWp6t, schlessera, schrapel, Shelob9, shprink, simonlampen, Soean, solal, tapsboy, tfrommen, tharsheblows, thenbrent, tierra, tlovett1, tnegri, tobych, Toddses, toro_unit, traversal, vanillalounge, vishalkakadiya, wanecek, web2style, webbgaraget, websupporter, westonruter, whyisjake, wonderboymusic, wpsmith, xknown, zyphonic.
Fixes #38373.
Built from https://develop.svn.wordpress.org/trunk@38832
git-svn-id: http://core.svn.wordpress.org/trunk@38775 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2016-10-19 22:55:32 -04:00
}
2016-10-30 21:48:41 -04:00
2020-07-06 23:22:03 -04:00
/**
* Checks if an array is made up of unique items .
*
* @ since 5.5 . 0
*
Code Modernization: Rename parameters that use reserved keywords in `wp-includes/rest-api.php`.
While using reserved PHP keywords as parameter name labels is allowed, in the context of function calls using named parameters in PHP 8.0+, this will easily lead to confusion. To avoid that, it is recommended not to use reserved keywords as function parameter names.
This commit:
* Renames the `$namespace` parameter to `$route_namespace` in `register_rest_route()`.
* Renames the `$function` parameter to `$function_name` in:
* `rest_handle_deprecated_function()`
* `rest_handle_deprecated_argument()`
* `rest_handle_doing_it_wrong()`
* Renames the `$array` parameter to `$input_array` in `rest_validate_array_contains_unique_items()`.
Follow-up to [52946], [52996], [52997], [52998], [53003], [53014], [53029], [53039], [53116], [53117], [53137], [53174], [53184], [53185], [53192], [53193], [53198], [53203], [53207], [53215], [53216], [53220], [53230], [53232], [53236], [53239], [53240], [53242], [53243], [53245], [53246], [53257], [53269], [53270], [53271], [53272], [53273], [53274], [53275], [53276], [53277], [53281], [53283], [53284], [53285], [53287], [53364], [53365], [54927], [54929], [54930], [54931], [54932], [54933], [54938], [54943], [54944], [54945], [54946], [54947], [54948], [54950], [54951], [54952], [54956], [54959], [54960], [54961], [54962].
Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
See #56788.
Built from https://develop.svn.wordpress.org/trunk@54964
git-svn-id: http://core.svn.wordpress.org/trunk@54516 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2022-12-13 13:28:11 -05:00
* @ param array $input_array The array to check .
2020-07-06 23:22:03 -04:00
* @ return bool True if the array contains unique items , false otherwise .
*/
Code Modernization: Rename parameters that use reserved keywords in `wp-includes/rest-api.php`.
While using reserved PHP keywords as parameter name labels is allowed, in the context of function calls using named parameters in PHP 8.0+, this will easily lead to confusion. To avoid that, it is recommended not to use reserved keywords as function parameter names.
This commit:
* Renames the `$namespace` parameter to `$route_namespace` in `register_rest_route()`.
* Renames the `$function` parameter to `$function_name` in:
* `rest_handle_deprecated_function()`
* `rest_handle_deprecated_argument()`
* `rest_handle_doing_it_wrong()`
* Renames the `$array` parameter to `$input_array` in `rest_validate_array_contains_unique_items()`.
Follow-up to [52946], [52996], [52997], [52998], [53003], [53014], [53029], [53039], [53116], [53117], [53137], [53174], [53184], [53185], [53192], [53193], [53198], [53203], [53207], [53215], [53216], [53220], [53230], [53232], [53236], [53239], [53240], [53242], [53243], [53245], [53246], [53257], [53269], [53270], [53271], [53272], [53273], [53274], [53275], [53276], [53277], [53281], [53283], [53284], [53285], [53287], [53364], [53365], [54927], [54929], [54930], [54931], [54932], [54933], [54938], [54943], [54944], [54945], [54946], [54947], [54948], [54950], [54951], [54952], [54956], [54959], [54960], [54961], [54962].
Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
See #56788.
Built from https://develop.svn.wordpress.org/trunk@54964
git-svn-id: http://core.svn.wordpress.org/trunk@54516 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2022-12-13 13:28:11 -05:00
function rest_validate_array_contains_unique_items ( $input_array ) {
2020-07-06 23:22:03 -04:00
$seen = array ();
Code Modernization: Rename parameters that use reserved keywords in `wp-includes/rest-api.php`.
While using reserved PHP keywords as parameter name labels is allowed, in the context of function calls using named parameters in PHP 8.0+, this will easily lead to confusion. To avoid that, it is recommended not to use reserved keywords as function parameter names.
This commit:
* Renames the `$namespace` parameter to `$route_namespace` in `register_rest_route()`.
* Renames the `$function` parameter to `$function_name` in:
* `rest_handle_deprecated_function()`
* `rest_handle_deprecated_argument()`
* `rest_handle_doing_it_wrong()`
* Renames the `$array` parameter to `$input_array` in `rest_validate_array_contains_unique_items()`.
Follow-up to [52946], [52996], [52997], [52998], [53003], [53014], [53029], [53039], [53116], [53117], [53137], [53174], [53184], [53185], [53192], [53193], [53198], [53203], [53207], [53215], [53216], [53220], [53230], [53232], [53236], [53239], [53240], [53242], [53243], [53245], [53246], [53257], [53269], [53270], [53271], [53272], [53273], [53274], [53275], [53276], [53277], [53281], [53283], [53284], [53285], [53287], [53364], [53365], [54927], [54929], [54930], [54931], [54932], [54933], [54938], [54943], [54944], [54945], [54946], [54947], [54948], [54950], [54951], [54952], [54956], [54959], [54960], [54961], [54962].
Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
See #56788.
Built from https://develop.svn.wordpress.org/trunk@54964
git-svn-id: http://core.svn.wordpress.org/trunk@54516 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2022-12-13 13:28:11 -05:00
foreach ( $input_array as $item ) {
2020-07-06 23:22:03 -04:00
$stabilized = rest_stabilize_value ( $item );
$key = serialize ( $stabilized );
if ( ! isset ( $seen [ $key ] ) ) {
$seen [ $key ] = true ;
continue ;
}
return false ;
}
return true ;
}
/**
* Stabilizes a value following JSON Schema semantics .
*
* For lists , order is preserved . For objects , properties are reordered alphabetically .
*
* @ since 5.5 . 0
*
* @ param mixed $value The value to stabilize . Must already be sanitized . Objects should have been converted to arrays .
* @ return mixed The stabilized value .
*/
function rest_stabilize_value ( $value ) {
if ( is_scalar ( $value ) || is_null ( $value ) ) {
return $value ;
}
if ( is_object ( $value ) ) {
_doing_it_wrong ( __FUNCTION__ , __ ( 'Cannot stabilize objects. Convert the object to an array first.' ), '5.5.0' );
return $value ;
}
ksort ( $value );
foreach ( $value as $k => $v ) {
$value [ $k ] = rest_stabilize_value ( $v );
}
return $value ;
}
2020-09-30 22:49:12 -04:00
/**
* Validates if the JSON Schema pattern matches a value .
*
* @ since 5.6 . 0
*
* @ param string $pattern The pattern to match against .
* @ param string $value The value to check .
* @ return bool True if the pattern matches the given value , false otherwise .
*/
function rest_validate_json_schema_pattern ( $pattern , $value ) {
$escaped_pattern = str_replace ( '#' , '\\#' , $pattern );
return 1 === preg_match ( '#' . $escaped_pattern . '#u' , $value );
}
/**
* Finds the schema for a property using the patternProperties keyword .
*
* @ since 5.6 . 0
*
* @ param string $property The property name to check .
* @ param array $args The schema array to use .
* @ return array | null The schema of matching pattern property , or null if no patterns match .
*/
function rest_find_matching_pattern_property_schema ( $property , $args ) {
if ( isset ( $args [ 'patternProperties' ] ) ) {
foreach ( $args [ 'patternProperties' ] as $pattern => $child_schema ) {
if ( rest_validate_json_schema_pattern ( $pattern , $property ) ) {
return $child_schema ;
}
}
}
return null ;
}
2020-10-20 14:24:09 -04:00
/**
* Formats a combining operation error into a WP_Error object .
*
* @ since 5.6 . 0
*
* @ param string $param The parameter name .
* @ param array $error The error details .
* @ return WP_Error
*/
function rest_format_combining_operation_error ( $param , $error ) {
$position = $error [ 'index' ];
$reason = $error [ 'error_object' ] -> get_error_message ();
if ( isset ( $error [ 'schema' ][ 'title' ] ) ) {
$title = $error [ 'schema' ][ 'title' ];
return new WP_Error (
2021-01-23 22:58:57 -05:00
'rest_no_matching_schema' ,
2020-10-20 14:24:09 -04:00
/* translators: 1: Parameter, 2: Schema title, 3: Reason. */
sprintf ( __ ( '%1$s is not a valid %2$s. Reason: %3$s' ), $param , $title , $reason ),
array ( 'position' => $position )
);
}
return new WP_Error (
2021-01-23 22:58:57 -05:00
'rest_no_matching_schema' ,
2020-10-20 14:24:09 -04:00
/* translators: 1: Parameter, 2: Reason. */
sprintf ( __ ( '%1$s does not match the expected format. Reason: %2$s' ), $param , $reason ),
array ( 'position' => $position )
);
}
/**
* Gets the error of combining operation .
*
* @ since 5.6 . 0
*
* @ param array $value The value to validate .
* @ param string $param The parameter name , used in error messages .
* @ param array $errors The errors array , to search for possible error .
* @ return WP_Error The combining operation error .
*/
function rest_get_combining_operation_error ( $value , $param , $errors ) {
// If there is only one error, simply return it.
if ( 1 === count ( $errors ) ) {
return rest_format_combining_operation_error ( $param , $errors [ 0 ] );
}
// Filter out all errors related to type validation.
$filtered_errors = array ();
foreach ( $errors as $error ) {
$error_code = $error [ 'error_object' ] -> get_error_code ();
$error_data = $error [ 'error_object' ] -> get_error_data ();
if ( 'rest_invalid_type' !== $error_code || ( isset ( $error_data [ 'param' ] ) && $param !== $error_data [ 'param' ] ) ) {
$filtered_errors [] = $error ;
}
}
// If there is only one error left, simply return it.
if ( 1 === count ( $filtered_errors ) ) {
return rest_format_combining_operation_error ( $param , $filtered_errors [ 0 ] );
}
// If there are only errors related to object validation, try choosing the most appropriate one.
if ( count ( $filtered_errors ) > 1 && 'object' === $filtered_errors [ 0 ][ 'schema' ][ 'type' ] ) {
$result = null ;
$number = 0 ;
foreach ( $filtered_errors as $error ) {
if ( isset ( $error [ 'schema' ][ 'properties' ] ) ) {
$n = count ( array_intersect_key ( $error [ 'schema' ][ 'properties' ], $value ) );
if ( $n > $number ) {
$result = $error ;
$number = $n ;
}
}
}
if ( null !== $result ) {
return rest_format_combining_operation_error ( $param , $result );
}
}
// If each schema has a title, include those titles in the error message.
$schema_titles = array ();
foreach ( $errors as $error ) {
if ( isset ( $error [ 'schema' ][ 'title' ] ) ) {
$schema_titles [] = $error [ 'schema' ][ 'title' ];
}
}
if ( count ( $schema_titles ) === count ( $errors ) ) {
/* translators: 1: Parameter, 2: Schema titles. */
2021-01-23 22:58:57 -05:00
return new WP_Error ( 'rest_no_matching_schema' , wp_sprintf ( __ ( '%1$s is not a valid %2$l.' ), $param , $schema_titles ) );
2020-10-20 14:24:09 -04:00
}
2021-02-07 07:44:04 -05:00
/* translators: %s: Parameter. */
return new WP_Error ( 'rest_no_matching_schema' , sprintf ( __ ( '%s does not match any of the expected formats.' ), $param ) );
2020-10-20 14:24:09 -04:00
}
/**
* Finds the matching schema among the " anyOf " schemas .
*
* @ since 5.6 . 0
*
* @ param mixed $value The value to validate .
* @ param array $args The schema array to use .
* @ param string $param The parameter name , used in error messages .
* @ return array | WP_Error The matching schema or WP_Error instance if all schemas do not match .
*/
function rest_find_any_matching_schema ( $value , $args , $param ) {
$errors = array ();
foreach ( $args [ 'anyOf' ] as $index => $schema ) {
if ( ! isset ( $schema [ 'type' ] ) && isset ( $args [ 'type' ] ) ) {
$schema [ 'type' ] = $args [ 'type' ];
}
$is_valid = rest_validate_value_from_schema ( $value , $schema , $param );
if ( ! is_wp_error ( $is_valid ) ) {
return $schema ;
}
$errors [] = array (
'error_object' => $is_valid ,
'schema' => $schema ,
'index' => $index ,
);
}
return rest_get_combining_operation_error ( $value , $param , $errors );
}
/**
* Finds the matching schema among the " oneOf " schemas .
*
* @ since 5.6 . 0
*
* @ param mixed $value The value to validate .
* @ param array $args The schema array to use .
* @ param string $param The parameter name , used in error messages .
* @ param bool $stop_after_first_match Optional . Whether the process should stop after the first successful match .
* @ return array | WP_Error The matching schema or WP_Error instance if the number of matching schemas is not equal to one .
*/
function rest_find_one_matching_schema ( $value , $args , $param , $stop_after_first_match = false ) {
$matching_schemas = array ();
$errors = array ();
foreach ( $args [ 'oneOf' ] as $index => $schema ) {
if ( ! isset ( $schema [ 'type' ] ) && isset ( $args [ 'type' ] ) ) {
$schema [ 'type' ] = $args [ 'type' ];
}
$is_valid = rest_validate_value_from_schema ( $value , $schema , $param );
if ( ! is_wp_error ( $is_valid ) ) {
if ( $stop_after_first_match ) {
return $schema ;
}
$matching_schemas [] = array (
'schema_object' => $schema ,
'index' => $index ,
);
} else {
$errors [] = array (
'error_object' => $is_valid ,
'schema' => $schema ,
'index' => $index ,
);
}
}
if ( ! $matching_schemas ) {
return rest_get_combining_operation_error ( $value , $param , $errors );
}
if ( count ( $matching_schemas ) > 1 ) {
$schema_positions = array ();
$schema_titles = array ();
foreach ( $matching_schemas as $schema ) {
$schema_positions [] = $schema [ 'index' ];
if ( isset ( $schema [ 'schema_object' ][ 'title' ] ) ) {
$schema_titles [] = $schema [ 'schema_object' ][ 'title' ];
}
}
// If each schema has a title, include those titles in the error message.
if ( count ( $schema_titles ) === count ( $matching_schemas ) ) {
return new WP_Error (
2021-01-23 22:58:57 -05:00
'rest_one_of_multiple_matches' ,
2020-10-20 14:24:09 -04:00
/* translators: 1: Parameter, 2: Schema titles. */
wp_sprintf ( __ ( '%1$s matches %2$l, but should match only one.' ), $param , $schema_titles ),
array ( 'positions' => $schema_positions )
);
}
return new WP_Error (
2021-01-23 22:58:57 -05:00
'rest_one_of_multiple_matches' ,
2021-02-07 07:44:04 -05:00
/* translators: %s: Parameter. */
sprintf ( __ ( '%s matches more than one of the expected formats.' ), $param ),
2020-10-20 14:24:09 -04:00
array ( 'positions' => $schema_positions )
);
}
return $matching_schemas [ 0 ][ 'schema_object' ];
}
2021-01-24 11:52:00 -05:00
/**
* Checks the equality of two values , following JSON Schema semantics .
*
* Property order is ignored for objects .
*
* Values must have been previously sanitized / coerced to their native types .
*
* @ since 5.7 . 0
*
* @ param mixed $value1 The first value to check .
* @ param mixed $value2 The second value to check .
* @ return bool True if the values are equal or false otherwise .
*/
function rest_are_values_equal ( $value1 , $value2 ) {
if ( is_array ( $value1 ) && is_array ( $value2 ) ) {
if ( count ( $value1 ) !== count ( $value2 ) ) {
return false ;
}
foreach ( $value1 as $index => $value ) {
if ( ! array_key_exists ( $index , $value2 ) || ! rest_are_values_equal ( $value , $value2 [ $index ] ) ) {
return false ;
}
}
return true ;
}
2021-04-04 14:07:04 -04:00
if ( is_int ( $value1 ) && is_float ( $value2 )
|| is_float ( $value1 ) && is_int ( $value2 )
) {
return ( float ) $value1 === ( float ) $value2 ;
}
2021-01-24 11:52:00 -05:00
return $value1 === $value2 ;
}
/**
* Validates that the given value is a member of the JSON Schema " enum " .
*
* @ since 5.7 . 0
*
* @ param mixed $value The value to validate .
* @ param array $args The schema array to use .
* @ param string $param The parameter name , used in error messages .
* @ return true | WP_Error True if the " enum " contains the value or a WP_Error instance otherwise .
*/
function rest_validate_enum ( $value , $args , $param ) {
$sanitized_value = rest_sanitize_value_from_schema ( $value , $args , $param );
if ( is_wp_error ( $sanitized_value ) ) {
return $sanitized_value ;
}
foreach ( $args [ 'enum' ] as $enum_value ) {
if ( rest_are_values_equal ( $sanitized_value , $enum_value ) ) {
return true ;
}
}
$encoded_enum_values = array ();
foreach ( $args [ 'enum' ] as $enum_value ) {
$encoded_enum_values [] = is_scalar ( $enum_value ) ? $enum_value : wp_json_encode ( $enum_value );
}
if ( count ( $encoded_enum_values ) === 1 ) {
/* translators: 1: Parameter, 2: Valid values. */
return new WP_Error ( 'rest_not_in_enum' , wp_sprintf ( __ ( '%1$s is not %2$s.' ), $param , $encoded_enum_values [ 0 ] ) );
}
/* translators: 1: Parameter, 2: List of valid values. */
return new WP_Error ( 'rest_not_in_enum' , wp_sprintf ( __ ( '%1$s is not one of %2$l.' ), $param , $encoded_enum_values ) );
}
2020-10-20 16:19:09 -04:00
/**
* Get all valid JSON schema properties .
*
* @ since 5.6 . 0
*
* @ return string [] All valid JSON schema properties .
*/
function rest_get_allowed_schema_keywords () {
return array (
'title' ,
'description' ,
'default' ,
'type' ,
'format' ,
'enum' ,
'items' ,
'properties' ,
'additionalProperties' ,
'patternProperties' ,
'minProperties' ,
'maxProperties' ,
'minimum' ,
'maximum' ,
'exclusiveMinimum' ,
'exclusiveMaximum' ,
'multipleOf' ,
'minLength' ,
'maxLength' ,
'pattern' ,
'minItems' ,
'maxItems' ,
'uniqueItems' ,
'anyOf' ,
'oneOf' ,
);
}
2016-10-30 21:48:41 -04:00
/**
* Validate a value based on a schema .
*
2016-12-27 04:21:44 -05:00
* @ since 4.7 . 0
2020-05-16 15:33:09 -04:00
* @ since 4.9 . 0 Support the " object " type .
* @ since 5.2 . 0 Support validating " additionalProperties " against a schema .
* @ since 5.3 . 0 Support multiple types .
* @ since 5.4 . 0 Convert an empty string to an empty object .
* @ since 5.5 . 0 Add the " uuid " and " hex-color " formats .
* Support the " minLength " , " maxLength " and " pattern " keywords for strings .
2020-07-06 23:22:03 -04:00
* Support the " minItems " , " maxItems " and " uniqueItems " keywords for arrays .
2020-05-16 15:56:09 -04:00
* Validate required properties .
2020-09-26 14:56:04 -04:00
* @ since 5.6 . 0 Support the " minProperties " and " maxProperties " keywords for objects .
2020-09-27 15:03:05 -04:00
* Support the " multipleOf " keyword for numbers and integers .
2020-09-30 22:49:12 -04:00
* Support the " patternProperties " keyword for objects .
2020-10-20 14:24:09 -04:00
* Support the " anyOf " and " oneOf " keywords .
2016-12-27 04:21:44 -05:00
*
2016-10-30 21:48:41 -04:00
* @ param mixed $value The value to validate .
* @ param array $args Schema array to use for validation .
* @ param string $param The parameter name , used in error messages .
* @ return true | WP_Error
*/
function rest_validate_value_from_schema ( $value , $args , $param = '' ) {
2020-10-20 14:24:09 -04:00
if ( isset ( $args [ 'anyOf' ] ) ) {
$matching_schema = rest_find_any_matching_schema ( $value , $args , $param );
if ( is_wp_error ( $matching_schema ) ) {
return $matching_schema ;
}
if ( ! isset ( $args [ 'type' ] ) && isset ( $matching_schema [ 'type' ] ) ) {
$args [ 'type' ] = $matching_schema [ 'type' ];
}
}
if ( isset ( $args [ 'oneOf' ] ) ) {
$matching_schema = rest_find_one_matching_schema ( $value , $args , $param );
if ( is_wp_error ( $matching_schema ) ) {
return $matching_schema ;
}
if ( ! isset ( $args [ 'type' ] ) && isset ( $matching_schema [ 'type' ] ) ) {
$args [ 'type' ] = $matching_schema [ 'type' ];
}
}
2020-07-04 15:53:03 -04:00
$allowed_types = array ( 'array' , 'object' , 'string' , 'number' , 'integer' , 'boolean' , 'null' );
if ( ! isset ( $args [ 'type' ] ) ) {
2020-08-08 21:46:07 -04:00
/* translators: %s: Parameter. */
2020-07-04 20:15:05 -04:00
_doing_it_wrong ( __FUNCTION__ , sprintf ( __ ( 'The "type" schema keyword for %s is required.' ), $param ), '5.5.0' );
2020-07-04 15:53:03 -04:00
}
2019-09-23 13:25:57 -04:00
if ( is_array ( $args [ 'type' ] ) ) {
2020-07-04 20:15:05 -04:00
$best_type = rest_handle_multi_type_schema ( $value , $args , $param );
2019-09-23 13:25:57 -04:00
2020-07-04 20:15:05 -04:00
if ( ! $best_type ) {
2020-10-20 14:24:09 -04:00
return new WP_Error (
'rest_invalid_type' ,
/* translators: 1: Parameter, 2: List of types. */
sprintf ( __ ( '%1$s is not of type %2$s.' ), $param , implode ( ',' , $args [ 'type' ] ) ),
array ( 'param' => $param )
);
2019-09-23 13:25:57 -04:00
}
2020-07-04 20:15:05 -04:00
$args [ 'type' ] = $best_type ;
2019-09-23 13:25:57 -04:00
}
2020-07-04 15:53:03 -04:00
if ( ! in_array ( $args [ 'type' ], $allowed_types , true ) ) {
_doing_it_wrong (
__FUNCTION__ ,
2020-08-08 21:46:07 -04:00
/* translators: 1: Parameter, 2: The list of allowed types. */
2020-08-08 22:00:04 -04:00
wp_sprintf ( __ ( 'The "type" schema keyword for %1$s can only be one of the built-in types: %2$l.' ), $param , $allowed_types ),
2020-07-04 15:53:03 -04:00
'5.5.0'
);
}
2021-01-28 13:00:58 -05:00
switch ( $args [ 'type' ] ) {
case 'null' :
$is_valid = rest_validate_null_value_from_schema ( $value , $param );
break ;
case 'boolean' :
$is_valid = rest_validate_boolean_value_from_schema ( $value , $param );
break ;
case 'object' :
$is_valid = rest_validate_object_value_from_schema ( $value , $args , $param );
break ;
case 'array' :
$is_valid = rest_validate_array_value_from_schema ( $value , $args , $param );
break ;
case 'number' :
$is_valid = rest_validate_number_value_from_schema ( $value , $args , $param );
break ;
case 'string' :
$is_valid = rest_validate_string_value_from_schema ( $value , $args , $param );
break ;
case 'integer' :
$is_valid = rest_validate_integer_value_from_schema ( $value , $args , $param );
break ;
default :
$is_valid = true ;
break ;
}
if ( is_wp_error ( $is_valid ) ) {
return $is_valid ;
}
if ( ! empty ( $args [ 'enum' ] ) ) {
$enum_contains_value = rest_validate_enum ( $value , $args , $param );
if ( is_wp_error ( $enum_contains_value ) ) {
return $enum_contains_value ;
2016-11-14 11:36:33 -05:00
}
2021-01-28 13:00:58 -05:00
}
2020-01-28 19:45:18 -05:00
2023-07-10 18:48:22 -04:00
/*
* The " format " keyword should only be applied to strings . However , for backward compatibility ,
* we allow the " format " keyword if the type keyword was not specified , or was set to an invalid value .
*/
2021-01-28 13:00:58 -05:00
if ( isset ( $args [ 'format' ] )
&& ( ! isset ( $args [ 'type' ] ) || 'string' === $args [ 'type' ] || ! in_array ( $args [ 'type' ], $allowed_types , true ) )
) {
switch ( $args [ 'format' ] ) {
case 'hex-color' :
if ( ! rest_parse_hex_color ( $value ) ) {
return new WP_Error ( 'rest_invalid_hex_color' , __ ( 'Invalid hex color.' ) );
}
break ;
2020-07-04 20:15:05 -04:00
2021-01-28 13:00:58 -05:00
case 'date-time' :
2024-09-17 19:24:12 -04:00
if ( false === rest_parse_date ( $value ) ) {
2021-01-28 13:00:58 -05:00
return new WP_Error ( 'rest_invalid_date' , __ ( 'Invalid date.' ) );
2020-07-06 23:22:03 -04:00
}
2021-01-28 13:00:58 -05:00
break ;
2020-06-07 18:42:13 -04:00
2021-01-28 13:00:58 -05:00
case 'email' :
if ( ! is_email ( $value ) ) {
return new WP_Error ( 'rest_invalid_email' , __ ( 'Invalid email address.' ) );
}
break ;
case 'ip' :
if ( ! rest_is_ip_address ( $value ) ) {
/* translators: %s: IP address. */
return new WP_Error ( 'rest_invalid_ip' , sprintf ( __ ( '%s is not a valid IP address.' ), $param ) );
}
break ;
case 'uuid' :
if ( ! wp_is_uuid ( $value ) ) {
/* translators: %s: The name of a JSON field expecting a valid UUID. */
return new WP_Error ( 'rest_invalid_uuid' , sprintf ( __ ( '%s is not a valid UUID.' ), $param ) );
}
break ;
2020-06-07 18:42:13 -04:00
}
2021-01-28 13:00:58 -05:00
}
2020-06-07 18:42:13 -04:00
2021-01-28 13:00:58 -05:00
return true ;
}
2020-07-06 23:22:03 -04:00
2021-01-28 13:00:58 -05:00
/**
* Validates a null value based on a schema .
*
* @ since 5.7 . 0
*
* @ param mixed $value The value to validate .
* @ param string $param The parameter name , used in error messages .
* @ return true | WP_Error
*/
function rest_validate_null_value_from_schema ( $value , $param ) {
if ( null !== $value ) {
return new WP_Error (
'rest_invalid_type' ,
/* translators: 1: Parameter, 2: Type name. */
sprintf ( __ ( '%1$s is not of type %2$s.' ), $param , 'null' ),
array ( 'param' => $param )
);
2016-10-30 21:48:41 -04:00
}
2017-10-04 04:27:47 -04:00
2021-01-28 13:00:58 -05:00
return true ;
}
2017-10-04 04:27:47 -04:00
2021-01-28 13:00:58 -05:00
/**
* Validates a boolean value based on a schema .
*
* @ since 5.7 . 0
*
* @ param mixed $value The value to validate .
* @ param string $param The parameter name , used in error messages .
* @ return true | WP_Error
*/
function rest_validate_boolean_value_from_schema ( $value , $param ) {
if ( ! rest_is_boolean ( $value ) ) {
return new WP_Error (
'rest_invalid_type' ,
/* translators: 1: Parameter, 2: Type name. */
sprintf ( __ ( '%1$s is not of type %2$s.' ), $param , 'boolean' ),
array ( 'param' => $param )
);
}
2020-07-04 20:15:05 -04:00
2021-01-28 13:00:58 -05:00
return true ;
}
/**
* Validates an object value based on a schema .
*
* @ since 5.7 . 0
*
* @ param mixed $value The value to validate .
* @ param array $args Schema array to use for validation .
* @ param string $param The parameter name , used in error messages .
* @ return true | WP_Error
*/
function rest_validate_object_value_from_schema ( $value , $args , $param ) {
if ( ! rest_is_object ( $value ) ) {
return new WP_Error (
'rest_invalid_type' ,
/* translators: 1: Parameter, 2: Type name. */
sprintf ( __ ( '%1$s is not of type %2$s.' ), $param , 'object' ),
array ( 'param' => $param )
);
}
$value = rest_sanitize_object ( $value );
if ( isset ( $args [ 'required' ] ) && is_array ( $args [ 'required' ] ) ) { // schema version 4
foreach ( $args [ 'required' ] as $name ) {
if ( ! array_key_exists ( $name , $value ) ) {
return new WP_Error (
'rest_property_required' ,
2020-05-16 14:44:09 -04:00
/* translators: 1: Property of an object, 2: Parameter. */
2021-01-28 13:00:58 -05:00
sprintf ( __ ( '%1$s is a required property of %2$s.' ), $name , $param )
);
2020-05-16 14:44:09 -04:00
}
2021-01-28 13:00:58 -05:00
}
} elseif ( isset ( $args [ 'properties' ] ) ) { // schema version 3
foreach ( $args [ 'properties' ] as $name => $property ) {
if ( isset ( $property [ 'required' ] ) && true === $property [ 'required' ] && ! array_key_exists ( $name , $value ) ) {
return new WP_Error (
'rest_property_required' ,
2020-05-16 14:44:09 -04:00
/* translators: 1: Property of an object, 2: Parameter. */
2021-01-28 13:00:58 -05:00
sprintf ( __ ( '%1$s is a required property of %2$s.' ), $name , $param )
);
2020-05-16 14:44:09 -04:00
}
}
2021-01-28 13:00:58 -05:00
}
2020-05-16 14:44:09 -04:00
2021-01-28 13:00:58 -05:00
foreach ( $value as $property => $v ) {
if ( isset ( $args [ 'properties' ][ $property ] ) ) {
$is_valid = rest_validate_value_from_schema ( $v , $args [ 'properties' ][ $property ], $param . '[' . $property . ']' );
if ( is_wp_error ( $is_valid ) ) {
return $is_valid ;
2020-09-30 22:49:12 -04:00
}
2021-01-28 13:00:58 -05:00
continue ;
}
2020-09-30 22:49:12 -04:00
2021-01-28 13:00:58 -05:00
$pattern_property_schema = rest_find_matching_pattern_property_schema ( $property , $args );
if ( null !== $pattern_property_schema ) {
$is_valid = rest_validate_value_from_schema ( $v , $pattern_property_schema , $param . '[' . $property . ']' );
if ( is_wp_error ( $is_valid ) ) {
return $is_valid ;
2020-09-30 22:49:12 -04:00
}
2021-01-28 13:00:58 -05:00
continue ;
}
2020-09-30 22:49:12 -04:00
2021-01-28 13:00:58 -05:00
if ( isset ( $args [ 'additionalProperties' ] ) ) {
if ( false === $args [ 'additionalProperties' ] ) {
return new WP_Error (
'rest_additional_properties_forbidden' ,
2019-09-02 20:41:05 -04:00
/* translators: %s: Property of an object. */
2021-01-28 13:00:58 -05:00
sprintf ( __ ( '%1$s is not a valid property of Object.' ), $property )
);
}
2019-08-15 13:17:55 -04:00
2021-01-28 13:00:58 -05:00
if ( is_array ( $args [ 'additionalProperties' ] ) ) {
$is_valid = rest_validate_value_from_schema ( $v , $args [ 'additionalProperties' ], $param . '[' . $property . ']' );
if ( is_wp_error ( $is_valid ) ) {
return $is_valid ;
2019-08-15 13:17:55 -04:00
}
2017-10-04 04:27:47 -04:00
}
}
2021-01-28 13:00:58 -05:00
}
2020-09-26 14:20:07 -04:00
2021-01-28 13:00:58 -05:00
if ( isset ( $args [ 'minProperties' ] ) && count ( $value ) < $args [ 'minProperties' ] ) {
return new WP_Error (
'rest_too_few_properties' ,
sprintf (
2021-04-04 14:30:05 -04:00
/* translators: 1: Parameter, 2: Number. */
2021-01-28 13:00:58 -05:00
_n (
'%1$s must contain at least %2$s property.' ,
'%1$s must contain at least %2$s properties.' ,
$args [ 'minProperties' ]
),
$param ,
number_format_i18n ( $args [ 'minProperties' ] )
)
);
}
2020-09-26 14:20:07 -04:00
2021-01-28 13:00:58 -05:00
if ( isset ( $args [ 'maxProperties' ] ) && count ( $value ) > $args [ 'maxProperties' ] ) {
return new WP_Error (
'rest_too_many_properties' ,
sprintf (
2021-04-04 14:30:05 -04:00
/* translators: 1: Parameter, 2: Number. */
2021-01-28 13:00:58 -05:00
_n (
'%1$s must contain at most %2$s property.' ,
'%1$s must contain at most %2$s properties.' ,
$args [ 'maxProperties' ]
),
$param ,
number_format_i18n ( $args [ 'maxProperties' ] )
)
);
2017-10-04 04:27:47 -04:00
}
2021-01-28 13:00:58 -05:00
return true ;
}
2019-09-23 13:25:57 -04:00
2021-01-28 13:00:58 -05:00
/**
* Validates an array value based on a schema .
*
* @ since 5.7 . 0
*
* @ param mixed $value The value to validate .
* @ param array $args Schema array to use for validation .
* @ param string $param The parameter name , used in error messages .
* @ return true | WP_Error
*/
function rest_validate_array_value_from_schema ( $value , $args , $param ) {
if ( ! rest_is_array ( $value ) ) {
return new WP_Error (
'rest_invalid_type' ,
/* translators: 1: Parameter, 2: Type name. */
sprintf ( __ ( '%1$s is not of type %2$s.' ), $param , 'array' ),
array ( 'param' => $param )
);
2019-09-23 13:25:57 -04:00
}
2021-01-28 13:00:58 -05:00
$value = rest_sanitize_array ( $value );
2020-09-27 15:03:05 -04:00
2021-01-28 13:00:58 -05:00
if ( isset ( $args [ 'items' ] ) ) {
foreach ( $value as $index => $v ) {
$is_valid = rest_validate_value_from_schema ( $v , $args [ 'items' ], $param . '[' . $index . ']' );
if ( is_wp_error ( $is_valid ) ) {
return $is_valid ;
}
2020-09-27 15:03:05 -04:00
}
2016-10-30 21:48:41 -04:00
}
2021-01-28 13:00:58 -05:00
if ( isset ( $args [ 'minItems' ] ) && count ( $value ) < $args [ 'minItems' ] ) {
2020-10-20 14:24:09 -04:00
return new WP_Error (
2021-01-28 13:00:58 -05:00
'rest_too_few_items' ,
sprintf (
2021-04-04 14:30:05 -04:00
/* translators: 1: Parameter, 2: Number. */
2021-01-28 13:00:58 -05:00
_n (
'%1$s must contain at least %2$s item.' ,
'%1$s must contain at least %2$s items.' ,
$args [ 'minItems' ]
),
$param ,
number_format_i18n ( $args [ 'minItems' ] )
)
2020-10-20 14:24:09 -04:00
);
2016-10-30 21:48:41 -04:00
}
2021-01-28 13:00:58 -05:00
if ( isset ( $args [ 'maxItems' ] ) && count ( $value ) > $args [ 'maxItems' ] ) {
return new WP_Error (
2021-03-01 11:32:08 -05:00
'rest_too_many_items' ,
2021-01-28 13:00:58 -05:00
sprintf (
2021-04-04 14:30:05 -04:00
/* translators: 1: Parameter, 2: Number. */
2021-01-28 13:00:58 -05:00
_n (
'%1$s must contain at most %2$s item.' ,
'%1$s must contain at most %2$s items.' ,
$args [ 'maxItems' ]
),
$param ,
number_format_i18n ( $args [ 'maxItems' ] )
)
);
}
if ( ! empty ( $args [ 'uniqueItems' ] ) && ! rest_validate_array_contains_unique_items ( $value ) ) {
2021-02-07 07:44:04 -05:00
/* translators: %s: Parameter. */
return new WP_Error ( 'rest_duplicate_items' , sprintf ( __ ( '%s has duplicate items.' ), $param ) );
2021-01-28 13:00:58 -05:00
}
return true ;
}
/**
* Validates a number value based on a schema .
*
* @ since 5.7 . 0
*
* @ param mixed $value The value to validate .
* @ param array $args Schema array to use for validation .
* @ param string $param The parameter name , used in error messages .
* @ return true | WP_Error
*/
function rest_validate_number_value_from_schema ( $value , $args , $param ) {
if ( ! is_numeric ( $value ) ) {
2020-10-20 14:24:09 -04:00
return new WP_Error (
'rest_invalid_type' ,
/* translators: 1: Parameter, 2: Type name. */
2021-01-28 13:00:58 -05:00
sprintf ( __ ( '%1$s is not of type %2$s.' ), $param , $args [ 'type' ] ),
2020-10-20 14:24:09 -04:00
array ( 'param' => $param )
);
2016-10-30 21:48:41 -04:00
}
2021-01-28 13:00:58 -05:00
if ( isset ( $args [ 'multipleOf' ] ) && fmod ( $value , $args [ 'multipleOf' ] ) !== 0.0 ) {
return new WP_Error (
'rest_invalid_multiple' ,
/* translators: 1: Parameter, 2: Multiplier. */
sprintf ( __ ( '%1$s must be a multiple of %2$s.' ), $param , $args [ 'multipleOf' ] )
);
}
if ( isset ( $args [ 'minimum' ] ) && ! isset ( $args [ 'maximum' ] ) ) {
if ( ! empty ( $args [ 'exclusiveMinimum' ] ) && $value <= $args [ 'minimum' ] ) {
2020-10-20 14:24:09 -04:00
return new WP_Error (
2021-01-28 13:00:58 -05:00
'rest_out_of_bounds' ,
/* translators: 1: Parameter, 2: Minimum number. */
sprintf ( __ ( '%1$s must be greater than %2$d' ), $param , $args [ 'minimum' ] )
2020-10-20 14:24:09 -04:00
);
2020-04-26 22:29:07 -04:00
}
2021-01-28 13:00:58 -05:00
if ( empty ( $args [ 'exclusiveMinimum' ] ) && $value < $args [ 'minimum' ] ) {
2020-04-26 22:29:07 -04:00
return new WP_Error (
2021-01-28 13:00:58 -05:00
'rest_out_of_bounds' ,
/* translators: 1: Parameter, 2: Minimum number. */
sprintf ( __ ( '%1$s must be greater than or equal to %2$d' ), $param , $args [ 'minimum' ] )
2020-04-26 22:29:07 -04:00
);
}
2021-01-28 13:00:58 -05:00
}
2020-04-26 22:29:07 -04:00
2021-01-28 13:00:58 -05:00
if ( isset ( $args [ 'maximum' ] ) && ! isset ( $args [ 'minimum' ] ) ) {
if ( ! empty ( $args [ 'exclusiveMaximum' ] ) && $value >= $args [ 'maximum' ] ) {
2020-04-26 22:29:07 -04:00
return new WP_Error (
2021-01-28 13:00:58 -05:00
'rest_out_of_bounds' ,
/* translators: 1: Parameter, 2: Maximum number. */
sprintf ( __ ( '%1$s must be less than %2$d' ), $param , $args [ 'maximum' ] )
2020-04-26 22:29:07 -04:00
);
}
2020-05-16 15:03:08 -04:00
2021-01-28 13:00:58 -05:00
if ( empty ( $args [ 'exclusiveMaximum' ] ) && $value > $args [ 'maximum' ] ) {
return new WP_Error (
'rest_out_of_bounds' ,
/* translators: 1: Parameter, 2: Maximum number. */
sprintf ( __ ( '%1$s must be less than or equal to %2$d' ), $param , $args [ 'maximum' ] )
);
2020-05-16 15:03:08 -04:00
}
2016-10-30 21:48:41 -04:00
}
2021-01-28 13:00:58 -05:00
if ( isset ( $args [ 'minimum' ], $args [ 'maximum' ] ) ) {
if ( ! empty ( $args [ 'exclusiveMinimum' ] ) && ! empty ( $args [ 'exclusiveMaximum' ] ) ) {
if ( $value >= $args [ 'maximum' ] || $value <= $args [ 'minimum' ] ) {
return new WP_Error (
'rest_out_of_bounds' ,
sprintf (
2021-04-04 14:30:05 -04:00
/* translators: 1: Parameter, 2: Minimum number, 3: Maximum number. */
2021-01-28 13:00:58 -05:00
__ ( '%1$s must be between %2$d (exclusive) and %3$d (exclusive)' ),
$param ,
$args [ 'minimum' ],
$args [ 'maximum' ]
)
);
}
2021-01-24 11:52:00 -05:00
}
2021-01-28 13:00:58 -05:00
if ( ! empty ( $args [ 'exclusiveMinimum' ] ) && empty ( $args [ 'exclusiveMaximum' ] ) ) {
if ( $value > $args [ 'maximum' ] || $value <= $args [ 'minimum' ] ) {
return new WP_Error (
'rest_out_of_bounds' ,
sprintf (
2021-04-04 14:30:05 -04:00
/* translators: 1: Parameter, 2: Minimum number, 3: Maximum number. */
2021-01-28 13:00:58 -05:00
__ ( '%1$s must be between %2$d (exclusive) and %3$d (inclusive)' ),
$param ,
$args [ 'minimum' ],
$args [ 'maximum' ]
)
);
}
2016-10-30 21:48:41 -04:00
}
2021-01-28 13:00:58 -05:00
if ( ! empty ( $args [ 'exclusiveMaximum' ] ) && empty ( $args [ 'exclusiveMinimum' ] ) ) {
if ( $value >= $args [ 'maximum' ] || $value < $args [ 'minimum' ] ) {
return new WP_Error (
'rest_out_of_bounds' ,
sprintf (
2021-04-04 14:30:05 -04:00
/* translators: 1: Parameter, 2: Minimum number, 3: Maximum number. */
2021-01-28 13:00:58 -05:00
__ ( '%1$s must be between %2$d (inclusive) and %3$d (exclusive)' ),
$param ,
$args [ 'minimum' ],
$args [ 'maximum' ]
)
);
}
}
if ( empty ( $args [ 'exclusiveMinimum' ] ) && empty ( $args [ 'exclusiveMaximum' ] ) ) {
if ( $value > $args [ 'maximum' ] || $value < $args [ 'minimum' ] ) {
return new WP_Error (
'rest_out_of_bounds' ,
sprintf (
2021-04-04 14:30:05 -04:00
/* translators: 1: Parameter, 2: Minimum number, 3: Maximum number. */
2021-01-28 13:00:58 -05:00
__ ( '%1$s must be between %2$d (inclusive) and %3$d (inclusive)' ),
$param ,
$args [ 'minimum' ],
$args [ 'maximum' ]
)
);
2016-10-30 21:48:41 -04:00
}
}
}
return true ;
}
2021-01-28 13:00:58 -05:00
/**
* Validates a string value based on a schema .
*
* @ since 5.7 . 0
*
* @ param mixed $value The value to validate .
* @ param array $args Schema array to use for validation .
* @ param string $param The parameter name , used in error messages .
* @ return true | WP_Error
*/
function rest_validate_string_value_from_schema ( $value , $args , $param ) {
if ( ! is_string ( $value ) ) {
return new WP_Error (
'rest_invalid_type' ,
/* translators: 1: Parameter, 2: Type name. */
sprintf ( __ ( '%1$s is not of type %2$s.' ), $param , 'string' ),
array ( 'param' => $param )
);
}
if ( isset ( $args [ 'minLength' ] ) && mb_strlen ( $value ) < $args [ 'minLength' ] ) {
return new WP_Error (
'rest_too_short' ,
sprintf (
2021-04-04 14:30:05 -04:00
/* translators: 1: Parameter, 2: Number of characters. */
2021-01-28 13:00:58 -05:00
_n (
'%1$s must be at least %2$s character long.' ,
'%1$s must be at least %2$s characters long.' ,
$args [ 'minLength' ]
),
$param ,
number_format_i18n ( $args [ 'minLength' ] )
)
);
}
if ( isset ( $args [ 'maxLength' ] ) && mb_strlen ( $value ) > $args [ 'maxLength' ] ) {
return new WP_Error (
'rest_too_long' ,
sprintf (
2021-04-04 14:30:05 -04:00
/* translators: 1: Parameter, 2: Number of characters. */
2021-01-28 13:00:58 -05:00
_n (
'%1$s must be at most %2$s character long.' ,
'%1$s must be at most %2$s characters long.' ,
$args [ 'maxLength' ]
),
$param ,
number_format_i18n ( $args [ 'maxLength' ] )
)
);
}
if ( isset ( $args [ 'pattern' ] ) && ! rest_validate_json_schema_pattern ( $args [ 'pattern' ], $value ) ) {
return new WP_Error (
'rest_invalid_pattern' ,
/* translators: 1: Parameter, 2: Pattern. */
sprintf ( __ ( '%1$s does not match pattern %2$s.' ), $param , $args [ 'pattern' ] )
);
}
return true ;
}
/**
* Validates an integer value based on a schema .
*
* @ since 5.7 . 0
*
* @ param mixed $value The value to validate .
* @ param array $args Schema array to use for validation .
* @ param string $param The parameter name , used in error messages .
* @ return true | WP_Error
*/
function rest_validate_integer_value_from_schema ( $value , $args , $param ) {
$is_valid_number = rest_validate_number_value_from_schema ( $value , $args , $param );
if ( is_wp_error ( $is_valid_number ) ) {
return $is_valid_number ;
}
if ( ! rest_is_integer ( $value ) ) {
return new WP_Error (
'rest_invalid_type' ,
/* translators: 1: Parameter, 2: Type name. */
sprintf ( __ ( '%1$s is not of type %2$s.' ), $param , 'integer' ),
array ( 'param' => $param )
);
}
return true ;
}
2016-10-30 21:48:41 -04:00
/**
* Sanitize a value based on a schema .
*
2016-12-27 04:21:44 -05:00
* @ since 4.7 . 0
2020-07-04 20:15:05 -04:00
* @ since 5.5 . 0 Added the `$param` parameter .
2020-10-20 14:24:09 -04:00
* @ since 5.6 . 0 Support the " anyOf " and " oneOf " keywords .
2021-10-14 22:04:56 -04:00
* @ since 5.9 . 0 Added `text-field` and `textarea-field` formats .
2016-12-27 04:21:44 -05:00
*
2020-07-04 20:15:05 -04:00
* @ param mixed $value The value to sanitize .
* @ param array $args Schema array to use for sanitization .
* @ param string $param The parameter name , used in error messages .
2020-07-06 23:22:03 -04:00
* @ return mixed | WP_Error The sanitized value or a WP_Error instance if the value cannot be safely sanitized .
2016-10-30 21:48:41 -04:00
*/
2020-07-04 20:15:05 -04:00
function rest_sanitize_value_from_schema ( $value , $args , $param = '' ) {
2020-10-20 14:24:09 -04:00
if ( isset ( $args [ 'anyOf' ] ) ) {
$matching_schema = rest_find_any_matching_schema ( $value , $args , $param );
if ( is_wp_error ( $matching_schema ) ) {
return $matching_schema ;
}
if ( ! isset ( $args [ 'type' ] ) ) {
$args [ 'type' ] = $matching_schema [ 'type' ];
}
$value = rest_sanitize_value_from_schema ( $value , $matching_schema , $param );
}
if ( isset ( $args [ 'oneOf' ] ) ) {
$matching_schema = rest_find_one_matching_schema ( $value , $args , $param );
if ( is_wp_error ( $matching_schema ) ) {
return $matching_schema ;
}
if ( ! isset ( $args [ 'type' ] ) ) {
$args [ 'type' ] = $matching_schema [ 'type' ];
}
$value = rest_sanitize_value_from_schema ( $value , $matching_schema , $param );
}
2020-07-04 15:53:03 -04:00
$allowed_types = array ( 'array' , 'object' , 'string' , 'number' , 'integer' , 'boolean' , 'null' );
if ( ! isset ( $args [ 'type' ] ) ) {
2020-08-08 21:46:07 -04:00
/* translators: %s: Parameter. */
2020-07-04 20:15:05 -04:00
_doing_it_wrong ( __FUNCTION__ , sprintf ( __ ( 'The "type" schema keyword for %s is required.' ), $param ), '5.5.0' );
2020-07-04 15:53:03 -04:00
}
2019-09-23 13:25:57 -04:00
if ( is_array ( $args [ 'type' ] ) ) {
2020-07-04 20:15:05 -04:00
$best_type = rest_handle_multi_type_schema ( $value , $args , $param );
2019-09-23 13:25:57 -04:00
2020-07-04 20:15:05 -04:00
if ( ! $best_type ) {
2019-09-23 13:25:57 -04:00
return null ;
}
2020-07-04 20:15:05 -04:00
$args [ 'type' ] = $best_type ;
2019-09-23 13:25:57 -04:00
}
2020-07-04 15:53:03 -04:00
if ( ! in_array ( $args [ 'type' ], $allowed_types , true ) ) {
_doing_it_wrong (
__FUNCTION__ ,
2020-08-08 21:46:07 -04:00
/* translators: 1: Parameter, 2: The list of allowed types. */
2020-08-08 22:00:04 -04:00
wp_sprintf ( __ ( 'The "type" schema keyword for %1$s can only be one of the built-in types: %2$l.' ), $param , $allowed_types ),
2020-07-04 15:53:03 -04:00
'5.5.0'
);
}
2016-10-30 21:48:41 -04:00
if ( 'array' === $args [ 'type' ] ) {
2020-07-04 20:15:05 -04:00
$value = rest_sanitize_array ( $value );
2020-07-06 23:22:03 -04:00
if ( ! empty ( $args [ 'items' ] ) ) {
foreach ( $value as $index => $v ) {
$value [ $index ] = rest_sanitize_value_from_schema ( $v , $args [ 'items' ], $param . '[' . $index . ']' );
}
2016-10-30 21:48:41 -04:00
}
2020-01-28 19:45:18 -05:00
2020-07-06 23:22:03 -04:00
if ( ! empty ( $args [ 'uniqueItems' ] ) && ! rest_validate_array_contains_unique_items ( $value ) ) {
2021-02-07 07:44:04 -05:00
/* translators: %s: Parameter. */
return new WP_Error ( 'rest_duplicate_items' , sprintf ( __ ( '%s has duplicate items.' ), $param ) );
2016-10-30 21:48:41 -04:00
}
2020-01-28 19:45:18 -05:00
2016-10-30 21:48:41 -04:00
return $value ;
}
2017-10-04 04:27:47 -04:00
if ( 'object' === $args [ 'type' ] ) {
2020-07-04 20:15:05 -04:00
$value = rest_sanitize_object ( $value );
2017-10-04 04:27:47 -04:00
foreach ( $value as $property => $v ) {
2017-10-24 17:05:49 -04:00
if ( isset ( $args [ 'properties' ][ $property ] ) ) {
2020-07-04 20:15:05 -04:00
$value [ $property ] = rest_sanitize_value_from_schema ( $v , $args [ 'properties' ][ $property ], $param . '[' . $property . ']' );
2020-09-30 22:49:12 -04:00
continue ;
}
$pattern_property_schema = rest_find_matching_pattern_property_schema ( $property , $args );
if ( null !== $pattern_property_schema ) {
$value [ $property ] = rest_sanitize_value_from_schema ( $v , $pattern_property_schema , $param . '[' . $property . ']' );
continue ;
}
if ( isset ( $args [ 'additionalProperties' ] ) ) {
2019-08-15 13:17:55 -04:00
if ( false === $args [ 'additionalProperties' ] ) {
unset ( $value [ $property ] );
} elseif ( is_array ( $args [ 'additionalProperties' ] ) ) {
2020-07-04 20:15:05 -04:00
$value [ $property ] = rest_sanitize_value_from_schema ( $v , $args [ 'additionalProperties' ], $param . '[' . $property . ']' );
2019-08-15 13:17:55 -04:00
}
2017-10-04 04:27:47 -04:00
}
}
return $value ;
}
2019-09-23 13:25:57 -04:00
if ( 'null' === $args [ 'type' ] ) {
return null ;
}
2016-10-30 21:48:41 -04:00
if ( 'integer' === $args [ 'type' ] ) {
return ( int ) $value ;
}
if ( 'number' === $args [ 'type' ] ) {
return ( float ) $value ;
}
if ( 'boolean' === $args [ 'type' ] ) {
return rest_sanitize_boolean ( $value );
}
2020-07-04 15:53:03 -04:00
// This behavior matches rest_validate_value_from_schema().
2020-07-04 16:42:06 -04:00
if ( isset ( $args [ 'format' ] )
&& ( ! isset ( $args [ 'type' ] ) || 'string' === $args [ 'type' ] || ! in_array ( $args [ 'type' ], $allowed_types , true ) )
) {
2016-10-30 21:48:41 -04:00
switch ( $args [ 'format' ] ) {
2020-03-11 22:42:08 -04:00
case 'hex-color' :
return ( string ) sanitize_hex_color ( $value );
2017-11-30 18:11:00 -05:00
case 'date-time' :
2016-10-30 21:48:41 -04:00
return sanitize_text_field ( $value );
2017-11-30 18:11:00 -05:00
case 'email' :
2020-01-28 19:45:18 -05:00
// sanitize_email() validates, which would be unexpected.
2016-10-30 21:48:41 -04:00
return sanitize_text_field ( $value );
2017-11-30 18:11:00 -05:00
case 'uri' :
2022-06-01 14:14:10 -04:00
return sanitize_url ( $value );
2016-10-30 21:48:41 -04:00
2017-11-30 18:11:00 -05:00
case 'ip' :
2016-10-30 21:48:41 -04:00
return sanitize_text_field ( $value );
2020-05-03 15:20:09 -04:00
case 'uuid' :
return sanitize_text_field ( $value );
2021-10-14 22:04:56 -04:00
case 'text-field' :
return sanitize_text_field ( $value );
case 'textarea-field' :
return sanitize_textarea_field ( $value );
2016-10-30 21:48:41 -04:00
}
}
2016-11-14 11:36:33 -05:00
if ( 'string' === $args [ 'type' ] ) {
2020-10-08 17:15:13 -04:00
return ( string ) $value ;
2016-11-14 11:36:33 -05:00
}
2016-10-30 21:48:41 -04:00
return $value ;
}
2018-12-13 17:25:49 -05:00
/**
* Append result of internal request to REST API for purpose of preloading data to be attached to a page .
* Expected to be called in the context of `array_reduce` .
*
* @ since 5.0 . 0
*
2020-06-20 08:58:10 -04:00
* @ param array $memo Reduce accumulator .
* @ param string $path REST API path to preload .
* @ return array Modified reduce accumulator .
2018-12-13 17:25:49 -05:00
*/
function rest_preload_api_request ( $memo , $path ) {
2023-07-10 18:48:22 -04:00
/*
* array_reduce () doesn ' t support passing an array in PHP 5.2 ,
* so we need to make sure we start with one .
*/
2018-12-13 17:25:49 -05:00
if ( ! is_array ( $memo ) ) {
$memo = array ();
}
if ( empty ( $path ) ) {
return $memo ;
}
2018-12-14 01:02:52 -05:00
$method = 'GET' ;
if ( is_array ( $path ) && 2 === count ( $path ) ) {
$method = end ( $path );
$path = reset ( $path );
if ( ! in_array ( $method , array ( 'GET' , 'OPTIONS' ), true ) ) {
$method = 'GET' ;
}
}
2024-11-25 05:10:17 -05:00
// Remove trailing slashes at the end of the REST API path (query part).
2021-08-20 19:44:57 -04:00
$path = untrailingslashit ( $path );
if ( empty ( $path ) ) {
$path = '/' ;
}
2018-12-13 17:25:49 -05:00
$path_parts = parse_url ( $path );
if ( false === $path_parts ) {
return $memo ;
}
2024-11-25 05:10:17 -05:00
if ( isset ( $path_parts [ 'path' ] ) && '/' !== $path_parts [ 'path' ] ) {
// Remove trailing slashes from the "path" part of the REST API path.
$path_parts [ 'path' ] = untrailingslashit ( $path_parts [ 'path' ] );
$path = str_contains ( $path , '?' ) ?
$path_parts [ 'path' ] . '?' . ( $path_parts [ 'query' ] ? ? '' ) :
$path_parts [ 'path' ];
}
2018-12-14 01:02:52 -05:00
$request = new WP_REST_Request ( $method , $path_parts [ 'path' ] );
2018-12-13 17:25:49 -05:00
if ( ! empty ( $path_parts [ 'query' ] ) ) {
parse_str ( $path_parts [ 'query' ], $query_params );
$request -> set_query_params ( $query_params );
}
$response = rest_do_request ( $request );
if ( 200 === $response -> status ) {
$server = rest_get_server ();
2022-04-19 10:40:09 -04:00
/** This filter is documented in wp-includes/rest-api/class-wp-rest-server.php */
$response = apply_filters ( 'rest_post_dispatch' , rest_ensure_response ( $response ), $server , $request );
2022-05-23 16:40:14 -04:00
$embed = $request -> has_param ( '_embed' ) ? rest_parse_embed_param ( $request [ '_embed' ] ) : false ;
$data = ( array ) $server -> response_to_data ( $response , $embed );
2018-12-13 17:25:49 -05:00
2018-12-14 01:02:52 -05:00
if ( 'OPTIONS' === $method ) {
$memo [ $method ][ $path ] = array (
'body' => $data ,
'headers' => $response -> headers ,
);
} else {
$memo [ $path ] = array (
'body' => $data ,
'headers' => $response -> headers ,
);
}
2018-12-13 17:25:49 -05:00
}
return $memo ;
}
2020-02-09 15:54:05 -05:00
/**
* Parses the " _embed " parameter into the list of resources to embed .
*
* @ since 5.4 . 0
*
* @ param string | array $embed Raw " _embed " parameter value .
* @ return true | string [] Either true to embed all embeds , or a list of relations to embed .
*/
function rest_parse_embed_param ( $embed ) {
if ( ! $embed || 'true' === $embed || '1' === $embed ) {
return true ;
}
$rels = wp_parse_list ( $embed );
if ( ! $rels ) {
return true ;
}
return $rels ;
}
2020-05-03 22:46:05 -04:00
/**
* Filters the response to remove any fields not available in the given context .
*
* @ since 5.5 . 0
2020-09-30 22:49:12 -04:00
* @ since 5.6 . 0 Support the " patternProperties " keyword for objects .
2020-10-20 14:24:09 -04:00
* Support the " anyOf " and " oneOf " keywords .
2020-05-03 22:46:05 -04:00
*
Code Modernization: Rename parameters that use reserved keywords in `phpunit/tests/rest-api/rest-*-controller.php`.
While using reserved PHP keywords as parameter name labels is allowed, in the context of function calls using named parameters in PHP 8.0+, this will easily lead to confusion. To avoid that, it is recommended not to use reserved keywords as function parameter names.
This commit:
* Renames the `$object` parameter to `$response_data` in:
* `WP_Test_REST_Attachments_Controller::additional_field_get_callback()`
* `WP_Test_REST_Autosaves_Controller::additional_field_get_callback()`
* `WP_Test_REST_Categories_Controller::additional_field_get_callback()`
* `WP_Test_REST_Comments_Controller::additional_field_get_callback()`
* `WP_Test_REST_Post_Statuses_Controller::additional_field_get_callback()`
* `WP_Test_REST_Post_Types_Controller::additional_field_get_callback()`
* `WP_Test_REST_Posts_Controller::additional_field_get_callback()`
* `WP_Test_REST_Revisions_Controller::additional_field_get_callback()`
* `WP_Test_REST_Tags_Controller::additional_field_get_callback()`
* `WP_Test_REST_Users_Controller::additional_field_get_callback()`
* Amends the `$data` and `$prepared` parameters for consistency in:
* `WP_REST_Controller::add_additional_fields_to_object()`
* `WP_REST_Controller::filter_response_by_context()`
* `rest_filter_response_by_context()`
Follow-up to [52946], [52996], [52997], [52998], [53003], [53014], [53029], [53039], [53116], [53117], [53137], [53174], [53184], [53185], [53192], [53193], [53198], [53203], [53207], [53215], [53216], [53220], [53230], [53232], [53236], [53239], [53240], [53242], [53243], [53245], [53246], [53257], [53269], [53270], [53271], [53272], [53273], [53274], [53275], [53276], [53277], [53281], [53283], [53284], [53285], [53287], [53364], [53365], [54927], [54929], [54930], [54931], [54932], [54933], [54938], [54943], [54944], [54945], [54946], [54947], [54948], [54950], [54951], [54952], [54956], [54959], [54960], [54961], [54962], [54964], [54965], [54969], [54970], [54971], [54972], [54996], [55000], [55011], [55013], [55014], [55015], [55016], [55017], [55020], [55021], [55023], [55027], [55028], [55034], [55036], [55037], [55038], [55039], [55049], [55050], [55060], [55062], [55064], [55065], [55076], [55077], [55078], [55081], [55090], [55100].
Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
See #56788.
Built from https://develop.svn.wordpress.org/trunk@55104
git-svn-id: http://core.svn.wordpress.org/trunk@54637 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2023-01-19 19:21:15 -05:00
* @ param array | object $response_data The response data to modify .
* @ param array $schema The schema for the endpoint used to filter the response .
* @ param string $context The requested context .
2020-05-03 22:46:05 -04:00
* @ return array | object The filtered response data .
*/
Code Modernization: Rename parameters that use reserved keywords in `phpunit/tests/rest-api/rest-*-controller.php`.
While using reserved PHP keywords as parameter name labels is allowed, in the context of function calls using named parameters in PHP 8.0+, this will easily lead to confusion. To avoid that, it is recommended not to use reserved keywords as function parameter names.
This commit:
* Renames the `$object` parameter to `$response_data` in:
* `WP_Test_REST_Attachments_Controller::additional_field_get_callback()`
* `WP_Test_REST_Autosaves_Controller::additional_field_get_callback()`
* `WP_Test_REST_Categories_Controller::additional_field_get_callback()`
* `WP_Test_REST_Comments_Controller::additional_field_get_callback()`
* `WP_Test_REST_Post_Statuses_Controller::additional_field_get_callback()`
* `WP_Test_REST_Post_Types_Controller::additional_field_get_callback()`
* `WP_Test_REST_Posts_Controller::additional_field_get_callback()`
* `WP_Test_REST_Revisions_Controller::additional_field_get_callback()`
* `WP_Test_REST_Tags_Controller::additional_field_get_callback()`
* `WP_Test_REST_Users_Controller::additional_field_get_callback()`
* Amends the `$data` and `$prepared` parameters for consistency in:
* `WP_REST_Controller::add_additional_fields_to_object()`
* `WP_REST_Controller::filter_response_by_context()`
* `rest_filter_response_by_context()`
Follow-up to [52946], [52996], [52997], [52998], [53003], [53014], [53029], [53039], [53116], [53117], [53137], [53174], [53184], [53185], [53192], [53193], [53198], [53203], [53207], [53215], [53216], [53220], [53230], [53232], [53236], [53239], [53240], [53242], [53243], [53245], [53246], [53257], [53269], [53270], [53271], [53272], [53273], [53274], [53275], [53276], [53277], [53281], [53283], [53284], [53285], [53287], [53364], [53365], [54927], [54929], [54930], [54931], [54932], [54933], [54938], [54943], [54944], [54945], [54946], [54947], [54948], [54950], [54951], [54952], [54956], [54959], [54960], [54961], [54962], [54964], [54965], [54969], [54970], [54971], [54972], [54996], [55000], [55011], [55013], [55014], [55015], [55016], [55017], [55020], [55021], [55023], [55027], [55028], [55034], [55036], [55037], [55038], [55039], [55049], [55050], [55060], [55062], [55064], [55065], [55076], [55077], [55078], [55081], [55090], [55100].
Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
See #56788.
Built from https://develop.svn.wordpress.org/trunk@55104
git-svn-id: http://core.svn.wordpress.org/trunk@54637 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2023-01-19 19:21:15 -05:00
function rest_filter_response_by_context ( $response_data , $schema , $context ) {
2020-10-20 14:24:09 -04:00
if ( isset ( $schema [ 'anyOf' ] ) ) {
Code Modernization: Rename parameters that use reserved keywords in `phpunit/tests/rest-api/rest-*-controller.php`.
While using reserved PHP keywords as parameter name labels is allowed, in the context of function calls using named parameters in PHP 8.0+, this will easily lead to confusion. To avoid that, it is recommended not to use reserved keywords as function parameter names.
This commit:
* Renames the `$object` parameter to `$response_data` in:
* `WP_Test_REST_Attachments_Controller::additional_field_get_callback()`
* `WP_Test_REST_Autosaves_Controller::additional_field_get_callback()`
* `WP_Test_REST_Categories_Controller::additional_field_get_callback()`
* `WP_Test_REST_Comments_Controller::additional_field_get_callback()`
* `WP_Test_REST_Post_Statuses_Controller::additional_field_get_callback()`
* `WP_Test_REST_Post_Types_Controller::additional_field_get_callback()`
* `WP_Test_REST_Posts_Controller::additional_field_get_callback()`
* `WP_Test_REST_Revisions_Controller::additional_field_get_callback()`
* `WP_Test_REST_Tags_Controller::additional_field_get_callback()`
* `WP_Test_REST_Users_Controller::additional_field_get_callback()`
* Amends the `$data` and `$prepared` parameters for consistency in:
* `WP_REST_Controller::add_additional_fields_to_object()`
* `WP_REST_Controller::filter_response_by_context()`
* `rest_filter_response_by_context()`
Follow-up to [52946], [52996], [52997], [52998], [53003], [53014], [53029], [53039], [53116], [53117], [53137], [53174], [53184], [53185], [53192], [53193], [53198], [53203], [53207], [53215], [53216], [53220], [53230], [53232], [53236], [53239], [53240], [53242], [53243], [53245], [53246], [53257], [53269], [53270], [53271], [53272], [53273], [53274], [53275], [53276], [53277], [53281], [53283], [53284], [53285], [53287], [53364], [53365], [54927], [54929], [54930], [54931], [54932], [54933], [54938], [54943], [54944], [54945], [54946], [54947], [54948], [54950], [54951], [54952], [54956], [54959], [54960], [54961], [54962], [54964], [54965], [54969], [54970], [54971], [54972], [54996], [55000], [55011], [55013], [55014], [55015], [55016], [55017], [55020], [55021], [55023], [55027], [55028], [55034], [55036], [55037], [55038], [55039], [55049], [55050], [55060], [55062], [55064], [55065], [55076], [55077], [55078], [55081], [55090], [55100].
Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
See #56788.
Built from https://develop.svn.wordpress.org/trunk@55104
git-svn-id: http://core.svn.wordpress.org/trunk@54637 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2023-01-19 19:21:15 -05:00
$matching_schema = rest_find_any_matching_schema ( $response_data , $schema , '' );
2020-10-20 14:24:09 -04:00
if ( ! is_wp_error ( $matching_schema ) ) {
if ( ! isset ( $schema [ 'type' ] ) ) {
$schema [ 'type' ] = $matching_schema [ 'type' ];
}
Code Modernization: Rename parameters that use reserved keywords in `phpunit/tests/rest-api/rest-*-controller.php`.
While using reserved PHP keywords as parameter name labels is allowed, in the context of function calls using named parameters in PHP 8.0+, this will easily lead to confusion. To avoid that, it is recommended not to use reserved keywords as function parameter names.
This commit:
* Renames the `$object` parameter to `$response_data` in:
* `WP_Test_REST_Attachments_Controller::additional_field_get_callback()`
* `WP_Test_REST_Autosaves_Controller::additional_field_get_callback()`
* `WP_Test_REST_Categories_Controller::additional_field_get_callback()`
* `WP_Test_REST_Comments_Controller::additional_field_get_callback()`
* `WP_Test_REST_Post_Statuses_Controller::additional_field_get_callback()`
* `WP_Test_REST_Post_Types_Controller::additional_field_get_callback()`
* `WP_Test_REST_Posts_Controller::additional_field_get_callback()`
* `WP_Test_REST_Revisions_Controller::additional_field_get_callback()`
* `WP_Test_REST_Tags_Controller::additional_field_get_callback()`
* `WP_Test_REST_Users_Controller::additional_field_get_callback()`
* Amends the `$data` and `$prepared` parameters for consistency in:
* `WP_REST_Controller::add_additional_fields_to_object()`
* `WP_REST_Controller::filter_response_by_context()`
* `rest_filter_response_by_context()`
Follow-up to [52946], [52996], [52997], [52998], [53003], [53014], [53029], [53039], [53116], [53117], [53137], [53174], [53184], [53185], [53192], [53193], [53198], [53203], [53207], [53215], [53216], [53220], [53230], [53232], [53236], [53239], [53240], [53242], [53243], [53245], [53246], [53257], [53269], [53270], [53271], [53272], [53273], [53274], [53275], [53276], [53277], [53281], [53283], [53284], [53285], [53287], [53364], [53365], [54927], [54929], [54930], [54931], [54932], [54933], [54938], [54943], [54944], [54945], [54946], [54947], [54948], [54950], [54951], [54952], [54956], [54959], [54960], [54961], [54962], [54964], [54965], [54969], [54970], [54971], [54972], [54996], [55000], [55011], [55013], [55014], [55015], [55016], [55017], [55020], [55021], [55023], [55027], [55028], [55034], [55036], [55037], [55038], [55039], [55049], [55050], [55060], [55062], [55064], [55065], [55076], [55077], [55078], [55081], [55090], [55100].
Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
See #56788.
Built from https://develop.svn.wordpress.org/trunk@55104
git-svn-id: http://core.svn.wordpress.org/trunk@54637 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2023-01-19 19:21:15 -05:00
$response_data = rest_filter_response_by_context ( $response_data , $matching_schema , $context );
2020-10-20 14:24:09 -04:00
}
}
if ( isset ( $schema [ 'oneOf' ] ) ) {
Code Modernization: Rename parameters that use reserved keywords in `phpunit/tests/rest-api/rest-*-controller.php`.
While using reserved PHP keywords as parameter name labels is allowed, in the context of function calls using named parameters in PHP 8.0+, this will easily lead to confusion. To avoid that, it is recommended not to use reserved keywords as function parameter names.
This commit:
* Renames the `$object` parameter to `$response_data` in:
* `WP_Test_REST_Attachments_Controller::additional_field_get_callback()`
* `WP_Test_REST_Autosaves_Controller::additional_field_get_callback()`
* `WP_Test_REST_Categories_Controller::additional_field_get_callback()`
* `WP_Test_REST_Comments_Controller::additional_field_get_callback()`
* `WP_Test_REST_Post_Statuses_Controller::additional_field_get_callback()`
* `WP_Test_REST_Post_Types_Controller::additional_field_get_callback()`
* `WP_Test_REST_Posts_Controller::additional_field_get_callback()`
* `WP_Test_REST_Revisions_Controller::additional_field_get_callback()`
* `WP_Test_REST_Tags_Controller::additional_field_get_callback()`
* `WP_Test_REST_Users_Controller::additional_field_get_callback()`
* Amends the `$data` and `$prepared` parameters for consistency in:
* `WP_REST_Controller::add_additional_fields_to_object()`
* `WP_REST_Controller::filter_response_by_context()`
* `rest_filter_response_by_context()`
Follow-up to [52946], [52996], [52997], [52998], [53003], [53014], [53029], [53039], [53116], [53117], [53137], [53174], [53184], [53185], [53192], [53193], [53198], [53203], [53207], [53215], [53216], [53220], [53230], [53232], [53236], [53239], [53240], [53242], [53243], [53245], [53246], [53257], [53269], [53270], [53271], [53272], [53273], [53274], [53275], [53276], [53277], [53281], [53283], [53284], [53285], [53287], [53364], [53365], [54927], [54929], [54930], [54931], [54932], [54933], [54938], [54943], [54944], [54945], [54946], [54947], [54948], [54950], [54951], [54952], [54956], [54959], [54960], [54961], [54962], [54964], [54965], [54969], [54970], [54971], [54972], [54996], [55000], [55011], [55013], [55014], [55015], [55016], [55017], [55020], [55021], [55023], [55027], [55028], [55034], [55036], [55037], [55038], [55039], [55049], [55050], [55060], [55062], [55064], [55065], [55076], [55077], [55078], [55081], [55090], [55100].
Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
See #56788.
Built from https://develop.svn.wordpress.org/trunk@55104
git-svn-id: http://core.svn.wordpress.org/trunk@54637 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2023-01-19 19:21:15 -05:00
$matching_schema = rest_find_one_matching_schema ( $response_data , $schema , '' , true );
2020-10-20 14:24:09 -04:00
if ( ! is_wp_error ( $matching_schema ) ) {
if ( ! isset ( $schema [ 'type' ] ) ) {
$schema [ 'type' ] = $matching_schema [ 'type' ];
}
Code Modernization: Rename parameters that use reserved keywords in `phpunit/tests/rest-api/rest-*-controller.php`.
While using reserved PHP keywords as parameter name labels is allowed, in the context of function calls using named parameters in PHP 8.0+, this will easily lead to confusion. To avoid that, it is recommended not to use reserved keywords as function parameter names.
This commit:
* Renames the `$object` parameter to `$response_data` in:
* `WP_Test_REST_Attachments_Controller::additional_field_get_callback()`
* `WP_Test_REST_Autosaves_Controller::additional_field_get_callback()`
* `WP_Test_REST_Categories_Controller::additional_field_get_callback()`
* `WP_Test_REST_Comments_Controller::additional_field_get_callback()`
* `WP_Test_REST_Post_Statuses_Controller::additional_field_get_callback()`
* `WP_Test_REST_Post_Types_Controller::additional_field_get_callback()`
* `WP_Test_REST_Posts_Controller::additional_field_get_callback()`
* `WP_Test_REST_Revisions_Controller::additional_field_get_callback()`
* `WP_Test_REST_Tags_Controller::additional_field_get_callback()`
* `WP_Test_REST_Users_Controller::additional_field_get_callback()`
* Amends the `$data` and `$prepared` parameters for consistency in:
* `WP_REST_Controller::add_additional_fields_to_object()`
* `WP_REST_Controller::filter_response_by_context()`
* `rest_filter_response_by_context()`
Follow-up to [52946], [52996], [52997], [52998], [53003], [53014], [53029], [53039], [53116], [53117], [53137], [53174], [53184], [53185], [53192], [53193], [53198], [53203], [53207], [53215], [53216], [53220], [53230], [53232], [53236], [53239], [53240], [53242], [53243], [53245], [53246], [53257], [53269], [53270], [53271], [53272], [53273], [53274], [53275], [53276], [53277], [53281], [53283], [53284], [53285], [53287], [53364], [53365], [54927], [54929], [54930], [54931], [54932], [54933], [54938], [54943], [54944], [54945], [54946], [54947], [54948], [54950], [54951], [54952], [54956], [54959], [54960], [54961], [54962], [54964], [54965], [54969], [54970], [54971], [54972], [54996], [55000], [55011], [55013], [55014], [55015], [55016], [55017], [55020], [55021], [55023], [55027], [55028], [55034], [55036], [55037], [55038], [55039], [55049], [55050], [55060], [55062], [55064], [55065], [55076], [55077], [55078], [55081], [55090], [55100].
Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
See #56788.
Built from https://develop.svn.wordpress.org/trunk@55104
git-svn-id: http://core.svn.wordpress.org/trunk@54637 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2023-01-19 19:21:15 -05:00
$response_data = rest_filter_response_by_context ( $response_data , $matching_schema , $context );
2020-10-20 14:24:09 -04:00
}
}
Code Modernization: Rename parameters that use reserved keywords in `phpunit/tests/rest-api/rest-*-controller.php`.
While using reserved PHP keywords as parameter name labels is allowed, in the context of function calls using named parameters in PHP 8.0+, this will easily lead to confusion. To avoid that, it is recommended not to use reserved keywords as function parameter names.
This commit:
* Renames the `$object` parameter to `$response_data` in:
* `WP_Test_REST_Attachments_Controller::additional_field_get_callback()`
* `WP_Test_REST_Autosaves_Controller::additional_field_get_callback()`
* `WP_Test_REST_Categories_Controller::additional_field_get_callback()`
* `WP_Test_REST_Comments_Controller::additional_field_get_callback()`
* `WP_Test_REST_Post_Statuses_Controller::additional_field_get_callback()`
* `WP_Test_REST_Post_Types_Controller::additional_field_get_callback()`
* `WP_Test_REST_Posts_Controller::additional_field_get_callback()`
* `WP_Test_REST_Revisions_Controller::additional_field_get_callback()`
* `WP_Test_REST_Tags_Controller::additional_field_get_callback()`
* `WP_Test_REST_Users_Controller::additional_field_get_callback()`
* Amends the `$data` and `$prepared` parameters for consistency in:
* `WP_REST_Controller::add_additional_fields_to_object()`
* `WP_REST_Controller::filter_response_by_context()`
* `rest_filter_response_by_context()`
Follow-up to [52946], [52996], [52997], [52998], [53003], [53014], [53029], [53039], [53116], [53117], [53137], [53174], [53184], [53185], [53192], [53193], [53198], [53203], [53207], [53215], [53216], [53220], [53230], [53232], [53236], [53239], [53240], [53242], [53243], [53245], [53246], [53257], [53269], [53270], [53271], [53272], [53273], [53274], [53275], [53276], [53277], [53281], [53283], [53284], [53285], [53287], [53364], [53365], [54927], [54929], [54930], [54931], [54932], [54933], [54938], [54943], [54944], [54945], [54946], [54947], [54948], [54950], [54951], [54952], [54956], [54959], [54960], [54961], [54962], [54964], [54965], [54969], [54970], [54971], [54972], [54996], [55000], [55011], [55013], [55014], [55015], [55016], [55017], [55020], [55021], [55023], [55027], [55028], [55034], [55036], [55037], [55038], [55039], [55049], [55050], [55060], [55062], [55064], [55065], [55076], [55077], [55078], [55081], [55090], [55100].
Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
See #56788.
Built from https://develop.svn.wordpress.org/trunk@55104
git-svn-id: http://core.svn.wordpress.org/trunk@54637 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2023-01-19 19:21:15 -05:00
if ( ! is_array ( $response_data ) && ! is_object ( $response_data ) ) {
return $response_data ;
2020-05-03 22:46:05 -04:00
}
if ( isset ( $schema [ 'type' ] ) ) {
$type = $schema [ 'type' ];
} elseif ( isset ( $schema [ 'properties' ] ) ) {
$type = 'object' ; // Back compat if a developer accidentally omitted the type.
} else {
Code Modernization: Rename parameters that use reserved keywords in `phpunit/tests/rest-api/rest-*-controller.php`.
While using reserved PHP keywords as parameter name labels is allowed, in the context of function calls using named parameters in PHP 8.0+, this will easily lead to confusion. To avoid that, it is recommended not to use reserved keywords as function parameter names.
This commit:
* Renames the `$object` parameter to `$response_data` in:
* `WP_Test_REST_Attachments_Controller::additional_field_get_callback()`
* `WP_Test_REST_Autosaves_Controller::additional_field_get_callback()`
* `WP_Test_REST_Categories_Controller::additional_field_get_callback()`
* `WP_Test_REST_Comments_Controller::additional_field_get_callback()`
* `WP_Test_REST_Post_Statuses_Controller::additional_field_get_callback()`
* `WP_Test_REST_Post_Types_Controller::additional_field_get_callback()`
* `WP_Test_REST_Posts_Controller::additional_field_get_callback()`
* `WP_Test_REST_Revisions_Controller::additional_field_get_callback()`
* `WP_Test_REST_Tags_Controller::additional_field_get_callback()`
* `WP_Test_REST_Users_Controller::additional_field_get_callback()`
* Amends the `$data` and `$prepared` parameters for consistency in:
* `WP_REST_Controller::add_additional_fields_to_object()`
* `WP_REST_Controller::filter_response_by_context()`
* `rest_filter_response_by_context()`
Follow-up to [52946], [52996], [52997], [52998], [53003], [53014], [53029], [53039], [53116], [53117], [53137], [53174], [53184], [53185], [53192], [53193], [53198], [53203], [53207], [53215], [53216], [53220], [53230], [53232], [53236], [53239], [53240], [53242], [53243], [53245], [53246], [53257], [53269], [53270], [53271], [53272], [53273], [53274], [53275], [53276], [53277], [53281], [53283], [53284], [53285], [53287], [53364], [53365], [54927], [54929], [54930], [54931], [54932], [54933], [54938], [54943], [54944], [54945], [54946], [54947], [54948], [54950], [54951], [54952], [54956], [54959], [54960], [54961], [54962], [54964], [54965], [54969], [54970], [54971], [54972], [54996], [55000], [55011], [55013], [55014], [55015], [55016], [55017], [55020], [55021], [55023], [55027], [55028], [55034], [55036], [55037], [55038], [55039], [55049], [55050], [55060], [55062], [55064], [55065], [55076], [55077], [55078], [55081], [55090], [55100].
Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
See #56788.
Built from https://develop.svn.wordpress.org/trunk@55104
git-svn-id: http://core.svn.wordpress.org/trunk@54637 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2023-01-19 19:21:15 -05:00
return $response_data ;
2020-05-03 22:46:05 -04:00
}
2020-07-21 17:22:03 -04:00
$is_array_type = 'array' === $type || ( is_array ( $type ) && in_array ( 'array' , $type , true ) );
$is_object_type = 'object' === $type || ( is_array ( $type ) && in_array ( 'object' , $type , true ) );
if ( $is_array_type && $is_object_type ) {
Code Modernization: Rename parameters that use reserved keywords in `phpunit/tests/rest-api/rest-*-controller.php`.
While using reserved PHP keywords as parameter name labels is allowed, in the context of function calls using named parameters in PHP 8.0+, this will easily lead to confusion. To avoid that, it is recommended not to use reserved keywords as function parameter names.
This commit:
* Renames the `$object` parameter to `$response_data` in:
* `WP_Test_REST_Attachments_Controller::additional_field_get_callback()`
* `WP_Test_REST_Autosaves_Controller::additional_field_get_callback()`
* `WP_Test_REST_Categories_Controller::additional_field_get_callback()`
* `WP_Test_REST_Comments_Controller::additional_field_get_callback()`
* `WP_Test_REST_Post_Statuses_Controller::additional_field_get_callback()`
* `WP_Test_REST_Post_Types_Controller::additional_field_get_callback()`
* `WP_Test_REST_Posts_Controller::additional_field_get_callback()`
* `WP_Test_REST_Revisions_Controller::additional_field_get_callback()`
* `WP_Test_REST_Tags_Controller::additional_field_get_callback()`
* `WP_Test_REST_Users_Controller::additional_field_get_callback()`
* Amends the `$data` and `$prepared` parameters for consistency in:
* `WP_REST_Controller::add_additional_fields_to_object()`
* `WP_REST_Controller::filter_response_by_context()`
* `rest_filter_response_by_context()`
Follow-up to [52946], [52996], [52997], [52998], [53003], [53014], [53029], [53039], [53116], [53117], [53137], [53174], [53184], [53185], [53192], [53193], [53198], [53203], [53207], [53215], [53216], [53220], [53230], [53232], [53236], [53239], [53240], [53242], [53243], [53245], [53246], [53257], [53269], [53270], [53271], [53272], [53273], [53274], [53275], [53276], [53277], [53281], [53283], [53284], [53285], [53287], [53364], [53365], [54927], [54929], [54930], [54931], [54932], [54933], [54938], [54943], [54944], [54945], [54946], [54947], [54948], [54950], [54951], [54952], [54956], [54959], [54960], [54961], [54962], [54964], [54965], [54969], [54970], [54971], [54972], [54996], [55000], [55011], [55013], [55014], [55015], [55016], [55017], [55020], [55021], [55023], [55027], [55028], [55034], [55036], [55037], [55038], [55039], [55049], [55050], [55060], [55062], [55064], [55065], [55076], [55077], [55078], [55081], [55090], [55100].
Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
See #56788.
Built from https://develop.svn.wordpress.org/trunk@55104
git-svn-id: http://core.svn.wordpress.org/trunk@54637 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2023-01-19 19:21:15 -05:00
if ( rest_is_array ( $response_data ) ) {
2020-07-21 17:22:03 -04:00
$is_object_type = false ;
} else {
$is_array_type = false ;
}
}
$has_additional_properties = $is_object_type && isset ( $schema [ 'additionalProperties' ] ) && is_array ( $schema [ 'additionalProperties' ] );
Code Modernization: Rename parameters that use reserved keywords in `phpunit/tests/rest-api/rest-*-controller.php`.
While using reserved PHP keywords as parameter name labels is allowed, in the context of function calls using named parameters in PHP 8.0+, this will easily lead to confusion. To avoid that, it is recommended not to use reserved keywords as function parameter names.
This commit:
* Renames the `$object` parameter to `$response_data` in:
* `WP_Test_REST_Attachments_Controller::additional_field_get_callback()`
* `WP_Test_REST_Autosaves_Controller::additional_field_get_callback()`
* `WP_Test_REST_Categories_Controller::additional_field_get_callback()`
* `WP_Test_REST_Comments_Controller::additional_field_get_callback()`
* `WP_Test_REST_Post_Statuses_Controller::additional_field_get_callback()`
* `WP_Test_REST_Post_Types_Controller::additional_field_get_callback()`
* `WP_Test_REST_Posts_Controller::additional_field_get_callback()`
* `WP_Test_REST_Revisions_Controller::additional_field_get_callback()`
* `WP_Test_REST_Tags_Controller::additional_field_get_callback()`
* `WP_Test_REST_Users_Controller::additional_field_get_callback()`
* Amends the `$data` and `$prepared` parameters for consistency in:
* `WP_REST_Controller::add_additional_fields_to_object()`
* `WP_REST_Controller::filter_response_by_context()`
* `rest_filter_response_by_context()`
Follow-up to [52946], [52996], [52997], [52998], [53003], [53014], [53029], [53039], [53116], [53117], [53137], [53174], [53184], [53185], [53192], [53193], [53198], [53203], [53207], [53215], [53216], [53220], [53230], [53232], [53236], [53239], [53240], [53242], [53243], [53245], [53246], [53257], [53269], [53270], [53271], [53272], [53273], [53274], [53275], [53276], [53277], [53281], [53283], [53284], [53285], [53287], [53364], [53365], [54927], [54929], [54930], [54931], [54932], [54933], [54938], [54943], [54944], [54945], [54946], [54947], [54948], [54950], [54951], [54952], [54956], [54959], [54960], [54961], [54962], [54964], [54965], [54969], [54970], [54971], [54972], [54996], [55000], [55011], [55013], [55014], [55015], [55016], [55017], [55020], [55021], [55023], [55027], [55028], [55034], [55036], [55037], [55038], [55039], [55049], [55050], [55060], [55062], [55064], [55065], [55076], [55077], [55078], [55081], [55090], [55100].
Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
See #56788.
Built from https://develop.svn.wordpress.org/trunk@55104
git-svn-id: http://core.svn.wordpress.org/trunk@54637 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2023-01-19 19:21:15 -05:00
foreach ( $response_data as $key => $value ) {
2020-05-03 22:46:05 -04:00
$check = array ();
2020-07-21 17:22:03 -04:00
if ( $is_array_type ) {
2020-05-03 22:46:05 -04:00
$check = isset ( $schema [ 'items' ] ) ? $schema [ 'items' ] : array ();
2020-07-21 17:22:03 -04:00
} elseif ( $is_object_type ) {
2020-05-03 22:46:05 -04:00
if ( isset ( $schema [ 'properties' ][ $key ] ) ) {
$check = $schema [ 'properties' ][ $key ];
2020-09-30 22:49:12 -04:00
} else {
$pattern_property_schema = rest_find_matching_pattern_property_schema ( $key , $schema );
if ( null !== $pattern_property_schema ) {
$check = $pattern_property_schema ;
} elseif ( $has_additional_properties ) {
$check = $schema [ 'additionalProperties' ];
}
2020-05-03 22:46:05 -04:00
}
}
if ( ! isset ( $check [ 'context' ] ) ) {
continue ;
}
if ( ! in_array ( $context , $check [ 'context' ], true ) ) {
2020-07-21 17:22:03 -04:00
if ( $is_array_type ) {
// All array items share schema, so there's no need to check each one.
Code Modernization: Rename parameters that use reserved keywords in `phpunit/tests/rest-api/rest-*-controller.php`.
While using reserved PHP keywords as parameter name labels is allowed, in the context of function calls using named parameters in PHP 8.0+, this will easily lead to confusion. To avoid that, it is recommended not to use reserved keywords as function parameter names.
This commit:
* Renames the `$object` parameter to `$response_data` in:
* `WP_Test_REST_Attachments_Controller::additional_field_get_callback()`
* `WP_Test_REST_Autosaves_Controller::additional_field_get_callback()`
* `WP_Test_REST_Categories_Controller::additional_field_get_callback()`
* `WP_Test_REST_Comments_Controller::additional_field_get_callback()`
* `WP_Test_REST_Post_Statuses_Controller::additional_field_get_callback()`
* `WP_Test_REST_Post_Types_Controller::additional_field_get_callback()`
* `WP_Test_REST_Posts_Controller::additional_field_get_callback()`
* `WP_Test_REST_Revisions_Controller::additional_field_get_callback()`
* `WP_Test_REST_Tags_Controller::additional_field_get_callback()`
* `WP_Test_REST_Users_Controller::additional_field_get_callback()`
* Amends the `$data` and `$prepared` parameters for consistency in:
* `WP_REST_Controller::add_additional_fields_to_object()`
* `WP_REST_Controller::filter_response_by_context()`
* `rest_filter_response_by_context()`
Follow-up to [52946], [52996], [52997], [52998], [53003], [53014], [53029], [53039], [53116], [53117], [53137], [53174], [53184], [53185], [53192], [53193], [53198], [53203], [53207], [53215], [53216], [53220], [53230], [53232], [53236], [53239], [53240], [53242], [53243], [53245], [53246], [53257], [53269], [53270], [53271], [53272], [53273], [53274], [53275], [53276], [53277], [53281], [53283], [53284], [53285], [53287], [53364], [53365], [54927], [54929], [54930], [54931], [54932], [54933], [54938], [54943], [54944], [54945], [54946], [54947], [54948], [54950], [54951], [54952], [54956], [54959], [54960], [54961], [54962], [54964], [54965], [54969], [54970], [54971], [54972], [54996], [55000], [55011], [55013], [55014], [55015], [55016], [55017], [55020], [55021], [55023], [55027], [55028], [55034], [55036], [55037], [55038], [55039], [55049], [55050], [55060], [55062], [55064], [55065], [55076], [55077], [55078], [55081], [55090], [55100].
Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
See #56788.
Built from https://develop.svn.wordpress.org/trunk@55104
git-svn-id: http://core.svn.wordpress.org/trunk@54637 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2023-01-19 19:21:15 -05:00
$response_data = array ();
2020-07-21 17:22:03 -04:00
break ;
}
Code Modernization: Rename parameters that use reserved keywords in `phpunit/tests/rest-api/rest-*-controller.php`.
While using reserved PHP keywords as parameter name labels is allowed, in the context of function calls using named parameters in PHP 8.0+, this will easily lead to confusion. To avoid that, it is recommended not to use reserved keywords as function parameter names.
This commit:
* Renames the `$object` parameter to `$response_data` in:
* `WP_Test_REST_Attachments_Controller::additional_field_get_callback()`
* `WP_Test_REST_Autosaves_Controller::additional_field_get_callback()`
* `WP_Test_REST_Categories_Controller::additional_field_get_callback()`
* `WP_Test_REST_Comments_Controller::additional_field_get_callback()`
* `WP_Test_REST_Post_Statuses_Controller::additional_field_get_callback()`
* `WP_Test_REST_Post_Types_Controller::additional_field_get_callback()`
* `WP_Test_REST_Posts_Controller::additional_field_get_callback()`
* `WP_Test_REST_Revisions_Controller::additional_field_get_callback()`
* `WP_Test_REST_Tags_Controller::additional_field_get_callback()`
* `WP_Test_REST_Users_Controller::additional_field_get_callback()`
* Amends the `$data` and `$prepared` parameters for consistency in:
* `WP_REST_Controller::add_additional_fields_to_object()`
* `WP_REST_Controller::filter_response_by_context()`
* `rest_filter_response_by_context()`
Follow-up to [52946], [52996], [52997], [52998], [53003], [53014], [53029], [53039], [53116], [53117], [53137], [53174], [53184], [53185], [53192], [53193], [53198], [53203], [53207], [53215], [53216], [53220], [53230], [53232], [53236], [53239], [53240], [53242], [53243], [53245], [53246], [53257], [53269], [53270], [53271], [53272], [53273], [53274], [53275], [53276], [53277], [53281], [53283], [53284], [53285], [53287], [53364], [53365], [54927], [54929], [54930], [54931], [54932], [54933], [54938], [54943], [54944], [54945], [54946], [54947], [54948], [54950], [54951], [54952], [54956], [54959], [54960], [54961], [54962], [54964], [54965], [54969], [54970], [54971], [54972], [54996], [55000], [55011], [55013], [55014], [55015], [55016], [55017], [55020], [55021], [55023], [55027], [55028], [55034], [55036], [55037], [55038], [55039], [55049], [55050], [55060], [55062], [55064], [55065], [55076], [55077], [55078], [55081], [55090], [55100].
Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
See #56788.
Built from https://develop.svn.wordpress.org/trunk@55104
git-svn-id: http://core.svn.wordpress.org/trunk@54637 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2023-01-19 19:21:15 -05:00
if ( is_object ( $response_data ) ) {
unset ( $response_data -> $key );
2020-05-03 22:46:05 -04:00
} else {
Code Modernization: Rename parameters that use reserved keywords in `phpunit/tests/rest-api/rest-*-controller.php`.
While using reserved PHP keywords as parameter name labels is allowed, in the context of function calls using named parameters in PHP 8.0+, this will easily lead to confusion. To avoid that, it is recommended not to use reserved keywords as function parameter names.
This commit:
* Renames the `$object` parameter to `$response_data` in:
* `WP_Test_REST_Attachments_Controller::additional_field_get_callback()`
* `WP_Test_REST_Autosaves_Controller::additional_field_get_callback()`
* `WP_Test_REST_Categories_Controller::additional_field_get_callback()`
* `WP_Test_REST_Comments_Controller::additional_field_get_callback()`
* `WP_Test_REST_Post_Statuses_Controller::additional_field_get_callback()`
* `WP_Test_REST_Post_Types_Controller::additional_field_get_callback()`
* `WP_Test_REST_Posts_Controller::additional_field_get_callback()`
* `WP_Test_REST_Revisions_Controller::additional_field_get_callback()`
* `WP_Test_REST_Tags_Controller::additional_field_get_callback()`
* `WP_Test_REST_Users_Controller::additional_field_get_callback()`
* Amends the `$data` and `$prepared` parameters for consistency in:
* `WP_REST_Controller::add_additional_fields_to_object()`
* `WP_REST_Controller::filter_response_by_context()`
* `rest_filter_response_by_context()`
Follow-up to [52946], [52996], [52997], [52998], [53003], [53014], [53029], [53039], [53116], [53117], [53137], [53174], [53184], [53185], [53192], [53193], [53198], [53203], [53207], [53215], [53216], [53220], [53230], [53232], [53236], [53239], [53240], [53242], [53243], [53245], [53246], [53257], [53269], [53270], [53271], [53272], [53273], [53274], [53275], [53276], [53277], [53281], [53283], [53284], [53285], [53287], [53364], [53365], [54927], [54929], [54930], [54931], [54932], [54933], [54938], [54943], [54944], [54945], [54946], [54947], [54948], [54950], [54951], [54952], [54956], [54959], [54960], [54961], [54962], [54964], [54965], [54969], [54970], [54971], [54972], [54996], [55000], [55011], [55013], [55014], [55015], [55016], [55017], [55020], [55021], [55023], [55027], [55028], [55034], [55036], [55037], [55038], [55039], [55049], [55050], [55060], [55062], [55064], [55065], [55076], [55077], [55078], [55081], [55090], [55100].
Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
See #56788.
Built from https://develop.svn.wordpress.org/trunk@55104
git-svn-id: http://core.svn.wordpress.org/trunk@54637 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2023-01-19 19:21:15 -05:00
unset ( $response_data [ $key ] );
2020-05-03 22:46:05 -04:00
}
} elseif ( is_array ( $value ) || is_object ( $value ) ) {
$new_value = rest_filter_response_by_context ( $value , $check , $context );
Code Modernization: Rename parameters that use reserved keywords in `phpunit/tests/rest-api/rest-*-controller.php`.
While using reserved PHP keywords as parameter name labels is allowed, in the context of function calls using named parameters in PHP 8.0+, this will easily lead to confusion. To avoid that, it is recommended not to use reserved keywords as function parameter names.
This commit:
* Renames the `$object` parameter to `$response_data` in:
* `WP_Test_REST_Attachments_Controller::additional_field_get_callback()`
* `WP_Test_REST_Autosaves_Controller::additional_field_get_callback()`
* `WP_Test_REST_Categories_Controller::additional_field_get_callback()`
* `WP_Test_REST_Comments_Controller::additional_field_get_callback()`
* `WP_Test_REST_Post_Statuses_Controller::additional_field_get_callback()`
* `WP_Test_REST_Post_Types_Controller::additional_field_get_callback()`
* `WP_Test_REST_Posts_Controller::additional_field_get_callback()`
* `WP_Test_REST_Revisions_Controller::additional_field_get_callback()`
* `WP_Test_REST_Tags_Controller::additional_field_get_callback()`
* `WP_Test_REST_Users_Controller::additional_field_get_callback()`
* Amends the `$data` and `$prepared` parameters for consistency in:
* `WP_REST_Controller::add_additional_fields_to_object()`
* `WP_REST_Controller::filter_response_by_context()`
* `rest_filter_response_by_context()`
Follow-up to [52946], [52996], [52997], [52998], [53003], [53014], [53029], [53039], [53116], [53117], [53137], [53174], [53184], [53185], [53192], [53193], [53198], [53203], [53207], [53215], [53216], [53220], [53230], [53232], [53236], [53239], [53240], [53242], [53243], [53245], [53246], [53257], [53269], [53270], [53271], [53272], [53273], [53274], [53275], [53276], [53277], [53281], [53283], [53284], [53285], [53287], [53364], [53365], [54927], [54929], [54930], [54931], [54932], [54933], [54938], [54943], [54944], [54945], [54946], [54947], [54948], [54950], [54951], [54952], [54956], [54959], [54960], [54961], [54962], [54964], [54965], [54969], [54970], [54971], [54972], [54996], [55000], [55011], [55013], [55014], [55015], [55016], [55017], [55020], [55021], [55023], [55027], [55028], [55034], [55036], [55037], [55038], [55039], [55049], [55050], [55060], [55062], [55064], [55065], [55076], [55077], [55078], [55081], [55090], [55100].
Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
See #56788.
Built from https://develop.svn.wordpress.org/trunk@55104
git-svn-id: http://core.svn.wordpress.org/trunk@54637 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2023-01-19 19:21:15 -05:00
if ( is_object ( $response_data ) ) {
$response_data -> $key = $new_value ;
2020-05-03 22:46:05 -04:00
} else {
Code Modernization: Rename parameters that use reserved keywords in `phpunit/tests/rest-api/rest-*-controller.php`.
While using reserved PHP keywords as parameter name labels is allowed, in the context of function calls using named parameters in PHP 8.0+, this will easily lead to confusion. To avoid that, it is recommended not to use reserved keywords as function parameter names.
This commit:
* Renames the `$object` parameter to `$response_data` in:
* `WP_Test_REST_Attachments_Controller::additional_field_get_callback()`
* `WP_Test_REST_Autosaves_Controller::additional_field_get_callback()`
* `WP_Test_REST_Categories_Controller::additional_field_get_callback()`
* `WP_Test_REST_Comments_Controller::additional_field_get_callback()`
* `WP_Test_REST_Post_Statuses_Controller::additional_field_get_callback()`
* `WP_Test_REST_Post_Types_Controller::additional_field_get_callback()`
* `WP_Test_REST_Posts_Controller::additional_field_get_callback()`
* `WP_Test_REST_Revisions_Controller::additional_field_get_callback()`
* `WP_Test_REST_Tags_Controller::additional_field_get_callback()`
* `WP_Test_REST_Users_Controller::additional_field_get_callback()`
* Amends the `$data` and `$prepared` parameters for consistency in:
* `WP_REST_Controller::add_additional_fields_to_object()`
* `WP_REST_Controller::filter_response_by_context()`
* `rest_filter_response_by_context()`
Follow-up to [52946], [52996], [52997], [52998], [53003], [53014], [53029], [53039], [53116], [53117], [53137], [53174], [53184], [53185], [53192], [53193], [53198], [53203], [53207], [53215], [53216], [53220], [53230], [53232], [53236], [53239], [53240], [53242], [53243], [53245], [53246], [53257], [53269], [53270], [53271], [53272], [53273], [53274], [53275], [53276], [53277], [53281], [53283], [53284], [53285], [53287], [53364], [53365], [54927], [54929], [54930], [54931], [54932], [54933], [54938], [54943], [54944], [54945], [54946], [54947], [54948], [54950], [54951], [54952], [54956], [54959], [54960], [54961], [54962], [54964], [54965], [54969], [54970], [54971], [54972], [54996], [55000], [55011], [55013], [55014], [55015], [55016], [55017], [55020], [55021], [55023], [55027], [55028], [55034], [55036], [55037], [55038], [55039], [55049], [55050], [55060], [55062], [55064], [55065], [55076], [55077], [55078], [55081], [55090], [55100].
Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
See #56788.
Built from https://develop.svn.wordpress.org/trunk@55104
git-svn-id: http://core.svn.wordpress.org/trunk@54637 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2023-01-19 19:21:15 -05:00
$response_data [ $key ] = $new_value ;
2020-05-03 22:46:05 -04:00
}
}
}
Code Modernization: Rename parameters that use reserved keywords in `phpunit/tests/rest-api/rest-*-controller.php`.
While using reserved PHP keywords as parameter name labels is allowed, in the context of function calls using named parameters in PHP 8.0+, this will easily lead to confusion. To avoid that, it is recommended not to use reserved keywords as function parameter names.
This commit:
* Renames the `$object` parameter to `$response_data` in:
* `WP_Test_REST_Attachments_Controller::additional_field_get_callback()`
* `WP_Test_REST_Autosaves_Controller::additional_field_get_callback()`
* `WP_Test_REST_Categories_Controller::additional_field_get_callback()`
* `WP_Test_REST_Comments_Controller::additional_field_get_callback()`
* `WP_Test_REST_Post_Statuses_Controller::additional_field_get_callback()`
* `WP_Test_REST_Post_Types_Controller::additional_field_get_callback()`
* `WP_Test_REST_Posts_Controller::additional_field_get_callback()`
* `WP_Test_REST_Revisions_Controller::additional_field_get_callback()`
* `WP_Test_REST_Tags_Controller::additional_field_get_callback()`
* `WP_Test_REST_Users_Controller::additional_field_get_callback()`
* Amends the `$data` and `$prepared` parameters for consistency in:
* `WP_REST_Controller::add_additional_fields_to_object()`
* `WP_REST_Controller::filter_response_by_context()`
* `rest_filter_response_by_context()`
Follow-up to [52946], [52996], [52997], [52998], [53003], [53014], [53029], [53039], [53116], [53117], [53137], [53174], [53184], [53185], [53192], [53193], [53198], [53203], [53207], [53215], [53216], [53220], [53230], [53232], [53236], [53239], [53240], [53242], [53243], [53245], [53246], [53257], [53269], [53270], [53271], [53272], [53273], [53274], [53275], [53276], [53277], [53281], [53283], [53284], [53285], [53287], [53364], [53365], [54927], [54929], [54930], [54931], [54932], [54933], [54938], [54943], [54944], [54945], [54946], [54947], [54948], [54950], [54951], [54952], [54956], [54959], [54960], [54961], [54962], [54964], [54965], [54969], [54970], [54971], [54972], [54996], [55000], [55011], [55013], [55014], [55015], [55016], [55017], [55020], [55021], [55023], [55027], [55028], [55034], [55036], [55037], [55038], [55039], [55049], [55050], [55060], [55062], [55064], [55065], [55076], [55077], [55078], [55081], [55090], [55100].
Props jrf, aristath, poena, justinahinon, SergeyBiryukov.
See #56788.
Built from https://develop.svn.wordpress.org/trunk@55104
git-svn-id: http://core.svn.wordpress.org/trunk@54637 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2023-01-19 19:21:15 -05:00
return $response_data ;
2020-05-03 22:46:05 -04:00
}
2020-06-25 18:13:10 -04:00
/**
* Sets the " additionalProperties " to false by default for all object definitions in the schema .
*
* @ since 5.5 . 0
2020-09-30 22:49:12 -04:00
* @ since 5.6 . 0 Support the " patternProperties " keyword .
2020-06-25 18:13:10 -04:00
*
* @ param array $schema The schema to modify .
* @ return array The modified schema .
*/
function rest_default_additional_properties_to_false ( $schema ) {
$type = ( array ) $schema [ 'type' ];
if ( in_array ( 'object' , $type , true ) ) {
if ( isset ( $schema [ 'properties' ] ) ) {
foreach ( $schema [ 'properties' ] as $key => $child_schema ) {
$schema [ 'properties' ][ $key ] = rest_default_additional_properties_to_false ( $child_schema );
}
}
2020-09-30 22:49:12 -04:00
if ( isset ( $schema [ 'patternProperties' ] ) ) {
foreach ( $schema [ 'patternProperties' ] as $key => $child_schema ) {
$schema [ 'patternProperties' ][ $key ] = rest_default_additional_properties_to_false ( $child_schema );
}
}
2020-06-25 18:13:10 -04:00
if ( ! isset ( $schema [ 'additionalProperties' ] ) ) {
$schema [ 'additionalProperties' ] = false ;
}
}
if ( in_array ( 'array' , $type , true ) ) {
if ( isset ( $schema [ 'items' ] ) ) {
$schema [ 'items' ] = rest_default_additional_properties_to_false ( $schema [ 'items' ] );
}
}
return $schema ;
}
2020-07-02 01:57:01 -04:00
/**
* Gets the REST API route for a post .
*
* @ since 5.5 . 0
*
* @ param int | WP_Post $post Post ID or post object .
2021-11-24 18:59:59 -05:00
* @ return string The route path with a leading slash for the given post ,
* or an empty string if there is not a route .
2020-07-02 01:57:01 -04:00
*/
function rest_get_route_for_post ( $post ) {
$post = get_post ( $post );
if ( ! $post instanceof WP_Post ) {
return '' ;
}
2021-10-31 19:16:58 -04:00
$post_type_route = rest_get_route_for_post_type_items ( $post -> post_type );
if ( ! $post_type_route ) {
2020-07-02 01:57:01 -04:00
return '' ;
}
2021-10-31 19:16:58 -04:00
$route = sprintf ( '%s/%d' , $post_type_route , $post -> ID );
2020-07-02 01:57:01 -04:00
/**
* Filters the REST API route for a post .
*
* @ since 5.5 . 0
*
* @ param string $route The route path .
* @ param WP_Post $post The post object .
*/
return apply_filters ( 'rest_route_for_post' , $route , $post );
}
2021-10-31 19:16:58 -04:00
/**
* Gets the REST API route for a post type .
*
* @ since 5.9 . 0
*
* @ param string $post_type The name of a registered post type .
2021-11-24 18:59:59 -05:00
* @ return string The route path with a leading slash for the given post type ,
* or an empty string if there is not a route .
2021-10-31 19:16:58 -04:00
*/
function rest_get_route_for_post_type_items ( $post_type ) {
$post_type = get_post_type_object ( $post_type );
if ( ! $post_type ) {
return '' ;
}
if ( ! $post_type -> show_in_rest ) {
return '' ;
}
$namespace = ! empty ( $post_type -> rest_namespace ) ? $post_type -> rest_namespace : 'wp/v2' ;
$rest_base = ! empty ( $post_type -> rest_base ) ? $post_type -> rest_base : $post_type -> name ;
$route = sprintf ( '/%s/%s' , $namespace , $rest_base );
/**
* Filters the REST API route for a post type .
*
* @ since 5.9 . 0
*
* @ param string $route The route path .
* @ param WP_Post_Type $post_type The post type object .
*/
return apply_filters ( 'rest_route_for_post_type_items' , $route , $post_type );
}
2020-07-02 01:57:01 -04:00
/**
* Gets the REST API route for a term .
*
* @ since 5.5 . 0
*
* @ param int | WP_Term $term Term ID or term object .
2021-11-24 18:59:59 -05:00
* @ return string The route path with a leading slash for the given term ,
* or an empty string if there is not a route .
2020-07-02 01:57:01 -04:00
*/
function rest_get_route_for_term ( $term ) {
$term = get_term ( $term );
if ( ! $term instanceof WP_Term ) {
return '' ;
}
2021-10-31 23:27:55 -04:00
$taxonomy_route = rest_get_route_for_taxonomy_items ( $term -> taxonomy );
if ( ! $taxonomy_route ) {
2020-07-02 01:57:01 -04:00
return '' ;
}
2021-10-31 23:27:55 -04:00
$route = sprintf ( '%s/%d' , $taxonomy_route , $term -> term_id );
2020-07-02 01:57:01 -04:00
/**
* Filters the REST API route for a term .
*
* @ since 5.5 . 0
*
* @ param string $route The route path .
* @ param WP_Term $term The term object .
*/
return apply_filters ( 'rest_route_for_term' , $route , $term );
}
2021-10-31 23:27:55 -04:00
/**
* Gets the REST API route for a taxonomy .
*
* @ since 5.9 . 0
*
* @ param string $taxonomy Name of taxonomy .
* @ return string The route path with a leading slash for the given taxonomy .
*/
function rest_get_route_for_taxonomy_items ( $taxonomy ) {
$taxonomy = get_taxonomy ( $taxonomy );
if ( ! $taxonomy ) {
return '' ;
}
if ( ! $taxonomy -> show_in_rest ) {
return '' ;
}
$namespace = ! empty ( $taxonomy -> rest_namespace ) ? $taxonomy -> rest_namespace : 'wp/v2' ;
$rest_base = ! empty ( $taxonomy -> rest_base ) ? $taxonomy -> rest_base : $taxonomy -> name ;
$route = sprintf ( '/%s/%s' , $namespace , $rest_base );
/**
* Filters the REST API route for a taxonomy .
*
* @ since 5.9 . 0
*
* @ param string $route The route path .
* @ param WP_Taxonomy $taxonomy The taxonomy object .
*/
return apply_filters ( 'rest_route_for_taxonomy_items' , $route , $taxonomy );
}
2020-07-02 01:57:01 -04:00
/**
* Gets the REST route for the currently queried object .
*
* @ since 5.5 . 0
*
* @ return string The REST route of the resource , or an empty string if no resource identified .
*/
function rest_get_queried_resource_route () {
if ( is_singular () ) {
$route = rest_get_route_for_post ( get_queried_object () );
} elseif ( is_category () || is_tag () || is_tax () ) {
$route = rest_get_route_for_term ( get_queried_object () );
} elseif ( is_author () ) {
$route = '/wp/v2/users/' . get_queried_object_id ();
} else {
$route = '' ;
}
/**
* Filters the REST route for the currently queried object .
*
* @ since 5.5 . 0
*
* @ param string $link The route with a leading slash , or an empty string .
*/
return apply_filters ( 'rest_queried_resource_route' , $route );
}
2020-09-06 22:37:07 -04:00
/**
* Retrieves an array of endpoint arguments from the item schema and endpoint method .
*
* @ since 5.6 . 0
*
* @ param array $schema The full JSON schema for the endpoint .
* @ param string $method Optional . HTTP method of the endpoint . The arguments for `CREATABLE` endpoints are
* checked for required values and may fall - back to a given default , this is not done
* on `EDITABLE` endpoints . Default WP_REST_Server :: CREATABLE .
* @ return array The endpoint arguments .
*/
function rest_get_endpoint_args_for_schema ( $schema , $method = WP_REST_Server :: CREATABLE ) {
$schema_properties = ! empty ( $schema [ 'properties' ] ) ? $schema [ 'properties' ] : array ();
$endpoint_args = array ();
2020-10-20 16:19:09 -04:00
$valid_schema_properties = rest_get_allowed_schema_keywords ();
$valid_schema_properties = array_diff ( $valid_schema_properties , array ( 'default' , 'required' ) );
2020-09-06 22:37:07 -04:00
foreach ( $schema_properties as $field_id => $params ) {
// Arguments specified as `readonly` are not allowed to be set.
if ( ! empty ( $params [ 'readonly' ] ) ) {
continue ;
}
$endpoint_args [ $field_id ] = array (
'validate_callback' => 'rest_validate_request_arg' ,
'sanitize_callback' => 'rest_sanitize_request_arg' ,
);
if ( WP_REST_Server :: CREATABLE === $method && isset ( $params [ 'default' ] ) ) {
$endpoint_args [ $field_id ][ 'default' ] = $params [ 'default' ];
}
if ( WP_REST_Server :: CREATABLE === $method && ! empty ( $params [ 'required' ] ) ) {
$endpoint_args [ $field_id ][ 'required' ] = true ;
}
foreach ( $valid_schema_properties as $schema_prop ) {
if ( isset ( $params [ $schema_prop ] ) ) {
$endpoint_args [ $field_id ][ $schema_prop ] = $params [ $schema_prop ];
}
}
// Merge in any options provided by the schema property.
if ( isset ( $params [ 'arg_options' ] ) ) {
// Only use required / default from arg_options on CREATABLE endpoints.
if ( WP_REST_Server :: CREATABLE !== $method ) {
$params [ 'arg_options' ] = array_diff_key (
$params [ 'arg_options' ],
array (
'required' => '' ,
'default' => '' ,
)
);
}
$endpoint_args [ $field_id ] = array_merge ( $endpoint_args [ $field_id ], $params [ 'arg_options' ] );
}
}
return $endpoint_args ;
}
2021-02-02 12:28:02 -05:00
/**
* Converts an error to a response object .
*
* This iterates over all error codes and messages to change it into a flat
2022-10-21 17:12:14 -04:00
* array . This enables simpler client behavior , as it is represented as a
2021-02-02 12:28:02 -05:00
* list in JSON rather than an object / map .
*
* @ since 5.7 . 0
*
* @ param WP_Error $error WP_Error instance .
*
* @ return WP_REST_Response List of associative arrays with code and message keys .
*/
function rest_convert_error_to_response ( $error ) {
$status = array_reduce (
$error -> get_all_error_data (),
2021-08-26 08:59:02 -04:00
static function ( $status , $error_data ) {
2021-02-02 12:28:02 -05:00
return is_array ( $error_data ) && isset ( $error_data [ 'status' ] ) ? $error_data [ 'status' ] : $status ;
},
500
);
$errors = array ();
foreach ( ( array ) $error -> errors as $code => $messages ) {
$all_data = $error -> get_all_error_data ( $code );
$last_data = array_pop ( $all_data );
foreach ( ( array ) $messages as $message ) {
$formatted = array (
'code' => $code ,
'message' => $message ,
'data' => $last_data ,
);
if ( $all_data ) {
$formatted [ 'additional_data' ] = $all_data ;
}
$errors [] = $formatted ;
}
}
$data = $errors [ 0 ];
if ( count ( $errors ) > 1 ) {
// Remove the primary error.
array_shift ( $errors );
$data [ 'additional_errors' ] = $errors ;
}
return new WP_REST_Response ( $data , $status );
}
Bootstrap/Load: Introduce functions to check whether WordPress is serving a REST API request.
This changeset introduces two functions:
* `wp_is_serving_rest_request()` returns a boolean for whether WordPress is serving an actual REST API request.
* `wp_is_rest_endpoint()` returns a boolean for whether a WordPress REST API endpoint is currently being used. While this is always the case if `wp_is_serving_rest_request()` returns `true`, the function additionally covers the scenario of internal REST API requests, i.e. where WordPress calls a REST API endpoint within the same request.
Both functions should only be used after the `parse_request` action.
All relevant manual checks have been adjusted to use one of the new functions, depending on the use-case. They were all using the same constant check so far, while in fact some of them were intending to check for an actual REST API request while others were intending to check for REST endpoint usage.
A new filter `wp_is_rest_endpoint` can be used to alter the return value of the `wp_is_rest_endpoint()` function.
Props lots.0.logs, TimothyBlynJacobs, flixos90, joehoyle, peterwilsoncc, swissspidy, SergeyBiryukov, pento, mikejolley, iandunn, hellofromTonya, Cybr, petitphp.
Fixes #42061.
Built from https://develop.svn.wordpress.org/trunk@57312
git-svn-id: http://core.svn.wordpress.org/trunk@56818 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2024-01-19 12:40:09 -05:00
/**
* Checks whether a REST API endpoint request is currently being handled .
*
* This may be a standalone REST API request , or an internal request dispatched from within a regular page load .
*
* @ since 6.5 . 0
*
* @ global WP_REST_Server $wp_rest_server REST server instance .
*
* @ return bool True if a REST endpoint request is currently being handled , false otherwise .
*/
function wp_is_rest_endpoint () {
/* @var WP_REST_Server $wp_rest_server */
global $wp_rest_server ;
// Check whether this is a standalone REST request.
$is_rest_endpoint = wp_is_serving_rest_request ();
if ( ! $is_rest_endpoint ) {
// Otherwise, check whether an internal REST request is currently being handled.
$is_rest_endpoint = isset ( $wp_rest_server )
&& $wp_rest_server -> is_dispatching ();
}
/**
* Filters whether a REST endpoint request is currently being handled .
*
* This may be a standalone REST API request , or an internal request dispatched from within a regular page load .
*
* @ since 6.5 . 0
*
* @ param bool $is_request_endpoint Whether a REST endpoint request is currently being handled .
*/
return ( bool ) apply_filters ( 'wp_is_rest_endpoint' , $is_rest_endpoint );
}