-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Unable to edit root entity #18676
Comments
Please post in English |
Sorry, I adjusted the text. |
Please use english for title as well. |
I can confirm this bug, and it has been introduced on version 10.0.17 I have 2 installations of GLPI, one of them installed with version 10.0.16, on which I could rename the root entity, and later I upgraded it to 10.0.17. The second installation, was directlly on 10.0.17 and I couldn't rename the root entity. |
Just tested on a fresh (nightly) install, I cannot reproduce. |
I guess thi issue is fixed; please try with nightly build |
@trasher, you're right, the change solving this bug is https://github.com/glpi-project/glpi/pull/18286/files |
Code of Conduct
Is there an existing issue for this?
Version
10.0.17
Bug description
In a new GLPI installation, when logging in for the first time and using the super-admin "glpi" password "glpi", I noticed that when trying to rename the root entity, a warning is returned saying "You do not have permission to perform this action. [Return to previous page]", considering that the user in question has full permissions for any type of change, I tested creating a new user and setting super-admin permissions for it, but I got the same problem.
Relevant log output
Page URL
No response
Steps To reproduce
1 - Log in using the credentials: user: "glpi" key: "glpi";
2 - Access the "Administration" >> "Entities" menu >> click on the root entity;
3 - Change the root entity name to any other name and click on add;
4 - a warning message will appear on the screen.
Your GLPI setup information
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: