You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
Go to Users
Click on the Capabilities row action for some user
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
Specifications
Plugin Version: 1.8.9
WordPress Version: 6.6.1
Other plugins installed: many, including Query Monitor 3.16.4
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:
ure_capabilities_groups_tree
filter. One such plugin is Query Monitor.Users
Capabilities
row action for some userExpected behavior
VAA's group should display as a direct child of URE's "Custom capabilities".
Screenshots
Specifications
Additional context
PR coming shortly (with a screenshot after the PR applied)
The text was updated successfully, but these errors were encountered: