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
When updating locations, the information cannot be saved as the “LDAP OU Search” field has become a mandatory field since one of the last updates. Even if you do not use LDAP synchronization for locations or have used it before.
Reproduction steps
Open a location to edit.
Change something and leave "LDAP OU Search" empty, as it was before.
Click Save.
Cannot be saved because field is mandatory.
Expected behavior
Open a location to edit.
Change something and leave "LDAP OU Search" empty, as it was before.
Click Save.
Changes will be saved.
Screenshots
Snipe-IT Version
v7.0.13 - build 15514 (master)
Operating System
Ubuntu
Web Server
Apache
PHP Version
8.1.2-1ubuntu2.19
Operating System
No response
Browser
No response
Version
No response
Device
No response
Operating System
No response
Browser
No response
Version
No response
Error messages
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.
Debug mode
Describe the bug
When updating locations, the information cannot be saved as the “LDAP OU Search” field has become a mandatory field since one of the last updates. Even if you do not use LDAP synchronization for locations or have used it before.
Reproduction steps
Expected behavior
Screenshots
Snipe-IT Version
v7.0.13 - build 15514 (master)
Operating System
Ubuntu
Web Server
Apache
PHP Version
8.1.2-1ubuntu2.19
Operating System
No response
Browser
No response
Version
No response
Device
No response
Operating System
No response
Browser
No response
Version
No response
Error messages
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: