-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Backends provided no user object for ... after upgrade 9.2.5 -> 10.0.2 - Sharing and user search FAILE #28510
Comments
Or may be it is some sort of something different is broken. I did some googling and found a topic, that with V10.x LDAP things are under development and may be change. https://central.owncloud.org/t/user-ldap-more-than-1000-users/7449 I did a "./occ -vv user:sync "OCA\User_LDAP\User_Proxy"" and now all users show up and can be searched ... Any feedback on this ? Thanks and regards |
@greinick So does this problem still persist, or was it fixed after you ran the scan? If it is fixed, can you please close your issue? Thanks |
@patrickjahns just for curiosity, did i miss that in the update/installation guide? I'll close the ticket, but a feedback on the question would be nice. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Steps to reproduce
or try to search an user globally or for scaring a file/folder.
and searching dose not display the user at all....
or if you search e.g. for "p" you get Götz Reinicke in the result ...
Expected behaviour
The file shared by that link should be downloadable.
Find the users as in the past from LDAP.
Actual behaviour
Internal Server Error.
Server configuration
Operating system: centos 6.7
Web server: apache https 2.2.15
Database: mysql 5.6.37
PHP version: 7.1.7
ownCloud version: 10.0.2
Updated from an older ownCloud or fresh install: yes from 9.2.5
Where did you install ownCloud from: owncloud repository
Signing status (ownCloud 9.0 and above):
The text was updated successfully, but these errors were encountered: