If a PHP 8.2 deprecation notice such as “Creation of dynamic property … is deprecated” appears, first confirm it names Download Plugins and Themes in ZIP from Dashboard (its classes use the Alg_Download_Plugins prefix). Then update the plugin to the latest version under Plugins > Installed Plugins. The notices are non-fatal, so the plugin keeps working meanwhile.
1. Confirm the source of the notice #
Deprecation notices name the file that triggered them. The Download Plugins and Themes classes carry the Alg_Download_Plugins prefix and live in the plugin’s includes/ folder (for example class-alg-download-plugins-core.php and class-alg-download-plugins-settings.php). If the file path in the notice belongs to a different plugin or your theme, fix that component instead.
2. Update to the latest version #
The current Pro release is a modern rewrite maintained for current PHP versions. Update Download Plugins and Themes to the latest version under Plugins > Installed Plugins, then reload the page to confirm the notice is gone. Keeping the plugin current is the correct long-term fix.
3. Hide deprecation notices on production (temporary) #
Deprecation notices are non-fatal: the plugin still works. While you finish updating everything, stop the notices from showing to visitors by turning off error display in wp-config.php, keeping the log so you can still review them:
// Do not display errors to visitors
@ini_set( 'display_errors', 0 );
define( 'WP_DEBUG_DISPLAY', false );
// Keep logging so you can review notices in wp-content/debug.log
define( 'WP_DEBUG_LOG', true );
This hides the notices rather than removing their cause, so treat it as a stopgap while you update the plugins and theme that produce them.
4. Test PHP upgrades on staging first #
Before raising the PHP version on a live site, run the same plugins and theme on a staging copy under the new PHP version. Clear any deprecation notices there, then apply the upgrade to production.
Still seeing notices? #
If a notice still names Download Plugins and Themes after updating, copy the exact message and file path from wp-content/debug.log, note your plugin, WordPress and PHP versions, and open a ticket on the Download Plugins and Themes support forum so it can be patched.
