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

[3.2.3] Tree sorting ignores resource id if called from icon above the tree #2126

Open
elcreator opened this issue Aug 10, 2023 · 5 comments
Milestone

Comments

@elcreator
Copy link

elcreator commented Aug 10, 2023

Tree sorting ignores selected (or highest parent resource id available for logged in manager) resource id if called from icon above the tree but works if called from the context menu.
I.e. it always calls backend with id=0 if called from the icon but calls with the resource id if called from the context menu on this resource.
It leads to inability to sort for everyone except admin who has rights for resource with id = 0

@elcreator elcreator changed the title Tree sorting ignores resource id if called from icon above tree Tree sorting ignores resource id if called from icon above the tree Aug 10, 2023
@Seiger
Copy link

Seiger commented Aug 29, 2023

@elcreator Can You share screen

@elcreator
Copy link
Author

Screenshot 2023-08-29 192610

@Seiger
Copy link

Seiger commented Aug 31, 2023

Please, check it with last updade core to version 3.2.3.

@elcreator
Copy link
Author

no, it was not helpful. Looks like it was only merged to 3.2.3 without additional fixes (I already performed updating this file from June 16 commit before).

@elcreator
Copy link
Author

just try to create non-admin manager user, assign to his group some resources, login with this profile and press on Sort button above the tree. Also here is my config regarding access to the root path:
image

@elcreator elcreator changed the title Tree sorting ignores resource id if called from icon above the tree [3.2.3] Tree sorting ignores resource id if called from icon above the tree Sep 27, 2023
@Seiger Seiger added this to the 3.2.x milestone Sep 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants