Suspected JS Conflict
Hi Muffin Group Support,
I'm running into a bug I believe is caused by a conflict between BeTheme/BeBuilder and WooCommerce, specifically involving Grouped Products.
Setup:
- Theme: BeTheme, version 28.5.3
- Builder: BeBuilder
- WordPress version: 7.0
- WooCommerce version: 10.9.4
- Site: https://kobin.cloudaccess.host
Issue:
I have a WooCommerce Grouped Product whose child products are Simple Products with "Sold Individually" enabled. Because of that setting, WooCommerce renders a checkbox for each child product instead of a quantity number field (this is standard WooCommerce behavior for sold-individually items in a grouped product).
Visually, the checkboxes work fine — I can click them and they appear checked. However, when I click "Add to Cart," WooCommerce always shows the error "Please choose the quantity of items you wish to add to your cart," even with boxes visibly checked.
I dug into this with Chrome DevTools and found that the checkbox's underlying `checked` DOM property does not change when clicked — it appears stuck, and the value WooCommerce reads for validation never actually updates, even though the checkbox looks checked on screen.
I confirmed this is theme-related: when I temporarily switched to a default theme (Storefront), the exact same Grouped Product worked correctly — checkboxes functioned normally and Add to Cart succeeded. Switching back to BeTheme reproduces the bug immediately. I've ruled out plugin conflicts (tested with all non-essential plugins deactivated) and WordPress/WooCommerce core versions (fully updated, bug persists).
Given that switching only the theme resolves it, this points to a BeTheme or BeBuilder script that's intercepting the checkbox click (likely for custom styling) without properly updating the checkbox's real checked state, which WooCommerce's own validation script then reads as unchecked.
Is this a known compatibility issue with WooCommerce Grouped Products + Sold Individually child products? If there's a fixed script version or recommended workaround, I'd really appreciate it — happy to provide screenshots, a screen recording, or DevTools console/element details if that's helpful.
Thanks for your help,
Doug Rooney
Rooney Creative
PLEASE RESPOND TO [email protected]
While waiting for a response from one of our team members, we recommend to check Support Center where it is highly likely that you will find the answer to your question in no time.
FAQ | Video Tutorials | How to