SECURITY WARNING: Never run commands you don't understand. Always review code before execution. Use at your own risk.
FixMyError.net
PHP New Added 9 October 2026

PHP: count(): Argument #1 ($value) must be of type Countable|array, null given

Since PHP 8.0, count() throws a TypeError for anything that is not an array or a Countable object. PHP 7.2 only warned, and before that count(null) quietly returned 0, so code that counted a value which might be null worked for years and breaks on upgrade. The fix belongs where the null comes from, such as an empty result or a missing request field, not inside count().

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
# Calls to review
grep -rn 'count(\$' src/ | head -50

// Before: $items is null when the field is missing
$total = count($data['items']);

// Default to an empty array at the source
$items = $data['items'] ?? [];
$rows  = $repository->findAll() ?? [];

// Or guard the call
$total = is_countable($rows) ? count($rows) : 0;

// Generators and iterators are not Countable
$total = iterator_count($generator);

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.

  1. 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.
  2. Regenerate the autoload map with composer dump-autoload -o before investigating a class-not-found error any further.
  3. 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.
  4. Enable full error display in development (display_errors=On, error_reporting=E_ALL). The default production settings hide the cause.
  5. 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 20 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.