WoodMart fix
WoodMart Filters, Swatches or Cart Not Working: Theme or Plugin?
WoodMart does not leave the shop to WooCommerce. The AJAX filters, the swatches, the quick view and the slide-out cart are the theme's own code laid over the plugin, so a fault in any of them has two possible owners. Working out which one is most of the repair.
1,760 shoppers clicked a filter and got a spinner. A second filter plugin collided with the AJAX shop.
What you are seeing
- Clicking a filter spins, then shows the same products or none
- Color and size swatches reverted to plain dropdown menus
- The cart icon says zero after a product was added
- Quick view opens an empty window or never opens at all
- A payment method or a field has gone missing from checkout
Why it happens on WoodMart
Most common first.
- 1
A second plugin doing a job WoodMart already does
WoodMart ships its own layered navigation widgets, swatches, wishlist, compare and quick view. Install a filter plugin or a swatch plugin beside them and both attach to the same products. The usual result is a filter that fires twice, or swatches drawn by one and ignored by the other.
- 2
The AJAX shop and a script that expects a full page load
With AJAX shop on, WoodMart swaps the product grid in place when a shopper filters, sorts or changes page. Scripts from other plugins that run only when a page loads never see the new products. Badges, custom buttons and tracking attached to the grid work on arrival and stop after the first filter click.
- 3
Swatches set on the wrong kind of attribute
WoodMart draws swatches from global attributes created under Products, Attributes, where each term carries its color, image or label. An attribute typed straight into a single product has no terms to carry a swatch, so it falls back to a dropdown. Product imports and bulk edits create these custom attributes without telling anyone.
- 4
Optimization that delays or caches the cart
The mini cart and its count are filled in by a WooCommerce script after the page loads. A plugin set to delay all JavaScript, to strip cart fragments or to cache pages for visitors who already hold a cart leaves the icon stuck at zero, or showing a stranger's total.
- 5
Old template overrides or a custom checkout layout
WoodMart overrides WooCommerce's templates with its own, and a child theme may override those again. Newer versions also let the cart and checkout be assembled from elements under WoodMart, Layouts. An old override, or a layout missing one element, is how a payment method, a coupon field or the order notes quietly disappear.
How to fix it, in order
Least invasive first. Stop at the step that fixes it.
- 1
Watch the browser console while you click
Work on a staging copy if the store is busy. In a private window open the shop, press F12 and choose Console. Click the filter, the swatch or Add to cart. A red error naming a script file tells you which plugin or theme file to look at.
- 2
Switch off duplicate plugins one at a time
Deactivate any third-party filter, swatch, wishlist or quick view plugin and retest after each. If the fault clears, decide which side should own that feature. To keep the plugin, turn off WoodMart's version of it in Theme Settings instead.
- 3
Test with AJAX shop off
Open WoodMart, Theme Settings and type AJAX into the search box at the top to find the AJAX shop option. Turn it off and filter again. If everything works with full page loads, a script on the page cannot cope with the in-place refresh, and the console usually says which.
- 4
Rebuild swatches from global attributes
Go to Products, Attributes, open the attribute and set a swatch on each term. Then edit an affected product and confirm it uses that global attribute with Used for variations ticked. If the options are missing entirely, not merely plain, that is product data, and the variations fix linked below covers it.
- 5
Keep optimization away from the cart
In the cache plugin, confirm that cart, checkout and my account are never cached and that visitors with a cart cookie are served fresh pages. If JavaScript is delayed or deferred, exclude WooCommerce's cart fragments script and the theme's scripts. Purge, then retest in a private window.
- 6
Check templates and the checkout layout
WooCommerce, Status, Templates lists outdated overrides. Update or delete the ones in the child theme. If a custom layout is assigned under WoodMart, Layouts, disable it briefly on staging and compare. Finish by placing a test order with each payment method.
Keep it from coming back
- Give each shop feature one owner: the theme or a plugin, not both
- Create attributes under Products, Attributes before importing products
- Retest filter, swatch, cart and checkout after every theme or WooCommerce update
- Add optimization settings one at a time and check the cart count after each
The permanent fix
A faster Next.js build, with a CMS made for your business
When the filter, the swatch plugin, the cache and the checkout layout have each been patched to tolerate the others, the shop works by truce. A Next.js storefront with a custom CMS builds filtering, variant selection and the cart as one piece of code written for your catalog, so there is no theme layer and plugin layer to disagree. That is worth weighing once the same faults return after every update.
| On WoodMart today | On Next.js with a custom CMS | |
|---|---|---|
| What you keep updated | WordPress, the theme, its builder and every bundled plugin, all in step | Nothing on a schedule. There is no theme or plugin stack to fall out of step |
| How a page is served | Built from the database on each visit, through the theme and its builder | Built ahead of time and served as finished files from servers near the visitor |
| How you edit it | A general-purpose builder with every option the theme ships | A CMS built around what your business actually changes: services, prices, photos, posts |
| What can break it | An update to any one of those parts, or a license that lapses | A change someone makes on purpose, tested before it goes live |
Your content, your addresses and your rankings come with you: every page is moved, every old address is redirected, and you get a login to an editor that only shows what you need. A repair is still the right call for many sites, and we will say so when it is.
Want this fixed on your WoodMart site?
Tell us what you are seeing. We look at the site, tell you plainly what is wrong and what it takes, and quote a fixed price before any work starts.
Which of these sounds like you? (pick any)
Frequently asked
Usually not. The theme includes layered navigation, price and stock filters and an AJAX shop, which covers most catalogs. A dedicated filter plugin earns its place on very large catalogs or unusual filtering rules. If you add one, remove the theme's filter widgets and test with AJAX shop both on and off.
The attribute is almost always a custom one typed into the product, not a global attribute with swatches set on its terms. Create the attribute under Products, Attributes and give each term a color, image or label, then move the product's variations onto it. A swatch plugin running beside the theme's own is the next most likely reason.
The count is updated by a script after the page loads. When an optimization plugin delays that script, or a page cache serves a stored copy to a visitor with a cart, the icon never refreshes. The product is in the cart all the same. Open the cart page to confirm, then fix the exclusions.
One test on a staging copy answers it. Activate the Storefront theme and repeat the action. If the cart, the variations or checkout fail there too, the fault is WooCommerce, an extension or the server. If they work, it sits in WoodMart, its Core plugin or a child theme override.
Keep reading
- ServiceeCommerce DevelopmentBuild a store that makes buying feel simple. We shape product pages, checkout, payments, tracking, and store workflows so customers can act with confidence.
- ServiceFixing WordPress PluginsOne bad plugin can take your whole site down. We fix plugin conflicts, fatal errors, and security holes fast — and build custom plugins when the off-the-shelf ones fall short.
- ServiceForms & Scripts Not WorkingA form that quietly fails is the most expensive bug on a website — you never see the leads you lost. We fix it, then prove the message arrives.