Improve Implementation of Query for Metabox Nested Groups

Feature Requests / Improvements
1

Bricks supports Metabox nested groups which is Great! :grinning:

Unfortunately it is not the easiest to work with when you have nested groups within nested groups.

With the current implementation you must manually nest the Bricks queries as well to get the data from groups which they themselves are nested.

This means putting queries on parent elements that query the parent nested group and in some cases actually requires an extra element to be added just so you can put a query on it to retrieve the data of the parent.

Instead could Bricks just detect that the MB Group is nested in one query and automatically figure out the parent groups and just return the data requested? (not sure if that is possible)

OR

at least have the ability to nest the MB Groups themselves in a single Bricks Query interface. For example if the type selected is a MB Group I can then add additional Types for the MB Group below to show the nesting.

image

This would make things more obvious to users how things work and give us cleaner page layouts since I wouldn’t have to add extra containers just for the purposes of querying for a nested group.

Note: This Feature Request resulted from the discussion in this post

5 Likes
2

Yes please, I’d really like to see this too! I just went through creating a ton of fields which contain nested groups within groups, to find out that Bricks cannot display these fields within the sub-groups. It’s a very unfortunate limitation. :disappointed: I’m very surprised by this issue.

3

I also think its really hard to work with nested metabox group. But sometimes I cant avoid that (e.g. having a cloneable group in a conditional group). So I also would love if this gets adressed and reworked <3

1 Like