Raluca

Hi Jairo,
You’re exactly right that CartCheckoutUtils::is_checkout_page() returns true if the current page is the designated Checkout Page, regardless of whether the actual woocommerce/checkout block is present.

@alexggj there isn’t another function that searches recursively. I recommend creating an issue to adjust has_block_in_page to also search recursively. Until then you can do the recursive search on your end by grabbing the the blocks and searching for the checkout block. I generated this snipped with Chat GPT. Hope this helps.

// Use WC_Blocks_Utils::get_blocks_from_page to grab the blocks from the page.
function search_blocks_recursively( $blocks, $block_name ) {
    foreach ( $blocks as $block ) {
        if ( $block['blockName'] === $block_name ) {
            return true;
        }
        
        if ( ! empty( $block['innerBlocks'] ) ) {
            if ( search_blocks_recursively( $block['innerBlocks'], $block_name ) ) {
                return true;
            }
        }
    }
    return false;
}

// Usage:
$checkout_page_id = wc_get_page_id('checkout');
if ( has_block_recursively( 'woocommerce/checkout', $checkout_page_id ) ) {
    // Checkout block found (even if nested)
}

• This reply was modified 11 months, 3 weeks ago by Raluca.

Rolling back to 9.7.1 would fix the issue. This week we’ll release 9.8.2 with a fix.

I’m facing the same issue. The fix was to enable and show the postal code field—once it’s filled in, the delivery options show up. But how can I switch back to the previous setup, where everything worked without requiring a postal code?

@marhabaparfumuri how were you removing the postal code?

Hi @cutu234,

Thank you for reaching out.

We tested your scenario and were able to replicate. We created a GitHub issue for this and surfaced it to our team.

Writing 65.00 in the Minimum order amount for the free shipping setting might be a temporary fix.

We regret any inconvenience this may cause and appreciate your patience as we work to resolve the issue.

Hi everyone,

We are tracking this issue on https://github.com/woocommerce/woocommerce/issues/53057. Our team is working on fixing this. Please follow the GitHub issue above for updates.