Upgravo › Guides

"Implicitly marking parameter as nullable is deprecated" – PHP 8.4 and WordPress plugins

Last reviewed 8 November 2026 · by Nicolás Alejandro Salinas

This notice appears after your host moves to PHP 8.4. It is a deprecation warning, not a fatal error: the site keeps working. It is also the most common notice of the PHP 8.4 cycle, because the pattern it flags was normal PHP for fifteen years and almost every plugin written before 2024 contains it.

What the message looks like

Deprecated: Some_Plugin::load(): Implicitly marking parameter $args as nullable
is deprecated, the explicit nullable type must be used instead
in /wp-content/plugins/some-plugin/includes/class-loader.php on line 42

The path after /wp-content/plugins/ names the plugin. One plugin can produce dozens of these at once, one per function, so a debug.log can grow by megabytes a day.

Why PHP 8.4 started complaining

Before PHP 8.4, giving a typed parameter a default of null made it nullable automatically:

function load( array $args = null ) { … }   // $args may be an array or null

PHP 8.4 deprecates that shortcut. The type must say so explicitly:

function load( ?array $args = null ) { … }  // one character added

The fix is mechanical and PHP tools do it automatically, so maintained plugins shipped it during 2024-2025. If you still see the notice in 2026, the plugin (or a library it bundles) has not been updated for PHP 8.4.

Does it break anything?

Not on PHP 8.4. The notice is a promise that a future PHP version will refuse the old form; nothing has broken yet. The real problems are side effects:

How to find the plugin responsible, manually

  1. Open wp-content/debug.log or the host's PHP error log.
  2. Search for Implicitly marking parameter.
  3. Group the lines by plugin folder. Expect a handful of plugins to account for most of them.
  4. Update those plugins. Check their changelog for "PHP 8.4".
  5. For a plugin still producing the notice after updating, open its support forum on WordPress.org. If the last release predates PHP 8.4 (November 2024) and the author is silent, plan a replacement.

The limit of this method: the log only shows code that ran while you were watching. A function used only at checkout, or by a weekly cron, will not appear until it fires.

How to check every plugin before switching to PHP 8.4

Upgravo reads the code of all installed plugins and themes and checks it against the PHP version you select, without running anything. Set the target to 8.4 and it lists every function with an implicitly nullable parameter, by plugin, file and line, before you change the host's PHP version.

Install it from WordPress.org: Upgravo – PHP Compatibility Check. The scan runs on your own server; no code is sent anywhere.

Upgravo results for PHP 8.4: a backup plugin with 310 notices, 149 of them implicitly nullable parameters, listed with file and line
A backup plugin scanned for PHP 8.4: 149 implicitly nullable parameters, next to the other 8.4 deprecations found in the same plugin.

What it does not catch: code generated at runtime (eval(), create_function()), and anything inside files too large to analyze on your hosting's memory limit, which the report lists as skipped.

Other PHP 8.4 notices you will see next to this one

All four are deprecations, not fatals, and all four are typical of plugins last updated before 2025.

If the plugin author won't fix it

Sources

More guides