nextcloud / nextcloud/files_fulltextsearch
Restore from deleted files doesn't re-index document content
Open
Nobody has claimed this yet.
0. Needs triage
bug
- Dominant language
- PHP
- Stars
- 72
- Forks
- 41
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 9
Description
Steps to reproduce
- delete file
- restore file
- search for content
Expected behaviour
Content of the restored file should be searchable.
Actual behaviour
Content is not available in the full text search.
When a document is removed and later restored from the deleted files, it's text is not searchable.
It look like the restore process do not re-index the file/content.
Nextcloud 32.0.2
file_fulltextsearch 32.0.2
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 reproducing the delete, restore, and search steps described in the issue on Nextcloud 32.0.2, then trace the restore flow and its full-text indexing behavior. Done means content in a restored file is searchable again, matching the expected behavior.
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
- 48/100