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

LDAP Select, LDAP Directory error when creating Form in a subentity #2645

Open
jcervantes-sipecom opened this issue Mar 18, 2022 · 1 comment

Comments

@jcervantes-sipecom
Copy link

Describe the bug
It's not possible to select LDAP Directory with Type LDAP Select, when the Form is created in a Subentity, or when the form is editing in a Subentity, not in the Root entity.

To Reproduce
Steps to reproduce the behavior:

  1. Create at least one LDAP Authentication
  2. Create a Subentity and go to it, not to the Root entity
  3. Create a new Form in this Subentity
  4. Create a section and a question LDAP Select type, clic en the select list LDAP Directory.
  5. See empty, close the Form not save the question
  6. In the same Form, go to Root Entity.
  7. In the same section create a question LDAP Select type, and select list LDAP Directory.
  8. As you can see the LDAP Directory list is diplayed, just in Root Entity.

Expected behavior
The ability of selecting LDAP Directory, in an entity and subentity, not just in the Root

Screenshots

image

image

GLPI / Plugins (please complete the following information):

  • GLPI version: 9.5.7
  • Plugin version: 2.12.5
  • I have a problem with Setup > General, I'm getting Item Not Found, I don't know why, so this is my print screen from my plugins:

image

Desktop (please complete the following information):

  • OS: Windows 10
  • Browser Edge
  • Version 99.0.1150.39 (Official build) (64-bit)

Additional context
The tests and screenshots are from my test environment, but this bug is also in my production environment.

@btry
Copy link
Collaborator

btry commented Mar 21, 2022

Hi

Read carefully the comments in the following patch, then decide if you should apply it or not. It should solve your problem, but will introduce some other concerns.

#2482

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

No branches or pull requests

2 participants