<?php
/**
 * Module Name: Blocks
 * Module Description: Expand your editor with custom Jetpack blocks for rich content and layout options.
 * Sort Order: 5
 * First Introduced: 13.9-a.8
 * Requires Connection: No
 * Auto Activate: Yes
 * Module Tags: blocks
 * Feature: Writing
 *
 * @package automattic/jetpack
 */

if ( ! defined( 'ABSPATH' ) ) {
	exit( 0 );
}

add_action( 'jetpack_activate_module_blocks', 'jetpack_blocks_activate_module' );

/**
 * Actions needed upon activating the blocks module.
 *
 * There is a legacy option to disable Jetpack blocks that we'll delete when this module is activated.
 * Via jetpack_get_default_modules filter, we remove blocks from the default if the option is true.
 * We'll leave that in place so _until the module is activated_ we will be sure to respect the previous
 * setting.
 *
 * @since 13.9
 * @return void
 */
function jetpack_blocks_activate_module() {
	delete_option( 'jetpack_blocks_disabled' ); // The function will check and return early if not present.
}

Jetpack_Gutenberg::load_block_editor_extensions();
Jetpack_Gutenberg::load_independent_blocks();
Jetpack_Gutenberg::register_block_metadata_collection();

/**
 * 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.
 *
 * 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.
 */
if ( is_admin() ) {
	add_action( 'enqueue_block_assets', array( 'Jetpack_Gutenberg', 'enqueue_block_editor_assets' ) );
} else {
	add_action( 'enqueue_block_editor_assets', array( 'Jetpack_Gutenberg', 'enqueue_block_editor_assets' ) );
}
add_filter( 'render_block', array( 'Jetpack_Gutenberg', 'display_deprecated_block_message' ), 10, 2 );