PHP New Added 9 September 2026

PHP: Fatal error: Call to a member function x() on null

A method was called on a variable holding null, which PHP 8 treats as a fatal Error rather than a warning. The null is nearly always the result of a lookup that found nothing: a find() with no row, an unloaded relation, or a dependency that was never injected because the container quietly fell back to a default.

Quick fix

Read the commands before running them. Anything that restarts a service, deletes data or changes permissions should be tried on a non-production system first.

Quick fix

// The nullsafe operator makes the whole chain null instead of fatal
$name = $order?->customer?->name;

// Better: fail where the value is produced, not where it is used
$order = Order::find($id) ?? throw new RuntimeException("order $id not found");

// Laravel turns a missing row into a 404 for you
$order = Order::findOrFail($id);

// Static analysis finds these before your users do
vendor/bin/phpstan analyse --level 6 app/

# The stack trace names the caller, which is where the null came from
tail -f storage/logs/laravel.log

How to diagnose PHP errors

PHP errors are dominated by per-request resource limits (memory_limit, max_execution_time) and by autoloading. Class-not-found errors are almost never missing code. They are a namespace that does not match the PSR-4 mapping, or a stale Composer autoload map. Laravel adds a caching layer that produces genuinely confusing errors when configuration is cached with the wrong environment.

If the quick fix above does not resolve it, work through these steps. They apply to this whole class of error, not just to this one message, which is usually what saves the time.

Read the real limits from the running process, not from a config file: php -i | grep -E 'memory_limit|max_execution_time'. CLI and FPM have separate configurations.
Regenerate the autoload map with composer dump-autoload -o before investigating a class-not-found error any further.
For Laravel, clear cached config and routes with php artisan optimize:clear. A config cache built in the wrong environment causes errors that survive every code change.
Enable full error display in development (display_errors=On, error_reporting=E_ALL). The default production settings hide the cause.
For PDO connection refusals, test the same credentials with the database's own CLI client to separate PHP configuration from database access.

Tools worth reaching for

php -i
composer dump-autoload -o
php artisan optimize:clear
Xdebug
tail -f storage/logs/laravel.log

Authoritative references

Primary documentation for this error, worth reading before applying any fix in production.

php.net php.net

Related PHP errors

See all 11 PHP errors →

Browse other categories

Something missing or wrong?

This entry is maintained by hand. If the fix is out of date, incomplete, or you have a better one, email a correction and it will be reviewed.