FacetWP Bricks Integration Addon

Building a filterable product or post listing with Bricks looks easy until the listing ignores the filters, pagination gets stuck on page one, or the filtering can't find the loop. This add-on is the bridge that lets FacetWP recognize Bricks Builder listings.

People filtering a catalog don't want more pages, they want fewer results

FacetWP handles filtering with facets (checkboxes, dropdowns, search, ranges, etc.) and this add-on lets those facets act on the listings you build with Bricks, without redoing the design in another system.

Which Bricks listings FacetWP Bricks Integration Addon supports

The add-on works with three Bricks elements:

• Posts: you tick the "Use FacetWP" checkbox in the element settings and paste your facet shortcodes into a Shortcode element.
• Query Loop: the loop you can enable on a Container, Block or Div. It needs a wrapper Div so FacetWP can detect the listing, and you must enable both "Use query loop" and "Use FacetWP".
• Products: available if WooCommerce is installed, with the same instructions as the Posts element.

Also, if an element doesn't offer the checkbox, FacetWP can be enabled by hand with a Bricks filter in the child theme's functions.php, using the element's internal ID (which is not the same as the CSS ID you see in the field).

Only one FacetWP listing per page

This is the limit that surprises people most: each page can only have one Bricks element with FacetWP enabled. If you were planning a homepage with three different filterable carousels, it won't work. Plan one page per filterable listing.

Another practical detail: if you see the error "FacetWP was unable to auto-detect the post listing", disable the "Cache query loops" option in Bricks, under Settings and Performance.

Pagination depends on the element you use

This is where setups most often fail, because each element behaves differently:

• Posts: use the element's own pagination (Pagination > Show) or a Pager facet. A separate Pagination element doesn't work with FacetWP.
• Query Loop: it does support a separate Pagination element, but it must sit in the same parent container as the Container, Block or Div with FacetWP enabled, and you must select that element in its "Query" setting. A Pager facet also works.
• Products: it has no pagination setting of its own; use a Pager facet. Neither the Pagination element nor the products pagination element works here.

It needs FacetWP and some preparation work

This add-on doesn't come with facets and doesn't filter by itself: it is an extension of FacetWP, so you need the main plugin and have to create the facets yourself. It doesn't design the listing either: you do that in Bricks.

• Already solved: FacetWP detecting and filtering the Bricks Posts, Query Loop and Products elements.
• You cover with FacetWP: creating the facets, indexing the data and placing their shortcodes on the page.
• You cover in Bricks: the design of the listing cards and their layout.
• You cover with code or a professional: any element that lacks the "Use FacetWP" checkbox, using the PHP filter described.

Frequently asked questions

Does it work with several filterable listings on the same page?

No. Only one Bricks element with FacetWP is supported per page.

Is it suitable for WooCommerce stores?

Yes, with the Bricks Products element, which appears when WooCommerce is installed. Use a Pager facet for pagination.

Can I use the Bricks Pagination element with Posts?

Not with FacetWP. Enable pagination inside the Posts element itself or use a Pager facet.

Do I need to know how to code?

Not for the usual cases: you just tick checkboxes. Code is only needed if you want to enable FacetWP on an element that doesn't offer that option.