Hi, coming from Nextcloud I found weird that Seafile doesn’t support file search among different libraries.
Please, correct me if I’m wrong, but I can search only when I’m inside a library.
I’d like to have a ‘global’ search.
The search bar in the upper right corner of the webinterface performs a global search for me.
Do you have elasticsearch enabled?
I have the search icon next to the bell icon on the right, but it doesn’t appear when I’m on My Libraries page. When I click the search button, this comes out
If I’m in Ebooks library, searching for a document existing in my Personal Documents library doesn’t return anything.
This is my seafevents.conf file (copied by the manual)
[INDEX FILES]
enabled = true
interval=10m
highlight = fvh
index_office_pdf=false
By the way, I’m on Seafile community 10.0.1, using latest docker image seafileltd/seafile-mc:latest
I’m using the pro edition, maybe this is not available in the CE.
What happens when you go to yourinstance.tld/search/ ?
@tschoesi I get Sorry, but the requested page could not be found.
@Cisco Well, actually, no. I’m not asking for full text file search. I’m asking to be able to make file search on all the libraries. Now, if I had a file but I didn’t know which library, I’d have to make a search inside each library
No search button in homepage
Very strange indeed. May that be because I’m using Seafile on Docker?
Is there anything I can do to troubleshoot the issue?
Should I open a issue on Github, maybe?
Hey Cisco, I really appreciate your help and effort!
By the way, I see that you don’t have the search bar on SF home page either, exactly like me.
But logging in here https://demo.seafile.com/, I have the search bar in the home page, so I suppose this is caused by the docker image (although I don’t know wethere the demo site uses docker or not).
Therefore, it looks like the next step would be to open a Github issue on the docker image repo.
Ok, I understand. So, the lack of search bar is because I’m using the Community Edition?
From my perspective, this is still a valid feature request.
But, if this is a commercial choice, I kind of understand, but from the technical point of view I find hard to explain the need of ElasticSearch when I’m already able to search inside the single library.
I’m not a developer, though, so I might miss some points.