Call to Undefined Function: Which File Was Supposed to Define It

PHP was asked to run a function that no loaded file has defined; the function usually exists, just in a file that was not loaded for this request. The full line reads PHP Fatal error: Uncaught Error: Call to undefined function download_url() in /var/www/html/wp-content/themes/mytheme/functions.php:88, followed by a stack trace. Visitors see "There has been a critical error on this website."

Read the function name before anything else. Where it normally lives tells you why it is missing.

Classify the function name

Get the file and line from debug.log with debug logging on. If wp-admin is down, the critical error guide covers recovery mode and deactivating the culprit.

Admin-only functions called on the front end

WordPress loads most of wp-admin/includes/*.php on admin screens only. A theme or plugin whose front-end form calls media_handle_upload(), or whose cron job calls download_url(), works perfectly while the developer tests in the dashboard, then fatals for the first visitor, REST request or cron run.

One exception changed recently: since WordPress 6.8, core loads wp-admin/includes/plugin.php on every request, so is_plugin_active() and get_plugins() only fail this way on older versions. The other admin files still need loading explicitly wherever you call their functions:

if ( ! function_exists( 'download_url' ) ) {
	require_once ABSPATH . 'wp-admin/includes/file.php';
}
$tmp = download_url( $url );
if ( is_wp_error( $tmp ) ) {
	// …
}

For a dependency check, class_exists( 'WooCommerce' ) or function_exists( 'wc_get_product' ) is more reliable than is_plugin_active(), which knows nothing about whether the plugin actually loaded. The media functions need wp-admin/includes/image.php, file.php and media.php together.

Pluggable functions called too early

wp-includes/pluggable.php defines functions that plugins are allowed to replace, so WordPress includes it after all active plugins. Calling wp_get_current_user() or is_user_logged_in() directly in a plugin's main file, outside any hook, runs before the file exists:

// Fails: runs when the plugin file is included.
if ( is_user_logged_in() ) { … }

// Works: runs once WordPress has set up the user.
add_action( 'init', function () {
	if ( is_user_logged_in() ) { … }
} );

Moving the call into a hook also gives correct results: the current user is only determined just before init.

A plugin the code depends on is off

Theme templates are the classic case: a template calls a WooCommerce or custom-fields function, someone deactivates that plugin, and every page using the template fatals. The fix depends on intent:

• If the plugin is required, reactivate it. A dependent plugin can declare the Requires Plugins header, which removes the dependency's Deactivate link on the Plugins screen while a dependent is active; a theme has no such header and needs an admin notice instead.
• If the feature is optional, guard the call: if ( function_exists( 'wc_get_product' ) ).

A plugin that failed to load because of its own fatal error also leaves its functions undefined; the first error in the log is the one to fix. Conflict testing tells you which plugin is involved if the stack trace is unclear.

PHP removed the function, or never had it

After a PHP upgrade, old code calling create_function() or each() stops working — both were removed in PHP 8.0. Update the plugin or theme; if it is abandoned, replace it. Similar breakage often arrives in a batch, covered in site not working after a PHP update.

Extension functions fail when the extension is missing from the PHP that serves the site: mysqli_* without mysqli (its own article), curl_* without curl, mb_* without mbstring. WordPress polyfills a few of these itself (mb_substr(), mb_strlen() and a couple of others), which is why a site can mostly work and fail only in a plugin that calls mb_strtolower(). Check Tools › Site Health › Info › Server for the web server's PHP, not php -m on the command line.

Typos and namespaces

If the function is your own: a misspelt name, or a function declared inside a namespace and called without it. Inside namespace Acme;, function helper() is really Acme\helper(). Calling helper() from a file with no namespace fails with Call to undefined function helper(). Use the full name or a use function statement.

Common mistakes

• Copying a function definition from wp-admin/includes into functions.php, which later fatals with Cannot redeclare when the admin loads the real one.
• Testing a fix only in wp-admin, where the admin-only functions exist anyway.
• Wrapping a required dependency in function_exists() so the page renders without the feature and nobody notices.
• Fixing the second error in the log instead of the first.

Verify

• Load the failing URL logged out, in a private window; admin-only bugs only show there.
• Trigger cron with wp cron event run --due-now and check debug.log for new "undefined function" lines.
• Request a REST endpoint of the site (/wp-json/) and confirm it returns JSON, not a critical error page.