A compare button and count are only useful if there’s somewhere for the shopper to actually see the side-by-side comparison once they’ve picked products.
Woo Compare’s List mode renders that page – a table of every product the shopper added, with their attributes lined up in rows.
For the full settings tour of every Woo Builder widget, see Woo Builder Settings Overview.
Requirement – This widget is a part of The Plus Addons for Elementor Pro, make sure it’s installed & activated to enjoy all its powers.
Before You Start
- Prerequisite: Elementor (free) installed and active.
- Prerequisite: WooCommerce installed and active, with at least one published product.
- Edition: all Woo Builder widgets are part of The Plus Addons for Elementor Pro – a Pro licence is required.
- Widget to enable: go to The Plus Addons > Widgets, search for Woo Compare and turn its toggle on.
- A dedicated page (for example “Compare”) to place this widget on.
Steps
- Create (or choose) a page to serve as your comparison page.
- Add the Woo Compare widget to it.
- From Type, choose List.
- Use the Field repeater to choose which product attributes/fields appear as rows in the comparison table (for example price, rating, stock status).
Once shoppers have added products (for example “Cropped Boxy Hoodie” and “Canvas Tote Bag”) using the Button mode elsewhere on the site, this page is meant to render them side by side.
As currently shipped, it does not. See Limitations below before building anything that depends on this page working.
Settings Overview
| Setting | What it does | Default |
|---|---|---|
| Type | Must be List to render the comparison table. | Button (change to List) |
| Field (repeater) | Which product attributes appear as comparison rows. | – |
Limitations
- Confirmed defect: the List page never finishes loading – it shows “Loading…” indefinitely. The front-end request to
admin-ajax.phpthat fetches the compared items’ data returns 403 Forbidden (confirmed via browser network trace), so the JavaScript that would render the table never receives its data. This happened with two different real items compared, not only in an empty state. - Reported as a product issue. The Button and Count modes (see the linked docs) are not affected and are confirmed working.
Not verified
So you know exactly what has and has not been checked:
- Whether the 403 is caused by a missing/incorrect AJAX nonce, a security plugin, or a server rule specific to this Docker site – the browser evidence confirms the symptom and its immediate cause (the AJAX call itself), not the underlying reason WordPress rejected it with 403.
