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
Install Nextcloud with an LDAP backend containing 10 thousands of users
Fill the user search textbox
Wait
Expected behaviour
To see some indication of search processing
Actual behaviour
Only at end of search, when results are listed, user know that is working.
Server configuration
Operating system: Debian 8
Web server: Apache 2.4.10
Database: PostgreSQL 9.4.1
PHP version: 5.6.30
Nextcloud version: 13
Updated from an older Nextcloud/ownCloud or fresh install: Updated from previous release
Where did you install Nextcloud from: Community
Details:
During the processing of the research, there is no indication that the research is being processed. For a backend with thousands of users, this can generate doubts to user about the processing.
The text was updated successfully, but these errors were encountered:
GitMate.io thinks possibly related issues are #6951 (Collaboration search brings up the same user multiple times), #7180 (Search field), #116 (Show login-history to user), #2086 (Show progress/spinner when create/delete user in web UI), and #9698 (Search is not working in Shared Folders by Other users).
- During the processing of the research, there is no indication that
the research is being processed.
- For a backend with thousands of users, this can generate doubts to
user about the processing.
Steps to reproduce
Expected behaviour
To see some indication of search processing
Actual behaviour
Only at end of search, when results are listed, user know that is working.
Server configuration
Operating system: Debian 8
Web server: Apache 2.4.10
Database: PostgreSQL 9.4.1
PHP version: 5.6.30
Nextcloud version: 13
Updated from an older Nextcloud/ownCloud or fresh install: Updated from previous release
Where did you install Nextcloud from: Community
Details:
During the processing of the research, there is no indication that the research is being processed. For a backend with thousands of users, this can generate doubts to user about the processing.
The text was updated successfully, but these errors were encountered: