nextcloud / nextcloud/fulltextsearch
Unified search has different behavior for file results vs fulltextsearch results
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 234
- Forks
- 64
- Avg merge
- 6h 18m
- Merged PRs (30d)
- 10
Description
When using the unified search function, file results use the openfile function, as in:
https://nextcloud.server/index.php/apps/files/files/######?dir=/pathtofile&openfile=true
This opens the selected file directly.
However, fulltextsearch results use the scrollto function, as in:
https://nextcloud.server/index.php/apps/files/files?dir=/pathtofile/&scrollto=filename
The scrollto function doesn't seem to work in v28 or v29, so it just shows the containing directory.
Would it be possible to use the openfile function for fulltextsearch results instead of the scrollto function?
Thanks!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing unified search handling for file results and fulltextsearch results, comparing the openfile and scrollto entry points described in the issue. Verify the behavior on Nextcloud v28 or v29, then confirm that fulltextsearch results open the selected file directly rather than only showing its containing directory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- search
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100