You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since I moved from NextCloud 28 onwards, I've noticed a change in the web interface behavior when moving files between folders. After moving a file from one folder to another using the "Move or Copy" option, the interface resets to the root directory (or the starting point) when I attempt to move another file. In previous versions, it would "remember" the last destination folder, allowing me to quickly move multiple files to the same location without navigating back each time. Now, I have to manually navigate to the destination folder again for every subsequent move, which significantly slows down the process.
Steps to reproduce
Log in to the Nextcloud web interface (version 28 or later).
Navigate to a folder containing a file (e.g., /FolderA/file1.txt).
Choose the file, select "Move or Copy," and move it to another folder (e.g., /FolderB).
Then choose another file and attempt to move another it using the same "Move or Copy" option.
Observe that the folder selection dialog resets to the current directory instead of defaulting to the previously used destination (/FolderB).
Expected behavior
After moving a file to a destination folder, the "Move or Copy" dialog should default to the last used destination folder when moving additional files, as it did in versions prior to 28. This would streamline the process of moving multiple files to the same location.
Actual Behavior
The "Move or Copy" dialog resets to the root directory (or initial view) after each move, requiring manual navigation to the destination folder every time.
This change disrupts workflows that involve moving multiple files to the same destination, making the process more time-consuming and less intuitive.
Would it be possible to restore the previous behavior or add an option to "remember" the last destination folder?
Thank you!
Nextcloud Server version
29
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.4
Web server
Apache (supported)
Database engine version
PostgreSQL
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
The text was updated successfully, but these errors were encountered:
Bug description
Since I moved from NextCloud 28 onwards, I've noticed a change in the web interface behavior when moving files between folders. After moving a file from one folder to another using the "Move or Copy" option, the interface resets to the root directory (or the starting point) when I attempt to move another file. In previous versions, it would "remember" the last destination folder, allowing me to quickly move multiple files to the same location without navigating back each time. Now, I have to manually navigate to the destination folder again for every subsequent move, which significantly slows down the process.
Steps to reproduce
/FolderA/file1.txt
)./FolderB
)./FolderB
).Expected behavior
After moving a file to a destination folder, the "Move or Copy" dialog should default to the last used destination folder when moving additional files, as it did in versions prior to 28. This would streamline the process of moving multiple files to the same location.
Actual Behavior
The "Move or Copy" dialog resets to the root directory (or initial view) after each move, requiring manual navigation to the destination folder every time.
This change disrupts workflows that involve moving multiple files to the same destination, making the process more time-consuming and less intuitive.
Would it be possible to restore the previous behavior or add an option to "remember" the last destination folder?
Thank you!
Nextcloud Server version
29
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.4
Web server
Apache (supported)
Database engine version
PostgreSQL
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?
The text was updated successfully, but these errors were encountered: