WP_REST_Comments_Controller::get_items_permissions_check( WP_REST_Request $request ): true|WP_Error

Compatibility

Present in every tracked release (6.7.7 to 7.1.0), and compiles on PHP 7.4 through 8.6-dev.

Parameters

$requestWP_REST_Request

Full details about the request.

Return value

true|WP_Error

True if the request has read access, error object otherwise.

Performance profile

How much work a call to WP_REST_Comments_Controller::get_items_permissions_check() does, and what it touches: the algorithmic scaling, the Zend instruction count per call across PHP versions, the hooks it hands control to, and the core code that calls it. Measured from the compiled opcodes, not a stopwatch, so every number is identical on any machine running the same PHP version, and every function in core is ranked by cost.

Cost class

Heavy

Reaches the database via get_post().

Scaling

Scales with input

The body loops, so the work grows with what you pass in.

Instructions

14–66

Executed per call on PHP 8.5, depending on the branch taken. The body compiles to 217.

Plugin surface

None

Nothing here hands control to plugin code.

Called by

0

Nothing in core calls this; the cost is only what you spend yourself.

What it touches

• querycontent queryget_post()called directly

Further down the call graph this can also reach hook, option, cache, serialize and transient. Those are the worst case, several calls deep and usually down an error path, not what a normal call pays.

What one call costs · 16 distinct outcomes

One number would be a lie: the work depends on which branch runs. These are every distinct cost WP_REST_Comments_Controller::get_items_permissions_check() can have, taken from its control-flow graph on PHP 8.5.

Uses · 7

• get_post()Retrieves post data given a post ID or post object.
• __()Retrieves the translation of $text.
• rest_authorization_required_code()Returns a contextual HTTP error code for authorization failure.
• current_user_can()Returns whether the current user has the specified capability.
• WP_REST_Comments_Controller::check_read_post_permission()Checks if the post can be read.
• WP_Error::__construct()Initializes the error.
• WP_REST_Comments_Controller::check_post_type_supports_notes()Check if post type supports notes.

Source code

View on Trac ↗View on GitHub ↗

125	public function get_items_permissions_check( $request ) {126		$is_note          = 'note' === $request['type'];127		$is_edit_context  = 'edit' === $request['context'];128		$protected_params = array( 'author', 'author_exclude', 'author_email', 'type', 'status' );129		$forbidden_params = array();130 131		if ( ! empty( $request['post'] ) ) {132			foreach ( (array) $request['post'] as $post_id ) {133				$post = get_post( $post_id );134 135				if ( ! empty( $post_id ) && $post && ! $this->check_read_post_permission( $post, $request ) ) {136					return new WP_Error(137						'rest_cannot_read_post',138						__( 'Sorry, you are not allowed to read the post for this comment.' ),139						array( 'status' => rest_authorization_required_code() )140					);141				} elseif ( 0 === $post_id && ! current_user_can( 'moderate_comments' ) ) {142					return new WP_Error(143						'rest_cannot_read',144						__( 'Sorry, you are not allowed to read comments without a post.' ),145						array( 'status' => rest_authorization_required_code() )146					);147				}148 149				if ( $post && $is_note && ! $this->check_post_type_supports_notes( $post->post_type ) ) {150					if ( current_user_can( 'edit_post', $post->ID ) ) {151						return new WP_Error(152							'rest_comment_not_supported_post_type',153							__( 'Sorry, this post type does not support notes.' ),154							array( 'status' => 403 )155						);156					}157 158					foreach ( $protected_params as $param ) {159						if ( 'status' === $param ) {160							if ( 'approve' !== $request[ $param ] ) {161								$forbidden_params[] = $param;162							}163						} elseif ( 'type' === $param ) {164							if ( 'comment' !== $request[ $param ] ) {165								$forbidden_params[] = $param;166							}167						} elseif ( ! empty( $request[ $param ] ) ) {168							$forbidden_params[] = $param;169						}170					}171					return new WP_Error(172						'rest_forbidden_param',173						/* translators: %s: List of forbidden parameters. */174						sprintf( __( 'Query parameter not permitted: %s' ), implode( ', ', $forbidden_params ) ),175						array( 'status' => rest_authorization_required_code() )176					);177				}178			}179		}180 181		// Re-map edit context capabilities when requesting `note` for a post.182		if ( $is_edit_context && $is_note && ! empty( $request['post'] ) ) {183			foreach ( (array) $request['post'] as $post_id ) {184				if ( ! current_user_can( 'edit_post', $post_id ) ) {185					return new WP_Error(186						'rest_forbidden_context',187						__( 'Sorry, you are not allowed to edit comments.' ),188						array( 'status' => rest_authorization_required_code() )189					);190				}191			}192		} elseif ( $is_edit_context && ! current_user_can( 'moderate_comments' ) ) {193			return new WP_Error(194				'rest_forbidden_context',195				__( 'Sorry, you are not allowed to edit comments.' ),196				array( 'status' => rest_authorization_required_code() )197			);198		}199 200		if ( ! current_user_can( 'edit_posts' ) ) {201			foreach ( $protected_params as $param ) {202				if ( 'status' === $param ) {203					if ( 'approve' !== $request[ $param ] ) {204						$forbidden_params[] = $param;

Changelog

Introduced in 4.7.0. Unchanged from 6.7.7 through 7.1.0.

1. 6.7.7
2. 6.8.8
3. 6.9.7
4. 7.0.4
5. 7.1.0

Signature, return type and hooks compared across 5 parsed releases.

About this page

Parsed data

Generated from the wordpress-develop 7.1.0 tag, from src/wp-includes/rest-api/endpoints/class-wp-rest-comments-controller.php, and regenerated for each WordPress release so it tracks the code rather than a snapshot of it.

Corrections

Something wrong on this page? Report it and it gets fixed in the next regeneration.