wppaste
WordPress

wp_get_post_terms( int $post_id = 0, string|string[] $taxonomy = 'post_tag', array $args = array() ): array|WP_Error

Since
2.8.0
Source
wp-includes/post.php:4372
Retrieves the terms for a post.

Compatibility

WordPress
since 2.8.0
PHP
7.4–8.6-dev
  • 6.7.7
  • 6.8.8
  • 6.9.7
  • 7.0.4
  • 7.1.0

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

Parameters

$post_idintoptional
The Post ID. Does not default to the ID of the global $post. Default 0.Default: 0
$taxonomystring|string[]optional
The taxonomy slug or array of slugs for which to retrieve terms. Default 'post_tag'.Default: 'post_tag'
$argsarrayoptional
Term query parameters. See WP_Term_Query::__construct() for supported arguments.Default: array()

  • $fieldsstringdefault: 'all'

    Term fields to retrieve.

Return value

array|WP_Error
Array of WP_Term objects on success or empty array if no terms were found.
WP_Error object if $taxonomy doesn't exist.

Performance profile

How much work a call to wp_get_post_terms() 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 wp_get_object_terms().

Scaling
Constant

No loop in the body: the same number of instructions runs whatever you pass in.

Instructions
18

Executed per call on PHP 8.5. The body compiles to 18.

Plugin surface
None

Nothing here hands control to plugin code.

Called by
3

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

What it touches

  • querycontent querywp_get_object_terms()called directly
  • hookthird-party callbacksapply_filters()one call below wp_get_post_terms()

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 · 1 distinct outcome

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

WhenInstructionsCalls it makes
always18wp_parse_args(), wp_get_object_terms()

Across PHP versions

Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 18 instructions, 18 executed per call, 0 branches. The work does not change between versions.

An instruction is not a fixed amount of time, so a matching count is not necessarily the same speed; what it rules out is a difference in the work itself.

Uses · 2

Used by · 3

Source code

View on Trac View on GitHub 

function wp_get_post_terms( $post_id = 0, $taxonomy = 'post_tag', $args = array() ) {	$post_id = (int) $post_id; 	$defaults = array( 'fields' => 'all' );	$args     = wp_parse_args( $args, $defaults ); 	$tags = wp_get_object_terms( $post_id, $taxonomy, $args ); 	return $tags;}

Changelog

Introduced in 2.8.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.0.4 tag, from src/wp-includes/post.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.