WP Grid Builder plugin review and common issues

Check browser DevTools Console for JavaScript errors during facet selection. The AJAX filter response must be valid JSON. Common causes: (1) a PHP error on the server is breaking the AJAX response — enable WP_DEBUG to surface errors; (2) a security plugin blocking WP Grid Builder’s AJAX endpoint; (3) a JavaScript conflict with another plugin’s scripts; (4) the grid and facet widget are on different pages (must be on the same page for direct filtering); (5) the WP Grid Builder cache needs clearing after configuration changes — clear it in WP Grid Builder → Settings → Cache.

WP Grid Builder uses an index for filtering performance. The index updates automatically when posts are created, updated, or deleted. If the index is out of sync: (1) manually rebuild the index in WP Grid Builder → Settings → Index → Rebuild Index; (2) for WooCommerce product price range filters, trigger a product save to update the price index; (3) if using a staging site where content was copied, the index must be rebuilt from scratch on the new domain; (4) ensure WordPress cron is running for automatic index updates.

In the WP Grid Builder card builder, custom fields are inserted using blocks or field placeholders. For ACF fields: (1) verify ACF is active and the field is assigned to the post type being displayed; (2) use the dynamic field block in the card builder and select ACF as the field source; (3) verify the field has a value for the posts being displayed — empty fields show nothing; (4) some ACF field types (Repeater, Flexible Content) require custom output formatting — use WP Grid Builder’s custom PHP card template for complex ACF field output.

Create a WP Grid Builder grid targeting WooCommerce products. In the facet settings, add: (1) a Checkbox facet for Product Category; (2) a Range Slider facet for Price (uses WP Grid Builder’s WooCommerce price field); (3) optionally a Rating facet and Stock Status facet. Design the product card with WP Grid Builder’s card builder: product image, title, price, rating, and Add to Cart button using WooCommerce dynamic fields. Place the grid and facets on a page using the WP Grid Builder shortcode or Elementor/Gutenberg widget.

In WP Grid Builder → Grid → [grid] → Settings → Pagination, select “Infinite Scroll” as the pagination type. Configure the scroll trigger: “Scroll” (loads when visitor scrolls near the bottom) or “Button” (loads on “Load More” click). Set the number of items to load per page and the transition animation. WP Grid Builder handles the AJAX loading of additional items, updating the DOM without page reload. Infinite scroll works with all facets — filtering and scrolling work together to progressively reveal matching content.

WP Grid Builder is better when you also need to control how items appear in the grid (integrated card builder) and when filtering performance at large scale is critical (indexed facets). FacetWP is better for sites where an existing display system (Elementor Pro Archive, a theme’s template) handles content display and FacetWP adds filtering on top — FacetWP integrates more broadly with existing content display systems. WP Grid Builder requires using its own grid/card system for display, which gives more control but requires adopting its card builder. For sites starting fresh where filtering and display are being built together, WP Grid Builder’s integrated approach is compelling.

Yes — WP Grid Builder supports filtering by any registered WordPress taxonomy, including custom taxonomies created by plugins like CPT UI, ACF, or custom code. Add a Checkbox, Radio, or Select facet targeting your custom taxonomy. WP Grid Builder builds the facet index for the custom taxonomy terms automatically. The filter displays the taxonomy terms with counts and filters the grid to matching posts. Custom taxonomy hierarchies (parent/child terms) are also supported with hierarchical display options in the facet settings.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.