Bug description
After creating a new folder in Files, using the current/parent folder share action can open the newly created child folder in the sharing/details sidebar instead of the parent folder.
This was reported by an enterprise customer after upgrading to Nextcloud 33.0.2.3. They mentioned a short screen recording, but the support export available during triage did not include the video, so this issue is based on the written reproduction sequence.
Steps to reproduce
- Open the Files app on Nextcloud 33.
- Create a new folder inside the current folder.
- Without selecting another item, use the current/parent folder share action from the breadcrumb/header menu.
- Observe the details/sharing sidebar.
Expected behavior
The sharing sidebar opens for the current/parent folder.
Actual behavior
The sidebar opens for the newly created child folder instead.
This can make it easy to add share recipients to the wrong folder if the sidebar title is not checked carefully.
Nextcloud Server version
33
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.4
Web server
Apache
Database engine version
MySQL/MariaDB
Is this bug present after an update or on a fresh install?
Upgraded to a major version
Are you using the Nextcloud Server Encryption module?
Encryption is disabled
What user-backends are you using?
- Default user-backend
- LDAP / Active Directory
- SSO - SAML
Configuration report
From the customer support report:
- Nextcloud 33.0.2.3 Enterprise
- Browser: Edge/Chrome 146 on Windows 10
files_sharing 1.25.2 enabled
groupfolders 21.0.7 enabled
- External storage disabled
Nextcloud Logs
No server log entries expected. This appears to be frontend state handling.
Additional info
Possible route/sidebar-state path:
- New folder creation navigates with the new child folder
fileid in route params while staying in the parent directory.
- Opening the sharing sidebar for the current folder passes the parent/current folder node.
- The active-node route watcher skips updating the route
fileid when the active node equals the active folder.
- The sidebar open state adds
opendetails=true while the previous child fileid can remain in the route.
- The file list can then re-apply that stale
fileid and open the child in the sidebar.
Bug description
After creating a new folder in Files, using the current/parent folder share action can open the newly created child folder in the sharing/details sidebar instead of the parent folder.
This was reported by an enterprise customer after upgrading to Nextcloud 33.0.2.3. They mentioned a short screen recording, but the support export available during triage did not include the video, so this issue is based on the written reproduction sequence.
Steps to reproduce
Expected behavior
The sharing sidebar opens for the current/parent folder.
Actual behavior
The sidebar opens for the newly created child folder instead.
This can make it easy to add share recipients to the wrong folder if the sidebar title is not checked carefully.
Nextcloud Server version
33
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.4
Web server
Apache
Database engine version
MySQL/MariaDB
Is this bug present after an update or on a fresh install?
Upgraded to a major version
Are you using the Nextcloud Server Encryption module?
Encryption is disabled
What user-backends are you using?
Configuration report
From the customer support report:
files_sharing1.25.2 enabledgroupfolders21.0.7 enabledNextcloud Logs
No server log entries expected. This appears to be frontend state handling.
Additional info
Possible route/sidebar-state path:
fileidin route params while staying in the parent directory.fileidwhen the active node equals the active folder.opendetails=truewhile the previous childfileidcan remain in the route.fileidand open the child in the sidebar.