PHP 8.4: Fix Deprecated Implicitly nullable parameters

Brooke .

• September 11, 2025 21:46

Hi,

I'd like to upgrade my production server to PHP 8.4 as PHP 8.3's active support ends in a few months. Brizy is the last plugin I am using that has Warnings that need to be resolved. While I understand that these are only warnings, they do fill up the logs and in this case are easy to fix. I'm hoping by reporting these you can get them resolved in an upcoming release.

Brizy Pro:

Deprecated    BrizyPro_Main::createDynamicContentLoopContext(): Implicitly marking parameter $wp_post as nullable is deprecated, the explicit nullable type must be used instead    
wp-content/plugins/brizy-pro/main.php:228

Deprecated    Brizy_Admin_Blocks_Main::enqueueMatchedGlobalBlockAssets(): Implicitly marking parameter $post as nullable is deprecated, the explicit nullable type must be used instead    
wp-content/plugins/brizy/admin/blocks/main.php:126

Brizy (free/core)

Deprecated    Brizy_Admin_Cloud::_init(): Implicitly marking parameter $project as nullable is deprecated, the explicit nullable type must be used instead
wp-content/plugins/brizy/admin/cloud.php:37

Deprecated    Brizy_Admin_Cloud::_init(): Implicitly marking parameter $cloudClient as nullable is deprecated, the explicit nullable type must be used instead
wp-content/plugins/brizy/admin/cloud.php:37

Thanks!

0

• 

  Ariel H.

  • September 12, 2025 08:14

  Hi Brooke.

  Thank you for contacting us.

  These are deprecation warnings, not fatal errors, so they won’t affect how Brizy works on your site. They appear because newer versions of PHP are stricter about how certain parameters are defined, and Brizy hasn’t yet fully adjusted to those changes yet.

  These warnings are not a cause for concern, and they will be addressed in upcoming future updates to ensure full compatibility.

  Best regards,
  Ariel H.

  -1
• 

  Brooke .

  • September 12, 2025 08:54

   

  These are deprecation warnings, not fatal errors, so they won’t affect how Brizy works on your site....These warnings are not a cause for concern

  This is not entirely true, as I mentioned in my initial post:

  While I understand that these are only warnings, they do fill up the logs and in this case are easy to fix. 

  You are correct that the warnings won't bring down a site, but if logging is enabled it is noticeable and noisy. As a PHP developer I monitor these types of warnings to ensure  mentioned Brizy is the last plugin in use with any such PHP 8.4 warnings. It is also not uncommon for these types of warnings to become fatal errors in the future. 

  I'm glad to hear that this will be addressed in a future release, I'm trying to decide if it's worth hot fixing locally or if I should wait for an official release with the fixes.

  Thanks for your attention.

  0
• 

  Ariel H.

  • September 12, 2025 09:23

  Hi Brooke,

  You’re right, these are not fatal errors, but they do clutter logs when enabled, and we understand how that can be disruptive. Our team is aware of your concern and is already working on a fix, which will be included in an upcoming version.

  Best regards,
  Ariel H.

  0

Please sign in to leave a comment.