2 Warnings on class.jetpack-gutenberg.php while start editing posts

It looks like temporary solution is commented line #776 in class.jetpack-gutenberg.php file. Is it correct?

    //$initial_state['social']['featureFlags'] = $social_initial_state['featureFlags'];

Suddenly getting the same error.

Hello there – thanks for reporting the issue! We are investigating the root source of the issue and will get back to you as soon as we have some updates. ??

Hello there – we have found the issue and working on fix already. Most probably the issue will be fixed in the next update of the plugin in version 13.7.1.

Same! Receiving this error in the WP Admin and interestingly it completely pushes the left Admin bar down (instead of appearing at top of page like a normal debug message) to where I can’t see all the menu options:

Notice: Undefined variable: social_initial_state in […my site…]/plugins/jetpack/class.jetpack-gutenberg.php on line 776

https://www.dropbox.com/scl/fi/0mz295lvy51z1m08mzmy6/Screen-Shot-2024-08-08-at-8.56.30-AM.png?rlkey=w7ih8vb5n06iyk08oty9k9kdw&dl=0

Core, theme, and plugins are all updated to latest as of today

Here’s as much of the error as I could copy from that sliver of window:

( ! ) Notice: Undefined variable: social_initial_state in /Users/jamesmonroe/Local Sites/mmonroedesign/app/public/wp-content/plugins/jetpack/class.jetpack-gutenberg.php on line 776
Call Stack
#	Time	Memory	Function	Location
1	0.0033	374432	{main}( )	.../post.php:0
2	0.5163	14329688	require( '/Users/jamesmonroe/Local Sites/mmonroedesign/app/public/wp-admin/edit-form-blocks.php )	.../post.php:187
3	1.2944	23257128	require_once( '/Users/jamesmonroe/Local Sites/mmonroedesign/app/public/wp-admin/admin-header.php )	.../edit-form-blocks.php:312
4	1.2954	23259680	do_action( $hook_name = 'admin_enqueue_scripts', ...$arg = variadic('post.php') )	.../admin-header.php:118
5	1.2954	23260056	WP_Hook->do_action( $args = [0 => 'post.php'] )	.../plugin.php:517
6	1.2954	23260056	WP_Hook->apply_filters( $value = '', $args = [0 => 'post.php'] )	.../class-wp-hook.php:348
7	1.2957	23263040	wp_common_block_scripts_and_styles( 'post.php' )	.../class-wp-hook.php:324
8	1.2957	23263040	do_action( $hook_name = 'enqueue_block_assets' )	.../script-loader.php:2447
9	1.2957	23263416	WP_Hook->do_action( $args = [0 => ''] )	.../plugin.php:517
10	1.2957	23263416	WP_Hook->apply_filters( $value = '', $args = [0 => ''] )	.../class-wp-hook.php:348
11	1.2965	23263416	Jetpack_Gutenberg::enqueue_block_editor_assets( '' )	.../class-wp-hook.php:324

( ! ) Notice: Trying to access array offset on value of type null in /Users/jamesmonroe/Local Sites/mmonroedesign/app/public/wp-content/plugins/jetpack/class.jetpack-gutenberg.php on line 776
Call Stack
#	Time	Memory	Function	Location
1	0.0033	374432	{main}( )	.../post.php:0
2	0.5163	14329688	require( '/Users/jamesmonroe/Local Sites/mmonroedesign/app/public/wp-admin/edit-form-blocks.php )	.../post.php:187
3	1.2944	23257128	require_once( '/Users/jamesmonroe/Local Sites/mmonroedesign/app/public/wp-admin/admin-header.php )	.../edit-form-blocks.php:312
4	1.2954	23259680	do_action( $hook_name = 'admin_enqueue_scripts', ...$arg = variadic('post.php') )	.../admin-header.php:118
5	1.2954	23260056	WP_Hook->do_action( $args = [0 => 'post.php'] )	.../plugin.php:517
6	1.2954	23260056	WP_Hook->apply_filters( $value = '', $args = [0 => 'post.php'] )	.../class-wp-hook.php:348
7	1.2957	23263040	wp_common_block_scripts_and_styles( 'post.php' )	.../class-wp-hook.php:324
8	1.2957	23263040	do_action( $hook_name = 'enqueue_block_assets' )	.../script-loader.php:2447
9	1.2957	23263416	WP_Hook->do_action( $args = [0 => ''] )	.../plugin.php:517
10	1.2957	23263416	WP_Hook->apply_filters( $value = '', $args = [0 => ''] )	.../class-wp-hook.php:348
11	1.2965	23263416	

For what it’s worth, those two warnings are no longer showing up on the backend of my WordPress.

Update: Nevermind, it’s still there.

• This reply was modified 3 months, 2 weeks ago by ferio252.

Hi there,

As mentioned before, we have found the issue and?are working on a fix already. Most probably, the issue will be fixed in the next update of the plugin in version 13.7.1 → GitHub issue

As a work-around, you can consider deactivating the notices, here are some tips.