nextcloud / nextcloud/server

[Bug]: Comment search works but target file list is empty

Open
#48,316 4 comments 1 reaction 1 assignee View on GitHub

@kesselb is already working on this.

Since Aug 12, 2025.

1. to develop 30-feedback bug feature: comments feature: search
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

⚠️ This issue respects the following points: ⚠️
Bug description

Unified search finds strings in the comments on files correctly, but - when clicking the result - not only is the the matching file not scrolled to, the entire file list of the target folder is empty.

Search result sends you to a URL like https://domain.tld/apps/files/files?dir=folder1/subfolder1&scrollto=file2.md. The scrollto doesn't seem to work and the contents of folder1/subfolder1 is shown as empty ("No files in here") even though not only are their really files there, but the matching one.

Steps to reproduce
  1. Add a comment on a file somewhere
  2. Search for a string in the comment
  3. Click the relevant search result
  4. You should find yourself in the correct folder, but without of the files located in said folder listed (including the target file)
Expected behavior

I'd expect to end up in the correct folder, with all files listed or at least the matching one.

Nextcloud Server version

30

Operating system

Debian/Ubuntu

PHP engine version

None

Web server

None

Database engine version

None

Is this bug present after an update or on a fresh install?

Fresh Nextcloud Server install

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

What user-backends are you using?
  • Default user-backend (database)
  • LDAP/ Active Directory
  • SSO - SAML
  • Other
Configuration report

No response

List of activated Apps

No response

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.