PHP 8.3 Deprecation Warnings

  • Resolved ispreview

    (@ispreview)


    2 years, 5 months ago

    Just started testing PHP 8.3 across our site, using the latest version of WordPress and NGG. Figured I’d just highlight the array of deprecation warnings the plugin produces once this is enabled.

    Deprecated: Calling get_class() without arguments is deprecated in /../wp-content/plugins/nextgen-gallery/vendor/imagely/pope-framework/lib/class.component_registry.php on line 47

Deprecated: Calling get_class() without arguments is deprecated in /../wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/nextgen_admin/package.module.nextgen_admin.php on line 542

Deprecated: Calling get_class() without arguments is deprecated in /../wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/nextgen_admin/package.module.nextgen_admin.php on line 276

Deprecated: Calling get_class() without arguments is deprecated in /../wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/nextgen_admin/package.module.nextgen_admin.php on line 276

Deprecated: Calling get_class() without arguments is deprecated in /../wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/nextgen_admin/package.module.nextgen_admin.php on line 276

Deprecated: Calling get_class() without arguments is deprecated in /../wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/nextgen_admin/package.module.nextgen_admin.php on line 276

Warning: Cannot modify header information - headers already sent by (output started at /../wp-content/plugins/nextgen-gallery/vendor/imagely/pope-framework/lib/class.component_registry.php:47) in /../wp-admin/includes/misc.php on line 1431

Warning: Cannot modify header information - headers already sent by (output started at /../wp-content/plugins/nextgen-gallery/vendor/imagely/pope-framework/lib/class.component_registry.php:47) in /../wp-includes/functions.php on line 7049

Warning: Cannot modify header information - headers already sent by (output started at /../wp-content/plugins/nextgen-gallery/vendor/imagely/pope-framework/lib/class.component_registry.php:47) in /../wp-admin/admin-header.php on line 9

Deprecated: Calling get_class() without arguments is deprecated in /../wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/nextgen_admin/package.module.nextgen_admin.php on line 792

Deprecated: Calling get_class() without arguments is deprecated in /../wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/nextgen_admin/package.module.nextgen_admin.php on line 196

    The three “Warning: Cannot modify header information – headers already sent” lines can probably be ignored, as they’re most likely a result of the surrounding deprecations.

    • This topic was modified 2 years, 5 months ago by ispreview.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Jaime Segura

    (@jaimeimagely)

    2 years, 5 months ago

    Hi @ispreview,

    Thanks for the heads up, we will start looking into PHP 8.3 compatibility soon, PHP 8.3 usage is pretty low at the moment since it was released less than one month ago.

    Also, WordPress itself has “Beta Support” for PHP 8.3:
    WordPress 6.4: Added “beta support”

    If anything is broken and gets fixed by switching to a previous version, please let me know so we can proceed to check it ourselves.

    Thanks.

    Jaime Segura

    (@jaimeimagely)

    2 years, 5 months ago

    Hi  @ispreview,

    We haven’t heard back from you in a few days, so I’m going to go ahead and close this thread for now. But if you’d like us to assist further, please feel welcome to continue the conversation (please just see my post above).

    Thanks!

    Thread Starter ispreview

    (@ispreview)

    2 years, 5 months ago

    Nothing changed at my end. The 8.3 deprecations are still an issue, so there’s not much more to add until NGG fixes them. The only reason it’s an issue with NGG is because of how often NGG triggers within WP, which means NGG deprecations fill up error logs on big sites and makes it tedious to spot other problems. Other plugins seem to fix these things rather more quickly.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘PHP 8.3 Deprecation Warnings’ is closed to new replies.