Product Collection Block

Hi @jayfry,

Ahh ah! I totally get how frustrating this can be situations like this can throw even the most experienced developer off balance.

The issue you’re running into is caused by the “ignoredHookedBlocks” metadata:

"ignoredHookedBlocks": ["woocommerce/product-summary", "woocommerce/product-stock-indicator"]

This is automatically injected to avoid block duplication. Even if you try to add product-summary or product-stock-indicator using block hooks, WordPress skips them if they’re listed in ignoredHookedBlocks.

A better approach would be to create a custom block pattern that includes the blocks you want. Here’s an example you can use:

function register_custom_product_collection_pattern() {
    if ( function_exists( 'register_block_pattern' ) ) {
        register_block_pattern(
            'my-theme/product-collection-extended',
            array(
                'title'       => __( 'Extended Product Collection', 'your-theme-slug' ),
                'description' => __( 'Product collection with summary and stock indicator', 'your-theme-slug' ),
                'content'     => '
<!-- wp:woocommerce/product-collection -->
<div class="wp-block-woocommerce-product-collection">
    <!-- wp:woocommerce/product-template -->
    <div class="wp-block-woocommerce-product-template">
        <!-- wp:woocommerce/product-image /-->
        <!-- wp:woocommerce/product-title /-->
        <!-- wp:woocommerce/product-summary /-->
        <!-- wp:woocommerce/product-price /-->
        <!-- wp:woocommerce/product-stock-indicator /-->
        <!-- wp:woocommerce/product-button /-->
    </div>
    <!-- /wp:woocommerce/product-template -->
</div>
<!-- /wp:woocommerce/product-collection -->',
                'categories'  => array( 'woocommerce' ),
            )
        );
    }
}
add_action( 'init', 'register_custom_product_collection_pattern' );

Once added, you can use this block pattern from the editor by searching for “Extended Product Collection”.

While I’m happy to help point you in the right direction, this kind of customization falls outside the general support scope. If you need more in-depth help, you can reach out to a developer via platforms like codeable.io, or post in Woo’s Slack community to get input from others.

Hi @jayfry.

Thank you for getting back to me and for the clarification. I’ve taken some time to review the situation, and it looks like the workaround that could resolve this would require more advanced custom coding.

Since this goes beyond our support scope, I recommend reaching out to a developer through platforms like codeable.io, or posting in the WooCommerce Slack community. Other experienced developers there might also offer alternative solutions that better fit your setup.