From f9385ac5fc0ecc3ed05555e4fd87c6b209f58463 Mon Sep 17 00:00:00 2001 From: Faisal Ahammad Date: Thu, 30 Jul 2026 17:25:27 +0600 Subject: [PATCH] fix(uppercase): enqueue frontend styles for uppercase rich-text format When the uppercase RichText format is applied to a core/paragraph block, the saved HTML contains but the CSS rule (.uppercase { text-transform: uppercase }) in style-coblocks-1.css was not loaded on the frontend. Two changes: - Widens has_coblocks_block() to pass the block_assets gate when post_content contains the uppercase format marker. This ensures coblocks-frontend is registered for the affected page. - Adds a render_block filter check that enqueues coblocks-frontend when a rendered block's content contains class="uppercase". Fixes #2654 --- includes/class-coblocks-block-assets.php | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/includes/class-coblocks-block-assets.php b/includes/class-coblocks-block-assets.php index eef7f0e5fe6..67801181c02 100644 --- a/includes/class-coblocks-block-assets.php +++ b/includes/class-coblocks-block-assets.php @@ -596,6 +596,11 @@ public function coblocks_enqueue_scripts_for_core_blocks( $block_content, $block ); } + // Enqueue frontend styles when a core block uses the uppercase rich-text format. + if ( false !== strpos( $block_content, 'class="uppercase"' ) ) { + wp_enqueue_style( 'coblocks-frontend' ); + } + return $block_content; } @@ -641,6 +646,8 @@ public function has_coblocks_block( WP_Post $post_object ) { array_filter( array( false !== strpos( $post_object->post_content, '