WP_REST_Posts_Controller::check_assign_terms_permission( WP_REST_Request $request ): bool

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

The request object with post and terms data.

Return value

bool

Whether the current user can assign the provided terms.

Performance profile

How much work a call to WP_REST_Posts_Controller::check_assign_terms_permission() 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_term().

Scaling

Scales with input

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

Instructions

15–41

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

Plugin surface

None

Nothing here hands control to plugin code.

Called by

2

2 places in core call this, so the cost is paid more often than your own code shows.

What it touches

• querycontent queryget_term()called directly
• hookthird-party callbacksapply_filters()one call below WP_REST_Posts_Controller::check_assign_terms_permission()

Further down the call graph this can also reach 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 · 2 distinct outcomes

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

Uses · 4

• wp_list_filter()Filters a list of objects, based on a set of key => value arguments.
• get_object_taxonomies()Returns the names or objects of the taxonomies which are registered for the requested object or object type, such as a post object or post type name.
• get_term()Gets all term data from database by term ID.
• current_user_can()Returns whether the current user has the specified capability.

Used by · 2

• WP_REST_Posts_Controller::create_item_permissions_check()Checks if a given request has access to create a post.
• WP_REST_Posts_Controller::update_item_permissions_check()Checks if a given request has access to update a post.

Source code

View on Trac ↗View on GitHub ↗

1695	protected function check_assign_terms_permission( $request ) {1696		$taxonomies = wp_list_filter( get_object_taxonomies( $this->post_type, 'objects' ), array( 'show_in_rest' => true ) );1697		foreach ( $taxonomies as $taxonomy ) {1698			$base = ! empty( $taxonomy->rest_base ) ? $taxonomy->rest_base : $taxonomy->name;1699 1700			if ( ! isset( $request[ $base ] ) ) {1701				continue;1702			}1703 1704			foreach ( (array) $request[ $base ] as $term_id ) {1705				// Invalid terms will be rejected later.1706				if ( ! get_term( $term_id, $taxonomy->name ) ) {1707					continue;1708				}1709 1710				if ( ! current_user_can( 'assign_term', (int) $term_id ) ) {1711					return false;1712				}1713			}1714		}1715 1716		return true;1717	}

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 6.9.7 tag, from src/wp-includes/rest-api/endpoints/class-wp-rest-posts-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.