From ffc5b622768c6d170e3b56a942fe952fa9cf539b Mon Sep 17 00:00:00 2001 From: Andrew Duthie Date: Wed, 30 Jan 2019 17:10:48 -0500 Subject: [PATCH] Plugin: Remove `user_can_richedit` filtering (#13608) --- lib/client-assets.php | 9 +-------- 1 file changed, 1 insertion(+), 8 deletions(-) diff --git a/lib/client-assets.php b/lib/client-assets.php index 469310edbe118..96986825e9bc2 100644 --- a/lib/client-assets.php +++ b/lib/client-assets.php @@ -893,13 +893,6 @@ function gutenberg_editor_scripts_and_styles( $hook ) { 'after' ); - // Ignore Classic Editor's `rich_editing` user option, aka "Disable visual - // editor". Forcing this to be true guarantees that TinyMCE and its plugins - // are available in Gutenberg. Fixes - // https://github.com/WordPress/gutenberg/issues/5667. - $user_can_richedit = user_can_richedit(); - add_filter( 'user_can_richedit', '__return_true' ); - wp_enqueue_script( 'wp-edit-post' ); wp_enqueue_script( 'wp-format-library' ); wp_enqueue_style( 'wp-format-library' ); @@ -1134,7 +1127,7 @@ function gutenberg_editor_scripts_and_styles( $hook ) { 'allowedMimeTypes' => get_allowed_mime_types(), 'styles' => $styles, 'imageSizes' => gutenberg_get_available_image_sizes(), - 'richEditingEnabled' => $user_can_richedit, + 'richEditingEnabled' => user_can_richedit(), // Ideally, we'd remove this and rely on a REST API endpoint. 'postLock' => $lock_details,