Feedback: Components with Slots are not reliable in production

Feature Requests / Improvements
1

I’ve been using Bricks for about four years and have always recommended it to others. However, we are slowly reaching a point where I can no longer recommend Bricks with the same confidence as before.

Over the past months I’ve been working heavily with Components, especially with Slots, and I’ve also opened several support tickets related to this.

I really like Bricks and think it’s a very powerful tool. But in its current state, Components with Slots simply don’t work reliably. In practice there are significant issues, and when combined with Slots the system shows major limitations. This makes me wonder whether this functionality was thoroughly tested before being released.

What concerns me even more is that the tickets I opened regarding these issues haven’t received any response so far, while development seems to be focusing on other areas (for example AI features).

In several cases I even recorded detailed videos to help reproduce and understand the problems. I provided everything that might help resolve the issue — screenshots, code examples, and video recordings — yet the problems were still not identified or addressed.

I understand that development priorities have to be set, but core functionality like Components should be stable and reliable first.

I’m sharing this feedback because I genuinely want Bricks to succeed. But at the moment it’s becoming increasingly difficult to recommend it with full confidence.

For context, I also shared feedback about WooCommerce integration recently but didn’t receive a response there either:
https://forum.bricksbuilder.io/t/plans-for-extensive-woocommerce-integration/38362

I also want to mention that in the past I regularly defended Bricks Builder and the team in various Facebook groups when criticism came up. I always did this because I believed in the product and the quality behind it.

However, if the current quality issues are not addressed, I won’t be able to continue doing that.

In my opinion, it would be better for Bricks to grow a bit slower while maintaining a very high level of stability and quality, rather than introducing more and more features while core functionality still has serious issues.

3 Likes
2

What’s an example of where components slots aren’t working / unreliable?

Admittedly I’ve only started to use properly since they were officially released a few weeks back, but no issues so far. Everything added inside the slots seem to behave normally out of the box.

Is it specific elements not working inside them or?

3

I have lots of cases where slots are nested 2 or 3 levels deep, still, lots of styles in the deeper levels are not loaded in frontend.

Also it has problems query loop component, when it’s on a component that’s inside a slot of another component. The loop is all broken in frontend.

I already created threads for these bugs and would love to see some hotfixes to make slots production ready.

2 Likes
4

For example, slots are currently not working properly with AJAX, which basically renders all cards with pagination useless.

There are also problems with inheriting component properties to lower-level components.

And there are other things that are difficult to explain. During development, I don’t always have time to examine the problems in detail. Before I spend hours trying to understand the problem, I use a workaround. At the moment, I am doing without many components and have changed my workflow so that I no longer work with slots, as problems arise too often. Describing all the problems in detail would take too much time. If you work with it and test it properly, you should encounter the problems.

In addition, the points that @Hawei mentioned.

5

Hi Stabilo,

Unfortunately, I don’t know which “tickets” you are referring to, but as far as I can see, there are two component slot reports from you, one of which is still in progress, while Matej is waiting for a response from you on the other (since January 28).

So if we’ve overlooked anything here, please let us know.

We currently have +8 tasks related to nested components/slots, so I am confident that these issues will also be resolved as soon as possible. However, due to the complexity of these features, this is easier said than done.

2 Likes
6

Unfortunately, I don’t have the time to open a ticket for every problem. It can sometimes take several hours to thoroughly investigate a problem and then write it up clearly in a ticket with code, images, videos if necessary, and follow-up communication. I can’t afford to do that. Sorry.

I’m sure you test your products yourselves, but I don’t think you test them thoroughly enough.

And as I said, I’ve been very happy with Bricks for years, but in my opinion, the components (slots) issue has not been fully resolved.

7

That’s not the point. You opened two tickets, one of which could be confirmed immediately and is being worked on. The other cannot be reproduced. We asked you to test it with a component we provided, but we never received any feedback.

So what exactly do you expect from us? We expect you to help us track down the problem so that we can solve it for you (and other users). To do this, however, we must be able to reproduce it—unfortunately, the bug-fix :magic_wand: is broken.

We do. But it is simply impossible to test every conceivable scenario in advance and catch every potential problem out of thin air.

No one claimed that. As I said, there are quite a few tasks related to this in progress, which are being resolved gradually.

1 Like