WordPress Call to Undefined Function
What Is This Error?
The “Call to Undefined Function” error is a fatal PHP error — meaning it stops WordPress from loading entirely. When PHP tries to execute a function it has no record of, it panics and halts. Visitors will typically see a white screen or a message like: Fatal error: Uncaught Error: Call to undefined function some_function_name() in /path/to/file.php on line 42.
This error almost always tells you the exact file and line number where the bad call happened. That’s actually good news — it gives you a clear starting point rather than leaving you guessing.
The function could be missing for several reasons: the plugin that defines it is turned off, the file containing it was never loaded, or the code is running too early in WordPress’s boot sequence. Once you identify which of these applies, the fix is usually straightforward.
Get free WordPress & AI tips
Join 500+ readers. No spam, unsubscribe anytime.
Why Does This Happen?
- A required plugin is deactivated: If your theme or a plugin calls a function that lives inside a different plugin, deactivating that dependency instantly removes the function from memory and triggers this error.
- The function is called too early in the load order: WordPress loads in stages. Calling certain functions before the
initorwp_loadedhook fires means those functions don’t exist yet when your code runs. - A typo in the function name: PHP does exact string matching on function names — one wrong character and it won’t find a match, even if the real function is right there in memory.
- A missing include or require statement: If the file that defines the function was never loaded via
include(),require(), orrequire_once(), PHP has no knowledge the function exists. - PHP version incompatibility: Functions like
str_contains()orarray_is_list()were introduced in PHP 8.0. Calling them on PHP 7.4 will throw this exact error.
How to Fix It — Step by Step
- Read the full error message. Note the function name, the file path, and the line number. This is your roadmap — do not skip this step.
You should see: Something like
Call to undefined function get_plugin_data()in a specific file on a specific line. - Identify which plugin or file defines that function. Search your
/wp-content/plugins/and/wp-content/themes/directories forfunction your_function_name.You should see: The file where the function is declared — this tells you which plugin or theme owns it.
- Reactivate the plugin that owns the function. Go to WordPress Admin → Plugins. If the plugin that defines the function is deactivated, activate it. This resolves the majority of cases.
You should see: Your site loads normally again and the error is gone.
- Wrap the call in a function_exists() check. If you’re editing custom code and the function might not always be available, add a guard:
if ( function_exists( 'your_function_name' ) ) { your_function_name(); }You should see: No fatal error — the block is skipped gracefully when the function is unavailable.
- Fix hook timing if the call is too early. Move the function call inside the correct WordPress action hook so it runs after WordPress has finished loading the necessary code:
add_action( 'init', function() { your_function_name(); });You should see: The function executes without error after WordPress has fully initialized.
- Check your PHP version. In WordPress Admin, go to Tools → Site Health → Info → Server. Confirm your PHP version meets the requirement of the function being called. Upgrade via your hosting control panel if needed.
You should see: A PHP version of 8.0 or higher listed, and the error resolved after the upgrade.
Common Mistakes When Fixing This
- Deleting the line that throws the error: Removing the function call without understanding its purpose breaks functionality silently. The right move is to restore the missing dependency, not erase the call.
- Ignoring the file path in the error message: Many people Google the function name without noting which file is calling it. This leads to generic fixes that don’t address your specific setup. Always start with the file and line number the error gives you.
- Over-relying on function_exists() as a permanent patch: Wrapping a call in
function_exists()silences the error but hides broken functionality. Treat it as a temporary safety net while you track down why the function is missing. - Re-saving wp-config.php or theme files without fixing the root cause: Saving files doesn’t reload missing plugins or fix incorrect hook timing. The actual dependency or timing issue must be addressed directly.
Frequently Asked Questions
Will this error take my entire site down?
Yes. It is a fatal PHP error, which means WordPress cannot continue executing. Every page — including wp-admin — may return a white screen or the raw error message until the issue is fixed.
Can a WordPress or plugin update cause this error?
Absolutely. Updates sometimes remove or rename functions. If your theme or a plugin was calling the old function name, the update instantly breaks compatibility and this error appears. Always check plugin changelogs for “breaking changes” before updating on a live site.
How do I debug this if I’m locked out of wp-admin?
Open your wp-config.php file via FTP or your hosting file manager and add these two lines: define('WP_DEBUG', true); and define('WP_DEBUG_LOG', true);. The full error with file path and line number will be written to /wp-content/debug.log, which you can read without needing wp-admin access.
Is this the same error as “Call to a member function on null”?
No — these are two different errors. “Call to a member function on null” means you’re calling a method on an object that turned out to be null. “Call to undefined function” means the function itself was never registered in PHP’s memory at all. The debugging approach is similar, but the root cause differs.