| @@ -27,20 +27,4 @@ | ||
| 27 | 27 | */ |
| 28 | 28 | function jetpack_blocks_activate_module() { |
| 29 | 29 | delete_option( 'jetpack_blocks_disabled' ); // The function will check and return early if not present. |
| 30 | 30 | } |
| 31 | - | |
| 32 | -Jetpack_Gutenberg::load_block_editor_extensions(); | |
| 33 | -Jetpack_Gutenberg::load_independent_blocks(); | |
| 34 | -Jetpack_Gutenberg::register_block_metadata_collection(); | |
| 35 | - | |
| 36 | -/** | |
| 37 | - * 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. | |
| 38 | - * | |
| 39 | - * 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. | |
| 40 | - */ | |
| 41 | -if ( is_admin() ) { | |
| 42 | - add_action( 'enqueue_block_assets', array( 'Jetpack_Gutenberg', 'enqueue_block_editor_assets' ) ); | |
| 43 | -} else { | |
| 44 | - add_action( 'enqueue_block_editor_assets', array( 'Jetpack_Gutenberg', 'enqueue_block_editor_assets' ) ); | |
| 45 | -} | |
| 46 | -add_filter( 'render_block', array( 'Jetpack_Gutenberg', 'display_deprecated_block_message' ), 10, 2 ); | |