← All changes | modules/blocks.php +21 -1 14.0.1 → 16.2 View file →

		@@ -1,8 +1,8 @@
1	1	<?php
2	2	/**
3	3	* Module Name: Blocks
4		- * Module Description: Add additional blocks to your site and post editors.
	4	+ * Module Description: Expand your editor with custom Jetpack blocks for rich content and layout options.
5	5	* Sort Order: 5
6	6	* First Introduced: 13.9-a.8
7	7	* Requires Connection: No
8	8	* Auto Activate: Yes
		@@ -11,8 +11,12 @@
11	11	*
12	12	* @package automattic/jetpack
13	13	*/
14	14
	15	+if ( ! defined( 'ABSPATH' ) ) {
	16	+ exit( 0 );
	17	+}
	18	+
15	19	add_action( 'jetpack_activate_module_blocks', 'jetpack_blocks_activate_module' );
16	20
17	21	/**
18	22	* Actions needed upon activating the blocks module.
		@@ -27,4 +31,20 @@
27	31	*/
28	32	function jetpack_blocks_activate_module() {
29	33	delete_option( 'jetpack_blocks_disabled' ); // The function will check and return early if not present.
30	34	}
	35	+
	36	+Jetpack_Gutenberg::load_block_editor_extensions();
	37	+Jetpack_Gutenberg::load_independent_blocks();
	38	+Jetpack_Gutenberg::register_block_metadata_collection();
	39	+
	40	+/**
	41	+ * We've switched from enqueue_block_editor_assets to enqueue_block_assets in WP-Admin because the assets with the former are loaded on the main site-editor.php.
	42	+ *
	43	+ * With the latter, the assets are now loaded in the SE iframe; the implementation is now faster because Gutenberg doesn't need to inject the assets in the iframe on client-side.
	44	+ */
	45	+if ( is_admin() ) {
	46	+ add_action( 'enqueue_block_assets', array( 'Jetpack_Gutenberg', 'enqueue_block_editor_assets' ) );
	47	+} else {
	48	+ add_action( 'enqueue_block_editor_assets', array( 'Jetpack_Gutenberg', 'enqueue_block_editor_assets' ) );
	49	+}
	50	+add_filter( 'render_block', array( 'Jetpack_Gutenberg', 'display_deprecated_block_message' ), 10, 2 );