Bricks already works great with Meta Box dynamic data when reading fields stored in Meta Box Custom Tables. However, there is currently a significant limitation when building catalog pages or complex archives:
- Query Loop Limitation: Bricks Query Loops cannot natively perform filtering, sorting, or meta-queries on fields stored in Meta Box Custom Tables, as the underlying query still expects standard wp_postmeta rows.
- Filtering & Faceting Limitations: Because Query Loops don’t natively map to Meta Box Custom Tables, dynamic filtering (like faceted search or attribute filtering) fails or requires heavy custom PHP hooks.
WHY THIS MATTERS:
For high-SKU stores or complex B2B catalogs (e.g., cutting tools, industrial hardware, machinery with dozens of technical parameters per item), relying on wp_postmeta causes massive table bloat and slows down queries drastically. Meta Box Custom Tables solve the DB bloat issue, but the current lack of Query Loop & Filter integration forces us into writing custom SQL or WP_Query overrides.
PROPOSED SOLUTION:
- Add native support in the Bricks Query Loop control panel to filter, order by, and meta-query fields originating from Meta Box Custom Tables.
- Extend Bricks Filter/Dynamic Data query architecture so that filtering systems can natively query Meta Box Custom Tables without falling back to standard wp_postmeta.
This would be a massive performance game-changer for enterprise, B2B, and large WooCommerce stores built with Bricks!