Skip to content
Permalink
Browse files

Docs: Clarify custom-fields support requirement for viewing custom po…

…st meta in REST API.

Fixes #47866.


git-svn-id: https://develop.svn.wordpress.org/trunk@45786 602fd350-edb4-49c9-b593-d223f7449a82
  • Loading branch information...
kadamwhite committed Aug 13, 2019
1 parent 457a57a commit 3d53fdba73e6699932a183b99c2ea197374233fe
Showing with 3 additions and 1 deletion.
  1. +3 −1 src/wp-includes/meta.php
@@ -1129,7 +1129,9 @@ function sanitize_meta( $meta_key, $meta_value, $object_type, $object_subtype =
* @type bool $single Whether the meta key has one value per object, or an array of values per object.
* @type string $sanitize_callback A function or method to call when sanitizing `$meta_key` data.
* @type string $auth_callback Optional. A function or method to call when performing edit_post_meta, add_post_meta, and delete_post_meta capability checks.
* @type bool $show_in_rest Whether data associated with this meta key can be considered public.
* @type bool $show_in_rest Whether data associated with this meta key can be considered public and
* should be accessible via the REST API. A custom post type must also declare
* support for custom fields for registered meta to be accessible via REST.
* }
* @param string|array $deprecated Deprecated. Use `$args` instead.
*

0 comments on commit 3d53fdb

Please sign in to comment.
You can’t perform that action at this time.