wppaste
WordPress

wp_json_file_decode( string $filename, array $options = array() ): mixed

Since
5.9.0
Source
wp-includes/functions.php:4725
Reads and decodes a JSON file.

Compatibility

WordPress
since 5.9.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

$filenamestring
Path to the JSON file.
$optionsarrayoptional
Options to be used with json_decode().Default: array()
  • $associativebooldefault: false

    Optional. When true, JSON objects will be returned as associative arrays. When false, JSON objects will be returned as objects.

Return value

mixed
Returns the value encoded in JSON in appropriate PHP type.
null is returned if the file is not found, or its content can't be decoded.

Performance profile

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

Reads or writes the filesystem via file_get_contents().

Scaling
Constant

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

Instructions
22–43

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

Plugin surface
None

Nothing here hands control to plugin code.

Called by
5

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

What it touches

  • serializeserialisationjson_decode()called directly
  • filesystemfilesystem accessfile_get_contents()called directly
  • hookthird-party callbacksdo_action()one call below wp_json_file_decode()

Further down the call graph this can also reach query, option, cache 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 · 3 distinct outcomes

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

WhenInstructionsCalls it makes
always22realpath(), wp_normalize_path(), __(), sprintf(), wp_trigger_error()
always29realpath(), wp_normalize_path(), wp_parse_args(), file_get_contents(), json_decode(), json_last_error()
always43realpath(), wp_normalize_path(), wp_parse_args(), file_get_contents(), json_decode(), json_last_error(), __(), json_last_error_msg(), sprintf(), wp_trigger_error()

Across PHP versions

Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 56 instructions, 22–43 executed per call, 2 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 · 4

Used by · 5

Source code

function wp_json_file_decode( $filename, $options = array() ) {	$result   = null;	$filename = wp_normalize_path( realpath( $filename ) ); 	if ( ! $filename ) {		wp_trigger_error(			__FUNCTION__,			sprintf(				/* translators: %s: Path to the JSON file. */				__( "File %s doesn't exist!" ),				$filename			)		);		return $result;	} 	$options      = wp_parse_args( $options, array( 'associative' => false ) );	$decoded_file = json_decode( file_get_contents( $filename ), $options['associative'] ); 	if ( JSON_ERROR_NONE !== json_last_error() ) {		wp_trigger_error(			__FUNCTION__,			sprintf(				/* translators: 1: Path to the JSON file, 2: Error message. */				__( 'Error when decoding a JSON file at path %1$s: %2$s' ),				$filename,				json_last_error_msg()			)		);		return $result;	} 	return $decoded_file;}

Changelog

Introduced in 5.9.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/functions.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.