How-to
Troubleshoot Theme Conflicts
Diagnose stale products, pagination, counts, sorting, mobile layout, cache, and template conflicts.
When to use this
Use this when the filter works in some setups but breaks in yours — products do not update, the layout looks wrong, or filtering does nothing on a page built with a page builder.
Before you start
- You can reproduce the problem on a specific page.
- You can temporarily switch themes or disable a plugin on a staging copy.
Steps
- Reproduce and locate. Confirm the exact page and which part fails:
- Check selectors first. Custom themes and builders often rename the product
- Isolate the source. On a staging copy, switch to a default WooCommerce
- Test the page builder loop. A builder may render its own product loop
- Check the cache. A cache plugin can serve a stale filtered page. Exclude
- Apply the narrowest fix that resolves it and retest the original page.
products, count, pagination, sort, or layout.
loop. Correct the AJAX selectors before anything else — see *Configure AJAX selectors for a custom theme*.
theme and test. If it works, the theme markup is the cause. If not, test with other plugins disabled.
instead of the WooCommerce one. Point the filter at the loop the builder actually outputs, or use the builder's WooCommerce loop element.
the filtered storefront from full-page cache, or clear the cache and retest.
Expected result
The conflict is traced to a specific source — theme markup, builder loop, or cache — and resolved with a targeted change, usually a selector or cache rule, rather than disabling features.
Troubleshooting
- Works after switching to a default theme. Fix the selectors for the custom
- Works after clearing cache, breaks again later. Add a cache exclusion for
theme rather than keeping the default theme.
the filtered pages instead of clearing cache by hand.
Related
- How-to: Configure AJAX selectors for a custom theme.
- Explanation: How compatibility and selectors work with custom themes.
- Reference: Plugin Settings — Compatibility.