Guard registration of post type and REST endpoints if option is not enabled

Author: chriszarate

src/wp-includes/post.php

@@ -657,38 +657,40 @@ function create_initial_post_types() {
 		)
 	);
 
-	register_post_type(
-		'wp_sync_storage',
-		array(
-			'labels'             => array(
-				'name'          => __( 'Sync Updates' ),
-				'singular_name' => __( 'Sync Update' ),
-			),
-			'public'             => false,
-			'_builtin'           => true, /* internal use only. don't use this when registering your own post type. */
-			'hierarchical'       => false,
-			'capabilities'       => array(
-				'read'                   => 'do_not_allow',
-				'read_private_posts'     => 'do_not_allow',
-				'create_posts'           => 'do_not_allow',
-				'publish_posts'          => 'do_not_allow',
-				'edit_posts'             => 'do_not_allow',
-				'edit_others_posts'      => 'do_not_allow',
-				'edit_published_posts'   => 'do_not_allow',
-				'delete_posts'           => 'do_not_allow',
-				'delete_others_posts'    => 'do_not_allow',
-				'delete_published_posts' => 'do_not_allow',
-			),
-			'map_meta_cap'       => false,
-			'publicly_queryable' => false,
-			'query_var'          => false,
-			'rewrite'            => false,
-			'show_in_menu'       => false,
-			'show_in_rest'       => false,
-			'show_ui'            => false,
-			'supports'           => array( 'custom-fields' ),
-		)
-	);
+	if ( get_option( 'enable_real_time_collaboration' ) ) {
+		register_post_type(
+			'wp_sync_storage',
+			array(
+				'labels'             => array(
+					'name'          => __( 'Sync Updates' ),
+					'singular_name' => __( 'Sync Update' ),
+				),
+				'public'             => false,
+				'_builtin'           => true, /* internal use only. don't use this when registering your own post type. */
+				'hierarchical'       => false,
+				'capabilities'       => array(
+					'read'                   => 'do_not_allow',
+					'read_private_posts'     => 'do_not_allow',
+					'create_posts'           => 'do_not_allow',
+					'publish_posts'          => 'do_not_allow',
+					'edit_posts'             => 'do_not_allow',
+					'edit_others_posts'      => 'do_not_allow',
+					'edit_published_posts'   => 'do_not_allow',
+					'delete_posts'           => 'do_not_allow',
+					'delete_others_posts'    => 'do_not_allow',
+					'delete_published_posts' => 'do_not_allow',
+				),
+				'map_meta_cap'       => false,
+				'publicly_queryable' => false,
+				'query_var'          => false,
+				'rewrite'            => false,
+				'show_in_menu'       => false,
+				'show_in_rest'       => false,
+				'show_ui'            => false,
+				'supports'           => array( 'custom-fields' ),
+			)
+		);
+	}
 
 	register_post_status(
 		'publish',
@@ -8665,27 +8667,29 @@ function wp_create_initial_post_meta() {
 		)
 	);
 
-	register_meta(
-		'post',
-		'_crdt_document',
-		array(
-			'auth_callback'     => static function ( bool $_allowed, string $_meta_key, int $object_id, int $user_id ): bool {
-				return user_can( $user_id, 'edit_post', $object_id );
-			},
-			/*
-			 * Revisions must be disabled because we always want to preserve
-			 * the latest persisted CRDT document, even when a revision is restored.
-			 * This ensures that we can continue to apply updates to a shared document
-			 * and peers can simply merge the restored revision like any other incoming
-			 * update.
-			 *
-			 * If we want to persist CRDT documents alongside revisions in the
-			 * future, we should do so in a separate meta key.
-			 */
-			'revisions_enabled' => false,
-			'show_in_rest'      => true,
-			'single'            => true,
-			'type'              => 'string',
-		)
-	);
+	if ( get_option( 'enable_real_time_collaboration' ) ) {
+		register_meta(
+			'post',
+			'_crdt_document',
+			array(
+				'auth_callback'     => static function ( bool $_allowed, string $_meta_key, int $object_id, int $user_id ): bool {
+					return user_can( $user_id, 'edit_post', $object_id );
+				},
+				/*
+				 * Revisions must be disabled because we always want to preserve
+				 * the latest persisted CRDT document, even when a revision is restored.
+				 * This ensures that we can continue to apply updates to a shared document
+				 * and peers can simply merge the restored revision like any other incoming
+				 * update.
+				 *
+				 * If we want to persist CRDT documents alongside revisions in the
+				 * future, we should do so in a separate meta key.
+				 */
+				'revisions_enabled' => false,
+				'show_in_rest'      => true,
+				'single'            => true,
+				'type'              => 'string',
+			)
+		);
+	}
 }

src/wp-includes/rest-api.php

@@ -430,9 +430,11 @@ function create_initial_rest_routes() {
 	$icons_controller->register_routes();
 
 	// Collaboration.
-	$sync_storage = new WP_Sync_Post_Meta_Storage();
-	$sync_server  = new WP_HTTP_Polling_Sync_Server( $sync_storage );
-	$sync_server->register_routes();
+	if ( get_option( 'enable_real_time_collaboration' ) ) {
+		$sync_storage = new WP_Sync_Post_Meta_Storage();
+		$sync_server  = new WP_HTTP_Polling_Sync_Server( $sync_storage );
+		$sync_server->register_routes();
+	}
 }
 
 /**