Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VAA group added a wrong level in URE's "Custom Capabilities" UI #134

Open
pbiron opened this issue Jul 29, 2024 · 0 comments · Fixed by #135
Open

VAA group added a wrong level in URE's "Custom Capabilities" UI #134

pbiron opened this issue Jul 29, 2024 · 0 comments · Fixed by #135
Assignees
Milestone

Comments

@pbiron
Copy link

pbiron commented Jul 29, 2024

Describe the bug

Since VAA 1.6.4 when the URE integration was added, the VAA node in URE's "Custom capabilities" UI is added at the wrong "level". It is added at level 3 and should be added at level 2.

Steps to reproduce the behavior:

  1. Install Activate at least 1 plugin (in addition to VAA) that also hooks into URE's ure_capabilities_groups_tree filter. One such plugin is Query Monitor.
  2. Go to Users
  3. Click on the Capabilities row action for some user
  4. See that VAA's "URE group" is displayed as a grandchild of URE's "Custom capabilities" node in the UI (see screenshot below). This makes it look like the VAA custom capabilities are somehow related to some other plugin.

Expected behavior

VAA's group should display as a direct child of URE's "Custom capabilities".

Screenshots

vaa-ure-custom-caps

Specifications

  • Plugin Version: 1.8.9
  • WordPress Version: 6.6.1
  • Other plugins installed: many, including Query Monitor 3.16.4
  • Theme: any
  • Browser: Chrome 127.0.6533.72 (Official Build) (64-bit)

Additional context

PR coming shortly (with a screenshot after the PR applied)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants