-
joekinsella115
Hi,
I’m running GeneratePress with GenerateBlocks Pro and WooCommerce. My mini cart is added via a GP Element (type: Site Header, displayed sitewide) using the WooCommerce Mini Cart block.
The mini cart works correctly on standard pages. However on WooCommerce product and category pages it renders at the bottom of the page below all content rather than as an overlay, and does not open correctly when clicked.
I’ve ruled out the following as causes:It happens on category pages which have no custom template and no ScrollSmoother wrapper — so it is not a smooth scroll conflict
I tested hooking my custom product layout via generate_before_main_content instead of a template_include filter and the issue persists on both approaches — so it is not caused by my custom template structureThe issue appears to be specific to WooCommerce template pages (product, category, shop) regardless of how the content is delivered. Standard WordPress pages work fine.
Questions:Is there a known conflict between GP Elements (Site Header) and WooCommerce block templates that causes the mini cart drawer to mount incorrectly on WooCommerce pages?
Is there a recommended way to use the WooCommerce Mini Cart block within a GP Element on WooCommerce-templated pages specifically?Thanks
-
joekinsella115
the page to test https://novorior.com/product/novorior-align/
home page which is static page which works fine: https://novorior.com/
i disbaled my css file for this page and the issue is still there which rules out the problem being that pages cusotm cs s
-
joekinsella115
Additionally the mini cart trigger button itself does not become visible on WooCommerce pages — it remains in its pre-hydration hidden state. It works correctly on standard WordPress pages. This suggests the Interactivity API hydration is not completing on WooCommerce-templated pages specifically. Both the button visibility and the drawer position issues are isolated to WooCommerce pages only.
-
joekinsella115
The custom single-product-empty.php template was breaking the block hydration because it was outputting a complete HTML document wrapper around get_header() which already outputs one.
-
George
Glad it’s sorted!
- You must be logged in to reply to this topic.