Whilst a deprecation notice is not critical, for developers that run in DEBUG mode to ensure their code works with the current PHP this creates an issue and in admin you get headers already sent.
The product development team is aware of the deprecation in PHP 8.2, and they have an issue in their workflow to take care of it. We don’t have a timeline for when it will be resolved, but it is in progress. Thank you.
Good to hear that it’s in progress! WP Engine is “force” updating all 7.4 and 8.0 installs directly to 8.2 without the option to have 8.1.
So developing with 8.2, so whilst “every” developer is developing with the debug on, this does indeed creates layout breaking output on the front-end.
Could I ask that your team move this up in priority? For us developers who work locally with XDebug, WP_DEBUG, and logging enabled, it completely breaks the WP Admin UI and floods the logs. This issue has been known about since July, the fix is extremely easy and only occurs in 2 places:
/var/www/html/public/content/plugins/gravityforms/includes/fields/class-gf-field-list.php on line 167
/var/www/html/public/content/plugins/gravityforms/includes/fields/class-gf-field-repeater.php on line 584
PHP 8.3 is coming out soon and WordPresss works just fine with PHP 8.2 (which was mentioned as a reason last time why this hasn’t been fixed yet).
The deprecated warning are visible for anyone on PHP 8.2 that add (or adjusts) define( 'WP_DEBUG', true ); in their wp-config.php file so I think most users don’t know about this. My question is if we know what functionality (if any) is affected by the deprecated code?
That really isn’t the issue, as no functionality will be impacted in PHP 8.2 by deprecated code. The issue is for professional developers that operate with debug on and the layouts get messed up. Gravity forms is the choice of many professional developers and they pay a lot of money for a quality product and to be put simply we expect a bit more from Gravity in terms of quality than they have delivered this time.