Changeset 60189 for branches/6.8/tests/phpunit/tests/blocks/applyBlockHooksToContentFromPostObject.php

Timestamp:

04/25/2025 07:21:31 PM (7 weeks ago)

Author:

jorbin

Message:

Block Hooks: Suppress insertion next to post content wrapper block.

As of [59523], Block Hooks are applied to post content. In order to allow for insertion of a hooked block as first_child or last_child of the containing Post Content block, we wrap the block's post content (as obtained from the DB) in a temporary <!-- wp:post-content --> wrapper block, apply the Block Hooks algorithm to the resulting markup, and remove the wrapper block. (The same technique is applied for the Synced Pattern block -- see [59543] -- as well as the Navigation block.)

However, this caused a problem when a hooked block was marked for insertion before before or after a Post Content block: The logic that's supposed to remove the temporary wrapper block after the Block Hooks algorithm runs erroneously removed that hooked block's delimiter instead of the wrapper block, producing garbled markup as a result.

This changeset fixes the issue by adding a hooked_block_types filter (with PHP_INT_MAX priority) that removes any blocks hooked before or after a Post Content block, if the current context is a post object. This prevents any blocks hooked that way from being "absorbed" into the corresponding post object's content; it retains the ability to hook blocks before and after a Post Content block in any other context (e.g. a template). (The same principle is applied to Synced Pattern and Navigation blocks.)

Reviewed by Jorbin.
Merges [60173] to 6.8 branch.

Props obenland, jorbin, gziolo, bernhard-reiter.
Fixes #63287.

Location:

branches/6.8

Files:

• . (modified) (1 prop)
• tests/phpunit/tests/blocks/applyBlockHooksToContentFromPostObject.php (modified) (3 diffs)

branches/6.8/tests/phpunit/tests/blocks/applyBlockHooksToContentFromPostObject.php

@@ -89 +89 @@
             )
         );
+
+        register_block_type(
+            'tests/hooked-block-after-post-content',
+            array(
+                'block_hooks' => array(
+                    'core/post-content' => 'after',
+                ),
+            )
+        );
+
+        register_block_type( 'tests/dynamically-hooked-block-before-post-content' );
     }
 
@@ -101 +112 @@
         $registry->unregister( 'tests/hooked-block' );
         $registry->unregister( 'tests/hooked-block-first-child' );
+        $registry->unregister( 'tests/hooked-block-after-post-content' );
+        $registry->unregister( 'tests/dynamically-hooked-block-before-post-content' );
     }
 
@@ -132 +145 @@
 
     /**
+     * @ticket 63287
+     */
+    public function test_apply_block_hooks_to_content_from_post_object_does_not_insert_hooked_block_before_container_block() {
+        $filter = function ( $hooked_block_types, $relative_position, $anchor_block_type ) {
+            if ( 'core/post-content' === $anchor_block_type && 'before' === $relative_position ) {
+                $hooked_block_types[] = 'tests/dynamically-hooked-block-before-post-content';
+            }
+
+            return $hooked_block_types;
+        };
+
+        $expected = '<!-- wp:tests/hooked-block-first-child /-->' .
+            self::$post->post_content .
+            '<!-- wp:tests/hooked-block /-->';
+
+        add_filter( 'hooked_block_types', $filter, 10, 3 );
+        $actual = apply_block_hooks_to_content_from_post_object(
+            self::$post->post_content,
+            self::$post,
+            'insert_hooked_blocks'
+        );
+        remove_filter( 'hooked_block_types', $filter, 10 );
+
+        $this->assertSame( $expected, $actual );
+    }
+
+    /**
      * @ticket 62716
      */