Collection: Developer
Filter: bricks/users/query_vars
Bricks users query variables can be manipulated before the query runs like so: The filter callback receives three arguments: $query_varsFilter: bricks/terms/query_vars
Bricks terms query variables can be manipulated before the query runs like so: The filter callback receives three arguments: $query_varsFilter: bricks/query/loop_object
The Bricks Query Loop supports 3 types of queries by default (Posts, Terms, and Users). But it can be extendedFilter: bricks/query/run
The Bricks Query Loop supports 3 types of queries by default (Posts, Terms and Users). But it can be extendedFilter: bricks/setup/control_options
Bricks offers a WordPress filter to add or remove control options. The control options are used throughout Bricks and allowFilter: bricks/assets/load_webfonts
Bricks 1.4 introduces the possibility to disable the loading of Google Fonts in the frontend using the Google service. WithFilter: bricks/code/disallow_keywords
Bricks 1.3.7 introduces another level of security when using the Code element to run code, e.g. when the "execute code"Filter: bricks/posts/merge_query
Since Bricks 1.3.7 you'll be able to decide if a certain element query should be merged with the WordPress mainFilter: bricks/element/render_attributes
Starting at Bricks 1.3.7 you may manipulate the HTML attributes of a given element using the following filter: The filterFilter: bricks/dynamic_data/read_more
If you use the dynamic data tag Read more you'll get an anchor tag (link) to the post with the label