[Bug]: Directory Name Not Automatically Updated After Renaming Without Browser Refresh

[fhongtao]

⚠️ This issue respects the following points: ⚠️

• This is a bug, not a question or a configuration/webserver/proxy issue.
• This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• I agree to follow Nextcloud's Code of Conduct.

Bug description

Description:

Hello Nextcloud Team,

I've encountered an issue where renaming a directory does not automatically update the name in the file view. The new name only appears after manually refreshing the browser.

Steps to reproduce

Steps to Reproduce:

Log in to Nextcloud as a regular user or admin.
Create a new directory in your file space.
Rename the directory to a different name.
Observe that the old name remains displayed.
Refresh the browser manually to see the updated directory name.

Expected behavior

Expected Behavior: The directory name should update immediately after renaming without needing to refresh the browser.

Actual Behavior: The old directory name remains visible until the browser is refreshed.

Environment:

Nextcloud version: 29.0.4
PHP version: (please fill in)
Database version: (please fill in)
Web server: (please fill in)
Thank you for your assistance!

Nextcloud Server version

29

Operating system

RHEL/CentOS

PHP engine version

PHP 8.1

Web server

Nginx

Database engine version

MySQL

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

Updated from a MINOR version (ex. 28.0.1 to 28.0.2)

Are you using the Nextcloud Server Encryption module?

None

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

[solracsf]

Upgrade to 29.0.5 and try again.

[fhongtao]

thanks

[joshtrichards]

Duplicate of #46604

Already fixed #46690 in 29.0.5