Hi, following the development of the last 1.5 years that went into Bricks 2.0 and the components feature, here is a list of the most limiting and annoying restrictions on components, loops and more.
Known issues are …
- Pagination or query results summary can break when the loop is wrapped in a container. (Anything can break when you have to refer to a loop item within a component, e.g. WP Grid Builder filters).
- Passing properties to child components is not supported. Component Property expansion
- Thus, components like a card with query loop are tightly coupled with a specific post type. Only in the component itself, you can hardcode the access to ACF fields.
- Hence, if you want to feed component instances with dynamic data and some with static data, you can only do that if it is not a looped one. Otherwise, maintain two equal components with different properties
- Hide/show a component instance conditionally does not work via well-known conditions. You need to add a special hide/show component property and more …
- The component edit button is a nightmare to reach. Going right on the instance, clicking settings icon left, select a component element on the right, edit on the left …
- A huge issue is the lack of a query loop element, which would automatically solve issue nr. 3, but there’s an unofficial one, so it seems doable solely by adding a new element SNN-BRX Child Theme, advanced features and gsap animations, acf, smtp, security, 301 logs, 404 logs, search logs - #91 by sinanisler
- And the restriction to one root elemfnt for loops, which prevents you from building listings with dynamically added headings, to group the looped entries. A calendar listing with dynamic month divider is not doable as is.
