nextcloud / nextcloud/server

[Bug]: Wrong message shown when an empty folder is accessed via Favourites

Open
#53,716 0 comments 0 reactions 1 assignee View on GitHub

@susnux is already working on this.

Since Jul 14, 2025.

0. Needs triage 30-feedback bug feature: files low
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

When a folder is added as a favourite, any empty subfolders accessed via the favourite menu will show a message which suggests only files which are also marked as favourtes would be displayed - but this is not the case. All files and folders under the favourite folder will be shown.

The message I see when accessing the folder from favourites:
Image
The message when accessing it directly:
Image

and when using favourites to access a subfolder which is not empty I still see non favourited files (as expected):
Image

Steps to reproduce
  1. Create a folder with a subfolder
  2. Add the parent folder as a favourite
  3. Access the subfolder via the favourites menu
Expected behavior

The empty folder should show the same message when accessed via favourites as it does when accessed directly from all files.

Nextcloud Server version

30

Operating system

Other

PHP engine version

PHP 8.1

Web server

Apache (supported)

Database engine version

MariaDB

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

None

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

List of activated Apps

Nextcloud Signing status

Nextcloud Logs

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.