Changeset 59523 for trunk/tests/phpunit/tests/blocks/applyBlockHooksToContent.php

Timestamp:

12/17/2024 10:35:17 AM (6 months ago)

Author:

Bernhard Reiter

Message:

Block Hooks: Enable for post content.

Block Hooks were previously only applied to layout elements such as templates, template parts, patterns, and navigation menus -- things that are edited in the Site Editor.

This changeset enables Block Hooks in post content. The parity between frontend and editor is preserved: Blocks inserted by Block Hooks are visible both on the frontend and in the editor, and any customizations made by the user are respected on the frontend.

This is possible thanks to setting the metadata.ignoredHookedBlocks attribute on anchor blocks (a technique first introduced in [57594]). For first child and last child insertion into a Post Content block, the corresponding post object's _wp_ignored_hooked_blocks post meta is set.

Props bernhard-reiter, gziolo, jonsurrell, karolmanijak, leewillis77.
Fixes #61074.

File:

• trunk/tests/phpunit/tests/blocks/applyBlockHooksToContent.php (modified) (1 diff)

trunk/tests/phpunit/tests/blocks/applyBlockHooksToContent.php

@@ -93 +93 @@
 
     /**
+     * @ticket 61074
+     */
+    public function test_apply_block_hooks_to_content_with_context_set_to_null() {
+        $content = '<!-- wp:tests/anchor-block /-->';
+
+        /*
+         * apply_block_hooks_to_content() will fall back to the global $post object (via get_post())
+         * if the $context parameter is null. However, we'd also like to ensure that the function
+         * works as expected even when get_post() returns null.
+         */
+        $this->assertNull( get_post() );
+
+        $actual = apply_block_hooks_to_content( $content, null, 'insert_hooked_blocks' );
+        $this->assertSame(
+            '<!-- wp:tests/anchor-block /--><!-- wp:tests/hooked-block /-->',
+            $actual
+        );
+    }
+
+    /**
      * @ticket 61902
      */