Fixing 'PHP Fatal error: Cannot redeclare function' in WordPress and Custom Apps

The Problem: Why PHP Stops Execution

PHP is strict about naming. If the engine sees two functions with the exact same name in the same scope, it panics. It throws a Fatal Error and kills the script instantly. This usually happens when you accidentally include the same file twice or when two different libraries use generic names like init() or send_email().

I ran into this recently while migrating a five-year-old legacy codebase into a modern framework. Here is the exact error that appeared in my error.log:

PHP Fatal error: Cannot redeclare send_email() (previously declared in /var/www/html/functions.php:10) in /var/www/html/helper.php on line 5

The Debug Process

Don't ignore the error message—it tells you exactly where the conflict lives. You get two vital clues:

• The original source: /var/www/html/functions.php:10 (The place where the function was first born).
• The conflict source: /var/www/html/helper.php on line 5 (The place where PHP tried to recreate it).

In 90% of cases, this happens for one of three reasons. You might be using include inside a loop. You might have two different files using identical names. Or, your composer.json autoloader might be misconfigured, loading the same file twice.

Solution 1: Switch to require_once

This is your first line of defense. If your error stems from including the same file multiple times—like a header and a footer both calling a config.php—switch to require_once or include_once.

The Wrong Way:

// In index.php
require 'functions.php';
require 'helper.php'; // If helper.php also calls require 'functions.php', the script crashes.

The Right Way:

// In index.php
require_once 'functions.php';
require_once 'helper.php';

The _once suffix tells PHP to keep a checklist of loaded files. If a file is already on the list, PHP ignores the second request. This simple change fixes the majority of redeclaration issues.

Solution 2: Wrap Functions in function_exists

If you are building a plugin or a shared library, you cannot control how other developers include your files. To prevent crashes, wrap your declarations in a conditional check. This is a mandatory standard in WordPress development.

if (!function_exists('send_email')) {
    function send_email($to, $subject, $message) {
        return mail($to, $subject, $message);
    }
}

By using this check, PHP only defines the function if the name is still available. If another script already claimed it, PHP simply skips the block and moves on.

Solution 3: Namespaces (The Professional Standard)

What if you have two functions that share a name but perform different tasks? You shouldn't have to rename them to something messy like send_email_v2_final(). Instead, use namespaces to keep them in separate "folders."

File: functions.php

namespace App\Core;

function send_email() {
    echo "Sending via Core Mailer...";
}

File: helper.php

namespace App\Utilities;

function send_email() {
    echo "Sending via Utility Helper...";
}

Usage:

use App\Core as CoreMail;
use App\Utilities as UtilMail;

CoreMail\send_email();
UtilMail\send_email();

Namespacing is the cleanest way to organize modern PHP. It allows App\Core\send_email and App\Utilities\send_email to exist side-by-side without any friction.

How to Verify the Fix

Once you apply a solution, follow these steps to ensure the error is gone for good:

• Clear the logs: Wipe your error_log, refresh your page, and check if the file stays empty.
• Check the CLI: Run php index.php in your terminal. If it executes without a stack trace, you're successful.
• Run Unit Tests: If you use PHPUnit, run your suite to ensure that your logic still works after renaming or wrapping functions.

Pro-Tips for Clean Code

• Always use require_once for core structural files like settings or database connections.
• Avoid generic names. Instead of init(), use something unique like stripe_payment_init().
• Adopt a Class-based structure. Methods inside classes don't suffer from global naming conflicts.
• Let Composer handle the heavy lifting. A PSR-4 autoloader eliminates the need for manual require statements entirely.