It probably just got missed. Itâs a small team and while this issue may be huge to you, it is pretty minor in general. Iâm sure theyâll look at it when they get a chance. No need to threaten.
Edit: Sorry if I struck a nerve, but Iâm just being real. The developers will take a look when theyâre able to.
I donât know if I have the data to speculate on how huge or minor this bug is for the community in general but I have been waiting for two months. So I feel that when it comes to how I phrase this question, itâs justified and nowhere near âthreateningâ as you are trying to make it sound.
You didnât hit a nerve you just keep getting into things you have no idea about. So your little mansplaining show you started here is not something anyone is interested in and if that sounds harsh, itâs because it is. For some of us, time here is money.
Definition of threatening = âhaving a hostile or deliberately frightening quality or manner.â I have simply asked if I should seek an alternative solution to solve this from another source.
I get the feeling that you just sit in this forum and answer people to start disputes, cause you have not helped or made a single personâs life easier in this thread with your self-explaining comments. Perhaps you just enjoy trying to kick in doors that are already open.
Hi @frontend-dev, this one seems to have skipped our attention. Sorry about that. We are looking into it, and update this post as soon as we know more. But does it still occur for you when using the latest version of Bricks (1.5.3)?
Hi, sorry for getting back to you super late, but it did not solve the problem. It just removed the error messages for me but all MB group data disappeared and now I canât get any Metabox group data to show up in the builder, unfortunately. Maybe I have done something wrong but Iâve tried every possible setup with groups with no luck. I ended up leaving the MB group setup to get everything dynamic and just went with normal MB fields (static content) for now.
Hi Christoffer,
Would you be so kind as to send temporary login credentials and a link to this thread to help@bricksbuilder.io using the email address you used during the purchase?
Please create a demo for us and explain the issues in detail in the email.
Very interested in a solution. Nested groups are indispensable, especially if you have page elements such as content cards with several items. You want to create one group and make that cloneable for a good user experience.
What exactly are you using the inner group for in your example? The text and URL fields could just be children of the outer (clonable) group, couldnât they?
Also you are using two nested queries in Bricks although you have only one clonable group â the outer one.
It seems like Meta Box group fields are always presented as an option in the query type dropdown even when they are not clonable. This shouldnât be the case, should it?
Letâs say you have a clonable group (to store locations). In there you have a text field (location title) and a (non clonable) group (location address) â this inner group is just there for organization purposes. In this location address group there are two text fields (zip and city).
With this setup in place it works to query the clonable (locations) group. It also works to get the location title within the clonable group. But it seems like it is not possible to get the text values from the (inner) group within the clonable group (ZIP and city).