WIP: Query loop terms choice - verify request: user can not user builder (7)

Browser: Chrome 138
OS: Windows
Plugins: ACF Pro
Additional information: Installation is using WP Bedrock
Bricks version: 2.0

Hello,

In my company’s project we have encountered an issue when trying to set displayed terms in component’s query loop. Screenshot was taken when editing component instance as an Editor user role. I have tried modyfying permissions in bricks as well as using “user role manager” plugin and was unable to prevent this error from displaying while keeping the role as “Editor”.

While writing this post something weird happened though. I changed the role of the account I’m writing about to Administrator. But it seems that capabilities set in builder settings were kept as for Editor. There’s “Redaction” capability group in my WP installation that’s assigned to Editor and it hides all default bricks elements, the goal is for the client - redaction of the site, to be able to use provided by us components and hand selected (or self-made with php) bricks elements. But whenever I changed role to Administrator i keep not seeing default elements (Which in this case is desired but that does not seem like default behavior?).

Also, Can I check anywhere what this error that displays as options in select field ( :sob: ) actually means? Is it solvable locally?

image


image
image

Hi @JMonka,

thank you for your report. I was able to replicate the issue and I’ve added it to our bug tracker. It looks like that for this specific action, it still seems like “Editor” does not have access to, even if you enable all capabilities.

Once we implement the fix, we will update this topic.

Best regards.
Matej

1 Like

Hello! Sorry to butt in. I’m having the same issue after updating to Bricks on a setup with Bricks 2.0 + JetEngine + User Role Editor. With a custom role, even though it has all capabilities enabled and full access to the builder, I get that same error. Thanks!

Hi @DavidFG and welcome to the forum.

This sounds like the same issue, and once it’s fixed, we will update this topic. Then you can test it and let us know.

Thank you,
Matej

1 Like

Hi @Matej ,

is there a roadmap when we can expect a fix for this bug?

We encounter the same bug and i dont want to give a lot of Editors the full Administrator role as a workaround. Is this bug only connected to the editor role? Or anything which is not Admin?

Thank you for our efforts!
Best regards

Hi @bene.vo and welcome to the forum :partying_face:

As for your question, no, I can’t give you any dates yet. I’ve checked our internal bug tracker and the task is still in progress.

While we tested it out (to replicate the issue) only with Editor role, I would think this will apply to all other roles.

Best regards,
Matej