Huan
Forum Replies Created
-
Thank you Nick. Block variations and filters sound fantastic until I realize they are indiscriminate. I hope they can be applied based on namespace, or
ancestor/parentproperty.In terms of inner blocks,
allowedBlocksshould be passed to all descendants and descendants should be able to overrideallowedBlocks. To my fuzzy knowledge, someone opened a related issue in Github?Got it. @properlypurple thank you so much!
Thanks Tobias, finally I got it right by wrapping TP block with a Group block, turning off Group block’s “Inner blocks use content width”, and setting alignment for Group block.
Users (like me) may attempt to set alignment for TP block, which doesn’t work. Thank you again and hopefully there will be no Group block workaround in the future.
- This reply was modified 2 years, 2 months ago by Huan.
I just used WordPress Playground (2024 theme) to add a Group block. Here are the classes it output:
class="wp-block-group alignwide has-global-padding is-layout-constrained wp-block-group-is-layout-constrained"Your testing site’s Group block outputs the wrong classes, which can lead you to incorrectly configure TP…
Thanks for your test page. It helped me locate the problem. Your Group block output different classes than mine.
Your Group block:
<div class="wp-block-group alignwide is-layout-flow wp-block-group-is-layout-flow"> <!-- TP block --> <div id="tablepress-1_wrapper" class="dataTables_wrapper"> <!-- the rest of TP --> </div> </div>My Group block:
<div class="wp-block-group alignwide has-global-padding is-layout-constrained wp-block-group-is-layout-constrained"> <!-- TP block --> <div id="tablepress-1_wrapper" class="dataTables_wrapper"> <!-- the rest of TP --> </div> </div>Therefore my
.dataTables_wrapperis impacted by.is-layout-constrained, whereas its sibling is not (I put many WP core blocks right next to WP block, in the same Group block, for comparison):body .is-layout-constrained > :where(:not(.alignleft):not(.alignright):not(.alignfull)) { max-width: var(--wp--style--global--content-size); margin-left: auto !important; margin-right: auto !important; }Other WP core blocks comply with Group block’s alignment settings, whereas TP block doesn’t!
Regarding horizontal scrolling, I changed to a different computer and I can see that
overflow-x:auto;effect, whereas on my original computer it didn’t appear across my 3 browsers. I haven’t restarted the original computer for a while due to so many tabs are in use. My fault!Thanks Tobias for your fast response. I tried your trick.
This time I deactivated all plugins except TP, switched to Twenty Twenty-Four theme, and put TP block inside a Group block (both set to Wide width), all issues persisted unfortunately.
(This time I imported a second WooCommerce Product CSV from another source into TP. My two TP table creation were through CSV import.)
I’m in rapid development of my staging site (runs on PHP 8.1) so by the time you visit that page, plugins and theme may change…
- This reply was modified 2 years, 3 months ago by Huan.
When I deactivated the plugin, the feedback field limits user’s input to one or two sentences. You don’t get detailed feedback from one or two sentences…
There’s no Delete-related UI inside each entry.

BTW, here is possible combo:
- FluentForms (Pro?)
- FluentSMTP
- FluentCRM (Pro?)
- Amazon SES
Can this combo make a newsletter signup popup form? It’s kind of too much setup and cost…
HubSpot, MailPoet are also candidates.
Thanks @pareshsojitra, I’m 100% confident that this will be added to core, it’s a matter of time, although it can take months or years…
Forum: Plugins
In reply to: [WooCommerce] Documentation on WC “blocks” customization for developers?Thank you @carolm29. The Github doc is helpful, which Google never show if not including “github” in search query 🤔
Searching Github with “repo:woocommerce/woocommerce-blocks variations” doesn’t show anything other than product variations.
I’d like to know if block variations are possible in Woo?
- This reply was modified 2 years, 5 months ago by Huan.
Forum: Reviews
In reply to: [WooCommerce] Woo “blocks” are the right direction to go!Product Details block should offer “expanded by default” layout option. At the moment the block is collapsed into tabs. I replace Product Details block with Post Content block instead! (with optional insertion of Additional Information shortcode)
Forum: Reviews
In reply to: [WooCommerce] Woo “blocks” are the right direction to go!Thank you @sandipmondal. Product Image Gallery block can have a ‘No thumbnail’ layout option as demonstrated by LV (desktop & mobile):
https://eu.louisvuitton.com/eng-e1/products/venus-monogram-nvprod4810078v/M82993
Another thing:
I found Related Products block doesn’t display Linked Products (Upsells and Cross-sells). But, I can use Product Collection (beta) block to display Hand-picked products, which can do what Related Products block is supposed to do.
Product Collection (beta) block is powerful, and Related Products block doesn’t display Linked Products. Should I use Product Collection (beta) block to replace most other query-loop-ish blocks?
Thanks!
- This reply was modified 2 years, 6 months ago by Huan.
Forum: Plugins
In reply to: [WooCommerce] remove_theme_support no longer works for WC blocks?Thanks @babylon1999, with your help, this finally achieves what I want by fixing the root cause:
// Remove Single Product gallery image zoom. add_filter( 'woocommerce_single_product_zoom_enabled', '__return_false' ); // Remove Single Product gallery image link. function wc_remove_link_on_thumbnails( $html ) { return strip_tags( $html, '<div><img>' ); } add_filter( 'woocommerce_single_product_image_thumbnail_html', 'wc_remove_link_on_thumbnails' );Hope this helps others too. Again, any improvement is welcome.
Forum: Plugins
In reply to: [WooCommerce] remove_theme_support no longer works for WC blocks?This PHP+CSS combination seems to work:
function wc_remove_image_effect_support() { remove_theme_support( 'wc-product-gallery-zoom' ); remove_theme_support( 'wc-product-gallery-lightbox' ); } add_action( 'wp', 'wc_remove_image_effect_support', 99 );.woocommerce .woocommerce-product-gallery__image { pointer-events: none; }Any improvement idea is appreciated.