NO BUG: Filter doesn't work on component

Bugs
1

I’ve got a query inside a component that has a filter added to it from outside the component. It used to work (glitchy but still filtering) in 1.12.1 but when I upgraded to 1.12.4, the filter has no effect at all.

image
image3840×1760 584 KB

Browser: FF 139.0 (64-bit)
OS: Windows 10
URL: Nyhetsarkiv - SCÖ - Dev Site

System Information

Theme Information
Theme name: Bricks
Theme version: 1.12.4
Theme author: Bricks
Theme author URI: https://bricksbuilder.io/
Theme is child theme:

WordPress Environment
Home URL: https://dev.samordning.org
REST API Prefix: wp-json
WP version: 6.7.2
WP debug:
WP language: en_US
WP multisite:
WP memory limit: 2 GB

Server Environment
Server info: LiteSpeed
MySQL version: 10.6.21
Postmeta table meta_value type: longtext
PHP version: 8.3.21
PHP post max size: 512M
PHP execution time limit: 90 - Recommended max_execution_time: 180 (or more)
PHP max input vars: 4000
PHP safe mode:
PHP memory limit: 3G
PHP max upload file size: 512M
PHP wp_remote_post: Success

Active Plugins
Admin and Site Enhancements (ASE) Pro (7.8.13) by wpase.com
Advanced Custom Fields PRO (6.3.12) by WP Engine
Advanced Themer for Bricks (3.1.3) by Maxime Beguin
FileBird Document Library (Pro) (3.0.2) by Ninja Team
FileBird Pro (6.4.2) by Ninja Team
Matomo Analytics - Ethical Stats. Powerful Insights. (5.3.0) by Matomo
Ungapped Widgets (1) by Ungapped
wp-Typography (5.11.0) by Peter Putzer
wpDataTables (7.2) by TMS-Plugins

2

Hi @FilWi,

as for now, I’ll mark this topic as no-bug, because in current implementations, connecting filters to the query loop, that is inside the component, is not supported. You can connect to the query loop that is on the main component element, but not if it’s inside a component.

Thanks for understadning,
Matej

3

Will all the these loop and component restrictions be fixed with an overhauled implementation of Bricks? Or is the focus of Bricks on previous Elementor users for the future and not Pro users?

4

With every new update, we are resolving many issues and implementing many new features and ideas.
Considering that components are still in “experimetnal” phase (as of Bricks 1.12.4 - if we only take stable releases), I think they are already powerful.
Sure, we will continue to improve components, but I can’t say what will be next to improve. Regarding this use case, it’s a little more technical and not a simple fix, but we are aware of it.

Best regards,
Matej

1 Like