Changeset 7476

Timestamp:

07/19/2018 03:04:13 AM (7 years ago)

Author:

coreymckrill

Message:

WordCamp Gutenberg Tweaks: Add hotfix for wpApiSettings bug

Starting in Gutenberg 3.1, the 'wp-api-request' script gets de-registered
and re-registered with a Gutenberg-specific version. Unfortunately, the
script doesn't also get re-localized with the wpApiSettings variable that's
needed for wp-api.js, unless the current screen contains an editor instance.

The bug was reported here:
​https://github.com/WordPress/gutenberg/issues/7488

And it should be fixed once the changes in this pull request get released:
​https://github.com/WordPress/gutenberg/pull/7566

In the meantime, this hotfix should ensure that wpApiSettings is available
regardless of the presence of an editor instance.

File:

• sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins/gutenberg-tweaks.php (modified) (1 diff)

sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins/gutenberg-tweaks.php

@@ -32 +32 @@
         add_action( 'admin_print_scripts-edit.php', __NAMESPACE__ . '\add_classic_param_to_add_new_button', 11    );
         add_action( 'admin_print_scripts',          __NAMESPACE__ . '\add_classic_param_to_admin_menus',     1    );
+
+        // @todo Hotfix for Gutenberg 3.1-3.2 breaking wpApiSettings. This will hopefully be unnecessary with 3.3.
+        // See https://github.com/WordPress/gutenberg/issues/7488
+        // See https://github.com/WordPress/gutenberg/pull/7566
+        if ( ! wp_script_is( 'wp-api-fetch', 'registered' ) ) {
+            add_action( 'wp_enqueue_scripts', 'gutenberg_extend_wp_api_backbone_client' );
+            add_action( 'admin_enqueue_scripts', 'gutenberg_extend_wp_api_backbone_client' );
+        }
     }
 }