wppaste
WordPress

validate_file_to_edit( string $file, string[] $allowed_files = array() ): string|void

Since
1.5.0
Source
wp-admin/includes/file.php:737
Makes sure that the file that was requested to be edited is allowed to be edited.

Description

Function will die if you are not allowed to edit the file.

Compatibility

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

$filestring
File the user is attempting to edit.
$allowed_filesstring[]optional
Array of allowed files to edit.
$file must match an entry exactly.Default: array()

Return value

string|void
Returns the file name on success, dies on failure.

Performance profile

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

Touches nothing outside its own arguments.

Scaling
Constant

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

Instructions
9–23

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

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

  • hookthird-party callbacksapply_filters()one call below validate_file_to_edit()

Further down the call graph this can also reach option, cache, serialize, query 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 validate_file_to_edit() can have, taken from its control-flow graph on PHP 8.5.

WhenInstructionsCalls it makes
always9–13validate_file()
$code != 1 && $code == 319validate_file(), __(), wp_die()
$code == 123validate_file(), __(), wp_die(), __(), wp_die()

Across PHP versions

PHPCompiledExecutedBranchesNotes
8.6-dev279–233
8.5279–233
8.4279–233
8.3279–233
8.2279–233
8.1279–2331 more instruction than PHP 7.4
7.4269–253

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 · 3

  • validate_file()Validates a file name and path against an allowed set of rules.
  • wp_die()Kills WordPress execution and displays HTML page with an error message.
  • __()Retrieves the translation of $text.

Source code

function validate_file_to_edit( $file, $allowed_files = array() ) {	$code = validate_file( $file, $allowed_files ); 	if ( ! $code ) {		return $file;	} 	switch ( $code ) {		case 1:			wp_die( __( 'Sorry, that file cannot be edited.' ) ); 			// case 2 :			// wp_die( __('Sorry, cannot call files with their real path.' )); 		case 3:			wp_die( __( 'Sorry, that file cannot be edited.' ) );	}}

Changelog

Introduced in 1.5.0. One change between 6.7.7 and 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.

7.1.0
Return type changed from string|void to string|null.verified against source
1.5.0
Introduced.from the docblock

About this page

Parsed data
Generated from the wordpress-develop 6.7.7 tag, from src/wp-admin/includes/file.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.