Issue with Brizy Pro

Patrick Chamayou

• March 04, 2026 10:39

Hello,

My website is running on PHP 8.3 and I am getting the following deprecated warnings with Brizy Pro:

Deprecated: GuzzleHttp\Promise\queue(): Implicitly marking parameter $assign as nullable is deprecated, the explicit nullable type must be used instead in /home/chpa1086/montpellier.cma-formation.eu/wp-content/plugins/brizy-pro/vendor/guzzlehttp/promises/src/functions.php on line 24
Deprecated: GuzzleHttp\Promise\each(): Implicitly marking parameter $onFulfilled as nullable is deprecated, the explicit nullable type must be used instead in /home/chpa1086/montpellier.cma-formation.eu/wp-content/plugins/brizy-pro/vendor/guzzlehttp/promises/src/functions.php on line 260
Deprecated: GuzzleHttp\Promise\each(): Implicitly marking parameter $onRejected as nullable is deprecated, the explicit nullable type must be used instead in /home/chpa1086/montpellier.cma-formation.eu/wp-content/plugins/brizy-pro/vendor/guzzlehttp/promises/src/functions.php on line 260
Deprecated: GuzzleHttp\Promise\each_limit(): Implicitly marking parameter $onFulfilled as nullable is deprecated, the explicit nullable type must be used instead in /home/chpa1086/montpellier.cma-formation.eu/wp-content/plugins/brizy-pro/vendor/guzzlehttp/promises/src/functions.php on line 285
Deprecated: GuzzleHttp\Promise\each_limit(): Implicitly marking parameter $onRejected as nullable is deprecated, the explicit nullable type must be used instead in /home/chpa1086/montpellier.cma-formation.eu/wp-content/plugins/brizy-pro/vendor/guzzlehttp/promises/src/functions.php on line 285
Deprecated: GuzzleHttp\Promise\each_limit_all(): Implicitly marking parameter $onFulfilled as nullable is deprecated, the explicit nullable type must be used instead in /home/chpa1086/montpellier.cma-formation.eu/wp-content/plugins/brizy-pro/vendor/guzzlehttp/promises/src/functions.php on line 307

 I understand this is related to the GuzzleHttp Promises library, but since it is bundled in Brizy Pro, could you please update the dependency or provide a fix for PHP 8.3

Thank you and have a nice day,
Patrick

0

• 

  Ariel H.

  • March 04, 2026 11:11

  Hi Patrick,

  Thank you for reaching out.

  The deprecated warnings are informational only and do not mean the site is broken or that there’s an issue with Brizy. They appear because PHP 8.3 is stricter with older coding standards and will flag them when debug mode is enabled. You can hide these notices by following the steps in this guide:
  https://thumbtube.com/blog/how-to-hide-deprecated-notices-in-wordpress/

  If you have any other questions, feel free to let us know.

  Best regards,
  Ariel H.

  0
• 

  Patrick Chamayou

  • March 04, 2026 12:41

  Thank you for your reply, but I'm not satisfied with this answer. Hiding deprecation notices is not a fix — it's a workaround that papers over a known compatibility issue. GuzzleHttp Promises has already addressed this in more recent versions. Bundling an outdated dependency and asking customers to suppress warnings instead of updating it is not acceptable maintenance practice. Could you please escalate this to your development team and provide a timeline for updating the bundled GuzzleHttp Promises library?

  0
• 

  Ariel H.

  • March 04, 2026 14:03

  Hi Patrick,

  Thank you for your detailed feedback and for explaining your concerns.

  You’re absolutely right that suppressing deprecation notices is only a temporary workaround and not a long-term solution. I’ve posted your feedback in our internal support team discussion forum so it can be reviewed.

  At the moment, I’m unfortunately not able to provide a timeline for when or if an update will be implemented but rest assured that your concerns have been shared internally.

  If possible, we would also appreciate it if you could post this request on our Ideas and Roadmap page as well: https://www.brizy.io/ideas-and-roadmap. This helps our product team track demand and prioritize improvements more effectively.

  Thank you again for bringing this to our attention.

  Kind regards,  
  Ariel H.

  0

Please sign in to leave a comment.