Upgravo › Guides

"Deprecated: Creation of dynamic property" in WordPress – what it means and how to fix it

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

This notice appears after your hosting moves to PHP 8.2 or newer. It is a warning, not an error: your site still works. But the plugin that triggers it is using a pattern PHP will remove in a future version, so it is a sign of code that has not been updated.

What the message looks like

Deprecated: Creation of dynamic property Some_Plugin::$settings is deprecated
in /wp-content/plugins/some-plugin/includes/class-main.php on line 80

The path after /wp-content/plugins/ tells you which plugin is responsible. If the path says /wp-content/themes/, it is your theme.

Why PHP 8.2 started complaining

Before PHP 8.2, a class could invent a property on the fly:

class Some_Plugin {
    public function __construct() {
        $this->settings = get_option( 'some_plugin_settings' ); // $settings was never declared
    }
}

PHP 8.2 deprecated this. The fix is one line in the plugin's code: declare the property.

class Some_Plugin {
    public $settings;
    public function __construct() {
        $this->settings = get_option( 'some_plugin_settings' );
    }
}

Since the fix is trivial, most maintained plugins shipped it during 2023-2024. If you still see the notice in 2026, the plugin is either unmaintained or you are running an old version.

Does it break anything?

Not today. A deprecation notice means "this still works, but will stop working in a future PHP version". PHP 9 is expected to turn it into an error. Until then the only real problems are:

How to find the plugin responsible, manually

  1. Open wp-content/debug.log (or your host's PHP error log).
  2. Search for Creation of dynamic property.
  3. Each line names a file path. Group them by plugin folder.
  4. Update each plugin. Most notices disappear after the update.
  5. For plugins that still trigger it after updating, check the plugin's support forum on WordPress.org. If the last update is more than a year old and the author does not reply, plan a replacement.

This works, but you only find the plugins that happened to run while you were watching the log. A plugin that only runs at checkout, or on a monthly cron, will not show up until it fires.

How to check every installed plugin at once

Upgravo scans the code of all your installed plugins and themes against the PHP version you choose, without running them. For PHP 8.2 it lists every file and line that creates a dynamic property, grouped by plugin, so you see the full list before upgrading instead of discovering it in the log afterwards.

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.2: UpdraftPlus with 155 notices, of which 150 are 'Creation of dynamic property', each with file and line
A backup plugin scanned for PHP 8.2: 150 dynamic properties, most of them in libraries the plugin ships inside its own folder.

What it does not catch: properties set through a variable name ($this->{$name}), code inside eval(), and classes whose parent Upgravo cannot find. An unknown parent means it stays silent rather than guessing.

If the plugin author won't fix it

Sources

More guides